fix MicrosoftDocs/windows-itpro-docs#10538

.openpublishing.redirection.json

@@ -19549,6 +19549,11 @@
       "source_path": "windows/client-management/mdm/proxy-csp.md",
       "redirect_url": "/windows/client-management/mdm/configuration-service-provider-reference",
       "redirect_document_id": false
+     },
+     {
+      "source_path": "windows/client-management/img-boot-sequence.md",
+      "redirect_url": "/windows/client-management/advanced-troubleshooting-boot-problems#boot-sequence",
+      "redirect_document_id": false
      }
   ]
 }

windows/client-management/advanced-troubleshooting-boot-problems.md

@@ -2,11 +2,11 @@
 title: Advanced troubleshooting for Windows boot problems
 description: Learn to troubleshoot when Windows can't boot. This article includes advanced troubleshooting techniques intended for use by support agents and IT professionals.
 ms.prod: w10
-ms.sitesec: library
+ms.technology: windows
-author: aczechowski
 ms.localizationpriority: medium
+ms.date: 06/02/2022
+author: aczechowski
 ms.author: aaroncz
-ms.date: 11/16/2018
 ms.reviewer: 
 manager: dougeby
 ms.topic: troubleshooting
@@ -15,16 +15,15 @@ ms.collection: highpri
 
 # Advanced troubleshooting for Windows boot problems
 
-<p class="alert is-flex is-primary"><span class="has-padding-left-medium has-padding-top-extra-small"><a class="button is-primary" href="https://vsa.services.microsoft.com/v1.0/?partnerId=7d74cf73-5217-4008-833f-87a1a278f2cb&flowId=DMC&initialQuery=boot" target='_blank'><b>Try our Virtual Agent</b></a></span><span class="has-padding-small"> - It can help you quickly identify and fix common Windows boot issues</span>
+<p class="alert is-flex is-primary"><span class="has-padding-left-medium has-padding-top-extra-small"><a class="button is-primary" href="https://vsa.services.microsoft.com/v1.0/?partnerId=7d74cf73-5217-4008-833f-87a1a278f2cb&flowId=DMC&initialQuery=boot" target='_blank'><b>Try our Virtual Agent</b></a></span><span class="has-padding-small"> - It can help you quickly identify and fix common Windows boot issues.</span>
 
 > [!NOTE]
-> This article is intended for use by support agents and IT professionals. If you're looking for more general information about recovery options, see [Recovery options in Windows 10](https://support.microsoft.com/help/12415).
+> This article is intended for use by support agents and IT professionals. If you're looking for more general information about recovery options, see [Recovery options in Windows 10](https://support.microsoft.com/windows/recovery-options-in-windows-31ce2444-7de3-818c-d626-e3b5a3024da5).
 
 ## Summary
 
 There are several reasons why a Windows-based computer may have problems during startup. To troubleshoot boot problems, first determine in which of the following phases the computer gets stuck:
 
-
 |   Phase   |     Boot Process     |                BIOS                |               UEFI                |
 |-----------|----------------------|------------------------------------|-----------------------------------|
 |     1     |       PreBoot        |      MBR/PBR (Bootstrap Code)      |           UEFI Firmware           |
@@ -32,31 +31,21 @@ There are several reasons why a Windows-based computer may have problems during
 |     3     |  Windows OS Loader   | %SystemRoot%\system32\winload.exe  | %SystemRoot%\system32\winload.efi |
 |     4     | Windows NT OS Kernel | %SystemRoot%\system32\ntoskrnl.exe |                                   |
 
-**1. PreBoot**
+1. **PreBoot**: The PC's firmware initiates a power-on self test (POST) and loads firmware settings. This pre-boot process ends when a valid system disk is detected. Firmware reads the master boot record (MBR), and then starts Windows Boot Manager.
 
-The PC’s firmware initiates a Power-On Self Test (POST) and loads firmware settings. This pre-boot process ends when a valid system disk is detected. Firmware reads the master boot record (MBR), and then starts Windows Boot Manager.
+2. **Windows Boot Manager**: Windows Boot Manager finds and starts the Windows loader (Winload.exe) on the Windows boot partition.
 
-**2. Windows Boot Manager**
+3. **Windows operating system loader**: Essential drivers required to start the Windows kernel are loaded and the kernel starts to run.
 
-Windows Boot Manager finds and starts the Windows loader (Winload.exe) on the Windows boot partition.
+4. **Windows NT OS Kernel**: The kernel loads into memory the system registry hive and other drivers that are marked as BOOT_START.
 
-**3. Windows operating system loader**
+    The kernel passes control to the session manager process (Smss.exe) which initializes the system session, and loads and starts the devices and drivers that aren't marked BOOT_START.
-
-Essential drivers required to start the Windows kernel are loaded and the kernel starts to run.
-
-**4. Windows NT OS Kernel**
-
-The kernel loads into memory the system registry hive and other drivers that are marked as BOOT_START.
-
-The kernel passes control to the session manager process (Smss.exe) which initializes the system session, and loads and starts the devices and drivers that aren't marked BOOT_START.
-
-Here's a summary of the boot sequence, what will be seen on the display, and typical boot problems at that point in the sequence. Before starting troubleshooting, you have to understand the outline of the boot process and display status to ensure that the issue is properly identified at the beginning of the engagement.
-
-![thumbnail of boot sequence flowchart.](images/boot-sequence-thumb.png)<br>
-[Click to enlarge](img-boot-sequence.md)<br>
 
+<a name="boot-sequence">
 
+Here's a summary of the boot sequence, what will be seen on the display, and typical boot problems at that point in the sequence. Before you start troubleshooting, you have to understand the outline of the boot process and display status to ensure that the issue is properly identified at the beginning of the engagement. Select the thumbnail to view it larger.
 
+:::image type="content" source="images/boot-sequence-thumb.png" alt-text="Diagram of the boot sequence flowchart." lightbox="images/boot-sequence.png":::
 
 Each phase has a different approach to troubleshooting. This article provides troubleshooting techniques for problems that occur during the first three phases.
 
@@ -69,7 +58,6 @@ Each phase has a different approach to troubleshooting. This article provides tr
 >
 > `Bcdedit /set {default} bootmenupolicy legacy`
 
-
 ## BIOS phase
 
 To determine whether the system has passed the BIOS phase, follow these steps:
@@ -93,19 +81,18 @@ If the screen is black except for a blinking cursor, or if you receive one of th
 - Bootmgr missing or corrupted
 - Unable to boot due to system hive missing or corrupted
 
-To troubleshoot this problem, use Windows installation media to start the computer, press Shift+F10 for a command prompt, and then use any of the following methods.
+To troubleshoot this problem, use Windows installation media to start the computer, press **Shift** + **F10** for a command prompt, and then use any of the following methods.
-
 
 ### Method 1: Startup Repair tool
 
 The Startup Repair tool automatically fixes many common problems. The tool also lets you quickly diagnose and repair more complex startup problems. When the computer detects a startup problem, the computer starts the Startup Repair tool. When the tool starts, it performs diagnostics. These diagnostics include analyzing startup log files to determine the cause of the problem. When the Startup Repair tool determines the cause, the tool tries to fix the problem automatically.
 
-To do this task of invoking the Startup Repair tool, follow these steps.
+To do this task of invoking the Startup Repair tool, follow these steps.
 
 > [!NOTE]
