Windows 10: Chkdsk not working?

I used the command chkdsk /f /r C: in CMD .exe running as Administrator.
I had the prompt about run it when PC restarts, but when I restart PC, nothing happens. I tried it twice, doesn't work. What I have to do?

I have Win10 x64 with Creators Update and all other updates.

:)

 

chkdsk

Nikolaos,

Best to run the CHKDSK /R overnight while sleeping. Turn off sleep mode or it may stop running. My 2TB HDD takes over five hours to complete. The /R stipulation examines all clusters/sectors and repairs damaged areas when possible. It takes a long time.

The /F stipulation is good to run before running the /R stipulation. It will mark areas of concern on the HDD that the /R stipulation will later correct

The CHKDSK /F takes only minutes to complete. Run it before the comprehensive and thorough CHKDSK /R.

If you force a shut down during a CHKDSK /R it
may resume where it left off when you reboot. You will simply have to wait for it to finish then. If it doesn't resume where it left off, then try running the /F stipulation
first without the /R stipulation to prime the system.

Are you having problems with your HDD from power outages, etc? The CHKDSK /R can certainly repair it. That is the good news.

Regards,

Wayne

 

chkdsk

Hello Ranil,

Check disk is a command that will schedule a scan on the hard disk when Windows 10 starts up. To run chkdsk
in elevated mode for Windows 10, means that you need to run as Administrator. You must run the command prompt with admin rights when you want to run
chkdsk.

Please click on this similar thread that has a helpful answer by Gerry C J Cornell on how to run
chkdsk in Windows 10.

Let us know if you need anything else. We're here to help.

 

try chkdsk c: /f /r what are you running it from as by default cmd is replaced with powershell

 

You're right. I've tried it on my 15063.138 Creators Update (twice, like you) and nothing happens. According to chkntfs c: it was scheduled to run.

Code: C:\WINDOWS\system32>chkdsk /f The type of the file system is NTFS. Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N) y This volume will be checked the next time the system restarts. C:\WINDOWS\system32>chkntfs c: The type of the file system is NTFS. Chkdsk has been scheduled manually to run on next reboot on volume C:.[/quote] @Brink has a tutorial on this on VistaForums.
https://www.vistax64.com/tutorials/1...tup-vista.html

At 'Step Two' it says use Regedit to look at BootExecute in...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

Looking at mine, I find it has both values on two separate lines!





Changing it to just autocheck autochk * doesn't restore normal functioning. Something must have run though, as chkntfs C: no longer reports a check as being scheduled and Regedit shows the original two-line value for BootExecute has returned. I'm not sure how applicable the rest of that tutorial is, there doesn't seem to be an equivalent here on TenForums.

 

@Siegfriedm, if you urgently need to run chkdsk on C: then you still can. Until there's a fix for this, there is another way to run Chkdsk /F on C: that does work.

Settings > Update & Security > Recovery > Advanced start-up
then...
Troubleshoot > Advanced options > Command prompt

Here too chkdsk will complain the disk is in use but instead of offering to schedule a check at restart it will offer to dismount the volume. Dismounted it can then run. The downside is that with C: dismounted chkdsk will not be able to write the results to the event log,

 

I have noticed this behaviour too. CHKDSK isn't triggered at boot time anymore.

 

I have justtried Chkdsk /F on my other PC, a 32-bit system. Being somewhat older and slower to boot, I briefly saw beneath the spinning dots on the black screen "Windows is checking the disk - 100%". So, something is triggered - but it doesn't run Chkdsk, as confirmed by looking for the results in the Event Log.
Read Chkdsk Log in Event Viewer in Windows 10

Running a Chkdsk command that can be run from within Windows, such as chkdsk /scan /perf c: does put its results in Event Log. It appears Chkdsk itself is in working order, but the launch at boot fails to run it.

 

So, if I don't want to dismount, I can just wait for a fix, right?

 

Oh.. noooo! my favourite MS util not working correctly?

How did they manage to break that?... was this not picked up by Insiders?

I'm sure it's an easy fix given it's just the initiation at boot that's broken, but nevertheless...

 

Works in an Admin Command console though, just tested it and it is working, Rebooted it checked C auto rebooted again with the 100% complete message, just fails if you do it through properties System Tools.

Edit: This is weird

Above works on this PC but doesn't on the other 2.

 

Same issue here, chkdsk scheduled to run but nothing happens on reboot (and the command entry stays in registry).

'Creators' don't have time to check disks, I guess! *Huh

 

Is it to do with normal shut down not restart. If you restart does it work as it may not have time if you do a normal shut down then starts?

 

It's not the Insider's responsibility to find such a basic error which is basically due to sloppy software engineering by MS.

 

I've just tried a Chkdsk C: /f after today's Cumulative Update, it now seems to be working normally again.

Cumulative Update KB4016871 Windows 10 v1703 Build 15063.296 - - Windows 10 Forums