Home OS Windows Windows Sandbox failed to start, Error 0x800706d9

Windows Sandbox failed to start, Error 0x800706d9

If you see this error message – Windows Sandbox failed to start out, Error 0x800706d9, There are not any extra endpoints obtainable from the endpoint mapper, then this submit could possibly show you how to.

Windows Sandbox error 0x800706d9

The sandbox error can occur due to file corruption, providers not working, and typically it’s due to a function replace. Follow the steered strategies to resolve the issue. But earlier than you start, be sure you have enabled virtualization settings in your pc BIOS or Firmware menu, which may be accessed throughout bootup of the pc.

  1. Check the standing of Hyper-V Related Services
  2. Disable and Enable Hyper-V
  3. Check for Cumulative Update in Windows

You will want admin permission to observe the steps to resolve the issue.

1] Check the standing of Hyper-V Related Services

Open Services Manager and be certain that the next Services are Started. If the are, Restart them; If ther or not, then Start them:

  • Network Virtualization Service
  • Virtual Disk
  • Hyper-V Virtual Machine Manager
  • Hyper-V Host Compute Service
  • Container Manager Services
  • Application Guard Container Service
  • Remote Procedure Call (RDC)

2] Disable and Enable Hyper-V

Eric O’Malley offered this workaround at Microsoft Answers.

Next, please navigate to the folders and Search for VHDX recordsdata and delete them however not from the recycle bin. You should unhide system recordsdata, hidden recordsdata, and so forth.



Having carried out that, activate and allow every little thing that was disabled earlier than deleting the VHDX file.

  • Enable Windows Sandbox
  • Turn on or Restart Container Manager Service
  • Turn on Windows Defender Random Folder Protection and Tamper Protection Service

Check if Windows Sandbox opens as regular. You might should restart the pc.

READ: Windows Sandbox not loading, opening, or working.

3] Check for Cumulative Updates

It is feasible that one of many function updates has damaged this, and the one manner out is Microsoft fixing it by way of a cumulative replace. In that case, you’ll have to preserve checking if there may be an replace that fixes it.

Let us know if something right here or one thing else helped you fic the issue.

Most Popular

Recent Comments