[Bug]: Windows Sandbox Fails to Start with an Error Code: 0x800705B4
### Windows Sandbox version 0.5.3 ### Windows build number 10.0.26200.7309 ### Other software _No response_ ### Steps to reproduce the bug 1. Uninstall Windows Sandbox from Windows Features in Control Panel. 2. Reinstall Windows Sandbox from Windows Features in Control Panel. 3. Start Windows Sandbox. 4. Windows Sandbox will be updated to the latest version. 5. Windows Sandbox logo will stall with a spinning circle for ten minutes or so. 6. An error code will show: 0x800705B4. ### Expected result Windows Sandbox is supposed to start after seeing a logo for three or five seconds. ### Actual result 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. ### Included System Information _No response_
Posted by CompactProducer on Dec 5, 2025, 3:39 PM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
[Bug]: Windows Sandbox Fails to Start with an Error Code: 0x800705B4
### Windows Sandbox version 0.5.3 ### Windows build number 10.0.26200.7309 ### Other software _No response_ ### Steps to reproduce the bug 1. Uninstall Windows Sandbox from Windows Features in Control Panel. 2. Reinstall Windows Sandbox from Windows Features in Control Panel. 3. Start Windows Sandbox. 4. Windows Sandbox will be updated to the latest version. 5. Windows Sandbox logo will stall with a spinning circle for ten minutes or so. 6. An error code will show: 0x800705B4. ### Expected result Windows Sandbox is supposed to start after seeing a logo for three or five seconds. ### Actual result 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. ### Included System Information _No response_
Comments (0)
No comments yet. Start the discussion.