Rootkit Scan Hangs

[galileo]

@Daniel

I have recently upgraded Cyberhawk from the 2.0.3 to the 2.0.4 version - both Pro versions (was updating an older machine that has been out of service for severla months). I did uninstall the 2.0.3 version per the instructions before installing 2.0.4. After installing, the 2.0.4 version will not perform a Rootkit scan (either Quick or Full). It scans about 10 to 20 files and then locks up.

I have uninstalled 2.0.4 and reinstalled it and had the same result. I am guessing that there is a corrupt registry key (?)...All files were deleted from the Novatix folder in Program Files following the removal. I am running XP Pro SP2 fully updated through 8.13.2007.

Any thoughts...?

BTW: I am a "former" CH beta tester....prior to the "acquisition"...;)

[djames]

This should have been fixed in 2.0.4. can you check in the Novatix folders to see if the files are the same version?

[galileo]

All files and folders from the prior version were removed prior to the install - including the All Users and Common Files locations. After a fresh install all file and folder dates show either 8.14.2007 (my install date) or 5.16.2007 (which I presume is your build date for that version)

Is there any problem with USB devices being attached during the install or during a scan?

I tried another install this evening and had the same result - Hang @ 10 files scanned. I am using Version 2.0.4.34...downloaded again today just to be sure...

This is really disappointing since this version works fine on other machines and the previous version worked fine on this machine :(

What registry keys should I check or clean out? Are any betas available to test out on this?

[galileo]

Further info:

CH crashes when accessing the scan scheduler dialogs. See image below. Note that this appears to be related to MSVCR80.DLL - which is not located in the system32 folder....assuming one has .NET installed. Are you distributing this dll with CH? Other error logs seem to indicate that CH cannot find this dll. Note also that this dll has caused problems with other software as well due to location and catalog entries.

Still not working but, getting closer to the issue...maybe :p

[galileo]

More info...

The error may be referencing a compatibility issue with MSVCR80 rather than simply not finding it - although it does appear to have been looking in the system32 folder also. The machine in question does have .NET 1.1, 2.0, and 3.0 installed on it.

I am wondering if the installation of .NET 3.0 may have generated some inconsistency in the dll files...? This is an odd one...:confused:

[djames]

Yes this is a little strange. The installation package for the Beta which will be out very very soon, is changed.
I will keep an eye out for this in the future build though.