📎 AI Summary:
The thread discusses recurring automatic disk checks (chkdsk) in Windows 7, often triggered by the "dirty bit" being set on drives—usually due to improper shutdowns or power issues. The user seeks advice on why this occurs and how to resolve it, with a detailed explanation from another user about clearing the dirty bit using commands like "fsutil dirty query" and "CHKNTFS /X." Troubleshooting further, the original poster encounters permission issues with "fsutil," which is resolved by running the Command Prompt as an administrator. Overall, the discussion provides guidance on preventing automatic disk checks caused by the dirty bit in Windows 7.
The thread discusses recurring automatic disk checks (chkdsk) in Windows 7, often triggered by the "dirty bit" being set on drives—usually due to improper shutdowns or power issues. The user seeks advice on why this occurs and how to resolve it, with a detailed explanation from another user about clearing the dirty bit using commands like "fsutil dirty query" and "CHKNTFS /X." Troubleshooting further, the original poster encounters permission issues with "fsutil," which is resolved by running the Command Prompt as an administrator. Overall, the discussion provides guidance on preventing automatic disk checks caused by the dirty bit in Windows 7.
Solution
oneextraid
Banned
I have experienced this after I perform a disk defrag. It only happens intermittently.
busydog
Essential Member
Welcome to "Dirty Bit"
What you're experiencing is what Windows 7 refers to as "setting the dirty bit" and what you have to do is unset that bit. Every time Windows 7starts, autochk.exe is called by the kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f verifies file system integrity and attempts to fix any problems with the volume. It is usually caused by a hard shut down or a power loss during a read-right operation on that particular drive.
That's easy to fix. First click <Start> <Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". The X tells Windows to NOT check that particular drive 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 now you want to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type "fsutil dirty query d:" and Windows will confirm that the dirty bit is not set on that drive.
What you're experiencing is what Windows 7 refers to as "setting the dirty bit" and what you have to do is unset that bit. Every time Windows 7starts, autochk.exe is called by the kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f verifies file system integrity and attempts to fix any problems with the volume. It is usually caused by a hard shut down or a power loss during a read-right operation on that particular drive.
That's easy to fix. First click <Start> <Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". The X tells Windows to NOT check that particular drive 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 now you want to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type "fsutil dirty query d:" and Windows will confirm that the dirty bit is not set on that drive.
