|
My question is this: Why is chkdsk.exe seemingly so arbitrary, on an OS volume, as to whether is actually kicks off after reboot? On dozens of different systems across multiple versions of Windows, when I need a machine to reboot and do a pre-boot file system check, it sometimes/often takes a couple of tries to get it to take. Quite often, said machine boots right into the login prompt / desktop, and never even pauses to show the black-and-white "press any key to cancel" screen. Granted, sometimes it works the first time, but it does the opposite enough that I've decided to ask about it. It doesn't seem to matter whether it's from a admin-elevated command prompt or the My Computer -> right-click drive -> Properties -> Tools method. Sometimes times it will happen and often it won't until the second, or fourth, attempt. Am I: a) specially cursed? b) blind/missing something? c) as frustrated as you by this? (Note I am not talking about the black-and-white "Checking file system" screen appearing and immediately cancelling itself. I'm talking about BIOS splash -> Windows boot animation -> login/desktop, no interruption.)
|
#
?
Dec 6, 2014 05:20
|
|
|
|
| # ? Apr 25, 2024 10:26 |
|
|
No one else has this problem?
|
|
#
?
Dec 14, 2014 05:21
|
|
|
I have never had your problem, checked around with the first liners and they haven't either. Sorry man.
|
|
#
?
Dec 14, 2014 11:25
|
|
|
I also have never seen or heard of this. I always invoke CHKDSK with the following command from an administrative command prompt: CHKDSK C: /F /V Then answer yes that I want to check the volume at next boot, and it always does.
|
|
#
?
Dec 14, 2014 18:30
|
|
|
Lol
|
|
#
?
Dec 16, 2014 15:44
|
|
|
Alereon posted:I also have never seen or heard of this. I always invoke CHKDSK with the following command from an administrative command prompt: At my work I have to run that command a couple times a week at least, and if I ask the drive to perform the check on itself during reboot it's really not all that reliable. What I've taken to doing is just loading HBCB on to a thumb drive, booting in to mini-XP and running chkdsk on there. That works every time.
|
|
#
?
Dec 16, 2014 20:04
|
|
|
Interesting replies. I am glad to know: 1) that I am not the only one on Earth to seem to notice this and 2) that the problem is not as common as otherwise I'm counting usages until I see it happen again.
|
|
#
?
Dec 17, 2014 06:40
|
|
|
I wonder if it could be related to antivirus or other similar software trying to load early in the boot process?
|
|
#
?
Dec 17, 2014 07:39
|
|
|
|
| # ? Apr 25, 2024 10:26 |
|
|
If CHKDSK C: /F fails to work for me I usually flag the volume as dirty: fsutil dirty set C: That works almost every time. If it fails to check, look at the BootExecute registry key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager). I have seen a few machines that chkdsk would not run at boot time because AVAST felt the startup scanner was more important then chkdsk.
|
|
#
?
Dec 17, 2014 21:46
|
|
