Cannot reset Volume Dirty Flag

L

Larry

On my Thinkpad T60 I have a 100Gb SATA Drive with one primary partition (&
the standard Recovery Partition). I am running WinXP Pro with Service Pack
3. When I try to DEFRAG the C:\ Drive I get a message that DEFRAG cannot run
due to a pending CHKDSK /f. When I check the volume Status "fsutil dirty
query C:" I find that "C: > DIRTY" I have run CGKDSK at least a dozen times,
the full 5 phases and they all complete normally with no errors found.
However, the DIRTY flag never gets reset.
In addition, I have run diagnostics (Drive fitness Test), no errors on the
drive.
Does anyone have any ideas as to how this can be reset without having to
reformat and reinstall?
Thank you,
Larry
 
J

Jose

On my Thinkpad T60 I have a 100Gb SATA Drive with one primary partition (&
the standard Recovery Partition).  I am running WinXP Pro with Service Pack
3.  When I try to DEFRAG the C:\ Drive I get a message that DEFRAG cannot run
due to a pending CHKDSK /f.  When I check the volume Status "fsutil dirty
query C:" I find that "C: > DIRTY" I have run CGKDSK at least a dozen times,
the full 5 phases and they all complete normally with no errors found.  
However, the DIRTY flag never gets reset.
In addition, I have run diagnostics (Drive fitness Test), no errors on the
drive.
Does anyone have any ideas as to how this can be reset without having to
reformat and reinstall?
Thank you,
Larry
Click to expand...

Assuming your drive is NTFS, from your command prompt, try:

chkntfs c: (tells you if the drive is dirty or not, what does it
say?)

chkntfs /x c: (unmount the drive - enter Y if prompted)

* Notice - this is chkNTFS...

Reboot, try again!
 
N

nass

Larry said:
On my Thinkpad T60 I have a 100Gb SATA Drive with one primary partition (&
the standard Recovery Partition). I am running WinXP Pro with Service Pack
3. When I try to DEFRAG the C:\ Drive I get a message that DEFRAG cannot run
due to a pending CHKDSK /f. When I check the volume Status "fsutil dirty
query C:" I find that "C: > DIRTY" I have run CGKDSK at least a dozen times,
the full 5 phases and they all complete normally with no errors found.
However, the DIRTY flag never gets reset.
In addition, I have run diagnostics (Drive fitness Test), no errors on the
drive.
Does anyone have any ideas as to how this can be reset without having to
reformat and reinstall?
Thank you,
Larry
Click to expand...

Hi larry,
Try the system File utilities Fsutil.exe to reset the dirty flag on your HDD
secotors.

Microsoft Windows XP - Fsutil
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx

Error messages when you try to gain access to an NTFS volume
http://support.microsoft.com/kb/311724

File System Utility- Fsutil.exe
http://commandwindows.com/fsutil.htm

HTH,
nass
 
J

Jose

I do not see any option in CHKDSK to reset the DIRTY Flag
Thank you, Larry
Click to expand...

The correct way to clear the dirty bit on an NTFS volume is to let
chkdsk do it. The volume is dirty for a reason and that reason needs
to be dealt with.

The fsutil, etc. lets you query or set the dirty bit, but not clear it
(or reset it).

Why would you even want to somehow clear it if you could knowing there
was a problem?

Did you try what I suggested earlier to get chkdsk to run on startup
(like it should)?
 
T

Tim Meddick

Nass,
while the 'fsutil' command can set the 'dirty flag' for a NTFS
volume - it cannot, however, re-set or 'clear' the 'dirty bit'. For
that, you are supposed to run chkdsk on the volume and that will clear
it. ...or is supposed to under normal circumstances.


==

Cheers, Tim Meddick, Peckham, London. :)
 
J

Jose

Nass,
          while the 'fsutil' command can set the 'dirty flag' for a NTFS
volume - it cannot, however, re-set or 'clear' the 'dirty bit'.  For
that, you are supposed to run chkdsk on the volume and that will clear
it. ...or is supposed to under normal circumstances.

==

Cheers,    Tim Meddick,    Peckham, London.    :)
Click to expand...

Didn't I just say that?!

If the drive is dirty, chkdsk should run at startup.

If the drive is dirty and chkdsk does not run at startup, do what I
said before.
 
J

ju.c

