From a511aaf2431a72e1d7b4c5852cfde29aabe88b27 Mon Sep 17 00:00:00 2001
From: Holger Wansing <hwansing@mailbox.org>
Date: Sun, 17 May 2020 12:27:32 +0200
Subject: Also mention Windows 10 fast-startup feature in-line with fast-boot
 from Windows 8

---
 en/preparing/pre-install-bios-setup.xml | 26 ++++++++++++++++----------
 1 file changed, 16 insertions(+), 10 deletions(-)

(limited to 'en')

diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml
index 194d12ef6..e0f030e9c 100644
--- a/en/preparing/pre-install-bios-setup.xml
+++ b/en/preparing/pre-install-bios-setup.xml
@@ -96,22 +96,28 @@ hardware; it is most critically invoked during the bootstrap process
   </sect2>
 
   <sect2 arch="x86" id="disable-fast-boot">
-    <title>Disabling the Windows 8 <quote>fast boot</quote> feature</title>
+    <title>Disabling the Windows <quote>fast boot</quote>/<quote>fast startup</quote> feature</title>
     <para>
-      Windows 8 offers a feature called <quote>fast boot</quote> to cut down system
+      Windows offers a feature (called <quote>fast boot</quote> in Windows 8,
+      <quote>fast startup</quote> in Windows 10) to cut down system
       startup time.  Technically, when this feature is enabled,
-      Windows 8 does not do a real shutdown and a real cold boot afterwards
+      Windows does not do a real shutdown and a real cold boot afterwards
       when ordered to shut down, but instead does something resembling a
       partial suspend to disk to reduce the <quote>boot</quote> time.  As long as Windows
-      8 is the only operating system on the machine, this is unproblematic,
-      but it can result in problems and data loss when you have a dual boot
-      setup in which another operating system accesses the same filesystems
-      as Windows 8 does.  In that case the real state of the filesystem can
-      be different from what Windows 8 believes it to be after the <quote>boot</quote>
+      is the only operating system on the machine, this is unproblematic,
+      but it can result in problems and data loss, when you have a dual boot
+      setup, in which another operating system accesses the same filesystems
+      as Windows does.  In that case the real state of the filesystem can
+      be different from what Windows believes it to be after the <quote>boot</quote>
       and this could cause filesystem corruption upon further write accesses
       to the filesystem.  Therefore in a dual boot setup, to avoid
-      filesystem corruption the <quote>fast boot</quote> feature has to be disabled
-      within Windows.
+      filesystem corruption the <quote>fast boot</quote>/<quote>fast startup</quote>
+      feature has to be disabled within Windows.
+    </para>
+    <para>
+      Furthermore, the Windows Update mechanism has (sometimes) been known to
+      automatically re-enable this feature, after it has been previously
+      disabled by the user. It is suggested to re-check this setting periodically.
     </para>
     <para>
       It may also be necessary to disable <quote>fast boot</quote> to
-- 
cgit v1.2.3