By https://www.facebook.com/mildlydisturbed
Publication Date: 2026-05-15 18:07:00
Today’s been my day of Microsoft directed hate. Most of it being at something else but I needed Sandbox today and was getting errors that I’d been disconnected from viewing it.
This was odd. I thought for a minute it might have been some Docker issue with virtualization but I jumped through some hoops and discovered it was running, it just was not accessible.
A series of troubleshooting land two competing AIs lead me to that it was having a problem deciding on whether to use the onboard GPU or the new (to it,) GPU I added when doing a remote desktop into the thing.
I use both GPUs as a note when I’m encoding video in Premiere… don’t harsh – ever little bit helps.
Disabling the onboard got me right into the app and I was able to view the scam of the morning in an isolated sandbox.
Supposedly putting two files in your desktop graphics settings and assigning them to a GPU will also work, which I did *after* I was in and running the thing having disabled the onboard.
The two apps to add under system, display, graphics are your hyper-v host compute service at c:\windows\System32\vmcompute.exe and the Windows Sandbox Client at c:\windows\system32\WindowsSandboxClient.exe
It’ll be a reboot before I determine if doing that worked, but I can disable a GPU for a hot second when required if need be.
