Windows Sandbox setting in Windows 10 May Update (1903)

Windows Sandbox is a complete one new feature Available exclusively for Windows 10 May Update or 1903.

The purpose of the new feature is to allow users to run applications in a secure environment, as it plays the role of a virtual machine.

So you can run separate even dangerous files which will not be able to affect your valuable data stored in the main system.

"At Microsoft we regularly encounter these situations, which is why we created Windows Sandbox: an isolated, temporary interface where you can run unreliable software without fear of infecting your computer.

Any software installed on Windows Sandbox remains in the sandbox only and cannot affect your server. "Once the Windows Sandbox is closed, all software with all the files are permanently deleted," says Microsoft.

But if you have already tried running Windows Sandbox, you will notice that there are no settings available for this feature. All you can do is start and close the Sandbox.

Of course it should be noted that the method described below is not necessarily the simplest, but you can change various Windows Sandbox settings using a configuration file that you can create manually.

The configuration file uses the .WSB format and after editing it you can start Windows Sandbox with the parameters you have set by simply double-clicking on this file.

But let's look at the settings you can have in Windows Sandbox:

Creating a Windows Sandbox configuration file may seem complicated at first, but it's very simple when you know what to do.

First of all, the default template to use is the following:

<configuration>

</configuration>

All settings that we will add should be placed between the above two tags.

Now let's create a virtual GPU, so Windows Sandbox will allow you to enable and disable vGPU. To do this, you must use the following commands:

vGPU enabled: <vgpu>Enable</vgpu>

vGPU disabled: <vgpu>Disable</vgpu>

In other words, the configuration file should look like the following if you want to have the vGPU disabled:

<configuration>

<vgpu>Disable</vgpu>

</configuration>

Easy; Let's move on to networking. The command to enable or disable the network is as follows:

Networking enabled: <networking>Enable</networking>

Networking disabled: <networking>Disable</networking>

This means that you want to turn off networking, your file should look like the following:

<configuration>

<networking>Disable</networking>

</configuration>

For mapped folders, the command will be as follows:

<mappedfolder>

    <hostfolder>path to folder</hostfolder>

    <readonly>value</readonly>

</mappedfolder>

And to run a command at startup (after loading Windows Sandbox), you must use the following command:

<logoncommand>

   <command />    

</logoncommand>

You can now combine all of the above to create more complex configuration files that allow you to customize your Windows Sandbox to suit your needs.

For example, if you want to turn off vGPU and networking and run any file at startup (we'll try Windows Calculator below), the configuration file should look like this:

<configuration>

<vgpu>Disable</vgpu>

<networking>Disable</networking>

<logoncommand>

   <command />tracing.exe

</logoncommand>

</configuration>

It may seem like a very simple file, but it will allow you to customize your Windows Sandbox exactly as you need it. Now if you are an experienced user you can do much more.

For example, with more advanced commands you can instruct Sandbox to download and run various scripts at startup, access certain folders, and run commands that automate the process of testing certain services within a network.

_____________________

• Cellebrite violates every device with iOS and Android
• Facebook Anti-social rules of domination