[SOLVED] Chkdsk does nothing after reboot.

S

scottmandu

Well-known member
Joined
Oct 15, 2015
Posts
86
Location
Manitoba, Canada
I tried a chkdsk /f /r from an andminstrator command prompt and reboot. I get the countdown timer and then a message "scanning and repairing drive c:" for a couple of seconds, and it reboots. It appears chkdsk does not run. Tried sfc /scannow command and it found no issues. Tried DISM /Online /Cleanup-Image /RestoreHealth and got "The restore operation completed successfully.The operation completed successfully." message. When I try chkdsk again i get the same behaviour. Any ideas?
 
Open administrative command prompt and type or copy and paste:

shutdown /r /o /f /t 00

When the computer reboots into Windows Recovery Environment (RE) > open command prompt > type: chkdsk /r /v > reboot as needed
 
Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

Following command will fixes errors on the disk and locates bad sectors and recovers readable information.


Code: 
Chkdsk C: /r



Please replace partition letter C: with Windows installed partition letter. When the computer boots into Windows Recovery Environment (WinRE) environment, the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assigned any other drive letter, usually D: drive letter is assign to Windows installed partition. The Bcdedit | find "osdevice" command can be used to find out the drive letter of the Windows installed partition, the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.
 
Before we delve into anything further, let's actually check the logs from the last run.

1. Download ListChkdskResult.exe by @SleepyDude and save it on your desktop.
2. Right-click this file and select Run as administrator (Allow if prompted) and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post.

Could you please also open an elevated command prompt window and enter the following command:

Rich (BB code): 
fsutil dirty query c:

May I also ask why you're running chkdsk to begin with?
 
x BlueRobot said:
Before we delve into anything further, let's actually check the logs from the last run.

1. Download ListChkdskResult.exe by @SleepyDude and save it on your desktop.
2. Right-click this file and select Run as administrator (Allow if prompted) and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post.

Could you please also open an elevated command prompt window and enter the following command:

Rich (BB code): 
fsutil dirty query c:

May I also ask why you're running chkdsk to begin with?
Click to expand...
Attached is my ListChkdskResult.txt. I get the message "Volume - c: is NOT Dirty". I run chksdk every couple of months or so just to fix issues.
 

Attachments

scottmandu said:
Attached is my ListChkdskResult.txt. I get the message "Volume - c: is NOT Dirty". I run chksdk every couple of months or so just to fix issues.
Click to expand...
Still have the same issue of when implementing a chkdsk command from the command line and rebooting. The timer counts down, I get the "scanning and repairing drive c:" for a couple of seconds, and it reboots immediately without actually doing anything.
 
Were you able to run chkdsk from either:
a) bootable flash drive (Media Creation Tool)
b) the computer's Windows Recovery Environment (RE)

Run the deepest chkdsk switch from Windows RE on the computer or the bootable flash drive and see if it makes any difference:
chkdsk /b /v
 
Make sure that the chkdsk switches are run the the Windows drive:

use bcdedit | find "osdevice"

or

C:
dir
D:
dir
E:
dir
 
So, it seems that most of the time you've run chkdsk it hasn't found any problems hence why it will make no attempt to repair anything. This is also why your dirty bit is not set.

Rich (BB code): 
Windows has scanned the file system and found no problems.
No further action is required.

Honestly, there is no reason to run chkdsk every few months, at best, you're simply going to be erasing some old index files and other metadata. When there is legitimate worthwhile corruption, then the dirty bit will be set and the operating system will request to run chkdsk at boot.

There was a couple of times yesterday where it claimed to find errors - literally just old index entries - however the latest run indicates that no errors were found. The check was run in scan mode only it seems and ran for 2 minutes?

Rich (BB code): 
Category: 0
Computer Name: LIVERNUGGET
Event Code: 26226
Record Number: 109889
Source Name: Chkdsk
Time Written: 08-21-2022 @ 04:35:01
Event Type: Information
User: 
Message: Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on C:
Volume label is Windows 10.

Rich (BB code): 
Total duration: 2.05 minutes (123381 ms).
 
On the earlier runs it seems that you also ran chkdsk in readonly mode as well?

