Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error in wef and win10 provision: much needed help #901

Open
shyampvagadiya opened this issue Jul 22, 2023 · 6 comments
Open

error in wef and win10 provision: much needed help #901

shyampvagadiya opened this issue Jul 22, 2023 · 6 comments

Comments

@shyampvagadiya
Copy link

  • Operating System Version: Host Machine Win 11
  • Deploying via: VMWare
  • Vagrant Version (if applicable): 2.3.7

Description of the issue:

For example:

I have tried installing wef and win10 machines many times and I run into the same issue everytime which is from WinRM as shown below. @clong please help with this issue. I would really appreciate your help with this issue. I have been stuck here for many weeks and I tried to find the answer to this error but no luck!

I get the following error message upon issuing reload --provision command.

Error message: wef


==> wef: Attempting graceful shutdown of VM...
An error occurred executing a remote WinRM command.

Shell: Cmd
Command: hostname
Message: Digest initialization failed: initialization error

Error message: win10


==> win10: Attempting graceful shutdown of VM...
An error occurred executing a remote WinRM command.

Shell: Cmd
Command: hostname
Message: Digest initialization failed: initialization error
@tridentholder
Copy link

Hi, I encountered the same error. Did you solve this

@jo3rg
Copy link

jo3rg commented Aug 1, 2023

This issue may be related to a vagrant bug, I've reported it over there:

https://github.com/hashicorp/vagrant/issues/13242
https://discuss.hashicorp.com/t/winrm-port-does-not-work-in-vagrantfile/54601

@r22tt
Copy link

r22tt commented Aug 16, 2023

I was able to resolve this by updating to dev build 2.3.8.dev. It would also work if you downgrade to 2.3.6.

@jo3rg
Copy link

jo3rg commented Sep 3, 2023

I was able to resolve this by updating to dev build 2.3.8.dev. It would also work if you downgrade to 2.3.6.

Same, the new dev branch fixed it for me too, Issue can be closed here too.

@tridentholder
Copy link

I was able to resolve this by updating to dev build 2.3.8.dev. It would also work if you downgrade to 2.3.6.

Same, the new dev branch fixed it for me too, Issue can be closed here too.

I don't get the fix, can you explain

@r22tt
Copy link

r22tt commented Sep 3, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants