From e3c14786ed92034eea0f0102d876d829495e937c Mon Sep 17 00:00:00 2001 From: illfated Date: Thu, 8 Aug 2019 23:28:54 +0200 Subject: [PATCH 01/10] Update advanced-troubleshooting-boot-problems.md - Set correct MarkDown spacing for [!NOTE] blocks - Add newline breaks to output text for readability - Reorder attrib command parameters to logical order - Add missing space between the command attrib and its parameters - Remove a redundant double backslash in a rename (`ren`) command - Remove redundant line "Start a text editor, such as Notepad." Closes #4631 --- .../advanced-troubleshooting-boot-problems.md | 52 ++++++++++--------- 1 file changed, 27 insertions(+), 25 deletions(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index e83a4bf8bd..a5e053d57f 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -14,8 +14,8 @@ ms.topic: troubleshooting # Advanced troubleshooting for Windows boot problems ->[!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). +> [!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). ## Summary @@ -58,14 +58,14 @@ Here is a summary of the boot sequence, what will be seen on the display, and ty Each phase has a different approach to troubleshooting. This article provides troubleshooting techniques for problems that occur during the first three phases. ->[!NOTE] ->If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle: +> [!NOTE] +> If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle: > ->`Bcdedit /set {default} recoveryenabled no` +> `Bcdedit /set {default} recoveryenabled no` > ->If the F8 options don't work, run the following command: +> If the F8 options don't work, run the following command: > ->`Bcdedit /set {default} bootmenupolicy legacy` +> `Bcdedit /set {default} bootmenupolicy legacy` ## BIOS phase @@ -98,8 +98,8 @@ The Startup Repair tool automatically fixes many common problems. The tool also To do this, follow these steps. ->[!NOTE] ->For additional methods to start WinRE, see [Entry points into WinRE](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre). +> [!NOTE] +> For additional methods to start WinRE, see [Entry points into WinRE](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre). 1. Start the system to the installation media for the installed version of Windows. **Note** For more information, see [Create installation media for Windows](https://support.microsoft.com/help/15088). @@ -132,8 +132,8 @@ To repair the boot sector, run the following 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. +> [!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. ### Method 3: Fix BCD errors @@ -153,10 +153,12 @@ If you receive BCD-related errors, follow these steps: 4. You might receive one of the following outputs: - - Scanning all disks for Windows installations. Please wait, since this may take a while...Successfully scanned Windows installations. Total identified Windows installations: 0 + - Scanning all disks for Windows installations. Please wait, since this may take a while... + Successfully scanned Windows installations. Total identified Windows installations: 0 The operation completed successfully. - - Scanning all disks for Windows installations. Please wait, since this may take a while... Successfully scanned Windows installations. Total identified Windows installations: 1 + - Scanning all disks for Windows installations. Please wait, since this may take a while... + Successfully scanned Windows installations. Total identified Windows installations: 1 D:\Windows Add installation to boot list? Yes/No/All: @@ -165,7 +167,7 @@ If the output shows **windows installation: 0**, run the following commands: ```dos bcdedit /export c:\bcdbackup -attrib c:\\boot\\bcd -h -r –s +attrib c:\\boot\\bcd -r –s -h ren c:\\boot\\bcd bcd.old @@ -174,10 +176,12 @@ bootrec /rebuildbcd After you run the command, you receive the following output: - Scanning all disks for Windows installations. Please wait, since this may take a while...Successfully scanned Windows installations. Total identified Windows installations: 1{D}:\Windows -Add installation to boot list? Yes/No/All: Y + Scanning all disks for Windows installations. Please wait, since this may take a while... + Successfully scanned Windows installations. Total identified Windows installations: 1 + {D}:\Windows + Add installation to boot list? Yes/No/All: Y -5. Try again to start the system. +5. Try restarting the system. ### Method 4: Replace Bootmgr @@ -187,26 +191,24 @@ If methods 1 and 2 do not fix the problem, replace the Bootmgr file from drive C 2. Run the **attrib** command to unhide the file: ```dos - attrib-s -h -r + attrib -r -s -h ``` 3. Run the same **attrib** command on the Windows (system drive): ```dos - attrib-s -h –r + attrib -r -s -h ``` 4. Rename the Bootmgr file as Bootmgr.old: ```dos - ren c:\\bootmgr bootmgr.old + ren c:\bootmgr bootmgr.old ``` -5. Start a text editor, such as Notepad. +5. Navigate to the system drive. -6. Navigate to the system drive. +6. Copy the Bootmgr file, and then paste it to the System Reserved partition. -7. Copy the Bootmgr file, and then paste it to the System Reserved partition. - -8. Restart the computer. +7. Restart the computer. ### Method 5: Restore System Hive From f408a76f0d9cb0f438269645fe0fd511b057a51f Mon Sep 17 00:00:00 2001 From: "Trond B. Krokli" <38162891+illfated@users.noreply.github.com> Date: Fri, 9 Aug 2019 07:53:39 +0200 Subject: [PATCH 02/10] Update windows/client-management/advanced-troubleshooting-boot-problems.md Windows RE link label text correction Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../client-management/advanced-troubleshooting-boot-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index a5e053d57f..5cc7a1e31a 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -99,7 +99,7 @@ The Startup Repair tool automatically fixes many common problems. The tool also To do this, follow these steps. > [!NOTE] -> For additional methods to start WinRE, see [Entry points into WinRE](https://docs.microsoft.com/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)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre). 1. Start the system to the installation media for the installed version of Windows. **Note** For more information, see [Create installation media for Windows](https://support.microsoft.com/help/15088). From 5285fe229403fe8041ba61b5ea96eb9b11624f5e Mon Sep 17 00:00:00 2001 From: "Trond B. Krokli" <38162891+illfated@users.noreply.github.com> Date: Fri, 9 Aug 2019 07:54:45 +0200 Subject: [PATCH 03/10] Update windows/client-management/advanced-troubleshooting-boot-problems.md - add required space between text and line end ellipsis Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../client-management/advanced-troubleshooting-boot-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 5cc7a1e31a..5076b4ed6b 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -153,7 +153,7 @@ If you receive BCD-related errors, follow these steps: 4. You might receive one of the following outputs: - - Scanning all disks for Windows installations. Please wait, since this may take a while... + - Scanning all disks for Windows installations. Please wait, since this may take a while ... Successfully scanned Windows installations. Total identified Windows installations: 0 The operation completed successfully. From 2294a2a7939f1ccbf6d4121b627de3d57e7ba341 Mon Sep 17 00:00:00 2001 From: "Trond B. Krokli" <38162891+illfated@users.noreply.github.com> Date: Fri, 9 Aug 2019 07:55:30 +0200 Subject: [PATCH 04/10] Update windows/client-management/advanced-troubleshooting-boot-problems.md - add required space between text and line end ellipsis Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../client-management/advanced-troubleshooting-boot-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 5076b4ed6b..629317da81 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -157,7 +157,7 @@ If you receive BCD-related errors, follow these steps: Successfully scanned Windows installations. Total identified Windows installations: 0 The operation completed successfully. - - Scanning all disks for Windows installations. Please wait, since this may take a while... + - Scanning all disks for Windows installations. Please wait, since this may take a while ... Successfully scanned Windows installations. Total identified Windows installations: 1 D:\Windows Add installation to boot list? Yes/No/All: From edae596f7951a509ea4f8ef9751840b14b980288 Mon Sep 17 00:00:00 2001 From: "Trond B. Krokli" <38162891+illfated@users.noreply.github.com> Date: Fri, 9 Aug 2019 07:55:40 +0200 Subject: [PATCH 05/10] Update windows/client-management/advanced-troubleshooting-boot-problems.md - add required space between text and line end ellipsis Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../client-management/advanced-troubleshooting-boot-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 629317da81..ea1e2def64 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -176,7 +176,7 @@ bootrec /rebuildbcd After you run the command, you receive the following output: - Scanning all disks for Windows installations. Please wait, since this may take a while... + Scanning all disks for Windows installations. Please wait, since this may take a while ... Successfully scanned Windows installations. Total identified Windows installations: 1 {D}:\Windows Add installation to boot list? Yes/No/All: Y From 4f0f4ef0d76ba0c2994f95eec0919cf3f729216a Mon Sep 17 00:00:00 2001 From: "Trond B. Krokli" <38162891+illfated@users.noreply.github.com> Date: Sun, 18 Aug 2019 14:14:56 +0200 Subject: [PATCH 06/10] Update windows/client-management/advanced-troubleshooting-boot-problems.md - remove indented Note text about creating installation media. Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../client-management/advanced-troubleshooting-boot-problems.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index ea1e2def64..f8be9b60e0 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -102,7 +102,6 @@ To do this, follow these steps. > For additional methods to start WinRE, see [Windows Recovery Environment (Windows RE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre). 1. Start the system to the installation media for the installed version of Windows. - **Note** For more information, see [Create installation media for Windows](https://support.microsoft.com/help/15088). 2. On the **Install Windows** screen, select **Next** > **Repair your computer**. From 00ce676a648d67e7e2d6f19445880790573f4cab Mon Sep 17 00:00:00 2001 From: "Trond B. Krokli" <38162891+illfated@users.noreply.github.com> Date: Sun, 18 Aug 2019 14:16:23 +0200 Subject: [PATCH 07/10] Update windows/client-management/advanced-troubleshooting-boot-problems.md - add previously removed text about creating installation media. Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../client-management/advanced-troubleshooting-boot-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index f8be9b60e0..5631e6ea44 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -101,7 +101,7 @@ To do this, follow these steps. > [!NOTE] > For additional methods to start WinRE, see [Windows Recovery Environment (Windows RE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre). -1. Start the system to the installation media for the installed version of Windows. +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). 2. On the **Install Windows** screen, select **Next** > **Repair your computer**. From ffb7a227228b9fe64d02540d66c65d161e764052 Mon Sep 17 00:00:00 2001 From: illfated Date: Sun, 18 Aug 2019 14:57:11 +0200 Subject: [PATCH 08/10] Update Method 4 description text - include method 3 in the mentioned methods tested before method 4 --- .../client-management/advanced-troubleshooting-boot-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 5631e6ea44..3ecd021c5c 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -184,7 +184,7 @@ After you run the command, you receive the following output: ### Method 4: Replace Bootmgr -If methods 1 and 2 do not fix the problem, replace the Bootmgr file from drive C to the System Reserved partition. To do this, follow these steps: +If methods 1, 2 and 3 do not fix the problem, replace the Bootmgr file from drive C to the System Reserved partition. To do this, follow these steps: 1. At a command prompt, change the directory to the System Reserved partition. From 7603218f3b5f40f17b1d3140cfac876c794ab42d Mon Sep 17 00:00:00 2001 From: illfated Date: Sun, 18 Aug 2019 15:22:43 +0200 Subject: [PATCH 09/10] MarkDown consistency follow-up + typo correction - add missing "DOS" code blocks for CMD outputs - add missing MarkDown spacing in quote indents for Note & Warning boxes - resolve a typo (winodw -> window) - add consistency by using uppercase letters for the command DISM --- .../advanced-troubleshooting-boot-problems.md | 27 +++++++++++-------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 3ecd021c5c..6dd05047b9 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -151,15 +151,18 @@ If you receive BCD-related errors, follow these steps: ``` 4. You might receive one of the following outputs: - - - Scanning all disks for Windows installations. Please wait, since this may take a while ... + ```dos + Scanning all disks for Windows installations. Please wait, since this may take a while ... Successfully scanned Windows installations. Total identified Windows installations: 0 The operation completed successfully. + ``` - - Scanning all disks for Windows installations. Please wait, since this may take a while ... + ```dos + Scanning all disks for Windows installations. Please wait, since this may take a while ... Successfully scanned Windows installations. Total identified Windows installations: 1 D:\Windows Add installation to boot list? Yes/No/All: + ``` If the output shows **windows installation: 0**, run the following commands: @@ -175,10 +178,12 @@ bootrec /rebuildbcd After you run the command, you receive the following output: + ```dos Scanning all disks for Windows installations. Please wait, since this may take a while ... Successfully scanned Windows installations. Total identified Windows installations: 1 {D}:\Windows Add installation to boot list? Yes/No/All: Y + ``` 5. Try restarting the system. @@ -268,16 +273,16 @@ For detailed instructions, see [How to perform a clean boot in Windows](https:// 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)](https://blogs.technet.microsoft.com/askcore/2012/04/15/troubleshooting-boot-issues-due-to-missing-driver-signature-x64/) ->[!NOTE] ->If the computer is a domain controller, try Directory Services Restore mode (DSRM). +> [!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" +> This method is an important step if you encounter Stop error "0xC00002E1" or "0xC00002E2" **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 +> [!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 problems can be solved. Modify the registry at your own risk. *Error code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)* @@ -308,11 +313,11 @@ For additional troubleshooting steps, see the following articles: To fix problems that occur after you install Windows updates, check for pending updates by using these steps: -1. Open a Command Prompt winodw in WinRE. +1. Open a Command Prompt window in WinRE. 2. Run the command: ```dos - dism /image:C:\ /get-packages + DISM /image:C:\ /get-packages ``` 3. If there are any pending updates, uninstall them by running the following commands: @@ -320,7 +325,7 @@ To fix problems that occur after you install Windows updates, check for pending DISM /image:C:\ /remove-package /packagename: name of the package ``` ```dos - Dism /Image:C:\ /Cleanup-Image /RevertPendingActions + DISM /Image:C:\ /Cleanup-Image /RevertPendingActions ``` Try to start the computer. From e5de9a81b04e7f0676a533a1a0ae520941d900d2 Mon Sep 17 00:00:00 2001 From: illfated Date: Sun, 18 Aug 2019 15:27:31 +0200 Subject: [PATCH 10/10] Code block correction - remove indent to make the actual code block work as intended, instead of the code block fence being part of the shown code. --- .../advanced-troubleshooting-boot-problems.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 6dd05047b9..5f1c4ea9c9 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -178,12 +178,12 @@ bootrec /rebuildbcd After you run the command, you receive the following output: - ```dos - Scanning all disks for Windows installations. Please wait, since this may take a while ... - Successfully scanned Windows installations. Total identified Windows installations: 1 - {D}:\Windows - Add installation to boot list? Yes/No/All: Y - ``` +```dos +Scanning all disks for Windows installations. Please wait, since this may take a while ... +Successfully scanned Windows installations. Total identified Windows installations: 1 +{D}:\Windows +Add installation to boot list? Yes/No/All: Y +``` 5. Try restarting the system.