Did you try using the User Profile Hive Cleanup Service?
Ran Avast pro with full scan: No detections, but several archive files were corrupted. It ran for over 6 hours and only got 60% through. I have several disks. All of the C drive got tested
to complete an anti-virus or anti-malware scan depends
on a variety of factors
- The program itself and how its scanning engine is designed to scan: using a signature database vs heuristic scanning or a combination of both.
- Options to scan for spyware, adware, riskware and potentially unwanted programs (PUPS).
- Options to scan memory, boot sectors, registry and alternate data streams (ADS).
- Type of scan performed: Deep, Quick or Custom scanning.
- What action has to be performed when malware is detected.
- A computer's hard drive size.
- Disk used capacity (number of files to include temporary files) that have to be scanned.
- Types of files (.exe, .dll, .sys, .cab, archived, compressed, packed, email, etc) that are scanned.
- Whether external drives are included in the scan.
- Competition for and utilization of system resources by the scanner.
- Other running processes and programs in the background.
- Interference from malware.
- Interference from the user.
To speed up your scans, uninstall unnecessary programs, clean out the temporary files
or use ATF Cleaner
first, temporarily disable any other real-time protection tools
, close all open programs and do not use
the computer during the scan. If the scan still seems slow or hangs, then try performing the scan in "safe mode
Using two security scanning engines at the same time can cause each to interfere with the other, cause systems hangs, false detections, unreliable results and other unpredictable behavior.Note: It is not unusual for an anti-virus or anti-malware scanner to be suspicious of some compressed, archived, .cab and packed files because they have difficulty reading what is inside them. These kind of files often trigger alerts by security software using heuristic detection because they are resistant to scanning (difficult to read). This resistance may also result in some scanners to stall (hang) on these particular types of files. Certain files in the System Volume Information Folder like the Tracking.log (created by the Distributed Link Tracking Service to store maintenance information) have also been reported as a source causing some scanners to hang.Additional Note
: If you are using a CD Emulator (Daemon Tools
, Alchohol 120%
, etc) be aware that they use rootkit-like techniques to hide from other applications and can interfere with investigative or anti-rootkit (ARK) tools. This interference can produce misleading or inaccurate scan results, false detection
of legitimate files, cause unexpected crashes, BSODs
, and general dross. This 'dross' often makes it hard to differentiate between genuine malicious rootkits and the legitimate drivers used by CD Emulators. In some cases, the drivers related to such tools can cause crashes or system hanging when attempting to boot into safe mode. Since CD Emulators use a hidden driver which can be seen as a rootkit and interfere with providing accurate results or cause other problems, it is recommended that they be removed or disabled until your scans have been completed.
Bleeping Computer DOES NOT recommend the use of registry cleaners/optimizers for several reasons: Registry cleaners are extremely powerful applications that can damage the registry by using aggressive cleaning routines and cause your computer to become unbootable
RanCcleaner. Lots of registry fixes.
The Windows registry
is a central repository (database) for storing configuration data, user settings and machine-dependent settings, and options for the operating system. It contains information and settings for all hardware, software, users, and preferences. Whenever a user makes changes to settings, file associations, system policies, or installed software, the changes are reflected and stored in this repository. The registry is a crucial component
because it is where Windows "remembers
" all this information, how it works together, how Windows boots the system and what files it uses when it does. The registry is also a vulnerable subsystem, in that relatively small changes done incorrectly can render the system inoperable. For a more detailed explanation, read Understanding The Registry
. Not all registry cleaners are created equal
. There are a number of them available but they do not all work entirely the same way. Each vendor uses different criteria as to what constitutes a "bad entry
". One cleaner may find entries on your system that will not cause problems when removed, another may not find the same entries, and still another may want to remove entries required for a program to work. Not all registry cleaners create a backup of the registry before making changes
. If the changes prevent the system from booting up, then there is no backup available to restore it in order to regain functionality. A backup of the registry is essential BEFORE
making any changes to the registry. Improperly removing registry entries can hamper malware disinfection
and make the removal process more difficult if your computer becomes infected. For example, removing malware related registry entries before the infection is properly identified can contribute to system instability and even make the malware undetectable
to removal tools. The usefulness of cleaning the registry is highly overrated and can be dangerous
. In most cases, using a cleaner to remove obsolete, invalid, and erroneous entries does not affect system performance but it can result in "unpredictable results
Unless you have a particular problem that requires a registry edit to correct it, I would suggest you leave the registry alone. Using registry cleaning tools unnecessarily
could lead to disastrous effects on your operating system such as preventing it from ever starting again. For routine use, the benefits to your computer are negligible while the potential risks are great
The first time I powered up I ended up in chkdsk on boot up
is a disk error checking utility that verifies the logical integrity of a file system. As you use your hard drive, it can develop bad sectors which slow down hard disk performance and make data writing difficult. Chkdsk scans the hard drive and will check the files and folders for file system errors, lost clusters, lost chains, and bad sectors. When encountering logical inconsistencies in file system data, it will perform the necessary actions to repair the file system data. The equivalent utility in earlier versions of Windows was called ScanDisk
Chkdsk will create and display a status report for a disk based on the file system and will list and correct errors on the disk. If used without parameters
, chkdsk displays the status of the disk in the current drive. Chkdsk scans the disk structures and disk surface for possible errors and inconsistencies in separate phases. During the first few phases, it checks the FAT or NTFS for lost clusters, cross-linked files and inconsistent directories. When these steps are completed, it asks you whether you want to run a full scan, during which it actually reads every single sector to prove that it is readable.
" are clusters that are neither in the free chain nor in any used file.
" are two files that both claim to use the same cluster.
Chkdsk can be run from the Windows Recovery Console (see correct way to run chkdsk)
, the command prompt
or through the Windows GUI
The main thing that keeps utilities like Chkdsk from running successfully is having other programs running in the background. Chkdsk will not check files that are being used by Windows so using Chkdsk in the Recovery Console is a way to resolve this.
Note If you specify the /r option, the /p option is implied. When you specify the chkdsk command without arguments, the command checks the current drive with no options in effect.
- The command chkdsk /p (only availabe in the Recovery Console) does an exhaustive check of the drive and corrects any errors.
- The command chkdsk /r locates bad sectors and recovers readable information. It will scan the surface of the disk for physical errors in the disk scan phase only and indicates that chkdsk should try to recover the data.
- The command chkdsk /f is available from within the Windows GUI and is the equivalent to chkdsk /p.
The Recovery Console
command paramters are explained here
. For additional command SYNTAX
, to include the Windows GUI, see here