{"action":"created","issue":{"url":"https://api.github.com/repos/Parallels/vagrant-parallels/issues/217","labels_url":"https://api.github.com/repos/Parallels/vagrant-parallels/issues/217/labels{/name}","comments_url":"https://api.github.com/repos/Parallels/vagrant-parallels/issues/217/comments","events_url":"https://api.github.com/repos/Parallels/vagrant-parallels/issues/217/events","html_url":"https://github.com/Parallels/vagrant-parallels/issues/217","id":110146076,"number":217,"title":"Issue connecting to windows 10 box with vagrant up","user":{"login":"apasquale","id":444754,"avatar_url":"https://avatars.githubusercontent.com/u/444754?v=3","gravatar_id":"","url":"https://api.github.com/users/apasquale","html_url":"https://github.com/apasquale","followers_url":"https://api.github.com/users/apasquale/followers","following_url":"https://api.github.com/users/apasquale/following{/other_user}","gists_url":"https://api.github.com/users/apasquale/gists{/gist_id}","starred_url":"https://api.github.com/users/apasquale/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/apasquale/subscriptions","organizations_url":"https://api.github.com/users/apasquale/orgs","repos_url":"https://api.github.com/users/apasquale/repos","events_url":"https://api.github.com/users/apasquale/events{/privacy}","received_events_url":"https://api.github.com/users/apasquale/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-10-07T03:29:44Z","updated_at":"2015-10-08T06:03:28Z","closed_at":"2015-10-08T06:03:28Z","body":"Hi,\r\n\r\nI have a Windows 10 box which I created using packer. I was able to successfully vagrant up initially, but after a month I wanted to add a new sync folder, so did a vagrant halt followed by a vagrant up.\r\n\r\nNow it hangs at:\r\n```\r\n==> vagrant-windows-10: Waiting for machine to boot. This may take a few minutes...\r\n    vagrant-windows-10: WinRM address: 10.211.58.3:5985\r\n    vagrant-windows-10: WinRM username: vagrant\r\n    vagrant-windows-10: WinRM transport: plaintext\r\n```\r\nUntil it finally errors with:\r\n```\r\nINFO interface: error: Timed out while waiting for the machine to boot. This means that\r\nVagrant was unable to communicate with the guest machine within\r\nthe configured (\"config.vm.boot_timeout\" value) time period.\r\n```\r\n\r\nNone of my sync folders are available after this.\r\n\r\nThe strange thing is, while its hung (or after it crashed) I am able to not only see the vm up and running, I can `vagrant ssh` and even `vagrant winrm -c \"echo hello\"` without an issue.\r\n\r\nThings I have tried:\r\n- Reconfiguring winrm (though that works fine with `vagrant winrm`)\r\n- Ensuring networks are set to private\r\n- Turning off the firewall\r\n- Disabling Windows Defender\r\n\r\nWhat I am running on:\r\n- MacBookPro11,3\r\n- OSX Yosemite (though upgraded to ElCapitan yesterday and made no difference to the result)\r\n- Vagrant v1.7.4\r\n- vagrant-parallels v1.5.0\r\n- Parallels v10.3.0\r\n\r\nGist for VagrantFile and logs: https://gist.github.com/apasquale/3b61d1df2dad45024df5\r\n\r\nIs there anything else I can try?\r\n"},"comment":{"url":"https://api.github.com/repos/Parallels/vagrant-parallels/issues/comments/146429108","html_url":"https://github.com/Parallels/vagrant-parallels/issues/217#issuecomment-146429108","issue_url":"https://api.github.com/repos/Parallels/vagrant-parallels/issues/217","id":146429108,"user":{"login":"apasquale","id":444754,"avatar_url":"https://avatars.githubusercontent.com/u/444754?v=3","gravatar_id":"","url":"https://api.github.com/users/apasquale","html_url":"https://github.com/apasquale","followers_url":"https://api.github.com/users/apasquale/followers","following_url":"https://api.github.com/users/apasquale/following{/other_user}","gists_url":"https://api.github.com/users/apasquale/gists{/gist_id}","starred_url":"https://api.github.com/users/apasquale/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/apasquale/subscriptions","organizations_url":"https://api.github.com/users/apasquale/orgs","repos_url":"https://api.github.com/users/apasquale/repos","events_url":"https://api.github.com/users/apasquale/events{/privacy}","received_events_url":"https://api.github.com/users/apasquale/received_events","type":"User","site_admin":false},"created_at":"2015-10-08T06:03:28Z","updated_at":"2015-10-08T06:03:28Z","body":"I think I have figured out what's going on here and I have a very hacky workaround...\r\n\r\nI started by `vagrant up` a fresh vm from scratch and ran `vagrant winrm -c \"hostname\"`\r\nI got the following result:\r\n```\r\nmbp-pas-sms:win10 $ vagrant winrm -c \"hostname\" dev\r\nvagrant-10\r\nmbp-pas-sms:win10 $\r\n```\r\n\r\nWhich looks much cleaner than the result I was getting earlier (a whole bunch of XML along with the response)\r\n\r\nAfter slowly bringing that VM back up to the same level as my existing vm (running puppet scripts module by module) I found that certain chocolatey packages such as Jump-Location, posh-git and psget were causing my call to `vagrant winrm` to start showing the XML and in some cases the hanging as well.\r\n\r\nSwitching back to my original VM, I commented out the entire contents of my powershell profile (C:\\Users\\vagrant\\Documents\\WindowsPowerShell\\Microsoft.PowerShell_profile.ps1) and this made my call to `vagrant winrm` clean again. This also allowed a clean `vagrant up` to happen.\r\n\r\nSo while I haven't figured out exactly what's causing the workaround, at least I know how to vagrant up again. It's not an issue with vagrant or any plugins so this issue can be closed.\r\n"}}