[SOLVED] Computer scanning C: drive every startup

[Tacatun]

Every startup my PC will attempt to scan and repair the C: drive but never actually does. During startup it will count down to the disk check but windows will start normally before the countdown even finishes.

I have followed the instructions at the following links to no success.
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-runs-scanning-and-repairing-c-on-every/77f8cf15-7c33-4f96-ba6e-8bc9280d5d54
https://answers.microsoft.com/en-us/windows/forum/all/scanning-and-repairing-unit-c-on-every-boot/74829847-4fa3-402b-b651-8271567d19b3

The only thing I noticed is that when running "chkdsk C: /f /r" as per the second link, it would freeze on stage 4.

Any suggestions on what to do next?

 

[johnbl]

you can run cmd.exe as an admin then run
fsutil.exe dirty query c:
to see if the dirty bit is set.

if it is set then on each boot chkdsk will run.
if chkdsk fails to complete the bit does not get reset.
you have to run a special chksdk command to fix this. I will see if i can find it.

------------
you might try:

• chkntfs C: (It shows whether your system has scheduled a check scan on the C: drive)
• chkntfs /x C: (to cancel the schedule)

I only had this problem one time and I do not recall the fix.
I think in involved doing a offline scan and offline fix option.
on the chckdsk command line.
chkdsk | Microsoft Learn
something like
chkdsk c: /f /scan /forceofflinefix

if you know what failed you can skip that checking using the ckddsk options.
in my case the problem came back until i fiqured out I needed a ssd firmware update to fix a cache problem that messed up the file system.

chkdsk phase 4 verifies that all of the clusters are usable.
you might want to skip this.
ChkDsk Process on NTFS Volumes - Windows 7 Tutorial (sourcedaddy.com)

windows will do this as a idle time background check in the system process. (can take days) SSD firmware will also do cleanup after 5 minutes of idle (before it goes to sleep)

 

[Fix_that_Glitch]

What does the health status look like?

 

[johnbl]

you can run cmd.exe as an admin then run
fsutil.exe dirty query c:
to see if the dirty bit is set.

if it is set then on each boot chkdsk will run.
if chkdsk fails to complete the bit does not get reset.
you have to run a special chksdk command to fix this. I will see if i can find it.

------------
you might try:

• chkntfs C: (It shows whether your system has scheduled a check scan on the C: drive)
• chkntfs /x C: (to cancel the schedule)

I only had this problem one time and I do not recall the fix.
I think in involved doing a offline scan and offline fix option.
on the chckdsk command line.
chkdsk | Microsoft Learn
something like
chkdsk c: /f /scan /forceofflinefix

if you know what failed you can skip that checking using the ckddsk options.
in my case the problem came back until i fiqured out I needed a ssd firmware update to fix a cache problem that messed up the file system.

chkdsk phase 4 verifies that all of the clusters are usable.
you might want to skip this.
ChkDsk Process on NTFS Volumes - Windows 7 Tutorial (sourcedaddy.com)

windows will do this as a idle time background check in the system process. (can take days) SSD firmware will also do cleanup after 5 minutes of idle (before it goes to sleep)

 

[Tacatun]

you can run cmd.exe as an admin then run
fsutil.exe dirty query c:
to see if the dirty bit is set.

if it is set then on each boot chkdsk will run.
if chkdsk fails to complete the bit does not get reset.
you have to run a special chksdk command to fix this. I will see if i can find it.

------------
you might try:

• chkntfs C: (It shows whether your system has scheduled a check scan on the C: drive)
• chkntfs /x C: (to cancel the schedule)

I only had this problem one time and I do not recall the fix.
I think in involved doing a offline scan and offline fix option.
on the chckdsk command line.
chkdsk | Microsoft Learn
something like
chkdsk c: /f /scan /forceofflinefix

if you know what failed you can skip that checking using the ckddsk options.
in my case the problem came back until i fiqured out I needed a ssd firmware update to fix a cache problem that messed up the file system.

chkdsk phase 4 verifies that all of the clusters are usable.
you might want to skip this.
ChkDsk Process on NTFS Volumes - Windows 7 Tutorial (sourcedaddy.com)

windows will do this as a idle time background check in the system process. (can take days) SSD firmware will also do cleanup after 5 minutes of idle (before it goes to sleep)

Tried your solution and others to no success. However, in the end it was an SSD firmware issue as you mentioned. Thank you for your help!