Windows Dirty Bit - Revision history

Wayne-workman.28155: /* Way 1 (clean method) */

2017-03-29T00:30:36Z

‎Way 1 (clean method)

Wayne-workman.28155: /* Way 2 (A little hackish) */

2016-07-20T01:55:02Z

‎Way 2 (A little hackish)

Wayne-workman.28155: Changed terminology to use capture instead of upload.

2016-07-08T04:55:06Z

Changed terminology to use capture instead of upload.

Wayne-workman.28155: /* Windows "Fast Startup" */

2016-05-07T03:50:02Z

‎Windows "Fast Startup"

Wayne-workman.28155: /* Windows "Fast Startup" */

2016-03-04T16:01:11Z

‎Windows "Fast Startup"

Wayne-workman.28155: /* Hibernation file */

2016-03-04T15:59:30Z

‎Hibernation file

Wayne-workman.28155: /* Hibernation file */

2016-03-04T15:55:40Z

‎Hibernation file

Wayne-workman.28155: Created page with "== The "Dirty Bit" == If you received this message (or a very similar one) from Partclone, it means that the Windows "Dirty Bit" is turned ON:

ntfsclone-ng.c: NTFS Volu..."

2016-03-04T15:54:16Z

Created page with "== The "Dirty Bit" == If you received this message (or a very similar one) from Partclone, it means that the Windows "Dirty Bit" is turned ON: <pre>ntfsclone-ng.c: NTFS Volu..."

New page

== The "Dirty Bit" ==

If you received this message (or a very similar one) from Partclone, it means that the Windows "Dirty Bit" is turned ON:

<pre>ntfsclone-ng.c: NTFS Volume '/dev/sda4' is scheduled for a check or it was shutdown uncleanly. Please boot Windows or fix it by fsck.</pre>

[[File:Partclone Windows Dirty Bit.jpg]]

The Windows "dirty bit" is set '''ON''' when:

*There are pending Windows updates

*There is a pending restart

*Fast Startup is enabled

*Windows is hibernated

*Windows is improperly shutdown

*There is a chkdsk scheduled

*Data corruption is detected

There are a number of ways to clear the dirty bit, but the best and easiest ways are to simply not have updates pending, disabling fast startup, shutting down windows properly, not having chkdsk scheduled, and having non-damaged HDDs and non-damaged partitions. '''AFTER''' making the necessary changes to clear the "dirty bit", windows should be restarted at least two times for it to clear properly.

== Hibernation file ==

Windows 8.0 and 8.1 use hibernation by default when shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG. Even when hibernation and fast startup is disabled, the hibernation file remains and the "Dirty Bit" remains '''ON''' and these things causes problems. There are a few ways to fix this.

=== Way 1 (clean method) ===

Turn off: "'''Turn on fast startup'''", located here: Control Panel (Classic View) -> Power Options -> Choose what the power button does -> Change Settings that are currently unavailable -> "Turn On Fast Startup & Hibernate"

Both of those settings should be turned off for use with FOG. They may be turned on at a later time via GPO or snapins.

Shutdown and then boot the system.

Then run this command from an '''elevated command prompt''' to disable hibernation and remove the hibernation file:

<pre>powercfg.exe /H off</pre>

Now you can shut down and reboot once or twice, and then upload your image via FOG.

=== Way 2 (A little hackish) ===

When you're ready to capture an image, do not shut down the computer. Instead, tell it to restart. The middle point of the restart is when the OS stops, and control is handed over to the system's firmware. During or just after this moment, you can push the power button to instantly turn off the computer. Now you can upload your image.

This is because without changing the settings (in way 1), a shutdown is actually a hibernate. A restart is the only real way to take the system down fully without changing settings. The reboot causes the system to shutdown fully, thus clearing the "dirty bit".

=== Way 3 (Very hackish, not clean) ===

This method is just as viable but not as clean or easy and requires timing.

You would open an elevated command prompt and then run:

<pre>chkdsk /F</pre>

Answer yes to schedule the checkdisk at the next reboot.

Now you would reboot and allow the checkdisk to run. At some point during the check disk (which may not be at 100%), check disk will tell the sytem to reboot.

'''At this moment, you need to boot to the network''' and upload your image to fog. If you miss this moment and windows boots, you will have to re-run chkdsk.

== Resources used ==

Major resources:

http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html

http://www.pclinuxos.com/forum/index.php?topic=126158.0

http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.html

Minor resources:

http://www.techsupportalert.com/freeware-forum/system/12944-method-of-shutdown-in-windows-8-1-makes-difference.html

http://www.sevenforums.com/performance-maintenance/304428-windows-7-always-running-chkdsk-particular-partition.html

http://www.techrepublic.com/blog/tr-dojo/delete-hiberfilsys-by-disabling-windows-hibernate-function/

== UEFI and BIOS coexistence / together ==

See this article:

[[BIOS_and_UEFI_Co-Existence]]

@@ Line 45: / Line 45: @@
 === Way 2 (A little hackish) ===
-When you're ready to capture an image, do not shut down the computer. Instead, tell it to restart. The middle point of the restart is when the OS stops, and control is handed over to the system's firmware. During or just after this moment, you can push the power button to instantly turn off the computer. Now you can capture your image.
+When you're ready to capture an image, do not shut down the computer. Instead, tell it to restart. The middle point of the restart is when the OS stops, and control is handed over to the system's firmware. When POST is happening, do your typical procedure to network boot and the image should capture.
 This is because without changing the settings (in way 1), a shutdown is actually a hibernate. A restart is the only real way to take the system down fully without changing settings. The reboot causes the system to shutdown fully, thus clearing the "dirty bit".

@@ Line 27: / Line 27: @@
 == Windows "Fast Startup" ==
-Windows 8.0, 8.1, and 10 (and most likely future Windows versions) have a feature called "Fast Startup". This feature basically sets windows so that a hibernation occurs whenever the system is shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG, and also marks the OS partition's "Dirty Bit" to ON. Even when hibernation and fast startup is disabled, the hibernation file remains and the "Dirty Bit" remains '''ON''' and these things causes problems. There are a few ways to fix this.
+Windows 8.0, 8.1, and 10 (and most likely future Windows versions) have a feature called "Fast Startup". This feature basically sets windows so that a hibernation occurs whenever the system is shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG, and also marks the OS partition's "Dirty Bit" to ON. Even when hibernation and fast startup is disabled, the hibernation file remains and the "Dirty Bit" remains '''ON''' and these things causes problems. There are a few ways to fix/get around this.
 === Way 1 (clean method) ===

@@ Line 27: / Line 27: @@
 == Windows "Fast Startup" ==
-Windows 8.0, 8.1, and 10 (and most likely future Windows versions) have a feature called "Fast Startup". This feature is basically a hibernation by default when shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG, and also marks the OS partition's "Dirty Bit" to ON. Even when hibernation and fast startup is disabled, the hibernation file remains and the "Dirty Bit" remains '''ON''' and these things causes problems. There are a few ways to fix this.
+Windows 8.0, 8.1, and 10 (and most likely future Windows versions) have a feature called "Fast Startup". This feature basically sets windows so that a hibernation occurs whenever the system is shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG, and also marks the OS partition's "Dirty Bit" to ON. Even when hibernation and fast startup is disabled, the hibernation file remains and the "Dirty Bit" remains '''ON''' and these things causes problems. There are a few ways to fix this.
 === Way 1 (clean method) ===

@@ Line 25: / Line 25: @@
 There are a number of ways to clear the dirty bit, but the best and easiest ways are to simply not have updates pending, disabling fast startup, shutting down windows properly, not having chkdsk scheduled, and having non-damaged HDDs and non-damaged partitions. '''AFTER''' making the necessary changes to clear the "dirty bit", windows should be restarted at least two times for it to clear properly.
-== Hibernation file ==
+== Windows "Fast Startup" ==
-Windows 8.0, 8.1, and 10 use hibernation by default when shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG. Even when hibernation and fast startup is disabled, the hibernation file remains and the "Dirty Bit" remains '''ON''' and these things causes problems. There are a few ways to fix this.
+Windows 8.0, 8.1, and 10 (and most likely future Windows versions) have a feature called "Fast Startup". This feature is basically a hibernation by default when shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG, and also marks the OS partition's "Dirty Bit" to ON. Even when hibernation and fast startup is disabled, the hibernation file remains and the "Dirty Bit" remains '''ON''' and these things causes problems. There are a few ways to fix this.
 === Way 1 (clean method) ===

@@ Line 31: / Line 31: @@
 === Way 1 (clean method) ===
-Turn off: "'''Turn on fast startup'''", located here:  Control Panel (Classic View) -> Power Options -> Choose what the power button does -> Change Settings that are currently unavailable -> "Turn On Fast Startup & Hibernate"
+Disable: "'''Turn on fast startup'''", located here:  Control Panel (Classic View) -> Power Options -> Choose what the power button does -> Change Settings that are currently unavailable -> "Turn On Fast Startup & Hibernate"
 Both of those settings should be turned off for use with FOG. They may be turned on at a later time via GPO or snapins.

@@ Line 41: / Line 41: @@
 <pre>powercfg.exe /H off</pre>
-Now you can shut down and reboot once or twice, and then upload your image via FOG.
+Now you can shut down and reboot once or twice, and then capture your image via FOG.
 === Way 2 (A little hackish) ===
-When you're ready to capture an image, do not shut down the computer. Instead, tell it to restart. The middle point of the restart is when the OS stops, and control is handed over to the system's firmware. During or just after this moment, you can push the power button to instantly turn off the computer. Now you can upload your image.
+When you're ready to capture an image, do not shut down the computer. Instead, tell it to restart. The middle point of the restart is when the OS stops, and control is handed over to the system's firmware. During or just after this moment, you can push the power button to instantly turn off the computer. Now you can capture your image.
 This is because without changing the settings (in way 1), a shutdown is actually a hibernate. A restart is the only real way to take the system down fully without changing settings. The reboot causes the system to shutdown fully, thus clearing the "dirty bit".
@@ Line 61: / Line 61: @@
 Now you would reboot and allow the checkdisk to run. At some point during the check disk (which may not be at 100%), check disk will tell the sytem to reboot.
-'''At this moment, you need to boot to the network''' and upload your image to fog. If you miss this moment and windows boots, you will have to re-run chkdsk.
+'''At this moment, you need to boot to the network''' and capture your image to fog. If you miss this moment and windows boots, you will have to re-run chkdsk.
 == Resources used ==