Windows 10: Drive is marked as dirty after each reboot

Hi,after the installation of 22H2 last week my drive C: constantly marks as dirty, with the permanent check every startup. Disk is Samsung SSD 970 EVO Plus 500GB and it is absolutely good.What can cause that odd behavior?

:)

 

Marking disk a dirty.

I know that you can use Fsutil to mark a volume as dirty. This in turn has the autochk run on the selected volume. But I was wondering if there was a way to mark the whole drive for chkdsk during the next reboot. Oh, this has to be done via cmd and one line commands. We use a client management software that allows the remote execution of cmd style commands. Thanks for the help.

 

Marking disk a dirty.

Welcome to the forum. Marking the disk dirty it should test the whole drive on start

 

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