Yet another screwy test. Background. Setting up a new tablet, and wanted something, but disk space was a concern and I won't be "testing" on this machine so I decided to take another look at Rollback Rx. First thing I did was install it in a virtual machine, and beat up on it. All the testing that follows was done on the VM machine. Passed fine. This got me thinking. For speed and disk space Rollback is a hands down winner. But for backup, that's another story. One of the prize features for me has been being able to image less frequently, and before installing anything, updating an FDISR archive. Then if I had big problems, I could always restore an image, no matter how old, and then get current with the FDISR archive. Tested and tried an true. Note here my only real concern is recovery to a current state. Old and varied snapshots aren't important, although with a little imagination.... When I installed Rollback for the first time, I forgot to uninstall FDISR. This didn't seem to cause a problem and so once I had Rollback working, I tried booting to my FDISR secondary. Couldn't log in, kept blue screening. But I got to thinking, and thus the "experiment" 1) Started clean, with FDISR and my 2 snapshots. I imaged the system with SP, and then created a FDISR archive on the 2nd drive, 2) Removed the secondary snapshot so I just had FDISR, but no snapshots. I then installed Rollback Rx, and did my thing with it. All is working fine. I then made some drastic changes to this machine, so it was radically different from when I started. Took a final snapshot with Rollback Rx, and then used FDISR to update the archive, I had made off disk. It seemed to work fine, checking the log file. Now the fun. Assume something went wrong, and I can't boot with Rollback, uninstall or whatever. 3) Booted to my SP recovery disk, and restored the image using the delete volume step, and restoring partition,mbr and track 0. Rebooted. System was like it was when I started. No trace of Rollback Preboot, or anything. 4) Booted to the secondary snapshot, restored from the image. Then refreshed the primary snapshot from the archive, and holding breath rebooted. 5) No rollback preboot screen and machine came up looking exactly like it was when I refreshed the archive. No sign of Rollback. I tried firing it up from the start menu and it said it was uninstalled. I suspected that was because it wasn't in the mbr, so I did an uninstall, and it actually removed the program. None of the normal snapshot questions. Just removed the program. 6) I then did a reinstall of Rollback and it worked just fine. It was like a clean install. In summary, I was able to image like I do now, use Rollback with it's advantages, but also keep an FDISR archive current, to use in a disaster recovery scenario. For me the best of both worlds. Next step try Rollback on my raid 0 drives. Pete PS. To anyone wondering why I use a VM machine, you can do all this stuff, and when done, wipe it all out.