Hello, I have a computer with Windows XP SP3, and Deep freeze 6, recently I installed Avast 7, but after some checks, I detected that, Avast inhibit any funtuon to activate the activetae/deactivate D.F., because of that, I am not able to unfreeze my computer.
There is no message, or any other visible condition, just, once avasta is installed (with deep freeze deactivated) to turn off all Avast process, and reinitiate the computer in order to be able to get into the DF configuration panel.
OBviosuly if I freeze the computer, I will not be able to, un freeeze my computer againg.
Those any one got the same condition?.
Thanks in advance for your help
That condition, does not occur with windows 7 and DF 7.
Not an incompatibility, but avast doing what it should protecting its files and folders. If if remember rightly you can exclude the avast folders in deep freeze. Try a forum search for Deep Freeze and see what it brings up.
As far as I had using DF, you can select disk or partitions, not individual folder, but, there are is some combination or avast configuration to un block the DF?, I found nothing related with DF and the specific condition.
Well it isn’t something that avast can unblock as essentially its self-defence is doing what it should prevent the programs files or folders from being modified. Don’t search for too defined a search term as the more you search for the lower the potential hit rate, just look for deep freeze.
Since you say there is “no message, or any other visible condition” it is somewhat hard to say what it might be as the self-defence module would alert if that was what it was.
When does this happen, e.g. when you run the deep freeze executable ?
I unfreeze my computer, make all updates, including new Avast version (previously I had Avast 6), after that (while the computer does not restar, I am able to manipulate DF), once I restart the computer, I was not able to manipulate DF. (still the computer is not freezed), in that moment, if I stop all Avast process, and reboot, I can manipulate again DF…
My problem is there is no information/messages to even hope to say it is happening.
Two areas to look at, the Behavior Shield and AutoSandbox and I’m not even sure if they are going to prove fruitful as they would normally throw up warning screens.
Check the C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\report\BehaviorShield.txt file for any deep freeze related files.
Check the C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log\autosandbox.log for any deep freeze related files.
Set both shields to Ask not auto and see if that displays any notice window:
From the avastUI > Real-Time Shields > Behavior Shield > Expert Settings, Action to take, set to Ask.
From the avastUI > Additional Protection > AutoSandbox > Settings, AutoSandbox mode, set to Ask.
Even if I include DF in the trust list, does not allow to open the configuration panel of DF. I presume that DF get blocked or something laike that, because of any Avast action. Also those not display any message related to DF
I will reinstal the computer, takin care of sequence of installation and configuring Avast, previos to freeze the computer. I will let you know what happens.
The exclusion should work, provided you pout the full path and correct file name in the exclusion.
This C:\Program Files\Faronics\Deep Freeze\Install C-0_$Df\FrzState2k.exe is the file to exclude the other file is the one doing the calling of this file.
Set the AutoSandbox to Ask, that allows you to select Run Normally and check the ‘Remember my answer for this program’ option.
Hello, no way to put it work as supouse to be, after the computer get freezed, even using the comand line “commands” for DF, work. Both programs super protect the computer, not allowing unblock or infreeze.
I will reinstall, following the next sequence: install DF, unfreeze the computer, install Avast 7, and configure sandbox and behavior parameters.
At last I did the re installation, after finishing the system install, I installed DF, reboot in thawed state, install avast 7, reboot, and configure sandbox and realtime module, and all work fine, and I rechequed, and the condition does not occurs with Windows 7 and Avast 7, even I did no configuration in Avast.