Microsoft has launched an Insider Preview Build which adds the features of the new Windows Sandbox. In simple terms, Windows Sandbox is half app and half virtually operated machine. It permits you to swiftly spin up a virtual clean OS taken from your system’s present state so that you can check the programs or contents in a secure and secluded environment that is isolated from your main system. Once you close the sandbox, it damages that state.
Presently, the sole method to employ Sandbox is to join the “Windows Insider Program” and keep your computer on the fast track for updates. You shouldn’t take this on your main computer because the fasttrack is currently unstable and may lead to data crashes, data loss or else. Since Microsoft has troubleshooting stable version of Windows outside of testing, you should put the Insider builds to a non-production computer, not the main computer.
When you install the “Insider build 18305” (or higher) then starting Sandbox is a simple procedure with the following steps:
1. Ensure the Virtualization is enabled
You require ensuring the enabled virtualization in BIOS of your system. You can check it with an easy way as given below:
• Tap “Ctrl+Shift+Esc” to fire up “Task Manager”.
• Head over to the “Performance” tab.
• Ensure “CPU” category is chosen on the left and the right and confirm the “Virtualization: Enabled”.
If the virtualization is not enabled, then you require enabling it in BIOS settings of your computer.
2. Turn on Nested Virtualization (Optional)
If you are checking out the Host system “Insider build” of the Windows in a virtual machine, and you desire to test Sandbox in that virtual machine then you will require taking the additional step of turning on nested virtualization. For doing this, fire up “PowerShell” in the version of Windows functioning inside the virtual machine and then insert the following command:
Set-VMProcessor -VMName<VMName> -ExposeVirtualizationExtensions $true
That permits your guest version of Windows in the virtual machine to expose the virtualization extensions so that Sandbox can employ them.
3. Enable the feature of Windows Sandbox
After ensuring the enabled virtualization, switching on the Windows Sandbox feature is the snap.
For doing this, follow the below steps:
• Navigate “Control Panel” after that then visit “Program” then go to”Turn Windows Features Off or On”.
• Enable the “Windows Sandbox” checkbox within the window of “Windows Features”.
• Press “OK” and then Windows will be restarted.
4. Fire it Up
Once Window restarts, you can search Windows Sandbox on the “Start Menu”. You may also insert “Windows Sandbox” into the search bar or find through the menu and then double-press on the Icon. When it inquires, allow it to have administrative privileges. Now, you should look at the replica of your present OS. There are some differences also. It is a clean Windows installation, that’s why you will look at the default wallpaper on screen and nothing much, but the default apps will be there to come up with Windows. The virtual OS is dynamically created from your main Windows OS, so it will always use the same version of Windows 10 that you are running and it will always be updated.
If you have ever employed a virtual machine before, then employing the Sandbox will feel you like an old hat. You can copy-paste contents directly into the Sandbox. Drop and drag doesn’t function here. When the file is in the Sandbox, then you may proceed it as usual. If you do have executable content, then you can install them in the Sandbox which nicely cordons off your main system. It is noted here that if you delete or remove a file in the Sandbox, then it doesn’t dump in the recycle bin instead, it is removed permanently. That’s why you will get a warning notice while deleting items.
Joey Williamsis a Microsoft Office expert and has been working in the technical industry since 2002. As a technical expert, Robert has written technical blogs, manuals, white papers, and reviews for many websites such as office.com/setup.