docker user granted requested logon type computer

Docker the user has not been granted the requested logon type at this computer.

Docker Desktop fails to start after upgrading - Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569)

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID:

Actual behavior

Docker desktop fails to start after upgrading

Expected behavior

Docker Desktop starts after updating the software

Information

I was running Docker Desktop 4.4.4. Because of group policy, I am unable to use the updater within the Docker Desktop application, I have to manually download the installer and run it with elevated privileges. After running the installer, Docker started and displayed the following error:

"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)"

Windows Version: Windows 10 1909 (Build 18363.2094) Docker Desktop 4.4.4 -> 4.5.1 Backend: Hyper-V (WSL disabled via GPO) Running Windows on bare metal.

Steps to reproduce the behavior

  1. Install Docker Desktop 4.4.4 w/ Hyper-V backend
  2. Upgrade to 4.5.1 using the install
  3. Watch the fireworks...

I got the error: <<Cluster resource 'Virtual Machine Configuration Teams' of type 'Virtual Machine Configuration' in clustered role '8 - Teams' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.>>

I researched and find out that NT Virtual Machine\Virtual Machines should be in the entries for Log on as a Service: NT Virtual Machine\Virtual Machines in the entries for Log on as a Service.

I checked and noticed that it is like that but we still get the error: //prntscr.com/va8obg

We are not able to move the virtual machines from one host to another. Please help us to fix the issue.

I am a happy Docker for Windows user and it has been of great help to have it running natively on Windows 10.

However since the last 2–3 updates, the experience around upgrading has not been positive. On all the occasions, the Docker daemon has failed to start and I have ended up uninstalling and installing it again at times.

I have found one issue recurring every time during the upgrade and this time I wanted to solve it (if possible) and here are my notes from it. It does look at a high level that there are still some issues with Docker → Microsoft Hyper-V → some Windows permissions → Windows Services but the link is not too clear to me.

Here are my notes:

Step 1

The Docker Icon in the System Tray will complain about some issue with and will turn RED.

Step 2

Remember that there is a great option available to see the Docker daemon logs and figuring out what happened. To get to the logs, right-click on the Docker App whale icon in the System Tray and click on Diagnose & Feedback

Step 3

In the Diagnose & Feedback section, you will find a link to the log file as highlighted below. Click on that.

This will bring up the Docker daemon log and if you had the daemon fail to start up, you can scroll to the bottom and take a look at the error that caused it. The log files are created in

%HOMEPATH%\AppData\Local\Docker

In my case, the two errors that I received as part of trying to restart Docker after the upgrade are listed below:

Failed to create VM “MobyLinuxVM”

[15:15:39.579][NamedPipeServer][Error ] Unable to execute Start: Failed to create VM “MobyLinuxVM”: The operation failed.An unexpected error occurred: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).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 System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[15:15:39.601][NamedPipeClient][Error ] Unable to send Start: Failed to create VM “MobyLinuxVM”: The operation failed.An unexpected error occurred: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).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).

A search of Docker forums / Knowledge Bases usually led to fingers being pointed at the following Windows Service (Windows Management Service):

The general recommendation is to Restart the service. You can restart it and it worked for me on one occasion but the next couple of times, it failed with another error given below:

Failed to start VM “MobyLinuxVM”

The detailed log is given below:

