What you did: Started the requested scan of the computer, a full scan is always required (recommended).
What actually happened or you actually saw: The virus scanner Hung, and stopped responding to the Stop Command, or the Kill window.
What you expected to happen or see: I expected that the scan would complete.
How you tried to fix it & what happened: ??? I saw a similar behaviour in version 4, and was informed that should wait for version 5, and retry the scan.
Details (exact version) of any software involved with download link: Premium version 5.0.162636.1135
Bugzilla id (mods use only):
Files appended
Screenshots illustrating the bug: None yet.
Screenshots of related event logs or the active processes list: None.
A CIS configuration report: None.
Crash or freeze dump file: None.
Your set-up
CIS version & configuration used: Premium version 5.0.162636.1135
Whether you imported a configuration, if so from what version: Upgraded my Installation.
Defense+ and Sandbox OR Firewall security level: Fw: Disabled, Defense: Disabled, Sandbox: Disabled.
OS version, service pack, no of bits, UAC setting, & account type: Windows XP Pro, SP3
Other security and utility software running: MicroSloth firewall
Please also add to the issue report an indication of any other security or utility software you are running.
Then I will forward this for investigation.
Some way of identifying the file involved would also be deeply appreciated. Ways of identifying the file involved are here. Making a hang dump is the simplest.
If the OS crashes there will be an OS crash dump. If you wait the OS will probably either crash or free up. If the latter you can get your dump. Maybe set it going overnight and come back in the morning and see what has happened.
Failing this the best you can do is probably a CIS config report or .cfgx file plus maybe a hi-jack this ( here) report. Devs will then know what you are running and can try-out likely candidates for conflicts.
Look in the bug forum help files for how to do these things (except Hijack this which is pretty self evident!).
I am still experiencing this issue. I have run the process explorer, and found that a High number of temporary files are created in c:\Windows\Temp directory.
How do I get this issue resolved? There is no OS Crash dump, not even after 12 hours (I need the computer for other purposes rather than waiting for a crash).
The problem is that when this occurs, nothing else can be accomplished. The computer is frozen.
If you can identify and list the file handles which are open when it hangs (different colour if I remember), you can then try scanning each individually (using right click scan) until you get a scan hang. Without a dump its a process of elimination.
The only other method is to record the directory being scanned when the hang occurs, then use a right click scan on every file in the directory. If there are a lot of files do a binary search - check half by right click using a multiple selection. If it’s in the half you check divide that in half…and so on until you have located it!
Also can you give your AV database version number please? It’s in more ~ about. (It’s not a date!)