3

After upgrading to Windows to 24H2, I'm unable to run Windows Sandbox, as it is stuck on the splash screen. There are no errors in the logs.

What I have tried so far:

  • Uninstall and install the Windows Sandbox and Hyper-V feature
  • Enable Containers-DisposableClientVM Enable-WindowsOptionalFeature -FeatureName "Containers-DisposableClientVM" -All -Online
  • DISM DISM /Online /Cleanup-image /RestoreHealth
  • sfc scan sfc /scannnow
  • bcedit bcdedit.exe /set hypervisorlaunchtype auto

Windows specifics:

  • Edition: Windows 11 Enterprise
  • Installed on: ‎17.11.2024
  • Version: 24H2
  • OS build: 26100.2314
  • Experience: Windows Feature Experience Pack 1000.26100.32.0
Giacomo1968
  • 58,727
Anton Kalcik
  • 211

3 Answers3

1

I also updated to Windows 11 24H2 and discovered that Windows Sandbox would not run. In my case it displayed a dialog with the message:

Windows Sandbox failed to initialize. The target device has insufficient resources to complete the operation. (0x80070142)

I fixed the problem by:

  • Running the Hyper-V Manager.
  • Selecting my PC in the Server list.
  • Right clicking and selecting Hyper-V Settings.
  • In the Hyper-V Settings form selecting NUMA Spanning.
  • In NUMA spanning window checking Allow virtual machines to span physical NUMA nodes
  • Apply/Ok change
  • Restart the PC.

After making this change Windows Sandbox ran successfully.

Giacomo1968
  • 58,727
AndyDBell
  • 111
0

Try re-enabling the Sandbox in Control Panel > Programs and Features > Turn Windows features on or off

Uncheck Windows Sandbox and click OK, then restart your computer.

Then follow those same steps again and re-enable Windows Sandbox and restart again.

If this doesn't work you can also try:

dism /online /Enable-Feature /FeatureName:"Containers-DisposableClientVM" -All

Also restart Sand Box-related services by pressing win + R and typing services.msc and look for below services then right click on them and click on restart.

Hyper-V Host Compute Service
Hyper-V Virtual Machine Management
Windows Sandbox Network Virtualization Service

music2myear
  • 49,799
NoScopeHero
  • 1
0

I had the same problem. Once I got tired of uninstalling that update to only see it being reinstalled at some later point, I tried many different options, including ones listed above. NONE had worked for me, unfortunately. Until I tried the following: I disabled vGPU in the .wsb file and it did fix the problem. The idea came from this thread: https://github.com/microsoft/Windows-Sandbox/issues/71

V. King
  • 1