Windows 10: Inconsistent error warnings: Errors detected, yet no errors detected

My laptop has suddenly started running CHKDSK during startup. After it completes and finishes booting I go to Properties > Tools > Error Checking of my C drive and click “Check”. It says errors were found on this drive and to repair drive now to prevent data loss. I click to run it, the system reboots, I see the prompt to cancel CHKDSK by pressing any key, let it run, the screen remains blank with just the little spinning dots. It finishes (in less than a minute, which is faster than it usually takes) and loads to desktop. I check the C drive properties again and it still says there are errors and to repair.


Running CHKDSK from CMD prompt I get “Windows has scanned the file system and found no problems. No further action is required.” Running a 3rd-party disk checker (Disk Doctor, Tune-Up Utilities) also reports no errors. Yet the properties dialog continues to warn that there are errors.


I can’t be certain when this started. Just noticed this yesterday when I booted up (I don’t usually stick around and watch the computer boot). Windows has all the latest updates/patches. This is an HP ENVY laptop that came with Windows 10 pre-installed.


Anyone have any ideas?

:)

 

Inconsistent error warnings: Errors detected, yet no errors detected

We're glad to know that you were able to resolve the issue. Thank you for with us the steps that made it work for you. Should you ever need some help in the future, please feel free to post in the community forum again.

Regards.

 

Inconsistent error warnings: Errors detected, yet no errors detected

No worries. The moderators will do it for you.

Regards.

 

I believe I solved it.

I booted into the recovery menu and then advanced options. I chose Command Prompt then ran the command CHKDSK C: /F

At Stage 3 it found errors and repaired them:
Errors in MFT bitmap attribute
Errors in volume bitmap

Afterwards, booting up and checking the drive status it now reports no errors finally. I guess the CHKDSK procedure didn't detect these errors when running during bootup. The other disk scanners I tried didn't pick them up either. This seems to have fixed it.