Rich (BB code): 
Category: 0
Computer Name: LIVERNUGGET
Event Code: 26213
Record Number: 109584
Source Name: Chkdsk
Time Written: 08-20-2022 @ 05:39:01
Event Type: Information
User: 
Message: Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.

Rich (BB code): 
Errors found.  CHKDSK cannot continue in read-only mode.
 
x BlueRobot said:
So, it seems that most of the time you've run chkdsk it hasn't found any problems hence why it will make no attempt to repair anything. This is also why your dirty bit is not set.

Rich (BB code): 
Windows has scanned the file system and found no problems.
No further action is required.

Honestly, there is no reason to run chkdsk every few months, at best, you're simply going to be erasing some old index files and other metadata. When there is legitimate worthwhile corruption, then the dirty bit will be set and the operating system will request to run chkdsk at boot.

There was a couple of times yesterday where it claimed to find errors - literally just old index entries - however the latest run indicates that no errors were found. The check was run in scan mode only it seems and ran for 2 minutes?

Rich (BB code): 
Category: 0
Computer Name: LIVERNUGGET
Event Code: 26226
Record Number: 109889
Source Name: Chkdsk
Time Written: 08-21-2022 @ 04:35:01
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot. 

Checking file system on C:
Volume label is Windows 10.

Rich (BB code): 
Total duration: 2.05 minutes (123381 ms).
Click to expand...
The read only scans were ran when I was playing with Aomei partition assistant where you can run chksdk within it. I know you can do it form a command line as well. I always thought that if you a ran a chksdk c: /f /r from a command prompt and rebooted....you would get a coundown timer...and then a "scanning and repairing drive c:" and then some other messages about the percentage progress for the five chksdk stages. It went quick if there werent any problems, and substantially longer if there issues. Now I dont get any information about the progress of stages. Is this normal?
 
scottmandu said:
Now I dont get any information about the progress of stages. Is this normal?
Click to expand...
No, you should get the progress messages still. I'm wondering if the partition assistant has done something to your partition which is preventing chkdsk running correctly? It seems that when you've attempted to run chkdsk from boot, the partition is still locked in read-only mode.

Could you please open an elevated command prompt and enter the following commands pressing enter in-between each one:

Rich (BB code): 
diskpart
list disk
select disk #
attributes disk


Please post the output in your next post. Please remember to change the # to the disk you wish to view.
 
x BlueRobot said:
No, you should get the progress messages still. I'm wondering if the partition assistant has done something to your partition which is preventing chkdsk running correctly? It seems that when you've attempted to run chkdsk from boot, the partition is still locked in read-only mode.

Could you please open an elevated command prompt and enter the following commands pressing enter in-between each one:

Rich (BB code): 
diskpart
list disk
select disk #
attributes disk

Please post the output in your next post. Please remember to change the # to the disk you wish to view.
Click to expand...
The Disk 0 is my SSD C: drive.


Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: LIVERNUGGET

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 223 GB 1024 KB
Disk 1 Online 931 GB 13 MB
Disk 2 Online 1863 GB 1024 KB
Disk 3 No Media 0 B 0 B
Disk 4 No Media 0 B 0 B
Disk 5 No Media 0 B 0 B
Disk 6 No Media 0 B 0 B

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> attributes disk
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No

DISKPART>
 
That seems to be okay to me, I would suggest removing the partition assistant tool for now and then trying chkdsk again. It's possible that one of it's drivers has injected itself into the storage stack and when chkdsk is ran, it goes and locks the disk to read-only mode.

Could you also please open a command prompt window and then the following command:

Rich (BB code): 
reg query HKLM\SOFTWARE\Microsoft\chkdsk /s

I doubt that anything has been modified here but it's worthwhile checking.

Also, you don't need to use /f and /r together, since /r includes the functionality of /f. The following is suffice:

Rich (BB code): 
chkdsk c: /r
 
x BlueRobot said:
That seems to be okay to me, I would suggest removing the partition assistant tool for now and then trying chkdsk again. It's possible that one of it's drivers has injected itself into the storage stack and when chkdsk is ran, it goes and locks the disk to read-only mode.