-> For additional methods to start WinRE, see [Windows Recovery Environment (Windows RE)](/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre).
+> For additional methods to start WinRE, see [Windows Recovery Environment (Windows RE)](/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#entry-points-into-winre).
 
-1. Start the system to the installation media for the installed version of Windows. For more information, see [Create installation media for Windows](https://support.microsoft.com/help/15088).
+1. Start the system to the installation media for the installed version of Windows. For more information, see [Create installation media for Windows](https://support.microsoft.com/windows/create-installation-media-for-windows-99a58364-8c02-206f-aa6f-40c3b507420d).
 
 2. On the **Install Windows** screen, select **Next** > **Repair your computer**.
 
@@ -117,28 +104,26 @@ To do this task of invoking the Startup Repair tool, follow these steps.
 
 The Startup Repair tool generates a log file to help you understand the startup problems and the repairs that were made. You can find the log file in the following location:
 
-**%windir%\System32\LogFiles\Srt\Srttrail.txt**
+`%windir%\System32\LogFiles\Srt\Srttrail.txt`
-
-
-For more information, see [A Stop error occurs, or the computer stops responding when you try to start Windows Vista or Windows 7](https://support.microsoft.com/help/925810/a-stop-error-occurs-or-the-computer-stops-responding-when-you-try-to-s)
 
+For more information, see [Troubleshoot blue screen errors](https://support.microsoft.com/sbs/windows/troubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3f73142c14ad).
 
 ### Method 2: Repair Boot Codes
 
 To repair boot codes, run the following command:
 
-```console
+```command
 BOOTREC /FIXMBR
 ```
 
 To repair the boot sector, run the following command:
 
-```console
+```command
 BOOTREC /FIXBOOT
 ```
 
 > [!NOTE]
-> Running **BOOTREC** together with **Fixmbr** overwrites only the master boot code. If the corruption in the MBR affects the partition table, running **Fixmbr** may not fix the problem.
+> Running `BOOTREC` together with `Fixmbr` overwrites only the master boot code. If the corruption in the MBR affects the partition table, running `Fixmbr` may not fix the problem.
 
 ### Method 3: Fix BCD errors
 
@@ -146,7 +131,7 @@ If you receive BCD-related errors, follow these steps:
 
 1. Scan for all the systems that are installed. To do this step, run the following command:
 
-   ```console
+   ```command
    Bootrec /ScanOS
    ```
 
@@ -154,7 +139,7 @@ If you receive BCD-related errors, follow these steps:
 
 3. If the problem isn't fixed, run the following commands:
 
-    ```console
+    ```command
     bcdedit /export c:\bcdbackup
     
     attrib c:\boot\bcd -r -s -h
@@ -172,38 +157,38 @@ If methods 1, 2 and 3 don't fix the problem, replace the Bootmgr file from drive
 
 1. At a command prompt, change the directory to the System Reserved partition.
 
-2. Run the **attrib** command to unhide the file:
+2. Run the `attrib` command to unhide the file:
 
-    ```console
+    ```command
     attrib -r -s -h
     ```
 
 3. Navigate to the system drive and run the same command:
 
-    ```console
+    ```command
     attrib -r -s -h
     ```
 
-4. Rename the Bootmgr file as Bootmgr.old:
+4. Rename the `bootmgr` file as `bootmgr.old`:
 
-    ```console
+    ```command
     ren c:\bootmgr bootmgr.old
     ```
 
 5. Navigate to the system drive.
 
-6. Copy the Bootmgr file, and then paste it to the System Reserved partition.
+6. Copy the `bootmgr` file, and then paste it to the System Reserved partition.
 
 7. Restart the computer.
 
-### Method 5: Restore System Hive
+### Method 5: Restore system hive
 
-If Windows can't load the system registry hive into memory, you must restore the system hive. To do this step,, use the Windows Recovery Environment or use Emergency Repair Disk (ERD) to copy the files from the C:\Windows\System32\config\RegBack to C:\Windows\System32\config.
+If Windows can't load the system registry hive into memory, you must restore the system hive. To do this step, use the Windows Recovery Environment or use the Emergency Repair Disk (ERD) to copy the files from the `C:\Windows\System32\config\RegBack` directory to `C:\Windows\System32\config`.
 
 If the problem persists, you may want to restore the system state backup to an alternative location, and then retrieve the registry hives to be replaced.
 
 > [!NOTE]
-> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check [this article](/troubleshoot/windows-client/deployment/system-registry-no-backed-up-regback-folder)
+> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more information, see [The system registry is no longer backed up to the RegBack folder starting in Windows 10 version 1803](/troubleshoot/windows-client/deployment/system-registry-no-backed-up-regback-folder).
 
 ## Kernel Phase
 
@@ -211,9 +196,7 @@ If the system gets stuck during the kernel phase, you experience multiple sympto
 
 - A Stop error appears after the splash screen (Windows Logo screen).
 
--   Specific error code is displayed.
+- Specific error code is displayed. For example, `0x00000C2` , `0x0000007B` , or `inaccessible boot device`.
-
-    For example, "0x00000C2" , "0x0000007B" , "inaccessible boot device" and so on.  
   - [Advanced troubleshooting for Stop error 7B or Inaccessible_Boot_Device](./troubleshoot-inaccessible-boot-device.md)
   - [Advanced troubleshooting for Event ID 41 "The system has rebooted without cleanly shutting down first"](troubleshoot-event-id-41-restart.md)
 
@@ -223,53 +206,45 @@ If the system gets stuck during the kernel phase, you experience multiple sympto
 
 To troubleshoot these problems, try the following recovery boot options one at a time.
 
-**Scenario 1: Try to start the computer in Safe mode or Last Known Good Configuration**
+### Scenario 1: Try to start the computer in Safe mode or Last Known Good Configuration
 
 On the **Advanced Boot Options** screen, try to start the computer in **Safe Mode** or **Safe Mode with Networking**. If either of these options works, use Event Viewer to help identify and diagnose the cause of the boot problem. To view events that are recorded in the event logs, follow these steps:
 
 1. Use one of the following methods to open Event Viewer:
 
-    -   Click **Start**, point to **Administrative Tools**, and then click
+    - Go to the **Start** menu, select **Administrative Tools**, and then select **Event Viewer**.
-        **Event Viewer**.
 
     - Start the Event Viewer snap-in in Microsoft Management Console (MMC).
 
-2.  In the console tree, expand Event Viewer, and then click the log that you
+2. In the console tree, expand Event Viewer, and then select the log that you want to view. For example, choose **System log** or **Application log**.
-    want to view. For example, click **System log** or **Application log**.
 
-3.  In the details pane, double-click the event that you want to view.
+3. In the details pane, open the event that you want to view.
 
-4.  On the **Edit** menu, click **Copy**, open a new document in the program in
+4. On the **Edit** menu, select **Copy**. Open a new document in the program in which you want to paste the event. For example, Microsoft Word. Then select **Paste**.
-    which you want to paste the event (for example, Microsoft Word), and then
-    click **Paste**.
-
-5.  Use the Up Arrow or Down Arrow key to view the description of the previous
-    or next event.
 
+5. Use the up arrow or down arrow key to view the description of the previous or next event.
 
 ### Clean boot
 
-To troubleshoot problems that affect services, do a clean boot by using System Configuration (msconfig).
+To troubleshoot problems that affect services, do a clean boot by using System Configuration (`msconfig`).
 Select **Selective startup** to test the services one at a time to determine which one is causing the problem. If you can't find the cause, try including system services. However, in most cases, the problematic service is third-party.
 
 Disable any service that you find to be faulty, and try to start the computer again by selecting **Normal startup**.
 
-For detailed instructions, see [How to perform a clean boot in Windows](https://support.microsoft.com/help/929135/how-to-perform-a-clean-boot-in-windows).
+For detailed instructions, see [How to perform a clean boot in Windows](https://support.microsoft.com/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd).
 
 If the computer starts in Disable Driver Signature mode, start the computer in Disable Driver Signature Enforcement mode, and then follow the steps that are documented in the following article to determine which drivers or files require driver signature enforcement:
-[Troubleshooting boot problem caused by missing driver signature (x64)](/archive/blogs/askcore/troubleshooting-boot-issues-due-to-missing-driver-signature-x64)
+[Troubleshooting boot problem caused by missing driver signature (x64)](/archive/blogs/askcore/troubleshooting-boot-issues-due-to-missing-driver-signature-x64)
 
 > [!NOTE]
 > If the computer is a domain controller, try Directory Services Restore mode (DSRM).
 >
 > This method is an important step if you encounter Stop error "0xC00002E1" or "0xC00002E2"
 
-
+#### Examples
-**Examples**
 
 > [!WARNING]
-> Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these
+> Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft can't guarantee that these problems can be solved. Modify the registry at your own risk.
-problems can be solved. Modify the registry at your own risk.
 
 *Error code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)*
 
@@ -279,21 +254,19 @@ To troubleshoot this Stop error, follow these steps to filter the drivers:
 
 2. Open the registry.
 
-3.  Load the system hive, and name it as "test."
+3. Load the system hive, and name it **test**.
 
-4.  Under the following registry subkey, check for lower filter and upper filter items for Non-Microsoft Drivers:  
+4. Under the following registry subkey, check for lower filter and upper filter items for non-Microsoft drivers:
 
-    **HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Class**  
+    `HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class`
 
-5.  For each third-party driver that you locate, click the upper or lower filter, and then delete the value data.
+5. For each third-party driver that you locate, select the upper or lower filter, and then delete the value data.
 
-6.  Search through the whole registry for similar items. Process as an appropriate, and then unload the registry hive.
+6. Search through the whole registry for similar items. Process as appropriate, and then unload the registry hive.
 
 7. Restart the server in Normal mode.
 
-For more troubleshooting steps, see the following articles:
+For more troubleshooting steps, see [Advanced troubleshooting for Stop error 7B or Inaccessible_Boot_Device](./troubleshoot-inaccessible-boot-device.md).
-
-- [Advanced troubleshooting for Stop error 7B or Inaccessible_Boot_Device](./troubleshoot-inaccessible-boot-device.md)
 
 To fix problems that occur after you install Windows updates, check for pending updates by using these steps:
 
@@ -301,16 +274,15 @@ To fix problems that occur after you install Windows updates, check for pending
 
 2. Run the command:
 
-    ```console
+    ```command
     DISM /image:C:\ /get-packages
     ```
 
 3. If there are any pending updates, uninstall them by running the following commands:
 
-    ```console
+    ```command
     DISM /image:C:\ /remove-package /packagename: name of the package
-    ```
+
-    ```console
     DISM /Image:C:\ /Cleanup-Image /RevertPendingActions
     ```
 
@@ -318,72 +290,67 @@ To fix problems that occur after you install Windows updates, check for pending
 
 If the computer doesn't start, follow these steps:
 
-1.  Open A Command Prompt window in WinRE, and start a text editor, such as Notepad.
+1. Open a command prompt window in WinRE, and start a text editor, such as Notepad.
 
-2.  Navigate to the system drive, and search for windows\winsxs\pending.xml.
+2. Navigate to the system drive, and search for `windows\winsxs\pending.xml`.
 
-3.  If the Pending.xml file is found, rename the file as Pending.xml.old.
+3. If the pending.xml file is found, rename the file as `pending.xml.old`.
 
-4.  Open the registry, and then load the component hive in HKEY_LOCAL_MACHINE as a test.
+4. Open the registry, and then load the component hive in HKEY_LOCAL_MACHINE as test.
 
-5.  Highlight the loaded test hive, and then search for the **pendingxmlidentifier** value.
+5. Highlight the loaded test hive, and then search for the `pendingxmlidentifier` value.
 
-6.  If the **pendingxmlidentifier** value exists, delete the value.
+6. If the `pendingxmlidentifier` value exists, delete it.
 
 7. Unload the test hive.
 
-8.  Load the system hive, name it as "test".
+8. Load the system hive, name it **test**.
 
 9. Navigate to the following subkey:
 
-    **HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Services\\TrustedInstaller**  
+    `HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TrustedInstaller`
 
-10. Change the **Start** value from **1** to **4**
+10. Change the **Start** value from `1` to `4`.
 
 11. Unload the hive.
 
 12. Try to start the computer.
 
-If the Stop error occurs late in the startup process, or if the Stop error is still being generated, you can capture a memory dump. A good memory dump can help determine the root cause of the Stop error. For details, see the following articles:
+If the Stop error occurs late in the startup process, or if the Stop error is still being generated, you can capture a memory dump. A good memory dump can help determine the root cause of the Stop error. For more information, see [Generate a kernel or complete crash dump](./generate-kernel-or-complete-crash-dump.md).
 
-- [Generate a kernel or complete crash dump](./generate-kernel-or-complete-crash-dump.md) 
+For more information about page file problems in Windows 10 or Windows Server 2016, see [Introduction to page files](./introduction-page-file.md).
 
-For more information about page file problems in Windows 10 or Windows Server 2016, see the following article:
+For more information about Stop errors, see [Advanced troubleshooting for Stop error or blue screen error issue](./troubleshoot-stop-errors.md).
-- [Introduction to page files](./introduction-page-file.md)
 
-For more information about Stop errors, see the following Knowledge Base article:
+Sometimes the dump file shows an error that's related to a driver. For example, `windows\system32\drivers\stcvsm.sys` is missing or corrupted. In this instance, follow these guidelines:
-- [Advanced troubleshooting for Stop error or blue screen error issue](./troubleshoot-stop-errors.md)
 
-
+- Check the functionality that's provided by the driver. If the driver is a third-party boot driver, make sure that you understand what it does.
-If the dump file shows an error that is related to a driver (for example, windows\system32\drivers\stcvsm.sys is missing or corrupted), follow these guidelines:
-
-- Check the functionality that is provided by the driver. If the driver is a third-party boot driver, make sure that you understand what it does.
 
 - If the driver isn't important and has no dependencies, load the system hive, and then disable the driver.
 
 - If the stop error indicates system file corruption, run the system file checker in offline mode.
 
-    - To do this, open WinRE, open a command prompt, and then run the following command:
+  - To do this action, open WinRE, open a command prompt, and then run the following command:
 
-        ```console
+    ```command
     SFC /Scannow /OffBootDir=C:\ /OffWinDir=C:\Windows
     ```
 
-        For more information, see [Using System File Checker (SFC) To Fix  Issues](/archive/blogs/askcore/using-system-file-checker-sfc-to-fix-issues)
+    For more information, see [Using system file checker (SFC) to fix issues](/archive/blogs/askcore/using-system-file-checker-sfc-to-fix-issues).
 
   - If there's disk corruption, run the check disk command:
 
-        ```console
+    ```command
     chkdsk /f /r
     ```
 
-    - If the Stop error indicates general registry corruption, or if you believe that new drivers or services were installed, follow these steps:
+- If the Stop error indicates general registry corruption, or if you believe that new drivers or services were installed, follow these steps:
 
-        1. Start WinRE, and open a Command Prompt window.
+  1. Start WinRE, and open a command prompt window.
   2. Start a text editor, such as Notepad.
-        3. Navigate to C:\Windows\System32\Config\.
+  3. Navigate to `C:\Windows\System32\Config\`.
-        4. Rename the all five hives by appending ".old" to the name.
+  4. Rename the all five hives by appending `.old` to the name.
-        5. Copy all the hives from the Regback folder, paste them in the Config folder, and then try to start the computer in Normal mode.
+  5. Copy all the hives from the `Regback` folder, paste them in the `Config` folder, and then try to start the computer in Normal mode.
 
 > [!NOTE]
-> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check [this article](/troubleshoot/windows-client/deployment/system-registry-no-backed-up-regback-folder).
+> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more information, see [The system registry is no longer backed up to the RegBack folder starting in Windows 10 version 1803](/troubleshoot/windows-client/deployment/system-registry-no-backed-up-regback-folder).

windows/client-management/img-boot-sequence.md

@@ -1,17 +0,0 @@
----
-title: Boot sequence flowchart
-description: View a full-sized view of the boot sequence flowchart. Use the link to return to the Advanced troubleshooting for Windows boot problems article.
-ms.date: 11/16/2018
-ms.reviewer: 
-manager: dansimp
-ms.author: dansimp
-author: dansimp
-ms.topic: article
-ms.prod: w10
----
-
-# Boot sequence flowchart
-
-Return to: [Advanced troubleshooting for Windows boot problems](advanced-troubleshooting-boot-problems.md)<br>
-
-![Full-sized boot sequence flowchart.](images/boot-sequence.png)