WSA doesn't work with PerfectDisk 13?

Ugh. Installed WSA to test it out, and it kept crashing PerfectDisk13 via the PDAGENTS1.EXE file.

I checked, it's not a monitored process in WSA. Google tells me others have had issues in the past with WSA and PD, are these issues still common?

Any tips?

 

This bug happens when WSA detects a threat. Such as EICAR test file. Immediately when the threat is discovered, PerfectDisk13 (PDAGENTS1.EXE) crashes.

My guess - there is a conflict on handles. PD tries to intercept any bad fragment write attempts, WSA is intercepting as well - and thus - crash. That's a rough guess. The defining aspect of PD13 is the realtime fragmentation prevention system, so this is a pretty serious WSA issue!

 

My suspicions were confirmed. When I disabled PerfectDisk13's Opti-Write, which is the module that intercepts bad fragments prior to write, WSA did not crash PerfectDisk when a threat was discovered.

There aren't any methods to exclude monitoring within PerfectDisk13 in regards to OptiWrite, so it's WSA's call on this one.

Any suggestions aside from disabling Optiwrite? (which won't happen)

 

i made a thread about this a while back and had the same issues with perfectdisk and wsa. for me 12.5 was not working while 13 did though. so this is odd.

 

The latest version from Perfectdisk doesn't work - but only if Optiwrite is active. Otherwise it seems fine.

http://docs.raxco.com/perfectdisk/12/EN/Automatic_Modes_Tab_Main_Screen.htm

At least fine SO FAR.. I haven't done any other testing yet, but this is pretty annoying as I rely on OptiWrite to keep defragging to a minimum (or not even required).

 

PD 13 and previous running fine with KIS and WSA here with all at default.

 

It may be linked to whilisting. Contact support to be sure that specific process is whitelisted in their database...

 

I agree - you will be able to tell if the process is active and you open Control Active Processes: if it is marked as "Monitor", change it to "Allow" which should fix it.

 

Hello,

FYI...
Up until Jan. 9, PD13 files were monitored. I wrote into support and had them whitelisted. Working fine here on my system now....

 

I had them set to allow under active process control, and it was still crashing.

Mind you, this was happening on a fresh, isolated laptop I use for testing, and then verified on an 'operational' desktop. It crashed both systems, but only when PD13 and WSA were paired together. That's running the latest full release of PD13 - by the way.