Manually Reset or Clear Dirty Bit in Windows without using CHKDSK

One mystery that has gone unsolved for the longest time now is the dirty bit on hard drive volumes. Basically a dirty bit is just a 1 hex value located somewhere hidden on the hard drive that Microsoft has never reveal until recently. Windows will check the dirty bit to determine if a volume can contain corrupted files due to hard resetting your Windows computer with files that are still opened or when you unplug a USB flash drive that is in the midst of copying a file.

When the computer boots up with the dirty bit enabled on a hard drive, you will be asked to check the disk for consistency before Windows is loaded. You can skip the disk checking by pressing any key but it will come back again the next time you start up your computer. This will usually keep happening until you let the drive be scanned or alternatively you can tell Windows to stop checking the specific drive. This method doesn’t clear the dirty bit on the drive though and simply forces Windows not to scan a drive on boot.

Checking file system on C: The type of the file system is NTFS

As for a USB flash drive or portable hard drive with the dirty bit enabled, plugging the drive into a Windows 7 computer will prompt a window that asks:

Do you want to scan and fix Removable Disk (G:)?

There might be a problem with some files on this device or disc. This can happen if you remove the device or disc before all files have been written to it.

If you close the popup or select “Continue without scanning”, then this popup will continue to haunt you until you decided to click the recommended Scan and Fix option.

There are guides on how to disable the scan and fix window by disabling the Shell Hardware Detection service but that really isn’t a viable solution since you’re telling Windows to ignore the problem rather than fixing the problem itself.

Do you want to scan and fix Removable Disk

There is a tool called fsutil.exe in Windows which can be used to check if a volume is dirty and can even be used to manually set a drive as dirty which will force the requests to scan it, but weirdly it cannot be used to clear the dirty bit. Someone has already reverse engineered the fsutil.exe to confirm it.

fsutil.exe dirty

So there seems to be 2 solutions to clear the dirty bit which is to trust the Microsoft disk checking utility by completing a check disk OR you can move the data away from the volume, format the drive and then move it back. Going with the first option would risk losing some of your files when the scan disk decides to turn them into CHK files. The second option is safer but takes a lot of time if you have a lot of files to move.

Here is a third method, and we’ve spent several hours locating the dirty bit on NTFS and FAT16/32 file systems so that we can manually reset or clear the dirty bit with a hex editor that supports disk editing. As we said earlier, the dirty bit is simply 1 hex value on the disc volume that needs to be reset and is easy to change again in future once you know how.

We’ve tried a total of 13 different hex editors which are wxHexEditor, HxD, 010 Editor, CI Hex Viewer, iBored, HexEdit Pro, Hackman Suite, DMDE, Hexprobe, FlexHEX, ADRC Hard Disk Hex Editor, WinHex and Hex Workshop. Only DMDE, WinHex and Hex Workshop were the editors able to write the data back to the disc but the last two are shareware tools. HxD is certainly one of the easiest tools to use and can make the needed changes but is a bit slower because it needs to manually search the drive for some values.

On Page 2 we’ll show how to clear the dirty bit for NTFS, FAT32, FAT16 and locked volumes.

83 Comments - Write a Comment

  1. Al 10 months ago
  2. Gabriel Fair 11 months ago
  3. Simone 1 year ago
  4. Lars De Volder 1 year ago
  5. Hosam 1 year ago
  6. Animadversor 2 years ago
    • mike 2 years ago
      • saul 2 years ago
    • P 2 years ago
      • J 1 year ago
      • D 1 year ago
      • M 1 year ago
      • Mohit 1 year ago
      • Renato 12 months ago
      • Sanchit 12 months ago
  7. David Orbell 3 years ago
  8. James Willoughby 3 years ago
    • Leah 2 years ago
    • saul 2 years ago
  9. Jim Willoughby 3 years ago
  10. Chris C. 3 years ago
  11. Joey 4 years ago
    • Tim Thorson 3 years ago
  12. Alan 4 years ago
    • bungiefan 3 years ago
  13. Ernest 5 years ago
  14. Sidney White 5 years ago
  15. irhmy 5 years ago
    • Widi Wong 5 years ago
      • Aurora Clayton 3 years ago
    • Liz 3 years ago
    • EKW 3 years ago
  16. Rohit 5 years ago
  17. boisecoder 5 years ago
    • Neil M 5 years ago
      • Andy 4 years ago
  18. tenbensel 5 years ago
    • boisecoder 5 years ago
    • Neil M 5 years ago
      • Jim 4 years ago
  19. George 5 years ago
  20. mindz 5 years ago
  21. Arslan 5 years ago
  22. Alexa J 5 years ago
  23. Georg 6 years ago
    • HAL9000 6 years ago
  24. Nani 6 years ago
  25. Paul Thomsen 6 years ago
  26. Clément 6 years ago
  27. ykc 6 years ago
  28. Phil 7 years ago
  29. Peter 7 years ago
  30. Cecilia Bartoli 7 years ago
  31. akj 7 years ago
  32. Darlene 7 years ago
  33. joe 7 years ago
    • HAL9000 7 years ago
  34. Dvorak 7 years ago
  35. Sport 8 years ago
  36. Swiftkidd 8 years ago
    • HAL9000 8 years ago
  37. Tony Sinclair 8 years ago
  38. Eric 8 years ago
  39. HRK 8 years ago
    • HAL9000 8 years ago
  40. Robert 8 years ago
  41. akaNeo 8 years ago
    • Laban 7 years ago
      • akaNeo 7 years ago
  42. plow_dog 8 years ago
  43. Nathan 8 years ago
  44. Untitled 8 years ago
    • HAL9000 8 years ago
  45. SuperMax11 8 years ago
    • HAL9000 8 years ago
  46. Don Cross 9 years ago
  47. Frank 9 years ago
    • MOSES 8 years ago
  48. Happy_Jack 9 years ago
  49. fabian 9 years ago
  50. Josey Mathew 10 years ago
  51. ahmadmaher 10 years ago
  52. no name 10 years ago

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Your comment is subject to approval. Read our Terms of Use. If you are seeking additional information on this article, please contact us directly.