windows sandbox just spinning at start ? 25h2 26200.7462

FreeBooter said:

I giving you why 0x800705B4 error code happens, it's timeout you use command line to install Windows Sandbox, so there is no problem with installation but for some reason Windows Sandbox won't open, and it times out with error code 0x800705B4.

Have you executed Sfc /Scannow the command if not try it.

Click to expand...

Yes dsim sfc and no error present all people in thge github link I posted and all alright the tmeout the bug its not for isntalling windows sandbox its when U start de sandbox windows create a virtual machine, this machine when run fine before de bug size its ober 200-300 MB but the bug as U can read below up to 1Gb and growing and when the sandbox get the timeout I supose into the code and U can see the error number....

Its a bug many user for many contries have this same issue.... its not a fail from a corrupted system....

Windows Sandbox logo will stall for ten minutes or so and an error code, 0x800705B4, will pop up. In C:\ProgramData\Microsoft\Windows\Containers\ContainerStorages, if I double-click a GUID (for example, ab243dfa-20dl-2k33-hjg8-2934hb767yh4), a sandbox.vhdx file will grow up to 1GB. After this, it gets deleted and Windows Sandbox exits with a 0x800705B4 error code.

rhadamantys said:

Yes dsim sfc and no error present all people in thge github link I posted and all alright the tmeout the bug its not for isntalling windows sandbox its when U start de sandbox windows create a virtual machine, this machine when run fine before de bug size its ober 200-300 MB but the bug as U can read below up to 1Gb and growing and when the sandbox get the timeout I supose into the code and U can see the error number....

Its a bug many user for many contries have this same issue.... its not a fail from a corrupted system....

Windows Sandbox logo will stall for ten minutes or so and an error code, 0x800705B4, will pop up. In C:\ProgramData\Microsoft\Windows\Containers\ContainerStorages, if I double-click a GUID (for example, ab243dfa-20dl-2k33-hjg8-2934hb767yh4), a sandbox.vhdx file will grow up to 1GB. After this, it gets deleted and Windows Sandbox exits with a 0x800705B4 error code.

Click to expand...

same, Sfc /Scannow etc finds nothing wrong. have some vmware machines, but faster to use sandbox sometimes.

Christophe Sperandio in github create a great post why the sandbox is not working​

So, I had some time to investigate this a little deeper.

Summary​

After installing KB5070311 (or maybe a previous patch) on Windows 11 Insider (Release Preview, build 26200.7462), Windows Sandbox no longer starts and fails with 0x800705B4 (timeout).

Root cause​

The directory C:\ProgramData\Microsoft\Windows\Containers\BaseImages is empty after the update. Sandbox cannot initialize without a base image and hangs until timeout.

Notes​

• Hyper‑V and WSL continue to work normally.
• Required features and services are enabled and running.
• Reinstalling the Sandbox feature does not recreate the BaseImages directory.
• Sandbox launches vmcompute and vmwp successfully, but never enters the Containers provisioning path. No container image resolution or storage access is attempted. This appears to be a regression in Sandbox scenario activation rather than a missing image or configuration issue.

Impact​

Windows Sandbox is completely unusable on affected systems.

Suspected regression​

Provisioning of Windows Sandbox base images appears broken starting with KB5070311 (or maybe a previous one).

Summary​

After installing KB5070311 (or maybe a previous patch) on Windows 11 Insider (Release Preview, build 26200.7462), Windows Sandbox no longer starts and fails with 0x800705B4 (timeout).

Root cause​

The directory C:\ProgramData\Microsoft\Windows\Containers\BaseImages is empty after the update. Sandbox cannot initialize without a base image and hangs until timeout.

Notes​

• Hyper‑V and WSL continue to work normally.
• Required features and services are enabled and running.
• Reinstalling the Sandbox feature does not recreate the BaseImages directory.
• Sandbox launches vmcompute and vmwp successfully, but never enters the Containers provisioning path. No container image resolution or storage access is attempted. This appears to be a regression in Sandbox scenario activation rather than a missing image or configuration issue.

Impact​

Windows Sandbox is completely unusable on affected systems.

Suspected regression​

Provisioning of Windows Sandbox base images appears broken starting with KB5070311 (or maybe a previous one).

Summary​

After installing KB5070311 (or maybe a previous patch) on Windows 11 Insider (Release Preview, build 26200.7462), Windows Sandbox no longer starts and fails with 0x800705B4 (timeout).

Root cause​

The directory C:\ProgramData\Microsoft\Windows\Containers\BaseImages is empty after the update. Sandbox cannot initialize without a base image and hangs until timeout.

Notes​

• Hyper‑V and WSL continue to work normally.
• Required features and services are enabled and running.
• Reinstalling the Sandbox feature does not recreate the BaseImages directory.
• Sandbox launches vmcompute and vmwp successfully, but never enters the Containers provisioning path. No container image resolution or storage access is attempted. This appears to be a regression in Sandbox scenario activation rather than a missing image or configuration issue.

Impact​

Windows Sandbox is completely unusable on affected systems.

Suspected regression​

Provisioning of Windows Sandbox base images appears broken starting with KB5070311 (or maybe a previous one).

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

Win11 25h2 26200.7623

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.<br><br>* All FileSystemControl, CreateFileMapping, QuerySecurityFile operations on system files (32.dll, .sdb) return SUCCESS.<br><br>* 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).<br><br>* Phase 1 (Sysprep): vmmemCmSysprep (PID 74012) writes continuously ~295MB+ offsets, 4-65KB blocks, all SUCCESS non-cached IO.<br><br>* Phase 2 (FirstBoot): Transitions to vmmemCmFirstBoot (PID 53304), reads/writes high offsets (341MB+, up to 820MB+), indicating guest OS OOBE/config in progress.<br><br>* 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.<br><br>* Activity continues post-Sysprep into FirstBoot, but Sandbox UI times out (likely 0x800705B4) waiting for guest readiness signal.<br><br>* Container orchestration fails handshake despite VM I/O healthy.

Environment:​

* Windows 11 25H2 Build 26200.7462<br><br>* Windows Sandbox 0.5.13 (Microsoft Store, 2025-09-11)<br><br>* 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

Windows sandbox is working just fine on my work and my personal desktop, with all updates completed. No issues here. Both intel and amd systems.

If your having issues, I suspect some type of corruption.

andrew129260 said:

Windows sandbox is working just fine on my work and my personal desktop, with all updates completed. No issues here. Both intel and amd systems.

If your having issues, I suspect some type of corruption.

Click to expand...

You're lucky you haven't been affected by the bug that's impacting thousands of PCs and laptops running Windows 11. I don't know why it works for you, but I can assure you it's not because your system is corrupted. As I mentioned above, I've run all sorts of tests and system diagnostics, and there are no errors of any kind, just like most people experiencing this bug.In fact, if you look at the analyses in the GitHub thread by Sandbox and others, they offer a lot of detail about what the bug is and which processes are failing.And everyone's waiting for Microsoft to release a fix or a new version correcting the error.Regards

If a bunch of people are having issues then there must be something connected or related. Software or something

It is running fine on my system. I wish I knew how to use it.

Finally with the lasts updates Microsoft fix the bug and the sandbox run again.

rhadamantys said:

Finally with the lasts updates Microsoft fix the bug and the sandbox run again.

Click to expand...

yes, working again now