Windows 10: Volume - c: is Dirty but not when I check in Windows Recovery Environment

On every startup, my computer asks if I want to press any key to skip disk checking C: . I have followed the usual advice of pressing shift-restart to boot in Windows Recovery Environment, and using the command prompt and typing:chkdsk C: /f /rletting that finish, and restarting my computer. But when I restart my computer, the same message of skip disk checking is still there. Even more confusing is, when I type:fsutil dirty query C: in Windows Recovery Environment, it says that Volume - c: is not dirty. But when I try to type that same command in the command prompt in normal Windows 10, it sa

:)

 

Dirty drive

It's showed 'Volume - c: is NOT Dirty' in the Windows Recovery Environment.

Then I clicked on continue to windows 11. I opened cmd and typed fsutil dirty query c: to see if it actually worked or not, It still shows the Volume - c: is Dirty

 

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

Hi sYn

Click the Power Button on your Start Menu

Press the Shift Key and click Restart

Your PC will boot into the Windows Recovery Environment

Go to Troubleshoot - Advanced Options - Command Prompt

Then run this command: chkdsk C: /f /r

Let that complete and restart your PC, then check if the dirty bit on your hard drive is still set to dirty:

fsutil dirty query c:

 

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