Unable to start sandbox.

Question

Unable to start sandbox.

SW Ho 25

Received an error message to prevent sandbox start.

The connection to the Windows Sandbox environment was lost.

An existing connection was forcibly closed by the remote host. (0x80072746)

Artur Kirkoriyan 5 Reputation points

2024-11-27T10:22:19.7366667+00:00

i have installed Hyper-V before, now i install wsl, and don't have any problems, after restart problem persist with windows sandbox.
frps 0 Reputation points

2024-12-19T00:10:05.2966667+00:00

Hi Artur,

Were you able to find a solution for the Windows Sandbox error? I started getting the exact same error, I'm assuming it was caused by the latest MS Updates. I tried disabling the feature, restarting and re-enabling but that didn't help. Wondering if you found a working solution?

Thank you
Nahshon Wiltshire 0 Reputation points

2024-12-21T23:44:52.08+00:00

Hey guys,

I had the same issue, I don't want to say that it is random but I was able to get the sandbox working again by simply running as admin. I tried looking through my Sysmon logs, stopped and restarted some type of Hyper-V service but to no avail.

You can try running as admin and see if that helps, if not you could provide your logs and we can compare to determine, which processes and services fail to start.

OS: Windows 11 Pro 24H2

Build: 26100.2605
marsavul 75 Reputation points

2025-02-19T09:08:15.2233333+00:00

Fixed the issue by disabling vGPU from Group Policy.

Open gpedit.msc, go to "Computer Configuration > Administrative Templates > Windows Components > Windows Sandbox"

and Disable:

"Allow vGPU sharing for Windows Sandbox"
Yasser Saeed 0 Reputation points

2025-04-02T18:37:25.98+00:00

For almost 2 yeasr, Sandbox was working perfectly fine until about 10 days ago, it rarly works and most of the time it dose not work.

Sometime the error is:

The connection to the Windows Sandbox environment was lost.

Expecting object to be local

Othertimes the error is:

The connection to the Windows Sandbox environment was lost.

An existing connection was forcibly closed by the remote host. (0x80072746)

Any idea why this is happening?

2 answers

Your answer

Artur Kirkoriyan 5 Reputation points

2024-11-27T10:22:19.7366667+00:00

i have installed Hyper-V before, now i install wsl, and don't have any problems, after restart problem persist with windows sandbox.
frps 0 Reputation points

2024-12-19T00:10:05.2966667+00:00

Hi Artur,

Were you able to find a solution for the Windows Sandbox error? I started getting the exact same error, I'm assuming it was caused by the latest MS Updates. I tried disabling the feature, restarting and re-enabling but that didn't help. Wondering if you found a working solution?

Thank you
Nahshon Wiltshire 0 Reputation points

2024-12-21T23:44:52.08+00:00

Hey guys,

I had the same issue, I don't want to say that it is random but I was able to get the sandbox working again by simply running as admin. I tried looking through my Sysmon logs, stopped and restarted some type of Hyper-V service but to no avail.

You can try running as admin and see if that helps, if not you could provide your logs and we can compare to determine, which processes and services fail to start.

OS: Windows 11 Pro 24H2

Build: 26100.2605
marsavul 75 Reputation points

2025-02-19T09:08:15.2233333+00:00

Fixed the issue by disabling vGPU from Group Policy.

Open gpedit.msc, go to "Computer Configuration > Administrative Templates > Windows Components > Windows Sandbox"

and Disable:

"Allow vGPU sharing for Windows Sandbox"
Yasser Saeed 0 Reputation points

2025-04-02T18:37:25.98+00:00

For almost 2 yeasr, Sandbox was working perfectly fine until about 10 days ago, it rarly works and most of the time it dose not work.

Sometime the error is:

The connection to the Windows Sandbox environment was lost.

Expecting object to be local

Othertimes the error is:

The connection to the Windows Sandbox environment was lost.

An existing connection was forcibly closed by the remote host. (0x80072746)

Any idea why this is happening?

Answer 1

marsavul 75

Fixed the issue by disabling vGPU sharing for Windows Sandbox from Group Policy.

Open gpedit.msc, go to "Computer Configuration > Administrative Templates > Windows Components > Windows Sandbox"

and Disable:

"Allow vGPU sharing for Windows Sandbox"

OR

Open powershell with administrator rights and enter the following command:

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Sandbox" /v AllowVGPU /t REG_DWORD /d 0 /f

Chagler Hochscheidt 0 Reputation points

2025-02-19T12:09:23.23+00:00

It worked! You solved a big problem for me, I was looking for a solution for a long time.

Thank you very much!
Shood 1 Reputation point

2025-02-26T18:48:36.1066667+00:00

Great! resolved on Windows 11
PIARD Clément 5 Reputation points

2025-02-27T10:39:25.6866667+00:00

Super !
Orest Bala 0 Reputation points

2025-03-20T12:07:40.15+00:00

it worked bro!
Yasser Saeed 0 Reputation points

2025-04-02T18:38:15.6733333+00:00

I tried this but I dont see >Windows Sandbox
MoBe 0 Reputation points

2025-04-03T08:44:00.9133333+00:00

Great, disabling ""Allow vGPU sharing for Windows Sandbox" from group policy

worked for me. At least I can use Windows SandBox. Thank you marsavul
Sadman Sakib 0 Reputation points

2025-04-26T01:34:01.77+00:00

It worked man... After three months of back and forth it worked, Thanks
Cameron Klenk 0 Reputation points

2025-06-18T19:33:13.3433333+00:00

Thank you so much marsavul, that worked for me!!

Answer 2

Anonymous

Hello

Thank you for posting in Q&A forum.

It can be caused by several issues. Here are some steps you can take to troubleshoot:

Ensure that Windows Sandbox and all related features (such as Virtual Machine Platform and Hyper-V) are enabled.
Restart Required Services:

Restart the necessary services for Windows Sandbox. Open the Services application and restart the following services:

Network Virtualization Service

Virtual Disk

Hyper-V Host Compute Service

Container Manager Service

Check your network connectivity.
Check the Event Viewer for any related error logs that might provide more details about why the connection is being closed. Look under Windows Logs > System and Windows Logs > Application.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best Regards,

Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Yegor Isakov 11 Reputation points

2025-02-07T01:59:11.6233333+00:00

Solution is unbelievably simple. The error message could also be like this: "The connection to the Windows Sandbox environment was lost.

Expecting object to be local"

Now you need to think: "Why Expected object is not local? or Why connection was forcibly closed by the remote host? " Because OneDrive is installed on your computer and Sandbox does not like its environment in clouds.

UNINSTALL ONEDRIVE from your computer and your Sandbox will come BACK. That's it, Voilà........
Yasser Saeed 0 Reputation points

2025-04-02T18:39:19.0333333+00:00

I followed your suggestion but did not help!

Share via

Unable to start sandbox.

2 answers

Your answer