New
#1
Is there a way to presist data on Windows sandbox?
In windows 10 sandbox when I close all data are gone, is there a way to presist the data ?
In windows 10 sandbox when I close all data are gone, is there a way to presist the data ?
The whole purpose of a sandbox is not to persist data. That said, I suppose you could take an image backup with the Sandbox active and then restore that backup to get the sandbox back. But then, you'd lose what had changed in the surrounding OS and filesystem around the sandbox.
Why do you want to do this? What are you trying to accomplish? If you can answer those questions, the community may have some useful suggestions for you.
HTH,
--Ed--
Thanks I will use hyber-v . I am testing some software and I dont want to reinstall and configure each time
Hi there
I don't think that's entirely true -- for example what about software that requires a reboot after install or testing configuration changes which may also require a re-boot --or even basic testing applications which use different sets of data.
IMO a Sandbox should definitely have the option of persistence -- at start up the sandbox application should be able to load an old one or a brand new one with a user prompt at start up.
What abut also testing different software versions and comparing --real pain to re-install each time.
Plenty of uses for a sandbox which don't necessarily need a full blown VM for testing. Of course a VM currently is easier to manage but a decent sandbox system should be an option where you don't need to have a full blown "Guest OS" running - specifically if you just want to test out some applications. For instance I might want to test EXCEL 2019 compared with EXCEL 2016 -- seems a bit "Over the top" to have to install a full VM for just testing 2 versions of the product -- on one sandbox I could test excel 2016 and on another the excel 2019 versions.
Another problem with (at least for Windows VM's) VM testing is that each Windows guest requires a different / new license -- a sandbox is running under the basic Windows OS so no extra license needed.
Cheers
jimbo
Install Windows 10 on a Hyper-V virtual machine, enable nested virtualization on that VM (tutorial). When done, add Sandbox feature to that VM.
Then, when you want to preserve the state of Sandbox, do as told in Method One in this tutorial: Windows Subsystem for Linux - Create a WSL Sandbox in Windows 10
Kari
Instead of a sandbox, use Snapshots instead. So, before you do any install or testing, create a snapshot of the VM, then when you are done, you can revert the VM back to the Snapshot!.
See The Microsoft Hyper-V snapshot explained
Use the program Sandboxie (which is now open source by the way). It let's you configure in detail what data is retained when you close the sandbox.