Hyper-V logon failure: the user has not been granted the requested logon type at this computer

Replies

6 suggested answers

·

4 replies

Add heading textAdd bold text, <Ctrl+b>Add italic text, <Ctrl+i>

Add a quote, <Ctrl+Shift+.> Add code, <Ctrl+e>

Insert Link

Add a bulleted list, <Ctrl+Shift+8>Add a numbered list, <Ctrl+Shift+7>Add a task list, <Ctrl+Shift+l>

Directly mention a user or teamReference an issue or pull request

Add heading textAdd bold text, <Ctrl+b>Add italic text, <Ctrl+i>Add a bulleted list, <Ctrl+Shift+8>Add a numbered list, <Ctrl+Shift+7>Add a task list, <Ctrl+Shift+l>

I've the same problem here.
If I restart the hyperV service, quit docker desktop and restart it, it works.
Diagnostic id : B70DF673-C29E-4AEC-999D-84F5ED5D8487/20190320090656

Same issue here. Have added user to docker-users but it still does this

Log B540725F-4F3B-4C5E-96F9-66E11A52B9E6/20190508093708

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

/remove-lifecycle stale

Still happening.

I got the same issue

`
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).
at New-MobyLinuxVM, : line 397
at New-MobyLinux, : line 182
at , : line 810

at Docker.Core.Pipe.NamedPipeClient.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.Actions.DoRestartVM(Settings previousSettings)
at Docker.Actions.<>c__DisplayClass34_0.b__0()
at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass18_0.<.ctor>b__1()`

Got the same issue, restarting the Windows Management Instrumentation service solved the issue.
Note: you may need to start the Services.msc as an administrator.

It's great that restarting a service or two manually resolves the issue temporarily, but there appears to be an underlying problem here that is causing Docker to crash randomly, sometimes at start-up, sometimes after running for hours, and restarting a service is only puts a band-aid on the problem until it happens again.

I really hope this issue can be reopened and looked into, because for me at least, Docker for Windows is unusable.

I'm getting this. I fixed it by restarting 'Hyper-V Host Compute Service' in Services

I've the same problem here.
If I restart the hyperV service, quit docker desktop and restart it, it works.
Diagnostic id : B70DF673-C29E-4AEC-999D-84F5ED5D8487/20190320090656

I could not find a hyperV service only a Hyper-V-... process.
I turned it off. Started docker desktop again as admin and now Docker is running.

Got the same issue, restarting the Windows Management Instrumentation service solved the issue.
Note: you may need to start the Services.msc as an administrator.

Just encountered this issue. I wonder if it could be related to putting the machine to sleep.

I just hit this. Docker Desktop was running fine. It wanted to update so I let it. It failed to start up with this error. Restarting the Hyper-V Virtual Machine Management (vmms) service worked around the problem. There's no need to restart WMI; that's a very large hammer (restarts a lot of other unaffected services).

This same here. It is happening almost every time after machine restart.

I'm getting this. I fixed it by restarting 'Hyper-V Host Compute Service' in Services

Did this and it started working fine.

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

How do I fix logon failure the user has not granted the requested logon type at this computer?

What has not been granted the requested logon type at this computer?

How do I add NT virtual machine to GPO?

How do I log into Hyper V?