Search the Community

Anybody else run into this problem? Normally, if you run chkdsk /f, and reboot, it runs it in that smaller blue console window, and then after completion finally boots up into Windows. Not doing that here anymore, for some reason. My disk Volume is "clean" (dirty bit is off). And the normal runs of chkdsk are pretty good (I get the "correcting errors in the volume bitmap" stuff, but nothing really outrageous here) So now what I notice (after having run chkdsk /f once) is that takes a noticably longer amount of time to finish booting up into Windows. And then if I reboot, it does the same thing again - takes a longer amount of time (than normal) to finish booting up (I can hear disk activity in the background, so evidently Task Manager is still trying!). So evidently it (chkdsk /f) is not ever running to completion. I am able to "fix" this problem by restoring the previous ERUNT backup made prior to running chkdsk /f. And of course, this whole scenario is repeatable. So far I haven't found any articles covering THIS specific problem (although there are several articles on problems with chkdsk, however) So apparently, "autochk.exe" is not able to succesfully run in the console mode after rebooting, but still even tries to as Windows boots up (since there is noticeable disk activity and it takes so long! Weird.