For Windows 10 and 11 only. Due to the version less than Windows 10 does not have the Sandbox feature as all.
Setup and run the Windows Sandbox with chosen parameters.
Add mapped folders from Host Operating System to get access to your files from inside the sandbox safe environment.
Assign your mapper folder to any path you like to see this folder inside or just drop it to the Sandbox's Desktop to quick access.
Set Mapper Folders as Read Only to keep it safe from possible deletion from inside SandBox
Add Logon Command. This command will be automatically executed once the Sandox environment is started.
Added a cool feature: Shell Context Menu to open any file directly in Sandbox Environment and will avoid you from copy/past this file manually. THIS OPTION DOES NOT EXIST IN SIMILAR APPLICATIONS, SO I AM THE FIRST.
The number of parameters, you can adjust is limited to what the Microsoft allow us to setup prior the Sandbox will be running. I cannot add anything more.
The options are available for you are: - Enable Virtual GPU for your SandBox. - Share the Network and Internet Connection from your Host to Sandbox. - Share Clipboard, so that you may copy/paste any file or text from Host to Sandbox and vise versa. - Redirect all your real printers from Host to Sandbox in order that you may print from Sandbox directly to the real printer. - Protected RDP Client Environments. - Redirect Audio Inputs. This option redirect any audio input devices from your host to Sandbox (Microphones, AUX inputs & etc.) - Redirect Video Inputs. This option redirect any video input devices from your host to Sandbox (Web-Cameras, Miracast and others) - Setting up the RAM memory for your Sandbox Environment. Keeping the value to ZERO will set the Sandbox adjust the RAM to the minimum required to run. Usually it is not less then 2 GB.
Another feature I have implemented is that the application will run automatically with elevated privileges (Administrator Rights). This is required to check the status of the Sandbox in you host OS to be sure that the application could work.
In case the Sandbox is disabled, then you will have ability to enable it with further question to restart the system in order the change to take effect and you may use Sandbox. Be sure that the Hyper-V is enabled in BIOS/UEFI, without it the sandbox will not run and the corresponding message will say you the same.
Finally, this is a very good tool to be used by everyone to have chance to safely test any untrusted or harmful to your system application. Any changes to the SandBox Environment will be destroyed once you close the Sandbox Window, what finally a great idea. And you OS will be kept safe and unchanged.
I recommend this application for everyone to start using with you SandBox.