How to reset chkdsk to the default behaviour:

Open the Run box and enter: cmd
In the command window type: chkntfs /d


ju.c


Tim Meddick said:
Nass,
while the 'fsutil' command can set the 'dirty flag' for a NTFS
volume - it cannot, however, re-set or 'clear' the 'dirty bit'. For
that, you are supposed to run chkdsk on the volume and that will clear
it. ...or is supposed to under normal circumstances.


==

Cheers, Tim Meddick, Peckham, London. :)
Click to expand...
 
T

Tim Meddick

"ju.c",
I am not the Original Poster!

In the post you have replied to, I was commenting on "nass" 's
suggestion that the OP use 'fsutil' to re-set drive C:'s 'dirty flag'
and clear it. This cannot be done with the 'fsutil' command. While
you can QUERY the current status and also SET the 'dirty flag', there is
no option to 'clear' or 're-set' the flag with this command....

Personally, I knew about the default settings of the 'Bootexecute'
registry value, and the various ways to set [re-set] them.

==

Cheers, Tim Meddick, Peckham, London. :)




ju.c said:
How to reset chkdsk to the default behaviour:

Open the Run box and enter: cmd
In the command window type: chkntfs /d


ju.c
Click to expand...
 
A

Arthur Shapiro

I have run CGKDSK at least a dozen times,
the full 5 phases and they all complete normally
Click to expand...

I suffered with this for months with my backup desktop machine. None of the
usual suggestions worked - the drive always came up from a boot as being
dirty, with the time-consuming nuisance of CHKDSK as a result.

I finally got annoyed enough to reinstall Windows on top of itself, thus not
losing anything - profiles, installed programs, etc, etc. I was pleased to
find that this permanently eliminated the problem.

As "they" don't publish much information (as far as I can tell) about what the
dirty bit actually is, and where it resides on a system, it becomes impossible
to know what actually got fixed. But it worked for me.

Art
 
N

nass

Hi Tim,
Me Either not the original Poster lol
When I gave Larry the 'fsutil' command utility not to check or repair the
HDD consistency or repair corrupt/damaged Sectors or system files for that
matter! I give it to him to reset the volum for dirty bits which in turn will
make the ((/* Autochk */)) to start on start up which he having problem with
running the system file checker.
Hence his saying" Does anyone have any ideas as to how this can be reset
without having.."

If you don't like Ju.c to reply/correct you, don't try to reply correct
other. It goes both ways. I don't mind people criticize me on the bases of
Constructive criticism not a destructive one, which will be met with a
ripping heads and tearing the person apart (logically on the internet).

I don't mean you or mean to offend you, just saying it in general no body
meant behind it. It is nice to share info and no one above the stage of
learning and knowing something new. If you said you know everything then you
are a lair, if you said I do learn then you know more!!!

Please take this with an open mind, no offence meant to you or anyone here.
Nice to have both of you on board to share knowledge and info. I'm always a
learner...

HTH,
nass

Tim Meddick said:
"ju.c",
I am not the Original Poster!

In the post you have replied to, I was commenting on "nass" 's
suggestion that the OP use 'fsutil' to re-set drive C:'s 'dirty flag'
and clear it. This cannot be done with the 'fsutil' command. While
you can QUERY the current status and also SET the 'dirty flag', there is
no option to 'clear' or 're-set' the flag with this command....

Personally, I knew about the default settings of the 'Bootexecute'
registry value, and the various ways to set [re-set] them.

==

Cheers, Tim Meddick, Peckham, London. :)




ju.c said:
How to reset chkdsk to the default behaviour:

Open the Run box and enter: cmd
In the command window type: chkntfs /d


ju.c
Click to expand...
Click to expand...
 
J

Jose

I suffered with this for months with my backup desktop machine.  None of the
usual suggestions worked - the drive always came up from a boot as being
dirty, with the time-consuming nuisance of CHKDSK as a result.

I finally got annoyed enough to reinstall Windows on top of itself, thus not
losing anything - profiles, installed programs, etc, etc.  I was pleased to
find that this permanently eliminated the problem.

As "they" don't publish much information (as far as I can tell) about what the
dirty bit actually is, and where it resides on a system, it becomes impossible
to know what actually got fixed.  But it worked for me.

Art
Click to expand...

Is should not really be a big deal if the OP would follow
instructions.

