Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The safest practical starting point is to run an untrusted Windows AI agent in a deliberately configured isolated environment, not in a default VM profile. Use Windows Sandbox for a short-lived task that does not need to retain files or settings. Use a Hyper-V virtual machine when the agent needs persistent state, repeatable tools, or longer-term storage. In either case, begin with networking and clipboard sharing disabled, expose no host folders unless they are essential, and provide only the minimum access the task requires.
Neither option guarantees safety. An agent can misuse any capability you give it, and virtualization does not eliminate every possible attack or escape path. Treat the guest as untrusted software, limit its routes to the host, and destroy or revert it after work that could have changed the environment.
Choose the isolation model before installing the agent
Your first decision is whether the guest should be disposable or persistent. That choice determines which Windows feature is a better fit and how much recovery work you will need if the agent behaves unexpectedly.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors| Concern | Windows Sandbox | Hyper-V virtual machine |
|---|---|---|
| State after shutdown | Software, files, and changes are discarded when the Sandbox window closes. | The virtual disk and installed software remain until you revert, reset, or delete the VM. |
| Typical use | One-off trials, analysis of an unfamiliar installer, or a short task with disposable inputs. | Agents that need installed dependencies, repeated runs, snapshots, or retained project data. |
| Resource profile | Microsoft describes Sandbox as lightweight compared with a full VM. | A full VM generally requires more deliberately assigned memory, storage, and processor capacity. |
| Network control | Networking is enabled by default but can be disabled in a .wsb configuration file. | You choose whether the virtual network adapter is connected and which virtual switch it uses. |
| Host-data paths | Clipboard sharing is enabled by default; host folders can be mapped with read or write access. | Clipboard, drive sharing, enhanced sessions, and other integration features must be reviewed individually. |
| Edition and compatibility | Available only on supported Windows editions, including Windows Pro; Windows Home is not supported. | Requires a Windows edition and hardware configuration that support the Hyper-V role, plus a guest operating system licensed and compatible with the agent. |
These are isolation features, not an agent safety certification. The right setup depends on whether the agent needs internet access, local files, credentials, clipboard content, peripherals, or persistence.
#1 Best Overall
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
Check prerequisites and the agent’s required access
Verify the Windows edition
Before following Sandbox instructions, open Settings > System > About and read the Windows specifications section. Windows Pro is among the editions that support Windows Sandbox; Windows Home is not. If Sandbox is absent from the optional-features list, confirm the edition rather than assuming the feature is broken.
Confirm hardware virtualization
Sandbox and Hyper-V use hardware-assisted virtualization. In Task Manager > Performance > CPU, check that Virtualization is enabled. If it is disabled, enable Intel VT-x or AMD-V (the exact wording depends on the firmware) in UEFI/BIOS, then restart. Corporate policies, another hypervisor, or firmware settings can still prevent a VM from starting.
Write an access inventory
Make a short list before creating the guest:
- Network: Does the agent need to reach a website, an API, package repositories, or a local service? If not, plan to disconnect it.
- Files: Which input files are essential, and can they be copied into a one-way staging folder instead of exposing a drive?
- Clipboard: Does the task genuinely require copying text or images between host and guest?
- Credentials: Can the agent run with a test account and temporary tokens rather than your Windows sign-in, browser profile, SSH keys, or cloud credentials?
- Peripherals: Does it need a camera, microphone, USB device, smart card, or printer? Avoid passing through hardware unless the task cannot work without it.
- Persistence: Which outputs must survive, and can they be exported as a small set of files instead of keeping the entire guest?
Every item on this list is a potential route from the agent to something you care about. Remove routes that are not required.
Configure Windows Sandbox for disposable work
Sandbox is useful when you want a clean Windows environment and are willing to lose everything in it at the end. Closing the Sandbox window removes its installed software, files, and state. Do not use it as the only copy of work you need to keep.
Enable the feature
- Open Turn Windows features on or off from the Start menu.
- Select Windows Sandbox, choose OK, and restart if Windows requests it.
- Launch Windows Sandbox from Start and wait for the isolated desktop to appear.
If the feature is not listed, recheck the Windows edition and virtualization status. A managed computer may also have the feature blocked by policy.
Start with networking disabled
Windows Sandbox networking is enabled by default. Microsoft warns that enabling networking can expose untrusted applications to the internal network. For an agent that does not need online access, disable it in the Sandbox configuration file rather than relying on the default.
Create a text file with a .wsb extension, for example agent-offline.wsb, containing:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
<Configuration>
<Networking>Disable</Networking>
<ClipboardRedirection>Disable</ClipboardRedirection>
</Configuration>Double-click the file to start Sandbox with those settings. The configuration applies when the session starts; close that session and launch it again after changing the file.
Rank #2
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
If the agent truly needs the internet, enable networking only for the required run and treat the guest as connected to an untrusted network. Prefer an account with no access to internal services, and do not assume that a web allow-list prevents every malicious connection.
Disable clipboard redirection
Clipboard redirection is enabled by default. With it enabled, text, images, copied credentials, and other clipboard content can cross between the host and guest. Set <ClipboardRedirection>Disable</ClipboardRedirection> unless the task specifically needs clipboard transfer.
If you must use the clipboard, keep the host clipboard empty of passwords, recovery codes, private keys, and confidential documents while the agent is running. Copy only the specific value needed, paste it, and clear the clipboard afterward.
Avoid mapped folders, or make them read-only
Sandbox can map a host directory into the guest. Microsoft cautions that exposing host directories may allow malicious software to affect the system or steal data. The safest choice is to map nothing. Instead, download or create a disposable input inside Sandbox when that is practical.
When a mapping is unavoidable, create a dedicated staging directory containing only the files required for this run. Map it read-only:
<Configuration>
<Networking>Disable</Networking>
<ClipboardRedirection>Disable</ClipboardRedirection>
<MappedFolders>
<MappedFolder>
<HostFolder>C:SandboxInput</HostFolder>
<SandboxFolder>C:Input</SandboxFolder>
<ReadOnly>true</ReadOnly>
</MappedFolder>
</MappedFolders>
</Configuration>Do not map your user profile, Desktop, Documents, Downloads, browser data, password stores, or an entire drive. A writable mapping gives the guest a direct place to modify or delete host files, so use write access only for a narrowly scoped exchange folder and remove it afterward.
Understand the memory setting
A Sandbox configuration can request a memory value. Microsoft documents 2,048 MB as the required minimum and says an insufficient value is automatically increased to that minimum. This is a product configuration behavior, not a performance or safety benchmark. Give the guest enough memory for the agent and its dependencies, but leave sufficient memory for the host to remain responsive.
End the session deliberately
Export the few outputs you need to a scanned, dedicated destination, then close the Sandbox window. Closing it discards the guest’s software, files, and state. If you need to repeat the task, start a new session from the same configuration file rather than trusting that the previous environment was clean.
Rank #3
- WINDOWS 11 PRO FOR WORKSTATIONS is for people with advanced needs such as data scientists, CAD professionals, researchers, media production teams, graphic designers, and animators.
- WINDOWS 11 PRO FOR WORKSTATIONS helps power through advanced workloads while providing server-grade data protection and performance, and includes all the features of Windows 11 Pro | Users will benefit from greater speed with faster processing and file transfers, greater resilience with server-grade storage, and the full power of high-performance hardware configurations.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine | Windows 11 Pro for Workstations is required licensing for systems with Intel Xeon or AMD Opteron processors.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
Build a persistent Hyper-V VM when state is necessary
Hyper-V is the better fit when the agent needs installed packages, a retained workspace, snapshots, or repeated runs. Persistence is also the main risk: an unwanted change remains in the virtual disk until you revert or rebuild it.
Enable Hyper-V and create a separate guest
- Open Turn Windows features on or off, select Hyper-V and its management tools, then restart if prompted. The available role depends on your Windows edition and hardware.
- Open Hyper-V Manager and choose New > Virtual Machine.
- Store the virtual machine configuration and virtual disk in a dedicated location with access permissions limited to administrators and the virtualization service.
- Assign only the memory, processor count, and disk capacity the agent needs. Avoid oversizing the guest, which can starve the host and other security tools.
- Install a supported Windows guest from media you obtained through a legitimate channel, apply updates, and create a separate local or organizational account for the agent.
- Install the agent and its dependencies only after deciding which integration features will be enabled.
Microsoft recommends securing the Hyper-V host, virtual machines, configuration files, and VM data. Protect the host first: keep Windows and firmware updated, use a strong administrator account, restrict physical and remote access, and back up VM files according to their sensitivity.
Choose the virtual switch carefully
A Hyper-V virtual network adapter can connect to an external, internal, or private virtual switch. An external switch gives the guest access to the physical network and possibly the internet. An internal switch permits communication between the host and guests. A private switch limits communication to guests on that switch. Select the least connected option that still supports the task.
Free tools Windows power users keep installed
One-click scans. No signup required.
For an offline agent, disconnect the network adapter in the VM settings or use a private switch with no route to the host’s production network. For an online agent, use a separate network segment or guest account with no privileged access to internal services. Network isolation reduces exposure; it does not make downloaded code trustworthy.
Limit integration features
Review every feature that makes the host visible to the guest. Depending on your Hyper-V version and connection method, that can include enhanced-session clipboard and drive sharing, removable-device access, audio, printers, and device redirection. Turn off anything the agent does not need. Do not connect the guest to your host’s browser profile, password manager, SSH agent, or personal cloud-synchronization folder.
Use checkpoints as recovery points, not as a security guarantee
Before installing a new tool or running an unfamiliar workflow, create a checkpoint or make a tested copy of the virtual disk. If the run changes the guest, shut it down and revert through Hyper-V Manager, or rebuild from a known-good image. A checkpoint does not undo actions already taken against an external network, a mapped host folder, or a copied credential.
Keep important output outside the guest only after scanning and reviewing it. If you need a persistent data directory, separate it from the operating-system disk and back it up independently. When the project ends, delete unused snapshots and securely retire the VM and its stored credentials.
Set permissions according to the agent’s actual job
For an offline document or code task
Use Sandbox with networking and clipboard disabled, no mapped folders, and a disposable input copy. If you need to provide files, map a read-only staging folder or copy them into the guest through a controlled process. Export results only after checking file types, scripts, and links.
Rank #4
- Windows 11Pro for Workstations
For a web research or API task
Use a guest with networking enabled only when necessary. Do not sign in with your personal browser session. Supply a narrowly scoped test account or token, set expiration where the service permits it, and revoke the credential after the run. Consider a Hyper-V VM if the agent needs its browser profile or installed extensions across sessions, but keep that profile separate from your everyday identity.
For a coding agent that installs tools
A persistent Hyper-V VM can avoid reinstalling dependencies, but treat the virtual disk as a development machine with untrusted code. Use a non-administrator account for routine work, restrict network access to required repositories, and snapshot before installing a new toolchain. Keep source code in a dedicated project directory rather than mapping your entire development drive.
For tasks involving secrets or regulated data
Do not place production credentials, private keys, customer records, or regulated data in a guest merely because it is virtualized. If the task can be redesigned to use synthetic data, do that. If real secrets are unavoidable, use the smallest scope and lifetime possible, record where they were exposed, and rotate them after the task.
Understand what each boundary does not stop
- Virtualization is not a guarantee against escape. A vulnerability in the host, hypervisor, guest additions, or a device integration could undermine isolation.
- Network denial is not data sanitization. An offline guest can still damage files that you map, and files exported from it can carry malicious content.
- Read-only mappings are one-way for writes, not a confidentiality barrier. The agent can read every file in the mapped directory, so the directory must contain only non-sensitive inputs.
- Reverting a VM does not revoke external access. It cannot undo an email sent, an API request made, or a credential copied to a remote service.
- Snapshots are not backups by themselves. A failed disk, host compromise, or accidental deletion can remove both the running VM and its checkpoints.
- Default settings are not a locked-down profile. Sandbox starts with networking and clipboard sharing enabled unless you explicitly change them.
A repeatable safe-run procedure
- Define the agent’s required network, files, clipboard, credentials, peripherals, and persistence.
- Select Sandbox for a disposable run or Hyper-V for a persistent, recoverable workspace.
- Patch the host and guest, verify hardware virtualization, and use a non-privileged agent account.
- Disable networking and clipboard sharing first. Add only the individual capability the task requires.
- Use no host-folder mapping where possible. If required, expose a dedicated folder and make it read-only.
- Remove personal credentials and browser profiles. Use temporary, least-privilege credentials for online work.
- Create a clean checkpoint or image before a persistent run.
- Observe network connections, file changes, and prompts during execution. Stop the guest if it requests unexplained access.
- Review and scan outputs before copying them to the host or opening them with trusted applications.
- Close Sandbox to discard it, or shut down and revert, rebuild, archive, or delete the Hyper-V VM according to your retention plan.
- Rotate any credential that entered the guest and remove temporary staging folders and exported files.
Troubleshoot common setup failures
Windows Sandbox will not start
Check the Windows edition, confirm virtualization is enabled in firmware and Task Manager, install pending Windows updates, and verify that another virtualization product or organizational policy is not blocking the feature. Reboot after enabling the optional feature.
The agent cannot reach the internet
Read the .wsb file and confirm that networking was not deliberately disabled. If networking is required, start a separate session with networking enabled and test DNS and HTTPS from inside the guest. Do not solve the problem by mapping host folders or enabling clipboard sharing.
Files are missing inside the guest
Confirm the mapped host path exists and that the Sandbox folder path is correct. Check whether the mapping is read-only and whether the agent is looking in the expected directory. Copy only the required files; do not broaden the mapping to an entire drive.
A Hyper-V VM is slow or unstable
Reduce competing host workloads, check available memory and disk space, and assign resources appropriate to the agent rather than maximum values. A resource shortage is not a reason to grant administrator access or reconnect sensitive host devices.
Recommended Free Tools
Bottom line
Use Windows Sandbox for short, disposable experiments and start it with networking and clipboard redirection disabled, no mapped folders, and only narrowly scoped exceptions. Use Hyper-V when persistence is necessary, but protect the host and VM files, choose the least-connected virtual switch, disable unnecessary integration features, and maintain a deliberate checkpoint or rebuild process. The security outcome comes from the permissions and routes you choose—not from the word “virtual machine” alone.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
