#RECOVER PEERGUARDIAN DRIVER#

Its origin seeds in targeting aggressive IPs while you use P2P.

It blocks connections to and from hosts specified in huge blocklists (thousands or millions of IP ranges).

So in short, from where I sit, there's nothing at all better about PB, and many things worse.īTW, I am running the latest STABLE version of PB. PeerGuardian is a privacy oriented firewall application.

#RECOVER PEERGUARDIAN DRIVER#

Also, PG removes its driver automatically when it's closed. There is no (native) way to remove the PB driver if the application or system crashes, as there is with PG. Other, minor GUI bugs from PG (in the settings dialog) are still there. The list editor has a GUI bug (at least when used at 120 DPI). If PeerGuardian crashed, please run ''Recover PeerGuardian'' from the start menu to attempt to recover from the problem. This could happen if PeerGuardian crashed and didn't have a chance to unload the driver, or if the file pgfilter.sys can't be found. Well, uhh, I have it configured not to display ANY 'Allowed' connections, so why display them at all? 'PeerGuardian is unable to load the packet filtering driver. Sometimes it displays the 'Generating List Cache.' notice even when I KNOW there have been no list updates.Īlso, each time I run PeerBlock, it displays a few 'Allowed' connections, and then issues a notice that it won't display any more of them to save resources. PeerBlock not only has the same delay, it forces it upon me TWO times each time I start it, for no apparent reason.

(I do understand the reason for that delay.) That version of PG runs perfectly for me, and the only annoyance with it is the 'Generating List Cache.' delay. There's no way I'm using this instead of PeerGuardian 2.0 6b.

Recover peerguardian