Verify the drive is dirty:

fsutil dirty query C:

chkntfs /X C:

The X tells Windows to NOT check that particular drive (C in this
example) on the next reboot. At this time, manually reboot your
computer, it should not do a CHKDSK and take you directly to Windows.

Once Windows has fully loaded, bring up another CMD prompt and type
and run CHKDSK manually by typing:

chkdsk /f /r C:

This should take you through the CHKDSK scan and will unset that dirty
bit. Finally, type

fsutil dirty query C:

and Windows will confirm that the dirty bit is not set on that drive.

Oh, happy day.
 
T

Tim Meddick

Nass,
I do apologise for being a bit quick off the mark.

I understand what you mean now, setting the 'bit' to force chkdsk to
run.

However, I [think] his problem is (and quite a few others, as having
done a 'google' on this) is that the 'dirty bit' is set - permanently.
This causes chkdsk to run every time (annoyingly for the OP) on boot,
and doesn't seem to cure the prob.

Concerning my previous post - I thought I was being reasonably polite.
I was merely pointing out to "ju.c" that I already knew about how to
configure 'chkdsk' at boot time. I was honestly miffed about why he
[seemed] was saying this to me (???). Perhaps in my eagerness to use a
few capitals and an exclamation mark, you may have thought I was
shouting. Again - sorry.

In all things I believe "do unto others" if people treated me in the
same way I [try to] treat others, then I would be eternally happy in
this world.

==

Cheers, Tim Meddick, Peckham, London. :)




nass said:
Hi Tim,
Me Either not the original Poster lol
When I gave Larry the 'fsutil' command utility not to check or repair
the
HDD consistency or repair corrupt/damaged Sectors or system files for
that
matter! I give it to him to reset the volum for dirty bits which in
turn will
make the ((/* Autochk */)) to start on start up which he having
problem with
running the system file checker.
Hence his saying" Does anyone have any ideas as to how this can be
reset
without having.."

If you don't like Ju.c to reply/correct you, don't try to reply
correct
other. It goes both ways. I don't mind people criticize me on the
bases of
Constructive criticism not a destructive one, which will be met with a
ripping heads and tearing the person apart (logically on the
internet).

I don't mean you or mean to offend you, just saying it in general no
body
meant behind it. It is nice to share info and no one above the stage
of
learning and knowing something new. If you said you know everything
then you
are a lair, if you said I do learn then you know more!!!

Please take this with an open mind, no offence meant to you or anyone
here.
Nice to have both of you on board to share knowledge and info. I'm
always a
learner...

HTH,
nass

Tim Meddick said:
"ju.c",
I am not the Original Poster!

In the post you have replied to, I was commenting on "nass" 's
suggestion that the OP use 'fsutil' to re-set drive C:'s 'dirty
flag'
and clear it. This cannot be done with the 'fsutil' command.
While
you can QUERY the current status and also SET the 'dirty flag', there
is
no option to 'clear' or 're-set' the flag with this command....

Personally, I knew about the default settings of the 'Bootexecute'
registry value, and the various ways to set [re-set] them.

==

Cheers, Tim Meddick, Peckham, London. :)




ju.c said:
How to reset chkdsk to the default behaviour:

Open the Run box and enter: cmd
In the command window type: chkntfs /d


ju.c


Nass,
while the 'fsutil' command can set the 'dirty flag' for a
NTFS volume - it cannot, however, re-set or 'clear' the 'dirty
bit'.
For that, you are supposed to run chkdsk on the volume and that
will
clear it. ...or is supposed to under normal circumstances.


==

Cheers, Tim Meddick, Peckham, London. :)






:

On my Thinkpad T60 I have a 100Gb SATA Drive with one primary
partition (&
the standard Recovery Partition). I am running WinXP Pro with
Service Pack
3. When I try to DEFRAG the C:\ Drive I get a message that
DEFRAG
cannot run
due to a pending CHKDSK /f. When I check the volume Status
"fsutil
dirty
query C:" I find that "C: > DIRTY" I have run CGKDSK at least a
dozen times,
the full 5 phases and they all complete normally with no errors
found.
However, the DIRTY flag never gets reset.
In addition, I have run diagnostics (Drive fitness Test), no
errors
on the
drive.
Does anyone have any ideas as to how this can be reset without
having to
reformat and reinstall?
Thank you,
Larry

