Dirty-Bit Set !

[Toppack]

We encountered a problem that 'chkdsk.exe' was running at Every boot-up,

and could Not find an easy way to disable it.

I found that by running 'cmd.exe' (command-prompt) and then running 'chkntfs.exe' with the command chkntfs /X C: ,

to disable chkdsk from running every time,

and then scheduled a run of 'chkdsk c: /f', at next boot-up, which I thought reset the 'Dirty-Bit'. :grin:

 

(I don't know what caused it to be 'set' in the Registry,

I was using that computer to test new hardware but no software-drivers were installed)

 

Dirty-bit is what it is Really called. :wink:

 

See Info about 'chkntfs' utility:

http://support.microsoft.com/kb/160963

 

Note - 'chkntfs' commands react differently on different OSs

[Toppack]

Well, I found that the Dirty-bit was Not Reset and there appears to be No way to do it, short of re-formatting the drive.

So I guess the query to the C: drive, at boot-up, will just remain Disabled on that computer, until I replace or format the boot-drive. :sad:

 

Note - Chkdsk /r can Not find any problems with that drive, ran it twice

and sfc /scannow did Not find any problems with drive

[enoskype]

Hi Toppack,

 

Did you have a chance to read fsutil dirty query C: post?

 

You may find that information useful.

 

Cheers.

[Toppack]

Hi Toppack,

 

Did you have a chance to read fsutil dirty query C: post?

 

You may find that information useful.

 

Cheers.

 

That tells about the command to 'SET' the Dirty-bit, using 'fsutil dirty set', (so chkdsk will run at bootup),

but Not a way to 'RESET' it, which is what I need to do.

 

I also tried manually changing data in the Registry, using regedit.exe Editor,

using path Info I found on Internet,

but that did not reset either. :-(

 

Note - evidently once it gets Set, there is no command to Reset it,

If there is, No-one seems to know where it is ???

[Toppack]

I'm not sure but from what I've read, I'm starting to think something in AVG-2013 Security program is the software that Set the Dirty-bit,

but I don't know how or why yet.

It may be because that is a Clone replacement drive and AVG thinks there is something wrong with it,

since it is different drive than the original.

But the strange thing is that it has been about 10 days since I replaced the drive,

without any chkdsk problems until now.

[Toppack]

I found one guy on Internet that said he was able to fix this problem

by using partition-resizing software, such as Partition-Manager or Partition-Magic,

to change the partition Size slightly,

to do the Reset, since it sort of does a re-format.

(then change it back to original size if needed)

 

I may try this sometime soon, if I can't find a better way.

[Toppack]

I could Never find a way to reset the Dirty-bit. :roll:

So, I Re-formated that drive and I'm now using it as a Clone-backup. :-D

[enoskype]

Hi Toppack

 

Just out of curiosity, did you try chkdsk /f for that specific drive from the elevated Command Prompt for the next startup of Windows to reset the Dirty-bit of the drive? Anyway, I think it is too late now since you have reformatted the drive.

 

Cheers.

[Toppack]

Hi Toppack

 

Just out of curiosity, did you try chkdsk /f for that specific drive from the elevated Command Prompt for the next startup of Windows to reset the Dirty-bit of the drive? Anyway, I think it is too late now since you have reformatted the drive.

 

Cheers.

 

Yes, I tried that and All the other utilities I could think of

and none of them touched it.

I ckecked on line for info, to see if it was even possible, without editing the Registry code, and found No way.

So, decided to Format instead of editing Registry code, since I had a good drive to replace it, with no problems.

Oh well, the drive is Happy in it's new duty as a Clone

and I'm Happy too. :-D