DeepFreeze DOES NOT work as intended?

This looks interesting. If you have SSM and DeepFreeze, try booting frozen, then set SSM in learning mode and then reboot. It will not have reset. SSM will be in learning mode when you reboot. Application permissions you made will stick, even after you reboot.

This looks interesting. If you have SSM and DeepFreeze, try booting frozen, then set SSM in learning mode and then reboot. It will not have reset. SSM will be in learning mode when you reboot. Application permissions you made will stick, even after you reboot.

Hi, folks: Hi,eniqmah: I am a DF user, your findings are interested to me. First let me get your situation in a right order. You have DF(volume c frozen), and SSM(learning mode). In DF's frozen mode you allowed SSM to learn application permissions. Then you reboot, assuming all changes made would have been erased upon this reboot process. To your surprise, those changes learned by SSM remained. Then you suspect that DF has failed its mission. Am I right? My immediate question is this: Do you have volume(partition) other than C ? And those application permission changes learned by SSM are on volume(partition) C or on other partitions? The answer to these two questions are the key to your puzzle. Can you provide them. Thanks.

Yeah that's pretty much correct.This is what happens.
My system has many partitions, only partition C is frozen. Application data for everything except Firefox is store on C.

1. I boot frozen with SSM Free in normal mode (Not learning mode)
2. I put SSM on learning mode.
3. I copy an executable test.exe from H to C and executed both of them from H AND C.
4. I rebooted (frozen). Saw that SSM is STILL in learning mode. Opened it up and looked at the rules and sure enough, test.exe is allowed to run from both C and H.

5. The only changes are: the rules were kept, the executable was erased from C, and SSM remained on learning mode.
6. I can, at this point, take SSM off learning mode and opt to keep those rules.

It would seem that this is more of a bug than a loop hole because even though these rules stuck, the executables would be wiped out and nothing would be running on startup that wasn't allowed before. It is just interesting how the configuration data from a previous session was able to stick.

Edit:

I've replicated this 1 more time since this post and, on last attempt, failed to replicate it.

Though not related to SSM, but further indication that DeepFreeze just may not be THAT deep, my laptop has failed on several occasions to apply the visual style that I had on the system BEFORE booting frozen. That is, when I boot frozen on my laptop, sometimes the visual styles will get applied, sometimes it will not even though the data for the visual style is stored in C:\WINDOWS\Resources\...etc.

Just tried a similar experiment on my system. I froze my c: partition then threw ssm into learning mode, upon reboot ssm is back to the way it was with learning mode off. I then added some application rules and put ssm into learning mode. Upon reboot ssm is back to normal, learning mode is off and the new application rules i made before are gone. Deepfreeze seems to work as intended on my system, its a mystery whats happening on yours.