[15:23:52.341][NamedPipeServer][Error ] Unable to execute Start: Failed to start VM “MobyLinuxVM”: ‘MobyLinuxVM’ failed to start.Synthetic SCSI Controller (Instance ID 5C7B051C-7C75–4B19-AE2C-B29C573C9D2E): Failed to Power on with Error ‘General access denied error’.Account does not have permission to open attachment ‘c:\users\public\documents\hyper-v\virtual hard disks\mobylinuxvm.vhdx’. Error: ‘General access denied error’.‘MobyLinuxVM’ failed to start. (Virtual machine ID 972E4520–702A-4AA1-A924–26498573917D)‘MobyLinuxVM’ Synthetic SCSI Controller (Instance ID 5C7B051C-7C75–4B19-AE2C-B29C573C9D2E): Failed to Power on with Error ‘General access denied error’ (0x80070005). (Virtual machine ID 972E4520–702A-4AA1-A924–26498573917D)‘MobyLinuxVM’: Account does not have permission to open attachment ‘c:\users\public\documents\hyper-v\virtual hard disks\mobylinuxvm.vhdx’. Error: ‘General access denied error’ (0x80070005). (Virtual machine ID 972E4520–702A-4AA1-A924–26498573917D) at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[15:23:52.361][NamedPipeClient][Error ] Unable to send Start: Failed to start VM “MobyLinuxVM”: ‘MobyLinuxVM’ failed to start.Synthetic SCSI Controller (Instance ID 5C7B051C-7C75–4B19-AE2C-B29C573C9D2E): Failed to Power on with Error ‘General access denied error’.Account does not have permission to open attachment ‘c:\users\public\documents\hyper-v\virtual hard disks\mobylinuxvm.vhdx’. Error: ‘General access denied error’.‘MobyLinuxVM’ failed to start. (Virtual machine ID 972E4520–702A-4AA1-A924–26498573917D)‘MobyLinuxVM’ Synthetic SCSI Controller (Instance ID 5C7B051C-7C75–4B19-AE2C-B29C573C9D2E): Failed to Power on with Error ‘General access denied error’ (0x80070005). (Virtual machine ID 972E4520–702A-4AA1-A924–26498573917D)‘MobyLinuxVM’: Account does not have permission to open attachment ‘c:\users\public\documents\hyper-v\virtual hard disks\mobylinuxvm.vhdx’. Error: ‘General access denied error’ (0x80070005). (Virtual machine ID 972E4520–702A-4AA1-A924–26498573917D)

The message “General access denied error” is a bit confusing here. My first thoughts were around my own account rights on this machine and there is no problem with that since I have full Administrator rights.

Once again, a search of Microsoft Knowledgebase (KB2249906) brought up the following article and which suggested that I needed to add the Virtual Machine SID to the Virtual Machine vhdx file.

The steps which I reproduce from the KB article were as follows:

  • Note down the Virtual Machine ID first from the error log. You will see it in there. For e.g. in my log it is as follows:
Virtual machine ID 972E4520–702A-4AA1-A924–26498573917D
  • Now look at the error message that we got:
Account does not have permission to open attachment ‘c:\users\public\documents\hyper-v\virtual hard disks\mobylinuxvm.vhdx’

Note down the full path of the Virtual Machine Hard disk image file name.

  • The next thing is to open an elevated command prompt. If you are not sure how to do that — just go to Start → Enter cmd → then Ctrl-Shift-Enter and click on “Yes” on the permissions screen.
  • Now give the following command:
icacls <Path of .vhd or .avhd file> /grant "NT VIRTUAL MACHINE\<Virtual Machine ID>":(F)

In brief, icacls is a command-line utility to modify the ACL for files/directories.

Step 4

Go to Microsoft Hyper-V and restart / start the MobyLinuxVM. Make sure that the State and Heartbeat values end up as follows:

Step 5

Now go ahead and restart Docker service.

Hopefully this works for you. If something else has worked for you, do share in the comments section.

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

To resolve this issue, edit the Access this computer from the network local policy on the desktop to restore the "Users" access group or add one or more user and group values to provide the required access. Alternatively this can be configured using Group Policy.

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

To solve “The user has not been granted the requested logon type at this computer” error, you should make sure that the login user and all groups that belong to are allowed to log on locally to this computer.

zusammenhängende Posts

Logon failure: the user has not been granted the requested logon type at this computer Docker
Terraform is not recognized as an internal or external command, operable program or batch file
Der Benutzer besitzt nicht den benötigten Anmeldetyp auf diesem Computer Docker

Toplist

Neuester Beitrag

Stichworte