Hi larry,
Try the system File utilities Fsutil.exe to reset the dirty flag
on
your HDD
secotors.

Microsoft Windows XP - Fsutil
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx

Error messages when you try to gain access to an NTFS volume
http://support.microsoft.com/kb/311724

File System Utility- Fsutil.exe
http://commandwindows.com/fsutil.htm

HTH,
nass
Click to expand...
Click to expand...
Click to expand...
 
J

Jose

On my Thinkpad T60 I have a 100Gb SATA Drive with one primary partition (&
the standard Recovery Partition).  I am running WinXP Pro with Service Pack
3.  When I try to DEFRAG the C:\ Drive I get a message that DEFRAG cannot run
due to a pending CHKDSK /f.  When I check the volume Status "fsutil dirty
query C:" I find that "C: > DIRTY" I have run CGKDSK at least a dozen times,
the full 5 phases and they all complete normally with no errors found.  
However, the DIRTY flag never gets reset.
In addition, I have run diagnostics (Drive fitness Test), no errors on the
drive.
Does anyone have any ideas as to how this can be reset without having to
reformat and reinstall?
Thank you,
Larry
Click to expand...

I decided to start over.

That Levono comes with some Rescue & Recovery software which (I read)
will not allow chkdsk to run unless R&R is uninstalled, disabled, you
use Recovery Console (if installed) or boot on an XP CD to Recovery
Console.

Of course it you boot into RC and use an XP CD, the SATA drivers would
have to be slip streamed into that boot process beforehand. Ha-ha-ha-
ha!!!


The problem is the tvtumon.sys driver, which is set to load at the
kernel initialization stage. This "locks" the boot drive, and causes
chkdsk /f and any other program that requires exclusive access to the
drive to fail as part of the BootExecute entry in the system registry.
The temporary fix is to change the start value for tvtumon in the
registry from 1 (loaded by I/O subsystem) to 2 (loaded by service
control manager). This fixes the problem with the chkdsk failing, but
I'm not sure what it does to R&R 4.2 functionality.

The specific registry entry is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tvtumon\
"Start"=dword:00000001

Change the dword to 2 and you are done.

NEXT!
 
N

nass

Hi Tim,
I didn't write my message for you to applogise Tim!
"Ju.c" like me and others like to keep the thread flowing, meaning
consistent and can help who will read it to get the benefit of reading it or
if he/she want to contribute to it. He didn't mean to answer you or correct
you, he just want it in a flow to keep the info in order.

I did find the Processor Explorer useful in this aspect. As it will show the
two entries for the Autochk* and the OP can remove the schedule chkdsk from
running.

Again I don't mean to defend or offend here.

Glad you got my point and glad to share this thread with and the other
helpers.
Regards,
nass


Tim Meddick said:
Nass,
I do apologise for being a bit quick off the mark.

I understand what you mean now, setting the 'bit' to force chkdsk to
run.

However, I [think] his problem is (and quite a few others, as having
done a 'google' on this) is that the 'dirty bit' is set - permanently.
This causes chkdsk to run every time (annoyingly for the OP) on boot,
and doesn't seem to cure the prob.

Concerning my previous post - I thought I was being reasonably polite.
I was merely pointing out to "ju.c" that I already knew about how to
configure 'chkdsk' at boot time. I was honestly miffed about why he
[seemed] was saying this to me (???). Perhaps in my eagerness to use a
few capitals and an exclamation mark, you may have thought I was
shouting. Again - sorry.

In all things I believe "do unto others" if people treated me in the
same way I [try to] treat others, then I would be eternally happy in
this world.

==

Cheers, Tim Meddick, Peckham, London. :)




nass said:
Hi Tim,
Me Either not the original Poster lol
When I gave Larry the 'fsutil' command utility not to check or repair
the
HDD consistency or repair corrupt/damaged Sectors or system files for
that
matter! I give it to him to reset the volum for dirty bits which in
turn will
make the ((/* Autochk */)) to start on start up which he having
problem with
running the system file checker.
Hence his saying" Does anyone have any ideas as to how this can be
reset
without having.."

If you don't like Ju.c to reply/correct you, don't try to reply
correct
other. It goes both ways. I don't mind people criticize me on the
bases of
Constructive criticism not a destructive one, which will be met with a
ripping heads and tearing the person apart (logically on the
internet).

