You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Still seeing Virtual Machine Platform is not enabled error upon install #747
Even though I enabled the feature in administrator Powershell and restarted my PC as the following, I still keep seeing the same error. Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform
Reproduction steps
Download the docker installer from US Microsoft Store.
Open the .exe file
Wait for the auto-load of Docker Desktop
Manually open the app since it doesn't do anything.
Watch the error message and do what the error message suggests.
Upon restart, open the app again to see the same error message.
Platform
Windows
Version information
Client:
Version: 29.8.2
API version: 1.56
Go version: go1.26.8
Git commit: 7fc2dff
Built: Wed Sep 30 19:35:42 2026
OS/Arch: windows/amd64
Context: desktop-linux
request returned 500 Internal Server Error for API route and version http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.56/version, check if the server supports the requested API version
From the diagnostics, Windows is still missing the components that Virtual Machine Platform installs, even after your restart, so Docker couldn't start its default Linux backend.
You've already found a good way forward: Docker VMM doesn't depend on that feature, so it's fine to keep using it. If you'd like the default WSL 2 backend working as well, could you open PowerShell as administrator and send us the output of these two commands?
Activity
joons5834 commentedon Oct 15, 2026
I changed VMM to
Docker VMMand the error message disappeared.voonyee commentedon Oct 20, 2026
Thanks for the detailed report.
From the diagnostics, Windows is still missing the components that Virtual Machine Platform installs, even after your restart, so Docker couldn't start its default Linux backend.
You've already found a good way forward: Docker VMM doesn't depend on that feature, so it's fine to keep using it. If you'd like the default WSL 2 backend working as well, could you open PowerShell as administrator and send us the output of these two commands?