Microsoft KB Archive/322275

= An Fsutil Query Does Not Work Properly on FAT or FAT32 Volumes =

Article ID: 322275

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows XP Professional

-



This article was previously published under Q322275





SYMPTOMS
If you use the fsutil command with the query parameter to check the status of the &quot;dirty&quot; bit on a FAT or FAT32 volume, Fsutil always indicates that the volume is not dirty.



CAUSE
This behavior occurs because Fsutil does not properly manage the dirty bit for FAT or FAT32 volumes. If you try to set the dirty bit on a FAT or FAT32 volume by using Fsutil, you receive a &quot;The Fsutil utility requires a local NTFS volume&quot; message.



STATUS
This behavior is by design.



MORE INFORMATION
The &quot;dirty&quot; bit is a bit in the boot sector (for FAT or FAT32 volumes), or in the MFT (for NTFS volumes), that is checked when Windows starts. This bit is checked to determine whether corruption has been detected in the file system. If the dirty bit is set on a volume, Autochk runs to correct any errors on the volume.

On NTFS volumes, the dirty bit is typically set only if the file system has detected potential corruption. In this case, an event is logged in the System event log.

You can use the fsutil command on NTFS volumes to query the current status of the dirty bit, or you can manually set the bit.

To query the current status of the dirty bit on a volume, use the following command:

fsutil dirty query :

To manually set the dirty bit on a volume, use the following command:

fsutil dirty set :

For both commands, replace  with the drive letter of the volume that you want to manage.

Keywords: kbprb KB322275

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.