I don't mean you or mean to offend you, just saying it in general no
body
meant behind it. It is nice to share info and no one above the stage
of
learning and knowing something new. If you said you know everything
then you
are a lair, if you said I do learn then you know more!!!

Please take this with an open mind, no offence meant to you or anyone
here.
Nice to have both of you on board to share knowledge and info. I'm
always a
learner...

HTH,
nass

Tim Meddick said:
"ju.c",
I am not the Original Poster!

In the post you have replied to, I was commenting on "nass" 's
suggestion that the OP use 'fsutil' to re-set drive C:'s 'dirty
flag'
and clear it. This cannot be done with the 'fsutil' command.
While
you can QUERY the current status and also SET the 'dirty flag', there
is
no option to 'clear' or 're-set' the flag with this command....

Personally, I knew about the default settings of the 'Bootexecute'
registry value, and the various ways to set [re-set] them.

==

Cheers, Tim Meddick, Peckham, London. :)




How to reset chkdsk to the default behaviour:

Open the Run box and enter: cmd
In the command window type: chkntfs /d


ju.c


Nass,
while the 'fsutil' command can set the 'dirty flag' for a
NTFS volume - it cannot, however, re-set or 'clear' the 'dirty
bit'.
For that, you are supposed to run chkdsk on the volume and that
will
clear it. ...or is supposed to under normal circumstances.


==

Cheers, Tim Meddick, Peckham, London. :)






:

On my Thinkpad T60 I have a 100Gb SATA Drive with one primary
partition (&
the standard Recovery Partition). I am running WinXP Pro with
Service Pack
3. When I try to DEFRAG the C:\ Drive I get a message that
DEFRAG
cannot run
due to a pending CHKDSK /f. When I check the volume Status
"fsutil
dirty
query C:" I find that "C: > DIRTY" I have run CGKDSK at least a
dozen times,
the full 5 phases and they all complete normally with no errors
found.
However, the DIRTY flag never gets reset.
In addition, I have run diagnostics (Drive fitness Test), no
errors
on the
drive.
Does anyone have any ideas as to how this can be reset without
having to
reformat and reinstall?
Thank you,
Larry

Hi larry,
Try the system File utilities Fsutil.exe to reset the dirty flag
on
your HDD
secotors.

Microsoft Windows XP - Fsutil
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx

Error messages when you try to gain access to an NTFS volume
http://support.microsoft.com/kb/311724

File System Utility- Fsutil.exe
http://commandwindows.com/fsutil.htm

HTH,
nass
Click to expand...
Click to expand...
Click to expand...
 
T

Tim Meddick

nass,
possibly the following may be relevant and /or of some interest
to you :

The key :

"HKLM\SYSTEM\CurrentControlSet\Control\Session Manager"


The reg value :

"BootExecute"


Some possible entries ; The first checks drive [c:] only for the 'dirty
bit' every boot (and if found, runs the 'chkdsk /p' scan ) :

autocheck autochk \??\C:


The second one, similarly, checks [c:] and [d:] :

autocheck autochk \??\C: \??\D:


This next one performs a full check (chkdsk /p) on drive [c:] on every
boot :

autocheck autochk /p \??\C:


....if you do try any of the above values for "BootExecute" , to return
it to it's default value type the following at the 'Command Prompt' :

chkntfs /d


*Note - Please exercise care when editing the registry, always create a
backup and / or create a 'System Restore' point first.

==

Cheers, Tim Meddick, Peckham, London. :)




nass said:
Hi Tim,
I didn't write my message for you to applogise Tim!
"Ju.c" like me and others like to keep the thread flowing, meaning
consistent and can help who will read it to get the benefit of reading
it or
if he/she want to contribute to it. He didn't mean to answer you or
correct
you, he just want it in a flow to keep the info in order.

I did find the Processor Explorer useful in this aspect. As it will
show the
two entries for the Autochk* and the OP can remove the schedule chkdsk
from
running.

Again I don't mean to defend or offend here.

Glad you got my point and glad to share this thread with and the other
helpers.
Regards,
nass


Tim Meddick said:
Nass,
I do apologise for being a bit quick off the mark.

I understand what you mean now, setting the 'bit' to force chkdsk to
run.

