Question Problem with sandbox

[acyclovir]

Hey everyone,

I’m seeing a weird one: when I open a link from eM Client into Windows Sandbox, the Sandbox spins up and Edge launches… but all I get is a permanent white square. The link never loads. eM Client also throws a permissions warning on the first try.

If I start the Sandbox with a .wsb that disables the virtual GPU, Edge works like normal. This tiny config does the trick:

• Is there a way to make Sandbox always start with vGPU disabled (some “default profile” or policy) so I don’t have to run a .wsb every time?
• Is there a proper fix that lets me keep vGPU enabled and avoid the white-square bug in Edge?
• Bonus: what’s the cleanest way to pass a URL into Sandbox so Edge opens it automatically when launching via a .wsb?

Thanks! If you’ve hit this before, I’d love to hear what worked for you.

 

[Bot]

Hey everyone,

I’m seeing a weird one: when I open a link from eM Client into Windows Sandbox, the Sandbox spins up and Edge launches… but all I get is a permanent white square. The link never loads. eM Client also throws a permissions warning on the first try.

If I start the Sandbox with a .wsb that disables the virtual GPU, Edge works like normal. This tiny config does the trick:

• Is there a way to make Sandbox always start with vGPU disabled (some “default profile” or policy) so I don’t have to run a .wsb every time?
• Is there a proper fix that lets me keep vGPU enabled and avoid the white-square bug in Edge?
• Bonus: what’s the cleanest way to pass a URL into Sandbox so Edge opens it automatically when launching via a .wsb?

Thanks! If you’ve hit this before, I’d love to hear what worked for you.

View attachment 292739

Hey acyclovir,

Sounds like a quirky issue with Windows Sandbox and Edge—I've seen similar reports pop up in forums, often tied to how the virtual GPU (vGPU) handles rendering in isolated environments. The permissions warning from eM Client is probably just it trying to hand off the link to the sandboxed browser, but the white square in Edge screams graphics-related glitch. Let's break this down based on what I know from tinkering with Sandbox configs. I'll keep it factual—no wild guesses here.

1. Making Sandbox always start with vGPU disabled: Unfortunately, there's no built-in "default profile" or global policy in Windows to force vGPU off every time without a config file. Sandbox launches with defaults unless you specify otherwise via a .wsb file. The cleanest workaround is to create a simple .wsb (like the one you mentioned) and set up a shortcut or script to launch it easily. For example, save this as DefaultSandbox.wsb:
   
   

   <Configuration>
     <VGpu>Disable</VGpu>
   </Configuration>

   
   Then, pin a shortcut to it on your taskbar or desktop. If you're comfy with scripting, you could use PowerShell or a batch file to automate launching it. No registry hacks or group policies directly control this that I'm aware of—Microsoft keeps Sandbox pretty locked down to prevent misuse.
   
2. Proper fix with vGPU enabled: This white-square bug in Edge inside Sandbox often stems from vGPU incompatibilities, especially if your host GPU drivers are outdated or if there's a mismatch with Hyper-V settings. First, ensure your Windows is fully updated (including optional updates for graphics), and check for Edge updates too. Some folks have fixed similar rendering issues by:
   • Disabling hardware acceleration in Edge (inside Sandbox): Launch Edge, go to edge://settings/system, and toggle off "Use hardware acceleration when available." Restart Edge.
   • Tweaking host GPU drivers: If you're on NVIDIA/AMD/Intel, grab the latest from their sites, not just Windows Update.
   • Running Sandbox with admin privileges or checking Hyper-V logs for errors (Event Viewer under Applications and Services Logs > Microsoft > Windows > Hyper-V).
   If that doesn't cut it, it might be a deeper bug—worth reporting via Feedback Hub if you're on Windows 11. I've not seen a universal fix that keeps vGPU on without side effects, but testing the above is a safe start.
   
3. Passing a URL into Sandbox automatically: Yep, you can do this via the .wsb file by adding a startup command. Modify your config like so (replace
   Example Domain
   with your URL):
   
   

   <Configuration>
     <VGpu>Disable</VGpu>  <!-- Or leave enabled if testing the fix -->
     <LogonCommand>
       <Command>start msedge.exe https://example.com</Command>
     </LogonCommand>
   </Configuration>

   
   When you launch this .wsb, Sandbox spins up and auto-opens Edge to that URL. If you're scripting this from eM Client or elsewhere, you could pass the URL dynamically via a PowerShell script that generates the .wsb on the fly—something like:
   
   

   param([string]$url)
   $wsbContent = @"
   <Configuration>
     <VGpu>Disable</VGpu>
     <LogonCommand>
       <Command>start msedge.exe $url</Command>
     </LogonCommand>
   </Configuration>
   "@
   $wsbContent | Out-File -FilePath "TempSandbox.wsb" -Encoding UTF8
   Start-Process "TempSandbox.wsb"

   
   Save that as a .ps1 and call it with the URL as an argument. Keeps things clean without manual edits each time.

If none of this clicks or you're hitting hardware-specific snags (like with certain GPUs), drop more details on your setup—Windows version, GPU, etc.—and I'll see if I can dig deeper. Anyone else run into this Edge whiteout in Sandbox?

Cheers!

 

[stonjean633]

Hey everyone,

I’m seeing a weird one: when I open a link from eM Client into Windows Sandbox, the Sandbox spins up and Edge launches… but all I get is a permanent white square. The link never loads. eM Client also throws a permissions warning on the first try.

If I start the Sandbox with a .wsb that disables the virtual GPU, Edge works like normal. This tiny config does the trick:

• Is there a way to make Sandbox always start with vGPU disabled (some “default profile” or policy) so I don’t have to run a .wsb every time?
• Is there a proper fix that lets me keep vGPU enabled and avoid the white-square bug in Edge?
• Bonus: what’s the cleanest way to pass a URL into Sandbox so Edge opens it automatically when launching via a .wsb?

Thanks! If you’ve hit this before, I’d love to hear what worked for you.

View attachment 292739

Kindly translate the Cyberlock message so peeps here can assist you further.

 

[danb]

Thank you for letting me know! Yeah, we could include this in the config: <VGpu>Disable</VGpu>, but I am not sure if that would be wise to do. This is the first report of something not working with the current config, and it might not be a good idea to make changes if it is working properly for everything else.

 

[cartaphilus]

Hey everyone,

I’m seeing a weird one: when I open a link from eM Client into Windows Sandbox, the Sandbox spins up and Edge launches… but all I get is a permanent white square. The link never loads. eM Client also throws a permissions warning on the first try.

If I start the Sandbox with a .wsb that disables the virtual GPU, Edge works like normal. This tiny config does the trick:

• Is there a way to make Sandbox always start with vGPU disabled (some “default profile” or policy) so I don’t have to run a .wsb every time?
• Is there a proper fix that lets me keep vGPU enabled and avoid the white-square bug in Edge?
• Bonus: what’s the cleanest way to pass a URL into Sandbox so Edge opens it automatically when launching via a .wsb?

Thanks! If you’ve hit this before, I’d love to hear what worked for you.

View attachment 292739

Given your username, maybe it's genital herpes?

 

[acyclovir]

Kindly translate the Cyberlock message so peeps here can assist you further.

Unable to open the webpage CyberLock - Automated and Effortless Zero-Trust Endpoint Protection. Please check your system settings

Thank you for letting me know! Yeah, we could include this in the config: <VGpu>Disable</VGpu>, but I am not sure if that would be wise to do. This is the first report of something not working with the current config, and it might not be a good idea to make changes if it is working properly for everything else.

Sandbox fails to open Edge