Windows Sandbox is one of the easiest ways to test files, scripts, applications, and troubleshooting steps in a clean, temporary Windows environment. But sometimes Sandbox starts without working internet access. In many cases, the problem is not the Sandbox feature itself—it is DNS resolution.
If Windows Sandbox can reach the network but cannot resolve website names, setting a known DNS server manually can bring connectivity back quickly. This guide shows three practical ways to do it: with Command Prompt, through Control Panel, and by using a reusable Windows Sandbox configuration file.
Why DNS can break Windows Sandbox networking
Windows Sandbox launches as an isolated, disposable Windows environment. Networking is normally enabled by default, but name resolution can still fail depending on the host network, VPN configuration, DNS forwarding, or local network policies. When DNS is the issue, the Sandbox may appear offline even though the underlying network connection is available.
The quick fix is to configure the Sandbox network adapter to use a DNS server directly. In the examples below, the DNS server is set to 8.8.8.8, but you can replace it with your preferred public DNS server or an internal corporate DNS server if that is required in your environment.
If you wan to take a look at my video recording instead of reading the you can find it here:
