I'm having a problem running Windows Sandbox on my Windows 11 PC. When I start Windows Sandbox, it stalls at the logo for ten minutes or so, and then an error message shows up: Restarting the PC and uninstalling and reinstalling Windows Sandbox don't correct the problem. Anybody else experiencing this problem?

Windows 11 pro jan 2016 update installed, the bug still here.... Win11 25h2 26200.7623

Here https://github.com/microsoft/Windows-Sandbox/issues/101 Some more user experience the same bug and some have use debug and procmon program to traied to explained the problem and causes. I hope Micrososft view the sandbox github, but appear its dead... I hope Microsoft create a fix o a update or something to reapir this bug

It's unbelievable how Microsoft is ignoring (the shitting) this problem, which affects me and countless other users.

i have deleted my double answer

Windows Sandbox fails to open with 0x800705B4

Michael Higham 265

I'm having a problem running Windows Sandbox on my Windows 11 PC.

When I start Windows Sandbox, it stalls at the logo for ten minutes or so, and then an error message shows up:

User's image

Restarting the PC and uninstalling and reinstalling Windows Sandbox don't correct the problem.

Anybody else experiencing this problem?

David Elliott 30 Reputation points

2025-12-12T11:37:46.44+00:00

Same here with Windows Sandbox not starting with (0.800705B4).

Windows Sandbox is turned on in "turn Windows features on & off."

Sandbox opened and worked normally previously but I am unsure if I tested this after update KB5070311. But it definitly does not work after KB5072033.
JM 65 Reputation points

2025-12-12T15:36:55.9266667+00:00

I have the exact same issue, and going to Windows Store just says Windows Sandbox is installed (there is no update pending for it)

Win 11 Build 26100.7462
daniel grandjean 0 Reputation points

2025-12-15T10:32:37.82+00:00

Not yet install KB5072033 and already not working.
Krzysztof Huryn 30 Reputation points

2025-12-19T09:31:58.7133333+00:00

Exactly the same issue here, since a week or so ago.
Windows 11 Pro 25H2 (OS Build 2600.7462).
Tried all the obvious steps including removing/re-adding the Sandbox feature.
Tried starting Sandbox with both standard settings and using my own .wsb with the <vGPU>Disable</vGPU> added. None of the methods work.
When activating Sandox, generation of the temp files in c:\ProgramData\Microsoft\Windows\Containers\ContainerStorages\ takes some minutes while the folder grows to just below 2 GB, then the (0x800705B4) error appears.
micTronic 0 Reputation points

2025-12-29T11:52:56.12+00:00

See the issue also reported here:
https://github.com/microsoft/Windows-Sandbox/issues/101
Bijan 0 Reputation points

2026-02-11T07:54:58.2966667+00:00

I noticed this problem in January. Tried updating to build 26200.7628 and reinstalling the sandbox. However, the issue still persists with a few minutes of loading—then the sandbox crashes with 0x800705B4.
CharlyArg 0 Reputation points

2026-05-10T20:04:56.6166667+00:00

Chiming in here as I have 22600.8246 and still having issues to start Sandbox in Windows 11. Oddly enough I found out that if I start it just as soon as I login, it will work; thus: application. In my case it was Moto's Smart Connect application (it connects to your smartphone). But worth it to check the ones open.

29 answers

rhadamantys 70

the user OReactko in github os windows sanbox issue opened wrote this

A little more technical details now that I could grab a whole trace with ProcMon:

1. Hyper-V Infrastructure Healthy:

* vmms.exe (PID 4048) and vmcompute.exe (PID 4356) successfully create/load VM config files (.vmcx), mappings for C32.dll/exe.

* All FileSystemControl, CreateFileMapping, QuerySecurityFile operations on system files (32.dll, .sdb) return SUCCESS.

* No ACCESS_DENIED, STATUS_FILE_LOCKED, or I/O timeouts in early VM setup phase.

2. Sandbox VHDX Creation & Growth:

* Sandbox VHDX: C67c5896-3699-4e6f-9b26-5cb6aa5dd754.vhdx (for the run I traced down).

* Phase 1 (Sysprep): vmmemCmSysprep (PID 74012) writes continuously ~295MB+ offsets, 4-65KB blocks, all SUCCESS non-cached IO.

* Phase 2 (FirstBoot): Transitions to vmmemCmFirstBoot (PID 53304), reads/writes high offsets (341MB+, up to 820MB+), indicating guest OS OOBE/config in progress.

* VHDX grows as expected during boot sequence, no disk/NTFS errors.

3. Failure Pattern:

* No explicit errors (IRP_MJ_DEVICE_CONTROL, DeviceIoControl failures) explaining timeout.

* Activity continues post-Sysprep into FirstBoot, but Sandbox UI times out (likely 0x800705B4) waiting for guest readiness signal.

* Container orchestration fails handshake despite VM I/O healthy.

Environment:

* Windows 11 25H2 Build 26200.7462

* Windows Sandbox 0.5.13 (Microsoft Store, 2025-09-11)

* Hyper-V features enabled, no WSL/VMware conflicts visible.

Implication: Product bug in Sandbox boot orchestration, not host storage/Hyper-V fault.

yeah, when I tried run Hyper-V VM, it was ok

Michael Hetzer 0 Reputation points

2026-01-18T08:33:07.0233333+00:00

Hoffentlich haben die bei Microsoft, diesen Fehler mitbekommen und arbeiten mit Hochdruck an diesem Problem. Es besteht weiterhin !!!

rhadamantys 70 Reputation points

2026-01-13T20:17:11.0533333+00:00

Windows 11 pro jan 2016 update installed, the bug still here....

Win11 25h2 26200.7623
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
rhadamantys 70 Reputation points

2026-01-13T11:56:34.6166667+00:00

Here https://github.com/microsoft/Windows-Sandbox/issues/101

Some more user experience the same bug and some have use debug and procmon program to traied to explained the problem and causes.

I hope Micrososft view the sandbox github, but appear its dead...

I hope Microsoft create a fix o a update or something to reapir this bug
Was this answer helpful?
Christophe Sperandio 5 Reputation points

2026-01-13T12:47:42.8433333+00:00

Yes! I'm the one having done the procmon analysis and posted on GitHub. I'm also feeding z reddit thread and opened a detailed feedback in the feedback hub... Hope we will get some visibility at some point!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
WILSON JIACOMINI 25 Reputation points

2026-01-07T15:55:08.39+00:00

It's unbelievable how Microsoft is ignoring (the shitting) this problem, which affects me and countless other users.
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Rainer Goldbach 0 Reputation points

2026-01-04T15:45:12.8266667+00:00

i have deleted my double answer
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.