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.

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

Siegfriedm said:

...when I restart PC, nothing happens. I tried it twice, doesn't work.

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:.

@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

NOTE: You will be replacing autocheck autochk /p \??\C: with autocheck autochk* instead. If BootExecute already has a Data value of autocheck autochk *, then you do not need to do this.

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.

Bree said:

@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,

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

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!