Windows 10: When I run fsutil dirty query c: it tells me that the drive is Dirty

When I run fsutil dirty query c: it tells me that the drive is Dirty.


The computer is only a few months old.

:)

 

Dirty Bit not same state on the two possible Command Prompts

Using Windows 10. When I enter Command Prompt with holding down shift key when restarting and using fsutil dirty query c: , the Dirty Bit state is 0 or off. When I enter Command Prompt (Admin) from running the Windows program and using fsutil
dirty query c: , the Dirty Bit is 1 or on. I think the latter condition is why I always get the Disk Check running notification when booting up. I've tried everything to clear the latter mentioned Dirty Bit state but nothing works. I saw one suggestion
to use a hex editor and actually go into the Bios? to put the Dirty Bit state back to 0, but don't feel comfortable with that. The disk check using
dskchk c: /f /r in the first mentioned Command Prompt shows the disk has no problems. Why are the Dirty Bit settings different? Could this be why Macruim does not want to clone the disk?

Thanks for any help and comments.

 

FSUTIL and Windows Update Failures.

Your rant is replete with misinformation... the noted link does not point directly to a flow chart of any kind.

Your "The command (fsutil dirty querry c may not tell the whole story..." leads some one to believe there is a story to be told, which is not the case. The command - fsutil dirty query C: - simply checks to see if the volume's dirty bit is set.

If the volume is dirty, the following output displays:

Volume C: is dirty

If the volume is not dirty, the following output displays:

Volume C: is not dirty

In your example - fsutil USN deletejournal /n /d c: - the usage of both the /n and the /d parameter simply makes no sense.

Your "...some users get unknown errors, or, fictitious error codes..." is itself fiction.

 

Windows 10 Scanning and repairing drive (\\?\C continued after replacing hard disk

This is an ongoing issue with Windows 10, where it thinks there is an issue with your drive when there is not . . .

Open a Command Prompt as Administrator, run this command to attempt to clear the dirty bit on your C drive:

chkntfs /x C:

Then run this command to see if the dirty bit is cleared on the drive

fsutil dirty query C: