Windows 10: Windows Sandbox failed to start, Error 0x800706d9

If you see this error message – Windows Sandbox failed to start, Error 0x800706d9, There are no more endpoints available from the endpoint mapper, then […]

This article Windows Sandbox failed to start, Error 0x800706d9 first appeared on TheWindowsClub.com.

read more...

 

Window sandbox fail to start 0x800706d9 (Hypervisor/Virtual Machine Support Driver element not found)

When I run the sandbox, error 0x800706d9 displayed

From the event viewer

The Container Manager Service service depends on the HV Host Service service which failed to start because of the following error:

The dependency service or group failed to start.

The HV Host Service service depends on the Hypervisor/Virtual Machine Support Driver service which failed to start because of the following error:

Element not found.

The Hypervisor/Virtual Machine Support Driver service failed to start due to the following error:

Element not found.

 

Windows sandbox does not start

I recently tried to use windows sandbox after enabling everything that's needed. However, when I run it I get the administrator prompt and then I get the icon, and that's it. I just see the windows sandbox icon on a blue background. Nothing starts. When
I alt+tab there is no name for the program. I have hyper-v enabled. After a while, I get an error saying "Windows Sandbox failed to start. Error 0x800706d9. There are no more endpoints available from the endpoint mapper. Would you like to submit a feedback
about this issue?"

 

Fix for Sandbox

Microsoft has acknowledged this issue now:

Windows Sandbox may fail to start with error code “0x80070002”Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.


Affected platforms:

• Client: Windows 10, version 1903

Next steps: We are working on a resolution and estimate a solution will be available in late June.