However, I [think] his problem is (and quite a few others, as having
done a 'google' on this) is that the 'dirty bit' is set -
permanently.
This causes chkdsk to run every time (annoyingly for the OP) on boot,
and doesn't seem to cure the prob.

Concerning my previous post - I thought I was being reasonably
polite.
I was merely pointing out to "ju.c" that I already knew about how to
configure 'chkdsk' at boot time. I was honestly miffed about why he
[seemed] was saying this to me (???). Perhaps in my eagerness to use
a
few capitals and an exclamation mark, you may have thought I was
shouting. Again - sorry.

In all things I believe "do unto others" if people treated me in the
same way I [try to] treat others, then I would be eternally happy in
this world.

==

Cheers, Tim Meddick, Peckham, London. :)




nass said:
Hi Tim,
Me Either not the original Poster lol
When I gave Larry the 'fsutil' command utility not to check or
repair
the
HDD consistency or repair corrupt/damaged Sectors or system files
for
that
matter! I give it to him to reset the volum for dirty bits which in
turn will
make the ((/* Autochk */)) to start on start up which he having
problem with
running the system file checker.
Hence his saying" Does anyone have any ideas as to how this can be
reset
without having.."

If you don't like Ju.c to reply/correct you, don't try to reply
correct
other. It goes both ways. I don't mind people criticize me on the
bases of
Constructive criticism not a destructive one, which will be met
with a
ripping heads and tearing the person apart (logically on the
internet).

I don't mean you or mean to offend you, just saying it in general
no
body
meant behind it. It is nice to share info and no one above the
stage
of
learning and knowing something new. If you said you know everything
then you
are a lair, if you said I do learn then you know more!!!

Please take this with an open mind, no offence meant to you or
anyone
here.
Nice to have both of you on board to share knowledge and info. I'm
always a
learner...

HTH,
nass

:

"ju.c",
I am not the Original Poster!

In the post you have replied to, I was commenting on "nass" 's
suggestion that the OP use 'fsutil' to re-set drive C:'s 'dirty
flag'
and clear it. This cannot be done with the 'fsutil' command.
While
you can QUERY the current status and also SET the 'dirty flag',
there
is
no option to 'clear' or 're-set' the flag with this command....

Personally, I knew about the default settings of the
'Bootexecute'
registry value, and the various ways to set [re-set] them.

==

Cheers, Tim Meddick, Peckham, London. :)




How to reset chkdsk to the default behaviour:

Open the Run box and enter: cmd
In the command window type: chkntfs /d


ju.c


Nass,
while the 'fsutil' command can set the 'dirty flag'
for a
NTFS volume - it cannot, however, re-set or 'clear' the 'dirty
bit'.
For that, you are supposed to run chkdsk on the volume and that
will
clear it. ...or is supposed to under normal circumstances.


==

Cheers, Tim Meddick, Peckham, London. :)






:

On my Thinkpad T60 I have a 100Gb SATA Drive with one primary
partition (&
the standard Recovery Partition). I am running WinXP Pro
with
Service Pack
3. When I try to DEFRAG the C:\ Drive I get a message that
DEFRAG
cannot run
due to a pending CHKDSK /f. When I check the volume Status
"fsutil
dirty
query C:" I find that "C: > DIRTY" I have run CGKDSK at least
a
dozen times,
the full 5 phases and they all complete normally with no
errors
found.
However, the DIRTY flag never gets reset.
In addition, I have run diagnostics (Drive fitness Test), no
errors
on the
drive.
Does anyone have any ideas as to how this can be reset
without
having to
reformat and reinstall?
Thank you,
Larry

Hi larry,
Try the system File utilities Fsutil.exe to reset the dirty
flag
on
your HDD
secotors.

Microsoft Windows XP - Fsutil
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx

Error messages when you try to gain access to an NTFS volume
http://support.microsoft.com/kb/311724

File System Utility- Fsutil.exe
http://commandwindows.com/fsutil.htm

HTH,
nass
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

f partition remains dirty for chkdsk? 2
chkdsk won't run on Restart 16
How to RESET "dirty bit" for NTFS volume 12
Chkdsk runs, dirty flag set, how to stop 5
External Drive will not Defrag - "chkdsk" issue 3
chkdsk hangs at 45% window xp 4
Chkdsk does not run, Defrag does not run, HEEELP please! 3
PLEASE HELP:dirty c: drive 1

Top