Suggested new feature or improvement
Windows Sandbox should offer an optional mode that preserves the sandbox state between launches until the user explicitly resets it.
The existing disposable behavior should remain the default. However, users should be able to create a persistent sandbox instance that retains installed applications, files, Windows settings, and configuration across application closures and host restarts.
A possible name would be Persistent Sandbox or Windows Playground.
Scenario
I want to use Windows Sandbox as a lightweight test and recovery environment across multiple sessions.
For example, I install diagnostic tools, browsers, PowerShell modules, prerequisite runtimes, and test applications, then configure the environment and restart it where required. Currently, closing Windows Sandbox deletes this entire setup, forcing me to repeat the provisioning process every time. Mapped folders preserve files but not installed applications, services, registry changes, Windows settings, or the complete system state.
I would like an optional persistent mode that retains the Sandbox state until I explicitly select Reset or Restore baseline. The current disposable behavior should remain the default.
This would provide a practical middle ground between a single-use Sandbox and a fully managed Hyper-V virtual machine. It would support multi-session software testing, troubleshooting, development, demonstrations, and an isolated “Plan B” Windows environment without requiring users to install and maintain a separate Windows VM.
Additional details
The current disposable behavior should remain the default. Persistence should be an optional and clearly identified mode, possibly named Persistent Sandbox or Windows Playground.
The persistent mode should preserve installed applications, files, registry changes, services, Windows settings, and updates between launches.
Users should be able to set the current state as a baseline, restore that baseline later, or reset the environment to a clean Windows image.
The interface should clearly indicate when persistence is enabled and warn that malware, credentials, browser data, and unwanted system changes may also persist.
Existing controls for networking, clipboard access, mapped folders, audio and video input, and GPU acceleration should remain available. Administrators should also be able to disable persistent mode through policy.
Mapped folders and startup scripts are not equivalent solutions. They can preserve selected files or automate installations, but they cannot preserve the complete configured operating system state.
A full Hyper-V virtual machine can provide persistence and checkpoints, but it requires substantially more setup, storage, configuration, and maintenance. This request is intended to provide a lightweight middle ground that retains the simplicity and fast startup of Windows Sandbox.
Related requests:
#98
#32
The requested behavior is simple: retain the complete environment until the user explicitly resets or restores it.
Alternatively, add a separate Windows Playground menu item that launches Windows Sandbox in a persistent, user-resettable mode.
Suggested new feature or improvement
Windows Sandbox should offer an optional mode that preserves the sandbox state between launches until the user explicitly resets it.
The existing disposable behavior should remain the default. However, users should be able to create a persistent sandbox instance that retains installed applications, files, Windows settings, and configuration across application closures and host restarts.
A possible name would be Persistent Sandbox or Windows Playground.
Scenario
I want to use Windows Sandbox as a lightweight test and recovery environment across multiple sessions.
For example, I install diagnostic tools, browsers, PowerShell modules, prerequisite runtimes, and test applications, then configure the environment and restart it where required. Currently, closing Windows Sandbox deletes this entire setup, forcing me to repeat the provisioning process every time. Mapped folders preserve files but not installed applications, services, registry changes, Windows settings, or the complete system state.
I would like an optional persistent mode that retains the Sandbox state until I explicitly select Reset or Restore baseline. The current disposable behavior should remain the default.
This would provide a practical middle ground between a single-use Sandbox and a fully managed Hyper-V virtual machine. It would support multi-session software testing, troubleshooting, development, demonstrations, and an isolated “Plan B” Windows environment without requiring users to install and maintain a separate Windows VM.
Additional details
The current disposable behavior should remain the default. Persistence should be an optional and clearly identified mode, possibly named Persistent Sandbox or Windows Playground.
The persistent mode should preserve installed applications, files, registry changes, services, Windows settings, and updates between launches.
Users should be able to set the current state as a baseline, restore that baseline later, or reset the environment to a clean Windows image.
The interface should clearly indicate when persistence is enabled and warn that malware, credentials, browser data, and unwanted system changes may also persist.
Existing controls for networking, clipboard access, mapped folders, audio and video input, and GPU acceleration should remain available. Administrators should also be able to disable persistent mode through policy.
Mapped folders and startup scripts are not equivalent solutions. They can preserve selected files or automate installations, but they cannot preserve the complete configured operating system state.
A full Hyper-V virtual machine can provide persistence and checkpoints, but it requires substantially more setup, storage, configuration, and maintenance. This request is intended to provide a lightweight middle ground that retains the simplicity and fast startup of Windows Sandbox.
Related requests:
#98
#32
The requested behavior is simple: retain the complete environment until the user explicitly resets or restores it.
Alternatively, add a separate Windows Playground menu item that launches Windows Sandbox in a persistent, user-resettable mode.