Peer Block

[larryllix]

If I run Peer Block and later turn it off, when I re-run Peer Block it will not boot if MBAM is running. I have proven this several times with MBAM not running and again with it.

"PeerBlock is unable to load the packet filtering driver.

This could happen if PeerBlock crashed and didn't have a chance to unload the driver, or if the pbfilter.sys can't be found

win32_error

CreateFile

2

The system cannot find the file specified"

This never happened in free usage but after recovering from a nast AntiSpyWareXP virus and purchasing a full copy of MalWareBytes PeerBlock requires the system to be rebooted in order to run again. (MBAM is already running) It appears to afflict it when PeerBlock is shut down.

No scans show signs of infection. AVG was removed after letting the second virus through that crippled both of these scanners AVG running at the time.

[Memnoch]

I've had this problem also, but it never occurred to me that MWB could be the cause.

I did install MWB a few weeks before my problem..I did did a Google Search & also went to the Peer Block Forums looking for answers.

This problem/error has been happening for a few years now & is pretty random.

Still, it seemd to me that if MWB was the problem someone would have noticed by now.

Anyway, I did fix the problem on my end & so far it's worked...this thread got my looking in the right direction & after tweaking it a bit..I might have gotten it right.

[larryllix]

Still, it seemd to me that if MWB was the problem someone would have noticed by now.

Anyway, I did fix the problem on my end & so far it's worked...this thread got my looking in the right direction & after tweaking it a bit..I might have gotten it right.

Thanx for the link. I did have a look and try the tweak for that registry entry. It is definitely involved but not working for this case. Right now I have de-commissioned malwarebytes and installed another free scanner that has found 22 instances of 9 viruses and PerrBlock has begun to function again. I may retry my purchased copy of MalWareBytes later to see if things are different.

Another issue that seems related is my emal folders get the message "Not closed properly...scanning for problems" everytime the machine is rebooted. After removal of Malwarebytes, this stopped also. hmmmmm....

I am definitely not as impressed with this software as I once was.

[larryllix]

I've had this problem also, but it never occurred to me that MWB could be the cause.

I did install MWB a few weeks before my problem..I did did a Google Search & also went to the Peer Block Forums looking for answers.

This problem/error has been happening for a few years now & is pretty random.

Still, it seemd to me that if MWB was the problem someone would have noticed by now.

Anyway, I did fix the problem on my end & so far it's worked...this thread got my looking in the right direction & after tweaking it a bit..I might have gotten it right.

I think I have proven that MalWareBytes has a few defeciencies that need to be repaired. I have removed it from my system and installed another freebie scanner, only to discover 22 incidences of another 12 viruses that mbam.exe didn't seem to want to find. Weird???

After reinstalling MawareBytes scanner again I found it interferes with PeerBlock again and PeerBlock will not boot. From your supplied link I dissovered some clues regarding this mechanism.

MalwareBytes seems to have problems with system parameters, especially how it leaves them for others to play with. This may be only when shut down from the systray icon.

IP Traffic Filter Driver gets shut off and PeerBlock uses the flag/driver also.

eMail files seems to be not closed properly when shutting down also. Eevery time I close WinXp and reboot it complains the "personal folders" were not closed properly and rescans. This add another 3-4 minutes to the already incredibly slow boot-up with the scanner enabled.

I have removed MalwareBytes scanner three times and installed it twice and found this to be the case, every time, while it is resident. Also, these problems disappear each time it is removed and another scanner installed.

Currently I am running with another scanner on a free trial basis. I guess the MalwareBytes purchase was a waste, for me, until some of these problems can be repaired.

[Memnoch]

MalwareBytes seems to have problems with system parameters, especially how it leaves them for others to play with. This may be only when shut down from the systray icon.

IP Traffic Filter Driver gets shut off and PeerBlock uses the flag/driver also.

I have removed MalwareBytes scanner three times and installed it twice and found this to be the case, every time, while it is resident. Also, these problems disappear each time it is removed and another scanner installed.

Since my fix has still been working on my machine, I'll leave mine alone for now.

I will test this theory later today on a friends machine, I was already planning on going over to fix her PeerBlock problem.

I'll try turning off Protection first..if no go I will un-install.

If her PB starts to work again MWB will stay off.

Right now I wish MWB had a way to browse to a file to add to the Ignore List.

[larryllix]

Right now I wish MWB had a way to browse to a file to add to the Ignore List.

This was one of the reasons I got rid of AVG. They must get a kickback to delete any file that has KeyGen.exe as a filename. If you rename file "keygen.exe" to "protected.keygen.exe." suddenly there were no viruses inside it. People reported this for years now and the answer always was to turn off the scanner, run the keygen and then turn on the scanner again....Look, no viruses in the system still. = it didn't spread. After many versions it still deleted every occurance of every KeyGen.exe I had obtained. Spyware, itself IMHO

It did have ignore lists to workaround that problem, though.

[Memnoch]

This was one of the reasons I got rid of AVG. They must get a kickback to delete any file that has KeyGen.exe as a filename. If you rename file "keygen.exe" to "protected.keygen.exe." suddenly there were no viruses inside it. People reported this for years now and the answer always was to turn off the scanner, run the keygen and then turn on the scanner again....Look, no viruses in the system still. = it didn't spread. After many versions it still deleted every occurance of every KeyGen.exe I had obtained. Spyware, itself IMHO

That's why I don't let AVG scan zip files...lol

OT: I can confirm 100% that MWB is the/or one of the problems with PeerBlock.

I tuned off Protection & Start With Windows, fired up PB & it was working again.

So for now I left MWB installed..but it's only a scanner now.

Since I fixed it a different way on my machine, I'll leave it as is...till something happens.

I do think this is something MWB should look into.

[larryllix]

I can confirm 100% that MWB is the/or one of the problems with PeerBlock.

I tuned off Protection & Start With Windows, fired up PB & it was working again.

So for now I left MWB installed..but it's only a scanner now.

Since I fixed it a different way on my machine, I'll leave it as is...till something happens.

I do think this is something MWB should look into.

MWB worked perfectly until I purchsed the registered version and turned on the resident protection.

I have since installed it on my wife's laptop and my WiFi pronter has become non-accessible. I have removed it and installed another freebie scanner, found nothing and re-installed the Printer drivers...working. After a proof period I will reinstall MlaWareBytes to investigate tampering with printer driver internals. I need to know what has damaged the setup of this printer. The WiFi printing system appears pretty sensitive to "weather changes", so far.

[nosirrah]

We are getting close to releasing 1.45 and there some changes in the services . At this point troubleshooting does not seem like a good idea as anything learned may lead to existing fixes .

PeerBlock is unable to load the packet filtering driver.

This sure does seem like an IP blocking conflict . Since MBAM can have its IP blocking disabled but still retain the file based protection you could try that config with your existing packet filtering software .

[Memnoch]

This sure does seem like an IP blocking conflict . Since MBAM can have its IP blocking disabled but still retain the file based protection you could try that config with your existing packet filtering software .

Disabling IP Blocking by right clicking Tray Icon lasts only till next Boot...

I hope 1.45 has a Box to check to turn it off.

[exile360]

Disabling IP Blocking by right clicking Tray Icon lasts only till next Boot...

I hope 1.45 has a Box to check to turn it off.

It does, and for now with version 1.44 you can use the info provided here listed under Registry Switches for Controlling IP-Blocking which will allow you to disable it from running at boot.