Discussion Locked

Win2k runs chkdsk after reboot...

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've got a computer that is constantly running chkdsk after the comptuer is rebooted, even after a proper shutdown. What is even more odd is that the chkdsk program will not find a single thing wrong with the drive.
I know how to disable this problem in WinNT but the registry entry doesnt exist in Win2000.
Need HELP!

10 replies

by sixfourtykilo

Windows logs events when it has trouble writing to the disk. If there is something wrong with your disk or if there isn't, at some point in time Windows is having difficulties. Something you may try is to disable power management support for the drives. Turn it off in Windows and the BIOS. If all else fails, rebuild, or replace the HD.

Hope this helps.
640k

by c1959j

I would make sure no errors show up in the event logs. If no errors are found, try applying service pack 2. We had a similar situation and applying this service pack seemed to alleviate the problem. Hope this helps.

by kirill lozovatsky

The registry entries used by Autochk to determine which volumes get checked at boot time are:
Hkey_local_machine\System\CurrentControlSet\Control\Session Manager\ BootExecute:REG_MULTI_SZ: autocheck autochk *

This is the default setting for Autochk, restore it into this view. Follow the Microsoft article to find more:Q218461

by estebandelatorre

Hardware or software? that's the question...
Discard Hardware:
Issue a tools like Norton disk doctor to verifiy disk surface. If no reports are generated, your HW is ok.
If it is not harware, its software... So, the main reason may be a bad shutdown or a corrupted HD (discarded both!)
Try to re-install SP1 for w2k and perform a shutdown with the minimun services running (shudown them one by one, using the service manager). Watch closelely to the event log.
This should fix or isolate the problem.
Whish it helps...

by mrc.hmt

All these answers were great clues in hunting down the problem behind this, however, as I later found out after watching the user work the computer, after they clicked shut down, they immediately hit the power button causing the improper shutdown.

This discussion is closed to new replies.