From 9d9ddaa541b5c29ff2e60acb1b7f58e52bc02486 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Sun, 28 Feb 2021 22:55:22 +0500 Subject: [PATCH 1/3] Added another cause of boot failure If there is a blank GPT entry, the boot partition will not work. Added this info. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/9145 --- .../client-management/troubleshoot-inaccessible-boot-device.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/client-management/troubleshoot-inaccessible-boot-device.md b/windows/client-management/troubleshoot-inaccessible-boot-device.md index bdb67e2528..ceefb0fe5e 100644 --- a/windows/client-management/troubleshoot-inaccessible-boot-device.md +++ b/windows/client-management/troubleshoot-inaccessible-boot-device.md @@ -37,6 +37,8 @@ Any one of the following factors might cause the stop error: * Corrupted files in the **Boot** partition (for example, corruption in the volume that's labeled **SYSTEM** when you run the `diskpart` > `list vol` command) +* If there is a blank GPT entry before the entry of the boot partition. + ## Troubleshoot this error Start the computer in [Windows Recovery Mode (WinRE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre). To do this, follow these steps. From cb68de8b985e65faa8913cb889f5e61ae7b1365e Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Sun, 28 Feb 2021 23:29:07 +0500 Subject: [PATCH 2/3] Update windows/client-management/troubleshoot-inaccessible-boot-device.md Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../client-management/troubleshoot-inaccessible-boot-device.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/troubleshoot-inaccessible-boot-device.md b/windows/client-management/troubleshoot-inaccessible-boot-device.md index ceefb0fe5e..c56106854e 100644 --- a/windows/client-management/troubleshoot-inaccessible-boot-device.md +++ b/windows/client-management/troubleshoot-inaccessible-boot-device.md @@ -37,7 +37,7 @@ Any one of the following factors might cause the stop error: * Corrupted files in the **Boot** partition (for example, corruption in the volume that's labeled **SYSTEM** when you run the `diskpart` > `list vol` command) -* If there is a blank GPT entry before the entry of the boot partition. +* If there is a blank GPT entry before the entry of the **Boot** partition. ## Troubleshoot this error From 2d2969a93faf1bcd5f9dd53c3405fb08dcb092b8 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Mon, 1 Mar 2021 12:23:03 +0500 Subject: [PATCH 3/3] Update windows/client-management/troubleshoot-inaccessible-boot-device.md Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../troubleshoot-inaccessible-boot-device.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/client-management/troubleshoot-inaccessible-boot-device.md b/windows/client-management/troubleshoot-inaccessible-boot-device.md index c56106854e..5a4572c445 100644 --- a/windows/client-management/troubleshoot-inaccessible-boot-device.md +++ b/windows/client-management/troubleshoot-inaccessible-boot-device.md @@ -35,9 +35,9 @@ Any one of the following factors might cause the stop error: * In unusual cases, the failure of the TrustedInstaller service to commit newly installed updates is because of component-based store corruptions -* Corrupted files in the **Boot** partition (for example, corruption in the volume that's labeled **SYSTEM** when you run the `diskpart` > `list vol` command) +* Corrupted files in the **Boot** partition (for example, corruption in the volume that's labeled **SYSTEM** when you run the `diskpart` > `list vol` command) -* If there is a blank GPT entry before the entry of the **Boot** partition. +* If there is a blank GPT entry before the entry of the **Boot** partition ## Troubleshoot this error