Docker Desktop for Windows 4 - Dotnet Errors after installation

[IDiston-VA]

• [ x] I have tried with the latest version of Docker Desktop
• [x ] I have tried disabling enabled experimental features
• [x ] I have uploaded Diagnostics
• Diagnostics ID: E9C80786-FD7F-43E1-ABEF-EEA426A9D3AC

After installation and initial reboot I receive two DotNet Errors

No1:
System.NullReferenceException: Object reference not set to an instance of an object.
at Docker.Core.Features.Features.d__16.MoveNext() in C:\workspaces\PR-16319\src\github.com\docker\pinata\win\src\Docker.Core\Features\Features.cs:line 91
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Docker.App.d__27.MoveNext() in C:\workspaces\PR-16319\src\github.com\docker\pinata\win\src\Docker.Desktop\App.cs:line 111
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

No2
System.NullReferenceException: Object reference not set to an instance of an object.
at Docker.Systray.Systray.ExitThreadCore() in C:\workspaces\PR-16319\src\github.com\docker\pinata\win\src\Docker.Desktop\Systray\Systray.cs:line 281
at System.Windows.Forms.Application.ThreadContext.ExitCommon(Boolean disposing)
at System.Windows.Forms.Application.ExitInternal()
at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Expected behavior

I beleive it should start up

Information

Yes

• Is the problem new? --> Yes, only tried today !

• Did the problem appear with an update? --> No

• Windows Version: 21H1 19043.1202

• Docker Desktop Version: 4

• WSL2 backend

• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: Yes. VMWare Workstation Version: 15.5.7 build-17171714

Steps to reproduce the behavior

1. Build Windows 10 fully patched VM
2. Download Docker Desktop for Windows
3. Install as Administrator
4. Select WSL
5. Restart VM

[IDiston-VA]

20210914222011.zip

[soroshsabz]

ITNOA

related to #12066
related to #12158

[IDiston-VA]

Managed to get a bit further by playing with the Processor settings in the VM Settings.

1. Uninstalled Docker and WSL Update
2. Removed AppData\Roaming\Docker, AppData\Roaming\Docker Desktop, AppData\Local\Docker
3. Shutdown VM
4. Unticked "Virtualize Intel VT-x/EPT or AMD-V/RVI"
5. Rebooted VM
6. Shutdown VM
7. Ticked "Virtualize Intel VT-x/EPT or AMD-V/RVI"
8. Started up VM
9. Installed Docker and WSL Update

So far so good.

[marcellus-trixus]

If it helps somebody, I experienced exactly same error when I had neither hyper-v nor wsl2 installed on my system (after fresh win reinstall). As soon as I installed hyper-v the docker started up normally.

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days 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

[docker-robott]

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