This question already has an answer here:
My windows chkdsk every boot. How to disable that?
|
This question already has an answer here: My windows |
|||
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
|
Go to run type |
|||
|
|
|
As grawity said, fix the problem. Since you say that chkdsk reports no errors, then your drive is probably on its last legs. Replace it now before it's too late. |
|||||||
|
|
This is most likely caused by a failure to unmount a volume when chkdsk was originally set to run - you now have what we call a "dirty" drive. There are a number of ways to fix this so here is what I'd do in this case: Use the Registry Editor to check and change a value:
Change the BootExecute entry from:
To:
Or do this: Start → Run → bring up a Command Prompt by typing in “CMD” (make sure it is running elevated... i.e. as administrator) and type:
Press Enter. This queries the drive, and more than likely it will tell you that it is dirty. Next, type:
Press Enter. The X tells Windows to NOT check that particular drive (c:) on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows. Once Windows has fully loaded, bring up another CMD prompt (elevated) and now you want to do a Chkdsk manually by typing:
This should take you through 5 stages of the scan and will unset that dirty bit. Reference: There was an old issue with Windows 7 and Avira AV software, not sure if this applies to you, surely it has been fixed by now.
Viruses are also known to cause this condition. You may be infected. Follow the order given below to properly disinfect your PC:
These last two are not AV software like Norton - they are on-demand scanners that only scan for nasties when you run the program and will not interfere with your installed AV. They can be run daily or weekly to ensure you are not infected. Be sure you update them before each scan. |
||||
|
|
|
Windows Update fixed my problem in February. It was before the Windows 7 SP1 update. |
|||
|
|
chkdskeven after a clean shutdown/reboot, there's likely to be some corruption... Does it report any errors after doing the checks? – grawity Jan 19 '11 at 11:02