Event log warnings concerning Diskeeper 2010

Hello,
I've been searching for an answer on Google and throughout many forums but I couldn't seem to find one so I figured I'd just ask here as this seems to be a good source of knowledge. I noticed numerous warnings in my event log concerning Diskeeper 2010 (I'm using Build:14.0.896.0) that state:

Category : 0
CategoryString :
EventCode : 1530
EventIdentifier : 1530
EventType : 2
Logfile : Application
Message : Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 20 user registry handles leaked from \Registry\User\S-1-5-21-3913409669-960638304-123155719-1001:
Process 3416 (\Device\HarddiskVolume1\Program Files\Diskeeper Corporation\Diskeeper\DkService.exe) has opened key \REGISTRY\USER\S-1-5-21-3913409669-960638304-123155719-1001


It goes on to list all the other keys Diskeeper has opened as well. On a whim, I wrote to Diskeeper tech support and asked them to explain and their reply was:

"Thank you for contacting us in regards to your Diskeeper software.
The registry activity noted in your email is not typical of Diskeeper software. This activity is quite suspicious and resembles the work of third-party malware which could be causing the DKService to unnecessarily access and hold on to registry keys.
The only advice we would be able to offer is to run a full system scan using a scanner that is not compromised on your system in order to determine the cause of the Event Log Warnings regarding the DKService and the registry keys listed."
Thank you,
Jun Dockins
Technical Support Rep.
Diskeeper Corporation

Now, I feel certain that I don't have malware on my system. I'm running Kaspersky 2010 and use Malwarebyte's Anti-Malware as a backup. I scan regularly and also keep tabs on all active outbound connections. I've scanned and scanned and they're always clean. I've tried multiple rootkit scanners, online scanners and just about everything else you could try. I just can't find anything wrong. I also get a warning concerning Wininit that states "Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications." Has anyone else seen this or does anyone have any ideas on what may be happening?

Despite Diskeeper's response, have you tried reinstalling the program? If they are right and the problem is caused by something else, the problem might return, but then perhaps not.

EDIT: I'm not familiar with Diskeeper, but I'm wondering if it has a background defrag function that is working in the background and is causing the error.

Thanks for the quick reply!! I did just find an update for my version. I installed that so I'm going to see if that makes any difference first. If not, I'll try re-installing the whole thing.

Any ideas on the "Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications." warning? That one really has me wondering. I have seen a few posts on various forums that claim that it's by design in 7. I might shoot an email to Microsoft and see what they say.

Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

I'm trying to think where is have seen that before. Isn't that part of the message given for an unsigned driver? If so, I would think that the program may not be totally compatible with Windows 7. Looking at the tech specs, it says that it will run on Windows 7, but that doesn't mean that it is actually compatible.

I use O&O Defrag, mostly because I prefer the way that it work, but their newest version is supposed to be compatible with W7, even though prior versions would run. It doesn't relate to your question, but when I asked their tech support about this, they said that the difference is because the new version defrags via zones, which the earlier versions didn't.

Well, if I don't get the registry issue resolved with Diskeeper, I will be looking for another defrag utility. I guess I mainly want to know if the warnings are something to really be concerned with or not. I was really hoping that DK tech support was going to say that it's just the way the software operates and nothing to be concerned with but, that wasn't the case. Again, I see no performance issues or anything else out of the ordinary but I know that doesn't mean everything is automatically ok. I know from browsing Google/other forums that other people are seeing the same error but they're caused by different apps in each case. There just doesn't seem to be a standard resolution yet.

As far as the dll issue, I always try to verify that what I put on the drives is compatible with 7 and the 64bit OS. I only have one piece of software (NFS Carbon) running in compatibility mode right now. The error is so vague that I can't narrow it down to the exact cause and that is what is driving me nuts! I try to address all issue as they appear in the logs and usually it's pretty straightforward but this one has me stumped for right now.

Well, I tried re-installing DK and I still get the same error log entries. I'm starting to wonder if it might be happening because DK is trying to do its thing and Kaspersky is running a rootkit scan or something else in the background. Anybody have any thoughts?

Does anybody else here running Diskeeper 2010 have any entries like the ones I'm seeing in their error logs? Anyone?

ghost446 said:

Does anybody else here running Diskeeper 2010 have any entries like the ones I'm seeing in their error logs? Anyone?

I am also getting the errors with diskeeper 2010. Just did a clean install of win 7 64, I think the first program I installed was diskeeper, same errors. Very long list of errors.

Perhaps it's time to consider a different defrag program to use.