Share via

Error 0x800706d9 In Windows Sandbox: Container Manager Service

John Doe 0 Reputation points
Jul 20, 2025, 12:48 PM

unnamed I have reset my PC multiple times before and this issue has never occurred for Windows (10) Sandbox. Yes, I have Windows 10 Pro, necessary for this program.

unnamed This was the first time I reset my PC from a USB Windows 10 installation media, if that matters. I did it by deleting all partitions ("Delete" button, again, if that matters).

unnamed This was the only tutorial I could find for this issue (Error 0x800706d9 in Windows Sandbox) which seemed to actually be trustworthy/most useful. (Deemed by other people on the official Microsoft support page, "accepted answer" at the top).

unnamed This was after getting to Step 5 of "Do this in the following order".

unnamed Since it cannot be started, it cannot be restarted. "Restart" is greyed out.

unnamed A diagram I found online which I believe is related to the issue. I don't know if this diagram is actually true or not but just stick with me.

unnamed The error message which sparked this whole issue.

Windows for home | Windows 10 | Performance and system failures
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ramesh 176.3K Reputation points Volunteer Moderator
    Jul 26, 2025, 1:11 PM

    Please open admin Command Prompt and run these commands:

    sc.exe config hvhost start= demand

net start hvhost

sc.exe qc cmservice

net start cmservice

    Post the output.

    Was this answer helpful?

    1 person found this answer helpful.
  2. Ramesh 176.3K Reputation points Volunteer Moderator
    Jul 25, 2025, 2:54 PM

    Please run MSINFO32.EXE as administrator.

    In MSINFO32, press Ctrl + S and save the system information report (.NFO file).

    Share the log file on OneDrive.

    Was this answer helpful?

    1 person found this answer helpful.
  3. tpowell 0 Reputation points
    Dec 30, 2025, 3:19 AM

    I had the same symptoms and none of the usual suspects fixed the problem:

    reinstalling "Windows Sandbox"

    sfc /scannow

    dism...

    restarting services...

    What actually worked was making sure Control flow guard (CFG) was enabled by default in Windows Security. In my case it was not.

    • Open "Windows Security"
    • Click on "App and Browser Control"
    • Click on "Exploit Protection Settings"
    • Make sure "Control flow guard (CFG)" is set to "On by default"
    • Next, go to the "Program Settings" Tab on the same page and check if "vmcompute.exe" is listed, if it is, remove it.
    • Reboot

    as stated here: https://superuser.com/a/1800537

    Was this answer helpful?

    0 comments
  4. Francisco Montilla 30,635 Reputation points Independent Advisor
    Jul 20, 2025, 2:22 PM

    Hello John,

    Windows Sandbox actually depends on the Firewall Service.

    When that service is disabled, you'll see 0x800706d9 - no more endpoints available from the endpoint mapper because the Firewall hosts key RPC endpoints Sandbox needs. Now let's get that service running again.

    Press Win+R, type services.msc and hit Enter. Scroll down to Windows Defender Firewall (it may still say “Windows Firewall” on older builds). Right-click, choose Properties, set the Startup type to Automatic, then click Start. Click OK and close the Services window.

    Now try starting the Container Manager Service. It should come up without error. After that, Windows Sandbox will launch normally.

    Give that a try and let me know if Sandbox fires up for you.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.