Closed jo3rg closed 6 months ago
I have the same issue with Windows 11 - is there a work around like using an older version of Vagrant? I suppose there is no installation package for Windows yet here: https://github.com/hashicorp/vagrant/releases/tag/2.3.8.dev%2B000032-f72cda8b
Vagrant version
Installed Version: 2.3.7
Host operating system
Windows 11 x64
Guest operating system
Windows Server 2019
Vagrant box
gusztavvargadr/windows-server-2019-standard
Thank you for your support Marketta
I have the same issue with Windows 11 - is there a work around like using an older version of Vagrant? I suppose there is no installation package for Windows yet here: https://github.com/hashicorp/vagrant/releases/tag/2.3.8.dev%2B000032-f72cda8b
Vagrant version
Installed Version: 2.3.7
Host operating system
Windows 11 x64
Guest operating system
Windows Server 2019
Vagrant box
gusztavvargadr/windows-server-2019-standard
Thank you for your support Marketta
Issue was fixed at least for me in https://github.com/hashicorp/vagrant/releases/download/2.3.8.dev%2B000086-5fc64cde/vagrant_2.3.8.dev_windows_i686.msi
I have the same issue with Windows 11 - is there a work around like using an older version of Vagrant? I suppose there is no installation package for Windows yet here: https://github.com/hashicorp/vagrant/releases/tag/2.3.8.dev%2B000032-f72cda8b
Vagrant version
Installed Version: 2.3.7
Host operating system
Windows 11 x64
Guest operating system
Windows Server 2019
Vagrant box
gusztavvargadr/windows-server-2019-standard
Thank you for your support Marketta
Issue was fixed at least for me in https://github.com/hashicorp/vagrant/releases/download/2.3.8.dev%2B000086-5fc64cde/vagrant_2.3.8.dev_windows_i686.msi
Seems to also have fixed the issue for me, thanks and issue can be closed from my pov.
I still have same issue with 2.4.0 on Mac.
Same here - also on Mac. I've had to roll back to version 2.3.6 to get Windows guests to work.
Had the same issue, roll back to 2.3.6 fixed it for me as well. Thanks for the suggestion @dstoliker 🙏🏻.
I have the same issue on arch linux, vagrant 2.4.0
Issue still persists on Arch Linux, Vagrant 2.4.0. Reproducible for example with Orange-Cyberdefense/GOAD. Downgrade to 2.3.6 and enabling OpenSSL legacy provider did not fix the issue.
UPDATE: Seems to be fixed with current git version, at least on Arch Linux, see https://github.com/Orange-Cyberdefense/GOAD/issues/141#issuecomment-1814321465
I have the same issue on manjaro (Linux5.15), vagrant 2.4.0
I have upgraded to version 2.4.1 on Mac. This issue appears to have been resolved in that version. 🎉
This has been resolved in the latest release, so closing this up.
Cheers!
I still have the same issue with Arch 20240101 amd64/ vagrant 2.4.1
Looks like the following is needed to get this to work: config.winrm.transport = :plaintext config.winrm.basic_auth_only = true
Debug output
Expected behavior
Vagrant should communicate with the guest through winrm. Or should show more detail info to recover.
Actual behavior
Fails to Initialize and Information is useless. May be related to winrm port forwarding as the first Windows 2016 Server instance was deployed without any problems (dc).
Reproduction information
vagrant up --debug
Vagrant version
Installed Version: 2.3.7
Host operating system
Windows 10 x64
Guest operating system
Windows Server 2016
Steps to reproduce
Vagrantfile
Full: https://github.com/clong/DetectionLab/blob/master/Vagrant/Vagrantfile WEF Part:
EDIT1: I think the bug may be related to this bug: https://discuss.hashicorp.com/t/winrm-port-does-not-work-in-vagrantfile/54601
EDIT2: Further analyses has shown that the right port & interface has been choosen but seems to have issues to authenticate:![image](https://github.com/hashicorp/vagrant/assets/12583919/5a551b2b-d688-4007-90df-8cd50e30b6ef)