Skip to content

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

Open

Description

@shyampvagadiya
  • 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

Activity

  1. tridentholder commented on Jul 22, 2023

    @tridentholder

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

  2. jo3rg commented on Aug 1, 2023

    @jo3rg

    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
    
  3. r22tt commented on Aug 16, 2023

    @r22tt

    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.

  4. jo3rg commented on Sep 3, 2023

    @jo3rg

    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.

  5. tridentholder commented on Sep 3, 2023

    @tridentholder

    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

  6. r22tt commented on Sep 3, 2023

    @r22tt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions