This may or may not mean any thing, but I'd like to know what it really means for users of FDISR. Abstract: Unlocker deletes the inactive snapshots and renames the active snapshot upon reboot, causing irreversible damage? Tools needed: Unlocker v. 1.5 Environment: Booting with deepfreeze in thawed mode, system folders not hidden/protected (this can be set in Folder options in control panel) ISR service not running on boot or is terminated after boot (via taskmanager) Assume active snapshot = folder "0" in directory "C:\$ISR", Assume inactive snapshots = folders "1" through"9" in "C:\$ISR" ( if the system has that many snapshots) Instructions to replicate: Step 1. Navigate to: "C:\$ISR\$APP" > replace ISR.ico with another/DIFFERENT icon with the same name. This step was just part of what I was doing ( trying to reshack the icon ), and may not be necessary to replicate the situation. Step 2. Navigate to: "C:\$ISR" > rightclick on the snapshot folder "0" to unlock the folder, this will lead you to the ability to rename that folder upon reboot > rightclick on snapshot folders"1" through "9" and delete them using unlocker. Step 3. Rebooting will lead to the ISR Service not being able to run > ISR can not start correctly to enable you to boot into another snapshot. Step 4. Navigate to: "C:\$ISR" and see that the snapshot folder "0" have been renamed to something else. Step 5. Reboot and press F1 to get into the FDISR boot menu > Error message: "0" folder not found - FirstDefense-ISR ERROR - Presss any key to boot Windows. Step 6. Press any key, boot to Windows to end up @ step 3. So essentially, after I do this to ISR, I am free to mess the system up, without much help from ISR to recover. So what does this really mean? Reinstall ISR from within the messed up system and restore from archive? Would some one try doing that and report back?