Could you also please open a command prompt window and then the following command:

Rich (BB code): 
reg query HKLM\SOFTWARE\Microsoft\chkdsk /s

I doubt that anything has been modified here but it's worthwhile checking.

Also, you don't need to use /f and /r together, since /r includes the functionality of /f. The following is suffice:

Rich (BB code): 
chkdsk c: /r
Click to expand...
Here are the results:
Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>reg query HKLM\SOFTWARE\Microsoft\chkdsk /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan
HarddiskVolume1 REG_DWORD 0x0
HarddiskVolume8 REG_DWORD 0x0
HarddiskVolume3 REG_DWORD 0x0
HarddiskVolume7 REG_DWORD 0x0
HarddiskVolume9 REG_DWORD 0x0
HarddiskVolume4 REG_DWORD 0x0
HarddiskVolume5 REG_DWORD 0x0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Verify
HarddiskVolume1 REG_DWORD 0x0

I am going to uninstall my Aomei partition assistant. I also updated my Easeus Todo Backup not long ago that creates a bootable preOS...I will uninstall that too.
 
scottmandu said:
Here are the results:
Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>reg query HKLM\SOFTWARE\Microsoft\chkdsk /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan
HarddiskVolume1 REG_DWORD 0x0
HarddiskVolume8 REG_DWORD 0x0
HarddiskVolume3 REG_DWORD 0x0
HarddiskVolume7 REG_DWORD 0x0
HarddiskVolume9 REG_DWORD 0x0
HarddiskVolume4 REG_DWORD 0x0
HarddiskVolume5 REG_DWORD 0x0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Verify
HarddiskVolume1 REG_DWORD 0x0

I am going to uninstall my Aomei partition assistant. I also updated my Easeus Todo Backup not long ago that creates a bootable preOS...I will uninstall that too.
Click to expand...
I uninstalled Aomei and Easus and there is no change. I get chkdsk messages after a reboot of my other drives...just not my boot c: drive.
 
Did a chkdsk c: /r and rebooted and then selected safe mode. The chkdsk ran normally with messages but booted normally. Tried again without safe mode and chkdsk does not run and there are no progress messages.
 
The fact that it runs within Safe Mode but not in normal mode would still suggest that a setting has been configured somewhere. Let's remove those registry values from the chkdsk subkey using FRST.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

x BlueRobot said:
The fact that it runs within Safe Mode but not in normal mode would still suggest that a setting has been configured somewhere. Let's remove those registry values from the chkdsk subkey using FRST.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
Click to expand...
Here are the contents of Fixlog.txt

Fix result of Farbar Recovery Scan Tool (x64) Version: 15-08-2022
Ran by Scott (25-08-2022 21:56:17) Run:3
Running from C:\Users\Scott\Desktop
Loaded Profiles: Scott
Boot Mode: Normal
==============================================

fixlist content:
*****************
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Verify|HarddiskVolume1

DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume1
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume3
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume4
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume5
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume7
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume8
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume9
*****************

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Verify\\HarddiskVolume1" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume1" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume3" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume4" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume5" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume7" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume8" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume9" => removed successfully

==== End of Fixlog 21:56:17 ====
 
scottmandu said:
Here are the contents of Fixlog.txt

Fix result of Farbar Recovery Scan Tool (x64) Version: 15-08-2022
Ran by Scott (25-08-2022 21:56:17) Run:3
Running from C:\Users\Scott\Desktop
Loaded Profiles: Scott
Boot Mode: Normal
==============================================

fixlist content:
*****************
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Verify|HarddiskVolume1

DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume1
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume3
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume4
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume5
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume7
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume8
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan|HarddiskVolume9
*****************

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Verify\\HarddiskVolume1" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume1" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume3" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume4" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume5" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume7" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume8" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\chkdsk\Scan\\HarddiskVolume9" => removed successfully

==== End of Fixlog 21:56:17 ====
Click to expand...
Tried a chkdsk c: /r at an administrator command prompt and rebooted...and still dont get chkdsdk messages.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top