KB2779204 – Live Migration Of Or Starting WS2012 Hyper-V VMs Fails With 0x80070569 Error

Ben Armstrong (MSFT Senior PM Lead with Hyper-V), aka The Virtual PC Guy, tweeted this morning about an issue where starting virtual machines on a Windows Server 2012 or Hyper-V Server 2012 host might fail with the following error:

Error 0x80070569 (‘VM_NAME’ failed to start worker process: Logon Failure: The user has not been granted the requested logon type at this computer.)

Live Migration of a virtual machine on the same hosts might also fail with this message:

Failed to create Planned Virtual Machine at migration destination: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569)

It’s one of those sometimes it’s happening and sometimes it’s not problems. Microsoft says that running GPUpdate /Force might temporarily resolve the issue.

The issue appears to be caused by a group policy issue that is preventing NT Virtual MachineVirtual Machines from having the right to Log on as a Service. According to Microsoft:

Usually, the Virtual Machine Management Service (VMMS) replaces this user permission at every Group Policy refresh to ensure it is always present. However, you may notice that Group Policy refresh does not function correctly in certain situations.

Microsoft is working on the problem. They have posted a number of workarounds in the KB article that you can use if you are experiencing the issue. Please don’t be a moron: only apply a workaround if you are experiencing the problem.

Technorati Tags: ,

3 thoughts on “KB2779204 – Live Migration Of Or Starting WS2012 Hyper-V VMs Fails With 0x80070569 Error”

  1. Hi Aidan

    useful site from which I’ve gotten some good tips. Have you heard of any update on this – 2 years on from the original “fast publish” article, it’s still a problem in 2012 R2 and I can’t find anything more up to date than the various workarounds, which aren’t exactly ideal even when one can get them to work – block inheritance isn’t something I’m keen to use, undoing my centralised management of who and what can log on as a service isn’t ideal either. Would be pretty annoyed with MS to discover they’ve done nothing with this nearly 2 years later.

  2. November 2015, I’m encountering the same error moving VMs with clustered Hyper-V on Server 2016 TP4 and S2D (no SOFS).
    I came across an article on a Dell website (this is not Dell hardware) suggesting restarting the WMI services — which also restarts a few other dependent services. It does seem to work temporarily, but the issue comes back.
    Interesting that it’s so persistent. Would be nice to think they will have it fixed before 2016 ships, but I’m not betting on it.
    — Ken

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.