Windows 10: Windows keep running chkdsk on my C: drive during startup, but always skips the process

It has been around two weeks since my laptop started to do an automatic check on my C: drive every startup, but somehow it never proceeds to actually check it it skips right away to the lock screen. I find this really odd because I have not force-shutdown my laptop for--at least--the last 6 months. Besides, I am pretty sure that this is not the first time my laptop did a disk check during startup, and when it does, it always continues until the process is 100% done



1st attempt of fixing this: Using the check disk tool in my C: drive's Properties menu



So I went to check my C: drive Properties and click on the "check" button in the "Tools" tab, and--as expected--it says that there are errors in my C: drive and I have to repair it, but I soon figure out that it is not possible to fix a C: drive while I am using the computer, thus, the repair can only be done during startup, but as always, when the system scans my C: drive during startup, it never actually complete the process,


2nd attempt of fixing this: Running the "chkdsk" command in cmd

After failing to check the disk in the Properties menu, I tried another method, which is to run the chkdsk command on my C: drive using cmd. I ran the "chkdsk /f /r c:" command, but as always, when my computer starts, it doesn't finish the scanning & fixing process.


3rd attempt of fixing this: Replacing autochk.exe in System32

I initially thought the autochk.exe in my laptop is corrupted but when I ran the "sfc /scannow" command in cmd, it finds "no integrity violation". I also have tried replacing my autochk.exe from another computer but it doesn't fix anything.



Running the "chkdsk" command in a read-only mode



I then tried to run the chkdsk command in a read-only mode without /f or /r and oddly, it says that "Windows has scanned the file system and found no problems. No further action is required", contrasting to what the system says when I checked the disk in the Properties menu. This is the same result as when I ran chkdsk to my D: drive which I'm certain, is healthy, bcs previously I've checked my D: drive in the Properties menu and it also said that there's no error found in it.



Long story short...

...when I checked my C: drive in the Properties menu, in the Tools tab, it says that there are errors in my disk, but when I ran the chkdsk command with cmd, it says otherwise, which leaves me with confusion on whether or not there is actually something wrong with my C: drive.


My assumption

I personally think that there is a bug that causes the system to falsely marks my C: drive as dirty, therefore, triggering autochk to check on C: during startup, but as there's no actual error in it, it skips the process, because aside from chkdsk c: didn't find any error, as I have mentioned before, there hasn't been a forced shutdown recently and I also did not feel a deterioration in my laptop's performance.


However, there's also a possibility that it's not a false positive, and therefore, I have to fix it as soon as possible before further damages happen.


I could really use some help to figure out whether or not there is actually something wrong with my C: drive

If it's just a false positive, what can I do to stop the system from running autochk during startup?

And if it is not, what is the problem and what should I do to fix it?


Thank you

:)

 

chkdsk c: /F

We appreciate the response. I'm referring to Check Disk (chkdsk) utility tool. If you haven't tried yet, we suggest that you run a chkdsk by:

• Press Windows Key + X button to bring up the power user menu.
• In the power user menu, select the Command Prompt (Admin) option.Click Yes when you are presented with a UAC window requesting permission to launch the Command Prompt as Administrator.
• In the new Command Prompt window, type chkdsk E: /f /r /x. Here you should replace E with your drive letter.

This option will run chkdsk to check and repair disk errors in Windows 10. The “/f” parameter tells CHKDSK to fix any errors it finds; “/r” tells it to locate the bad sectors on the drive and recover readable information; “/x” forces the drive to dismount
before the process starts.

Keep us updated with the result.

 

chkdsk c: /F

It might be an error on the drive. We suggests that you follow the troubleshooting steps below:

• Run Disk Cleanup utility to clear your junk files.
• Open an elevated CMD type sfc /scannow and hit Enter to run the System File Checker.
  
• Once the scan is completed, restart your computer. Remember to exit ChkDsk
  during boot.
• Next, again open CMD as admin type
  Dism /Online /Cleanup-Image /RestoreHealth and hit Enter to repair the Windows image.
• Now see if ChkDsk able to complete the scan.

Note: Before doing the steps, make sure you save a back up of your files.

Let us know how it goes.

 

chkdsk on boot drive won't run at startup

I am trying to image my boot hard drive in order to migrate the data to an ssd. The backup software (Macrium Reflect) first checks the file system, but reports an "MFT corrupt error", and indicates to run chkdsk c: /r to fix the issue. I opened power shell and attempted to run chkdsk c: /r, but of course as its a boot drive, it says it can't lock the drive and do I want to have chkdsk run after the next re-start. I indicate Yes, and then restart the PC. As expected, during boot up I get a message saying the disk check will run in like 10 seconds and it counts down. The count down reaches zero and a message indicates that it is starting the scan and repair process. However, after a few seconds, the screen goes black and a normal Windows reboot occurs. I have tried running this over ten times with various combinations of chkdsk c: /f /r /x and the result is almost always the same. Only one time did it actually start to scan the disk, but as it is a lengthy process I let it run overnight and the next morning windows 10 had restarted. I went to check the event log to see what chkdsk had done, and there was no log, almost as if it stopped and rebooted without finishing the chkdsk process.

I am running Windows 10, version 2004, OS Build 19041.685, installed 11/20/2020. The PC is a Dell XPS 8300 with a core i-5 processor and 8 GB of RAM. The hard drive is a 1 TB drive.

Messages on this forum indicated that there was a similar problem in the early 2017 time frame after a Windows update, but that it was fixed in the next release.

Any suggestions on how to solve this are appreciated.