Microsoft has released an Insider Preview Build that includes the new Windows Sandbox feature. If you are in the fast lane, you can download and use it today.
What is Sandbox?
In short, Windows Sandbox is half an app, half a virtual machine. It lets you quickly create a virtual, clean operating system that reflects the current state of your system so that you can test programs or files in a secure environment that is isolated from your main system. Closing the sandbox will destroy this state. Nothing can get from the sandbox to your main Windows installation, and there's nothing left after closing.
RELATED: Windows 1
How do I get it? 19659003] For now, you can only use Sandbox by joining the Windows Insider program and putting your PC on the fast track for updates. You should not do this on your main PC. The fast lane may be unstable and may lead to data loss, crashes or other nasty surprises. Because Microsoft has difficulty publishing stable versions of Windows outside of testing, you should leave the insider builds on a nonproductive PC.
After you install Insider Build 18305 (or later), installing and starting Sandbox is a simple process.
Step 1: Make sure virtualization is turned on
First, make sure virtualization is enabled in your system's BIOS. This is usually standard, but there is an easy way to verify this. Start Task Manager by pressing Ctrl + Shift + Esc and then go to the Performance tab. Make sure that the "CPU" category is selected on the left and right. Make sure "Virtualization: Enabled" is displayed.
If virtualization is not enabled, you must enable it in the BIOS settings of your PC before proceeding.
Step 2: Enable nested virtualization when you run the host system in a virtual machine (optional)
If you test the insider build from Windows in a If you are already testing a virtual machine and sandboxing in To test this VM, you must enable nested virtualization.
To do this, start PowerShell in the Windows version that is running in the VM, and then issue a problem from the following command:
-ExposeVirtualizationExtensions $ true
This causes Your guest version of Windows in the VM can expose the virtualization extensions so Sandbox can use them.
Step 3: Enable the Windows Sandbox feature
After the mak To enable virtualization is enabled, enabling the Windows Sandbox feature is a breeze.
Go to Control Panel> Programs> Turn Windows Features On or Off. (By the way, we have a detailed description of how to use these Windows features if you want to learn more.)
In the Windows window, enable the "Windows Sandbox" option.
Click "OK," and then restart Windows.
Third Step: Fire It Up
After restarting Windows, you will find the Windows Sandbox in the Start menu. Either enter "Windows Sandbox" in the search bar, or dig through the menu, and then double-click the icon. When prompted, allow him / her administrator rights.
You should see a close copy of your current operating system.
There are some differences. It is a clean Windows installation. So you see the default wallpaper and nothing but the standard apps that come with Windows.
The virtual operating system is dynamically generated by your Windows operating system so it will always be displayed Run the same version of Windows 10 that you are using, and it's always up-to-date. The latter The fact is that a traditional VM takes the time to update the operating system itself.
How do I use it?
If you've ever used a VM, the sandbox is used to make me feel old-fashioned. You can copy and paste files directly into the sandbox just like any other VM. Drag & Drop does not work. Once the file is in the sandbox, you can proceed as usual. If you have an executable file, you can install it in the sandbox where it will be dropped from your main system.
One thing to keep in mind: If you delete a file in the sandbox, it will not delete the trash. Instead, it is permanently deleted. You receive a warning when deleting items.
When you're done testing, you can close the sandbox just like any other app. This will completely erase the snapshot, including any changes you have made to the operating system and any files you have copied there. Microsoft was kind enough to give a warning first.
The next time you start Sandbox, you'll find a clean thing again, and you can start testing again.
Impressive, Sandbox runs well on minimal hardware. We ran the test for this article on a Surface Pro 3, an obsolete device without a dedicated graphics card. Initially, the sandbox was noticeably slow, but after a few minutes it ran surprisingly well given the restrictions.
This better speed was also maintained when closing and reopening the app. Running a virtual machine has traditionally required more power. Due to the narrower use cases with Sandbox (you do not need to install multiple operating systems, run multiple instances or even create multiple snapshots), the bar is slightly lower. But that's exactly what the Sandbox does so well.
Credit: D-Krab / Shutterstock.com