From 0b54331172ecc794b48f6e38556881adbd7137cb Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Sat, 18 Dec 2021 10:05:59 +0500 Subject: [PATCH 1/3] Update advanced-troubleshooting-boot-problems.md --- .../advanced-troubleshooting-boot-problems.md | 42 +++---------------- 1 file changed, 6 insertions(+), 36 deletions(-) diff --git a/windows/client-management/advanced-troubleshooting-boot-problems.md b/windows/client-management/advanced-troubleshooting-boot-problems.md index 8a7c060339..0c976ceceb 100644 --- a/windows/client-management/advanced-troubleshooting-boot-problems.md +++ b/windows/client-management/advanced-troubleshooting-boot-problems.md @@ -150,49 +150,19 @@ If you receive BCD-related errors, follow these steps: 2. Restart the computer to check whether the problem is fixed. -3. If the problem is not fixed, run the following command: - - ```console - Bootrec /rebuildbcd - ``` - -4. You might receive one of the following outputs: - - ```console - 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. - ``` - - ```console - 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: +3. If the problem is not fixed, run the following commands: ```console bcdedit /export c:\bcdbackup - attrib c:\\boot\\bcd -r –s -h + attrib c:\boot\bcd -r -s -h - ren c:\\boot\\bcd bcd.old + ren c:\boot\bcd bcd.old bootrec /rebuildbcd ``` - - After you run the command, you receive the following output: - - ```console - 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. +4. Restart the system. ### Method 4: Replace Bootmgr @@ -206,7 +176,7 @@ If methods 1, 2 and 3 do not fix the problem, replace the Bootmgr file from driv attrib -r -s -h ``` -3. Run the same **attrib** command on the Windows (system drive): +3. Navigate to the system drive and run the same command: ```console attrib -r -s -h @@ -394,7 +364,7 @@ If the dump file shows an error that is related to a driver (for example, window - To do this, open WinRE, open a command prompt, and then run the following command: ```console - SFC /Scannow /OffBootDir=C:\ /OffWinDir=E:\Windows + 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) From d8387f1fd56d24278ca2b7f4aa4c9cf82e5e894c Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Sat, 18 Dec 2021 10:14:25 +0500 Subject: [PATCH 2/3] Update trusted-platform-module-services-group-policy-settings.md --- .../trusted-platform-module-services-group-policy-settings.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md b/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md index 56600aa23a..c934a6161a 100644 --- a/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md +++ b/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md @@ -36,7 +36,7 @@ The following Group Policy settings were introduced in Windows. ## Configure the level of TPM owner authorization information available to the operating system >[!IMPORTANT] ->Beginning with Windows 10 version 1607 and Windows Server 2016, this policy setting is no longer used by Windows, but it continues to appear in GPEdit.msc for compatibility with previous versions. Beginning with Windows 10 version 1703, the default value is 5. This value is implemented during provisioning so that another Windows component can either delete it or take ownership of it, depending on the system configuration. For TPM 2.0, a value of 5 means keep the lockout authorization. For TPM 1.2, it means discard the Full TPM owner authorization and retain only the Delegated authorization. +>Beginning with Windows 10 version 1703, the default value is 5. This value is implemented during provisioning so that another Windows component can either delete it or take ownership of it, depending on the system configuration. For TPM 2.0, a value of 5 means keep the lockout authorization. For TPM 1.2, it means discard the Full TPM owner authorization and retain only the Delegated authorization. This policy setting configured which TPM authorization values are stored in the registry of the local computer. Certain authorization values are required in order to allow Windows to perform certain actions. @@ -149,4 +149,4 @@ If you don't want users to see the recommendation to update TPM firmware, you ca - [Trusted Platform Module](trusted-platform-module-top-node.md) - [TPM Cmdlets in Windows PowerShell](/powershell/module/trustedplatformmodule/?view=win10-ps&preserve-view=true) -- [Prepare your organization for BitLocker: Planning and Policies - TPM configurations](../bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies.md) \ No newline at end of file +- [Prepare your organization for BitLocker: Planning and Policies - TPM configurations](../bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies.md) From 3e908026f1ace25e9b0f3738d9a602248ed75f44 Mon Sep 17 00:00:00 2001 From: Tina Burden Date: Mon, 20 Dec 2021 07:41:42 -0800 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../trusted-platform-module-services-group-policy-settings.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md b/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md index c934a6161a..c70105fc3b 100644 --- a/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md +++ b/windows/security/information-protection/tpm/trusted-platform-module-services-group-policy-settings.md @@ -35,8 +35,8 @@ The following Group Policy settings were introduced in Windows. ## Configure the level of TPM owner authorization information available to the operating system ->[!IMPORTANT] ->Beginning with Windows 10 version 1703, the default value is 5. This value is implemented during provisioning so that another Windows component can either delete it or take ownership of it, depending on the system configuration. For TPM 2.0, a value of 5 means keep the lockout authorization. For TPM 1.2, it means discard the Full TPM owner authorization and retain only the Delegated authorization. +> [!IMPORTANT] +> Beginning with Windows 10 version 1703, the default value is 5. This value is implemented during provisioning so that another Windows component can either delete it or take ownership of it, depending on the system configuration. For TPM 2.0, a value of 5 means keep the lockout authorization. For TPM 1.2, it means discard the Full TPM owner authorization and retain only the Delegated authorization. This policy setting configured which TPM authorization values are stored in the registry of the local computer. Certain authorization values are required in order to allow Windows to perform certain actions.