deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 19:03:46 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update advanced-troubleshooting-boot-problems.md

Browse Source 
- 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
This commit is contained in:
illfated
2019-08-08 23:28:54 +02:00
parent 7cbf92d618
commit e3c14786ed
1 changed files with 27 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
windows/client-management/advanced-troubleshooting-boot-problems.md
View File

@ -14,8 +14,8 @@ ms.topic: troubleshooting
# Advanced troubleshooting for Windows boot problems # Advanced troubleshooting for Windows boot problems
>[!NOTE] > [!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/help/12415).
## Summary ## 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. Each phase has a different approach to troubleshooting. This article provides troubleshooting techniques for problems that occur during the first three phases.
>[!NOTE] > [!NOTE]
>If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle: > 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 ## BIOS phase
@ -98,8 +98,8 @@ The Startup Repair tool automatically fixes many common problems. The tool also
To do this, follow these steps. To do this, follow these steps.
>[!NOTE] > [!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 [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. 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). **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 BOOTREC /FIXBOOT
``` ```
>[!NOTE] > [!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 ### 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: 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. 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 D:\Windows
Add installation to boot list? Yes/No/All: Add installation to boot list? Yes/No/All:
@ -165,7 +167,7 @@ If the output shows **windows installation: 0**, run the following commands:
```dos ```dos
bcdedit /export c:\bcdbackup bcdedit /export c:\bcdbackup
attrib c:\\boot\\bcd -h -r –s attrib c:\\boot\\bcd -r –s -h
ren c:\\boot\\bcd bcd.old ren c:\\boot\\bcd bcd.old
@ -174,10 +176,12 @@ bootrec /rebuildbcd
After you run the command, you receive the following output: 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 Scanning all disks for Windows installations. Please wait, since this may take a while...
Add installation to boot list? Yes/No/All: Y 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 ### 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: 2. Run the **attrib** command to unhide the file:
```dos ```dos
attrib-s -h -r attrib -r -s -h
``` ```
3. Run the same **attrib** command on the Windows (system drive): 3. Run the same **attrib** command on the Windows (system drive):
```dos ```dos
attrib-s -h –r attrib -r -s -h
``` ```
4. Rename the Bootmgr file as Bootmgr.old: 4. Rename the Bootmgr file as Bootmgr.old:
```dos ```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. 7. Restart the computer.
8. Restart the computer.
### Method 5: Restore System Hive ### Method 5: Restore System Hive