Windows 10: Volume - c is Dirty. Could this be an error or is this something more serious that I should...

My PC began booting up with scanning and repairing disk C: . And so I went through the forums looking for an answer and going into the secured boot-up and opening the command console and using chkdsk c: /f /r. I was able to fix the issue of having the disk cleaning and repairing appearing on every boot-up. However whenever I use fsutil dirty query c: is still shows that the C: is dirty. Is there anything I can do to fix this or should I just ignore it as it is no longer causing me any issues. Any help would be greatly appreciated.

:)

 

Windows 10 says c: is dirty

ran fsutildirty query c:

reported volume - c: is dirty.

i restarted the system several times, it still gives me the same error.

 

Cannot clean up dirty volume in any way

Recently my laptop has started showing the "Scanning and Repairing Volume C:" message on every single boot up. After doing some research and running some scans, I discovered that my C: drive (the SSD on which Windows is installed) is "Dirty".

I have been looking for different methods of fixing it, however, I was left with the following results:

• Windows detects that there is an error on the drive, and even marks it as an "Important" security warning. It recommends the "Repair Disk" option, which reboots the PC, supposedly fixes the problems, and boots back up normally. After following this process, literally nothing changed. Volume C: is still marked as dirty, and scans are being run at every boot up.
  
• Playing around with "chkntfs" and "chkdsk" commands doesn't seem to help, either. I tried adding /f and/or /r flags (and also /x to the chkntfs one) hoping it would fix the problem, but it hasn't. After every chkdsk reboot, the "fsutil dirty query c:" result always comes back as Dirty.
  
• As this is the volume on which Windows is installed, I have 2 ways of repairing it via cmd: restarting the laptop with every check (mentioned above, doesn't work) OR via starting the cmd from the Recovery Boot Up screen: this way, I tried troubleshooting without Windows running, and therefore being able to run scans on it. The problem with this attempt was that apparently the C: volume wasn't being marked Dirty when not active. As soon as I loaded the Recovery cmd, the first command to try was "fsutil dirty query c:" and it came back as negative. After the next normal boot up though, it's dirty again.
  

I've been trying to get to the bottom of this but can't seem to find a good enough solution, maybe someone with better understanding of this topic might help me out..?

 

Is it bad if I leave Volume - c: is Dirty?

Hey Dave! Thank you for the fast response!

When i ran chkdsk C: /f /r /x it told me to chkdsk cannot run because the volume is in use by another process. would you like to schedule this volume to be checcked next restart? I do (Y)

then restart my pc and its does the repairing and scanning on startup for like 5 seconds then i sign in and we back to square 1 with volume C is dirty still.