Privatefirewall, so what went wrong?

64 bit W7 system here. I decided to try Pf (had it on an XP machine for a few years) but the installation resulted in W7s version of the bsod. Did I have to turn W7s firewall off prior to installation? I'd assumed the install wizard would do that. All I know is when I booted to finish the installation Windows hung and there wasn't anything being written to my SSD. Pretty nice how after I forced another shutdown and booted again, W7 offered automatic restore.

 

I have tried it several times on both Win 7 and Vista (both 64 bit) and always got BSOD's shortly after the install reboot. I never pursued the problem but just went back to my previous firewall. I was and am happy with my current firewall but just wanted to try Private Firewall because so many had good things to say. I can't really help you any with your problem but just wanted to let you know that at least you are not the only one to have this experience.

 

Thank you and quite interesting!

 

If you tried many FWs on your PC, simple uninstalls always leave remnants in the registry. You have to take them out. On a newly installed system, I have no problem with PFW

 

I actually run PF on severals computers for many years without any BSOD,

OS are Vista x64 SP2 (all editions), Seven x64 SP1 (all editions), except entreprise version and starter version.

You can use this little app to know what happened and send e-mail to M Greg Salvato and i'm sure he will fix that.

http://www.nirsoft.net/utils/blue_screen_view.html


Rules.

 

Here is Privacyware support if needed. I believe they're very helpful and prompt: http://www.privacyware.com/support_ticket.html

 

As I recall, PF does not require a reboot after installation?

In fact, one way not to have issues with PF after installation is to open and close all your applications while it is in the training period. I beleive the training period is 10 mins. after initial install but can be manually extended.

And PF will turn off the WIN 7 firewall during installation; not sure about third party ones. If you had a third party firewall installed. I would recommend uninstalling and removing all remenants prior to installing PF.

Also all real time AV. antispy, etc. software should be disabled when installing PF. This could be your primary culprit.

 

This same problem (BSOD) happened to me when I tried to install PrivateFirewall on top of BitDefender AV one time. I uninstalled the AV, installed PF, reinstalled the AV and the system ran fine.

IMO, Itman is on the right track in his post...

 

It did request a reboot. I didn't have any firewall save for W7s. Sounds like it could be Norton A-V.

 

The first thing that asks is a restart.
To OP,never had BSOD with PF although i've experienced some lags right after restart.And i always use clean Comodo Time Machine snapshots when i install new security.

 

The developer will recommend that you unistall NAV 2011/12, install PF, and then reinstall NAV.

I found that disabling NAV's autoprotect protection and then installing PF was sufficient. Once the PF reboot completes, then enable NAV's auto-protect protection. You should also set minimally ccsvchst.exe in PF's Applications section from Limited to Allow.

I also subsequently added the PFGui.exe and pfsvc.exe from PF x(86) folder in WIN 7 x64 to NAV's auto-protect/Sonar/Downloads exceptions. This eliminated boot conflicts between the two.