Hyper-V Virtual Machine Error 0x80070569

If you find you are getting a similar error 0x80070569 on Hyper-V 2012, you might be experiencing something similar to this.

So I jumped on to one of my Hyper-V hosts the other day to bang out a fresh Virtual Machine. I clicked on Create New Virtual Machine and BAM!, I get this error.

 

 

Try restarting the Hyper-V Virtual Machine Management Service.

I wasn't sure if I could restart this service while I had Virtual Machines running, but since it was on my home lab environment, I thought I'd give it a shot. The service restarted with no issues on any of my virtual machines. What's more, when I tried to create a virtual machine, it worked, no error. I'm not sure why this happens or why restarting the service fixes it as it seems by the error to be a permissions issue but as a work around it seems to do the trick.

 

Tagged . Bookmark the permalink.

26 Responses to Hyper-V Virtual Machine Error 0x80070569

  1. Erik says:

    Thanks! Worked for me. Maybe it was a stability issue with the service… who knows???

  2. Erik says:

    Thanks! Worked for me. Maybe it was a stability issue with the service… who knows???

  3. Fraser says:

    Worked for me too and all of my VM’s continued to run fine. Thanks.

  4. Fraser says:

    Worked for me too and all of my VM’s continued to run fine. Thanks.

  5. supermario (@supermario580) says:

    Worked for me too! Thanks for your post! πŸ™‚

    F1 with a smile.

  6. supermario (@supermario580) says:

    Worked for me too! Thanks for your post! πŸ™‚

    F1 with a smile.

  7. Gene says:

    Wow, 1 year later and this is still an issue for Microsoft. Thank you, Wolffhaven, your solution worked across all of our _up_to_date_ Hyper-V hosts.

  8. Gene says:

    Wow, 1 year later and this is still an issue for Microsoft. Thank you, Wolffhaven, your solution worked across all of our _up_to_date_ Hyper-V hosts.

  9. Rossg says:

    Worked for me too. One would think MS would have fixed this by now.

  10. Rossg says:

    Worked for me too. One would think MS would have fixed this by now.

  11. Pat says:

    Worked for me! No impact on running VMs. Thanks!

  12. Pat says:

    Worked for me! No impact on running VMs. Thanks!

  13. Peter S. says:

    I ran into this issue on Windows 10 and your solution worked perfectly. Many thanks for taking the time to share it!

    For the benefit of the search engines…
    The specific error I got was:

    [Window Title]
    New Virtual Machine Wizard

    The server encountered an error while creating

    [Content]
    The operation failed.

    An unexpected error occurred: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

    [Expanded Information]
    The operation failed.

    The Hyper-V Virtual Machine Management service encountered an unexpected error: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

  14. Peter S. says:

    I ran into this issue on Windows 10 and your solution worked perfectly. Many thanks for taking the time to share it!

    For the benefit of the search engines…
    The specific error I got was:

    [Window Title]
    New Virtual Machine Wizard

    The server encountered an error while creating

    [Content]
    The operation failed.

    An unexpected error occurred: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

    [Expanded Information]
    The operation failed.

    The Hyper-V Virtual Machine Management service encountered an unexpected error: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

  15. YaEl (@outlandier) says:

    Thank you,
    This was driving me crazy.

  16. YaEl (@outlandier) says:

    Thank you,
    This was driving me crazy.

  17. Brent says:

    That was easy. Thanks, was getting a generic error on a new 2012R2 install. Simply restarting the service worked.

  18. Brent says:

    That was easy. Thanks, was getting a generic error on a new 2012R2 install. Simply restarting the service worked.

  19. Surjeet says:

    Super hit.. I was having a similar issue on Windows 10 1607 build.. people like you who take the time to share makes a lot of difference to the community πŸ™‚

  20. Surjeet says:

    Super hit.. I was having a similar issue on Windows 10 1607 build.. people like you who take the time to share makes a lot of difference to the community πŸ™‚

  21. Foltran says:

    Works! thanks

  22. Foltran says:

    Works! thanks

  23. mike says:

    worked for me too

  24. mike says:

    worked for me too

  25. Genie says:

    This issue is STILL affecting 2012 & R2 hyper-v machines (I have had the issue for many years now).
    It sure is annoying how frequent it happens!

  26. Genie says:

    This issue is STILL affecting 2012 & R2 hyper-v machines (I have had the issue for many years now).
    It sure is annoying how frequent it happens!

Leave a Reply

Your email address will not be published. Required fields are marked *