T wrote:
Hi All,

I had a customer yesterday with a crashed Windows Nein,
oops Windows Ten update. I did my magic and got him
back to norm. The last thing that did to work
was a constant chkdsk at bot, due to a dirty NTFS flag.

Now this information is indeed all over the web, but I am
posting it here because I get straight to the point
(I am not paid by the word).

By the way chkdsk is "suppose" to clear the dirty flag, but
doesn't always work.

-T

Here are my notes:


To stop a scheduled or repeating chkdsk at boot:

Reference:
http://www.thewindowsclub.com/check-...tartup-windows


1) modify the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\BootExecute

change
autocheck autochk * /r\DosDevice\C:
to
autocheck autochk *


2) If it is already set that way, the NTFS dirty flag may be set.

Windows: to check the dirty flag:
fsutil dirty query g:


Windows: presuming the issue is with the C: drive:
Note: must be run from an Administrators CMD shell:
CHKNTFS /X C:

Linux:
# ntfsfix -d device (/dev/sda1)

Yes, somebody figured out where the Dirty bit is
stored, so we no longer have to be held hostage :-)

Note that Linux, on some operations, sets the Dirty bit
on purpose, with the intention of forcing an invocation of
CHKDSK when Windows runs. So that bit does get a good workout
at times.

Paul