Fix Windows Sandbox No Internet Connection

If Windows Sandbox has no internet connection, the fix is usually to enable the network adapter in the sandbox configuration file or to correct the host machine’s virtual switch settings. This article walks you through the exact steps to restore network access, explains why the issue happens, and covers related troubleshooting for Windows 10 and Windows 11.

Why Windows Sandbox Loses Internet

Windows Sandbox runs a lightweight, isolated desktop environment using Hyper-V virtualization. By default, it shares the host’s network connection through a virtual switch. However, several things can break this connection:

• The sandbox configuration file (.wsb) has networking disabled.
• The Hyper-V Virtual Switch or the host’s network adapter drivers are outdated or misconfigured.
• Windows Firewall or third-party security software blocks the virtual adapter.
• The host’s VPN or proxy software interferes with the virtual network.
• Windows Sandbox service or Hyper-V components are partially disabled.

Understanding these causes helps you apply the right fix without unnecessary restarts.

Fix 1: Enable Networking in the Sandbox Configuration

Windows Sandbox uses a plain-text configuration file to control features like networking, clipboard, and GPU. If you launched the sandbox with a .wsb file that had <Networking>Disabled</Networking>, you’ll have no internet. Here’s how to fix it:

1. Create a new text file and rename it to sandbox.wsb (or edit the existing one).
2. Open it with Notepad and paste the following:

<Configuration>
  <Networking>Enabled</Networking>
</Configuration>

3. Save the file and double-click it to launch Windows Sandbox with networking enabled.

If you normally launch Windows Sandbox from the Start menu (without a config file), networking is enabled by default, so this fix only applies if you’re using a custom configuration.

Fix 2: Reset the Hyper-V Virtual Switch

The virtual switch that connects the sandbox to your network can get stuck after a Windows update or a driver change. Resetting it often restores connectivity:

1. Open PowerShell as Administrator.
2. Run Get-VMSwitch to list virtual switches. Note the name of the default switch (usually “Default Switch” or “WSL”).
3. Run Disable-NetAdapter -Name "vEthernet (Default Switch)" -Confirm:$false to disable the host-side virtual adapter.
4. Run Enable-NetAdapter -Name "vEthernet (Default Switch)" to re-enable it.
5. Restart the sandbox.

If the adapter doesn’t appear, check that Hyper-V is fully enabled (see Fix 4).

Fix 3: Check Windows Firewall and Security Software

Windows Firewall can block the virtual adapter if the network profile is set to “Public” or if a rule restricts Hyper-V traffic. To allow it:

1. Open Windows Security → Firewall & network protection.
2. Click “Allow an app through firewall”.
3. Ensure “Windows Sandbox” is checked for both Private and Public networks. If it’s not listed, click “Change settings” then “Allow another app” and browse to C:\Windows\System32\WindowsSandbox.exe.
4. If you use third-party antivirus, temporarily disable its firewall to test. If that restores internet, add an exception for Windows Sandbox and the Hyper-V virtual switch.

Fix 4: Verify Hyper-V and Windows Sandbox Features Are Enabled

Windows Sandbox requires the Hyper-V platform and the Windows Sandbox feature itself. If either is disabled, networking may fail or the sandbox won’t start at all.

1. Open “Turn Windows features on or off” (search for it in the Start menu).
2. Ensure these are all checked:
   • Hyper-V (including Hyper-V Management Tools and Hyper-V Platform)
   • Virtual Machine Platform
   • Windows Hypervisor Platform
   • Windows Sandbox
3. Click OK and restart if prompted.

After a restart, try launching the sandbox again. If the features were already enabled, proceed to the next fix.

Fix 5: Update Network Drivers and Windows

Outdated or corrupted network drivers are a common cause of virtual networking failures. Update them via Device Manager:

1. Press Win + X and select Device Manager.
2. Expand “Network adapters”.
3. Right-click your physical Wi-Fi or Ethernet adapter and choose “Update driver”.
4. Select “Search automatically for drivers”.

Also check Windows Update for optional driver updates. If the problem started after a Windows update, consider rolling back the update (Settings → Windows Update → Update history → Uninstall updates) and see if that restores connectivity.

Fix 6: Reset Windows Sandbox and Hyper-V Services

Sometimes the underlying services need a restart. Open PowerShell as Administrator and run:

Restart-Service vmms
Restart-Service hns

Then restart the sandbox. If that doesn’t help, you can reset the entire Windows Sandbox by deleting its state files:

1. Close Windows Sandbox.
2. In File Explorer, go to %ProgramData%\Microsoft\Windows\Hyper-V and delete the “Sandbox” folder (if present).
3. Restart the sandbox. This resets the virtual machine’s state, not your host files.

Common Misconceptions

One common misconception is that Windows Sandbox uses the same network stack as a regular virtual machine. In reality, it uses a lightweight “default switch” that is managed by the Host Network Service (HNS). This means that VPN software on the host often breaks the sandbox’s internet because the VPN adapter doesn’t expose the same network to the virtual switch. If you use a VPN, try disconnecting it temporarily to test. Another misconception is that the sandbox can’t have internet at all by design—it can, and it does by default unless you disabled it.

When to Use a Virtual Machine Instead

If you need persistent networking settings, or you want to configure static IPs, port forwarding, or multiple network adapters, Windows Sandbox is too limited. In those cases, use a full Hyper-V virtual machine or VirtualBox. Sandbox is meant for quick, disposable tests—not for running network-dependent services.

Frequently Asked Questions

Why does my Windows Sandbox have no internet after a Windows update?

Windows updates can reset Hyper-V settings or replace network drivers. Re-applying the fixes above, especially resetting the virtual switch and updating drivers, usually resolves it.

Can I use a proxy or VPN inside Windows Sandbox?

Yes, but the proxy or VPN must be configured inside the sandbox itself. The host’s VPN doesn’t automatically extend to the sandbox because the default switch uses NAT. You can configure a proxy in the sandbox’s Windows settings if your network requires one.

Does Windows Sandbox support Wi-Fi directly?

No, the sandbox uses a virtual Ethernet adapter that connects through the host’s network stack. It doesn’t see your physical Wi-Fi adapter directly, but it can access the internet if the host’s connection works.

Is it safe to disable Windows Firewall to fix the sandbox?

No, disabling the firewall entirely is not recommended. Instead, add a specific rule for Windows Sandbox or the Hyper-V virtual switch as described in Fix 3. That maintains security while allowing the sandbox to connect.

Why does my sandbox work but with slow internet?

Slow performance can be due to the host’s network congestion, antivirus scanning, or the default switch’s NAT overhead. Try closing bandwidth-heavy applications on the host and ensure your physical adapter is running at full speed.

Related

• Selecting CSS Pseudo-Elements with Selenium
• Myspace vs Twitter: Key Differences Explained
• ERR_NETWORK_CHANGED: How to Fix Chrome Error