Onedrive seems to have created its own drive G partition and moved my previous drive G partition to drive L

(1) As was said earlier, your Disk Management is fine. It is normal for it not to show the secret MSR (Microsoft Reserved) partition. Yours is partition 1 on Disk 0. That pushes all the others up...

DISKPART> list part

Partition ### Type Size Offset

---

Partition 1 Reserved 128 MB 17 KB <<<MSR partition -- Disk 0, Partition 1

Partition 2 System 100 MB 129 MB <<<EFI -- Disk 0, Partition 2

Partition 3 Primary 930 GB 229 MB <<<Windows (C:)

Partition 4 Recovery 627 MB 930 GB <<<Recovery -- Disk 0. Partition 4

(2) You have proven your DVD will work properly when booted through the BIOS Boot Menu which is F8 for you. That is good. So, memorize how to do a /Import there (if/when necessary), which is...

DiskPart <<<Enter DiskPart

List Vol <<<List the volumes & their letters

Exit <<<Exit DiskPart

=== You should recognize the Windows volume by its label or size ===

=== Note its letter which may not be C: in this environment ===

=== Use that letter instead of X: in the following command ===

BCDEdit /Import X:\BU\BCD_Backup /Clean <<<Restore the backup BCD

Close the Command Prompt, & click "Continue" to return to Windows.

(3) You made a typo with...

BCDEdit /Set {fwbootmgr} Displayorder {bootmgr} /Addfirst

Instead of {bootmgr}, you entered a second {fw...}. I'm surprised there wasn't an error message. It did nothing. It did not add {bootmgr} to the top. Therefore, it never went to {bootmgr}. And that probably was a good thing, because you did enter the following correctly, but it didn't work (though it said it did)...

BCDEdit /Set {bootmgr} Device partition=\Device\HarddiskVolume2

Instead, it left the value at "unknown". So, it would have been a failed boot, (& you'd have had to do the /Import). But you did get the Path from the other command...

I don't know what to make of that. It's spooky. But let's try it booted to Windows at an Administrator Command Prompt...

Type "CMD" into Search, & click "Run as Administrator".

BCDEdit /Enum {bootmgr} <<<Show old {bootmgr}

BCDEdit /Set {bootmgr} Device partition=\Device\HarddiskVolume2

BCDEdit /Enum {bootmgr} <<<Show new {bootmgr}

If the Device is there & the Path is still there, then do this (otherwise don't do it)...

BCDEdit /Enum {fwbootmgr} <<<Show current {fwbootmgr}

BCDEdit /Set {fwbootmgr} Displayorder {bootmgr} /Addfirst

BCDEdit /Enum {fwbootmgr} <<<Show new {fwbootmgr}

That should add {bootmgr} to the top of the Displayorder list, meaning the next boot will go there. If all looks good, try the reboot. If it fails to boot, do the /Import using the DVD if necessary. (But if it gives you access to the internal recovery environment, use that.)

We may not need to do the /RebuildBCD. If this much works, we probably can fix your recovery environment entries in a similar manner using ReagentC. Then Shift+Restart will get you there.

Hi PCR...

My head hurts! based on all your responses above, I pulled together as much as I could to try and get this right. I got more things to go what seems to be correct, but not sure all is good ...yet (if it can be made good).

So here's what I did today... for now I ignored the remove Letter H that you said was attached to the recovery partition

1. with the DVD in the drive, restarted PC and when the message to press Del or F2 came up on the screen kept pressing F8 as per the linked article you cave me to get hotkeys access to the Bios settings. When the list of options came up I chose the UEFI option from a list of more than in my Normal Bios.
2. When the message came up to press any key to continue (took a while to find the any key :-) think 'm a little punchy by now, I hit the enter key.

3 Windows installation screen came up and this time looked different that before (smaller) but still only had the install or repair option. I clicked on repair. and the choose an option screen came up .. I chose Troubleshoot.

4. Troubleshoot produced the following screen and I chose Command prompt

Once in the command prompt followed your instructions.

(3) Your BCD looks as before. We want /RebuildBCD to fix that. The Firmware Boot Manager (fwbootmgr) doesn't go to the Windows Boot Manager....

I did not see anything that addressed this in your instructions following next, but did follow then precisely and all commands executed successfully :

Here would be a fix...

(a) Add {bootmgr} to top of Displayorder, meaning boot will go there...

BCDEdit /Enum {fwbootmgr} <<<Show current {fwbootmgr}

BCDEdit /Set {fwbootmgr} Displayorder {bootmgr} /Addfirst

BCDEdit /Enum {fwbootmgr} <<<Show new {fwbootmgr}

(b) Fix Device & Path in the {bootmgr}...

BCDEdit /Enum {bootmgr}

BCDEdit /Set {bootmgr} Device partition=\Device\HarddiskVolume2

BCDEdit /Set {bootmgr} Path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

BCDEdit /Enum {bootmgr}

So now you should see {bootmgr} at the top of the Displayorder list, & it has Device & Path values. If you don't see it, then restore your backup before you reboot...

---

BCDEdit /Import C:\BU\BCD_Backup /Clean

The results of the doing the above are shown below...

the next screen shows the operations for your part (b) above

Notice that the device is marked as Unknown, but the path information is there. I think this is still a problem no?

Since all executed successfully, I assumed things were good so I rebooted and used diskpart under windows the remove the Letter H from the partition assigned to. is seemed to work ok as H is no longer there, as it no longer appears in file explorer/

however, when I look at disk management things look a bit wonky I think...

Notice the red arrow. Pointing to Disk 0 ( windows system SSD) show partition 2 being the EFI partition, but it is partition 1, while where the arrow is pointing says it is partition 4 but there is no partition 4 but the partition it points to is partition 3 based on the size of 627 MB

So my questions now are:

1. is everything OK (despite me thinking not so)

2. Is the BCD OK or still needing to be fixed (somehow)?

3. What about the ..."Your BCD looks as before. We want /RebuildBCD to fix that." ? If need to do this still please tell me how and where this needs to be done. and will that fix things?

Thanks for sticking with me on this. I so very much appreciate your help.

Cheers!

Garry

(1) OK, you've got a backup of the current BCD (C:\BU\BCD_Backup) which can be restored as I wrote earlier (if necessary). But we need to be sure you can get that DVD booted properly in order to do it (since we can't trust the internal recovery environment yet). Yes, try to boot to it as I wrote using the Boot Menu F-Key while in UEFI mode. That will constitute a UEFI boot to the DVD. Hopefully, it can then do UEFI work. No need to remake the backup, but see whether you can do a BCDEdit.

(2) How did that letter H get onto your Recovery partition? It really shouldn't be there in Windows. It will get one automatically in the recovery environment, but it shouldn't last rebooted back to Windows. This shouldn't affect your letter G.

DiskPart <<<Enter DiskPart

List Vol <<<List the volume numbers & letters

Select Vol 3 <<<Select the Recovery volume

Remove Letter=H <<<Remove its letter

List Vol <<<Show the letter is gone

Exit <<<Exit

(3) Your BCD looks as before. We want /RebuildBCD to fix that. The Firmware Boot Manager (fwbootmgr) doesn't go to the Windows Boot Manager....

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {c4337ee8-11b0-11ec-ab4f-806e6f6e6963} <<<What is this? A mini {bootmgr}?

                        {c4337ee7-11b0-11ec-ab4f-806e6f6e6963}       <<<A hard drive -- but which?

                        {c4337ee3-11b0-11ec-ab4f-806e6f6e6963}       <<<CD/DVD drive

                        {c4337ee6-11b0-11ec-ab4f-806e6f6e6963}       <<<What is this? A mini {bootmgr}?

timeout 0

And the real Windows Boot Manager has lost its device & path values...

Windows Boot Manager

---

identifier {bootmgr}

device unknown

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

resumeobject {00699258-3744-11eb-956e-efd836ee9db2}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Here would be a fix...

(a) Add {bootmgr} to top of Displayorder, meaning boot will go there...

BCDEdit /Enum {fwbootmgr} <<<Show current {fwbootmgr}

BCDEdit /Set {fwbootmgr} Displayorder {bootmgr} /Addfirst

BCDEdit /Enum {fwbootmgr} <<<Show new {fwbootmgr}

(b) Fix Device & Path in the {bootmgr}...

BCDEdit /Enum {bootmgr}

BCDEdit /Set {bootmgr} Device partition=\Device\HarddiskVolume2

BCDEdit /Set {bootmgr} Path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

BCDEdit /Enum {bootmgr}

So now you should see {bootmgr} at the top of the Displayorder list, & it has Device & Path values. If you don't see it, then restore your backup before you reboot...

BCDEdit /Import C:\BU\BCD_Backup /Clean

Otherwise, do the reboot. But -- if it doesn't -- you'll have to find a way to get to a recovery environment & do the /Import as I wrote earlier, i.e., do a List Vol to see the letter Windows has there first. Actually, that puts you in the same boat as if we just go ahead & do the /RebuildBCD.

HI PCR .. in reading through your last response, there is much to digest there. I decided to tackle each item, one by one starting with (1) question in green below, and post the results from there before continuing on to part 2 whuch I =need ed to reread several times. I am hoping that this first question being answered will be able to determine what if anything needs to be done next. I have included screen shots of disk management as well as diskpart info as requested. lets see where we are at now.

(1) Can you do those BCDEdit commands while booted to Windows? YES I can How about at the internal recovery environment (Shift+Restart)? Did Not TRy since was able to do it in windows directly Then let me see a "BCDEdit /Enum All".

yes... I managed to do several BCDEdit commands and have them work while booted to windows. included creating the backup of the BCD and the BCDEdit /Enum all. See the bolded text below

2021-10-27 11:12 AM

Microsoft Windows [Version 10.0.19042.1288]

(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd \

C:&gt;dir

Volume in drive C is Local Disk

Volume Serial Number is 3FA8-6782

Directory of C:\

09/13/2021 02:14 PM <DIR> $WINDOWS.~BT

09/12/2019 05:33 PM 0 a.txt

10/14/2014 09:06 PM 72 Autoconfig.ini

10/12/2021 06:18 PM 31,834 b$ cclear-ON1 and others 2021-10-12.reg

10/25/2021 01:16 PM <DIR> BU

04/08/2014 07:34 PM 262,144 BzEngineTempFile16217.dk

03/22/2016 05:23 PM 9,835 config.xml

09/26/2019 08:56 AM <DIR> easeus_tb_cloud

09/13/2021 05:03 PM <DIR> ESD

04/29/2020 06:40 PM <DIR> HP Universal Print Driver

03/11/2016 06:13 PM <DIR> HP_LaserJet_Pro_MFP_M127-M128

08/11/2021 12:57 PM <DIR> HP_LaserJet_Pro_MFP_M225-M226

03/11/2016 07:18 PM <DIR> HP_M127_128_FW_Update

12/05/2020 02:38 PM <DIR> inetpub

11/08/2016 09:38 AM 68,400 INFO.2

01/03/2014 03:32 PM <DIR> Intel

04/26/2016 11:35 PM <DIR> Logs

09/04/2019 06:21 PM 562 most recent - map network drive to Igiveup.reg

10/21/2016 08:36 AM <DIR> NPE

12/07/2019 02:14 AM <DIR> PerfLogs

10/23/2021 05:10 PM <DIR> Program Files

10/12/2021 04:56 PM <DIR> Program Files (x86)

12/02/2014 09:40 PM <DIR> reduced size

12/07/2019 12:49 PM <DIR> Reg backup

10/21/2016 08:28 AM 248 rescue.info

08/17/2015 05:46 PM <DIR> System.sav

09/09/2021 02:00 PM <DIR> temp

07/09/2021 04:46 PM <DIR> Users

10/26/2021 05:10 PM <DIR> Windows

12/23/2017 08:14 PM <DIR> Windows10Upgrade

           8 File(s)        373,095 bytes 

          22 Dir(s)  709,660,008,448 bytes free 

C:&gt;cd windows

C:\Windows>cd system32

<<<<<<<<<------- entered dir command here and listed a ton of directories that I deleted as irrelevent here------------>

        5068 File(s)  2,770,439,279 bytes 

         211 Dir(s)  709,659,840,512 bytes free 

C:\Windows\System32>cd bu

The system cannot find the path specified.

---

C:\Windows\System32>cd \bu

---

C:\BU>dir

Volume in drive C is Local Disk

Volume Serial Number is 3FA8-6782

---

Directory of C:\BU

---

10/25/2021 01:16 PM <DIR> .

10/25/2021 01:16 PM <DIR> ..

           **0 File(s)              0 bytes** 

           **2 Dir(s)  709,659,119,616 bytes free** 

---

---

C:\BU>bcdedit /Export C:\bu\BCD_Backup

The operation completed successfully.

---

C:\BU>dir

Volume in drive C is Local Disk

Volume Serial Number is 3FA8-6782

---

Directory of C:\BU

---

10/27/2021 11:11 AM <DIR> .

10/27/2021 11:11 AM <DIR> ..

10/27/2021 11:11 AM 32,768 BCD_Backup

           **1 File(s)         32,768 bytes** 

           **2 Dir(s)  709,658,501,120 bytes free** 

---

C:\BU>

exited from cmd at this point

---

came back into Cmd here and tried the BCDEit /Enum all...

---

Microsoft Windows [Version 10.0.19042.1288]

(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>bcdedit /enum All

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {c4337ee8-11b0-11ec-ab4f-806e6f6e6963}

                    {c4337ee7-11b0-11ec-ab4f-806e6f6e6963} 

                    {c4337ee3-11b0-11ec-ab4f-806e6f6e6963} 

                    {c4337ee6-11b0-11ec-ab4f-806e6f6e6963} 

timeout 0

Windows Boot Manager

---

identifier {bootmgr}

device unknown

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

resumeobject {00699258-3744-11eb-956e-efd836ee9db2}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Firmware Application (101fffff)

---

identifier {c4337ee3-11b0-11ec-ab4f-806e6f6e6963}

description CD/DVD Drive

Firmware Application (101fffff)

---

identifier {c4337ee6-11b0-11ec-ab4f-806e6f6e6963}

device partition=\Device\HarddiskVolume2

path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

description Windows Boot Manager

Firmware Application (101fffff)

---

identifier {c4337ee7-11b0-11ec-ab4f-806e6f6e6963}

description Hard Drive

Firmware Application (101fffff)

---

identifier {c4337ee8-11b0-11ec-ab4f-806e6f6e6963}

device partition=\Device\HarddiskVolume2

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

Windows Boot Loader

---

identifier {current}

device partition=C:

path \WINDOWS\system32\winload.efi

description Windows 10

locale en-US

inherit {bootloadersettings}

recoverysequence {201ca33c-3744-11eb-ab08-a9da93046d68}

displaymessageoverride Recovery

recoveryenabled Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \WINDOWS

resumeobject {00699258-3744-11eb-956e-efd836ee9db2}

nx OptIn

bootmenupolicy Standard

Windows Boot Loader

---

identifier {201ca33c-3744-11eb-ab08-a9da93046d68}

device partition=H:

path \windows\system32\winload.efi

description Windows Recovery Environment

locale en-US

inherit {bootloadersettings}

displaymessage Recovery

osdevice partition=H:

systemroot \windows

nx OptIn

bootmenupolicy Standard

winpe Yes

Windows Boot Loader

---

identifier {becbfbbb-74c1-11e3-a193-d3e592cc6be4}

device partition=C:

path \windows\system32\winload.efi

description Windows Recovery Environment

inherit {bootloadersettings}

osdevice partition=C:

systemroot \windows

nx OptIn

winpe Yes

Resume from Hibernate

---

identifier {00699258-3744-11eb-956e-efd836ee9db2}

device partition=C:

path \WINDOWS\system32\winresume.efi

description Windows Resume Application

locale en-US

inherit {resumeloadersettings}

recoverysequence {201ca33c-3744-11eb-ab08-a9da93046d68}

recoveryenabled Yes

allowedinmemorysettings 0x15000075

filedevice partition=C:

filepath \hiberfil.sys

bootmenupolicy Standard

debugoptionenabled No

Windows Memory Tester

---

identifier {memdiag}

device unknown

path \boot\memtest.exe

description Windows Memory Diagnostic

locale en-US

inherit {globalsettings}

badmemoryaccess Yes

EMS Settings

---

identifier {emssettings}

bootems No

Debugger Settings

---

identifier {dbgsettings}

debugtype Serial

debugport 1

baudrate 115200

RAM Defects

---

identifier {badmemory}

Global Settings

---

identifier {globalsettings}

inherit {dbgsettings}

                    {emssettings} 

                    {badmemory} 

Boot Loader Settings

---

identifier {bootloadersettings}

inherit {globalsettings}

                    {hypervisorsettings} 

Hypervisor Settings

---

identifier {hypervisorsettings}

hypervisordebugtype Serial

hypervisordebugport 1

hypervisorbaudrate 115200

Resume Loader Settings

---

identifier {resumeloadersettings}

inherit {globalsettings}

Device options

---

identifier {201ca33d-3744-11eb-ab08-a9da93046d68}

description Windows Recovery

ramdisksdidevice partition=H:

ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options

---

identifier {becbfbbc-74c1-11e3-a193-d3e592cc6be4}

description Ramdisk Options

ramdisksdidevice partition=C:

ramdisksdipath \Recovery\becbfbbb-74c1-11e3-a193-d3e592cc6be4\boot.sdi

C:\WINDOWS\system32>

then exited.

disk management screen shot...follows

![Image](https://learn-attachment.microsoft.com/api/attachments/0397f100-c5be-490e-b90b-32a59d4fddf9?platform=QnA

and here is the related DiskPart info. I find it curious that Volume 0 and Volume 1 which are DVD devices are showing up where they are in the bolded lines below

2021-10-27 10:55 AM

Microsoft Windows [Version 10.0.19042.1288]

(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.

On computer: GARRY-INTEL1

DISKPART> list vol

Volume ### Ltr Label Fs Type Size Status Info

---

Volume 0 Y DVD-ROM 0 B No Media

Volume 1 Z DVD-ROM 0 B No Media

Volume 2 C Local Disk NTFS Partition 930 GB Healthy Boot

Volume 3 FAT32 Partition 100 MB Healthy System

Volume 4 H NTFS Partition 627 MB Healthy Hidden

Volume 5 D Application NTFS Partition 58 GB Healthy

Volume 6 E Data1 NTFS Partition 429 GB Healthy

Volume 7 F Data2 NTFS Partition 488 GB Healthy

Volume 8 G WorkArea1 NTFS Partition 886 GB Healthy

Volume 9 I Removable 0 B No Media

Volume 10 J Removable 0 B No Media

Volume 11 K Removable 0 B No Media

Volume 12 M Removable 0 B No Media

DISKPART> select vol 3

Volume 3 is the selected volume.

DISKPART> detail part

Partition 2

Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b

Hidden : Yes

Required: No

Attrib : 0X8000000000000000

Offset in Bytes: 135266304

Volume ### Ltr Label Fs Type Size Status Info

---

* Volume 3 FAT32 Partition 100 MB Healthy System

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.

On computer: GARRY-INTEL1

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset

---

Partition 1 Reserved 128 MB 17 KB

Partition 2 System 100 MB 129 MB

Partition 3 Primary 930 GB 229 MB

Partition 4 Recovery 627 MB 930 GB

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.

On computer: GARRY-INTEL1

DISKPART> select vol 2

Volume 2 is the selected volume.

DISKPART> detail part

Partition 3

Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

Hidden : No

Required: No

Attrib : 0000000000000000

Offset in Bytes: 240123904

Volume ### Ltr Label Fs Type Size Status Info

---

* Volume 2 C Local Disk NTFS Partition 930 GB Healthy Boot

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>

I did try to deal with item (2) of yours but I may not have booted correctly into the bios as I just did the normal delete key press while booting. The link you provided says different key required to get to the bootmgr options. Doing it the way I did, produced the same failed results as before with the BCDEdit commands.

If you want me to go ahead and follow the steps in item 2 more carefully this time I will if you think it is necessary.

Thanks again for all your help.

Cheers!

Garry

(1) Can you do those BCDEdit commands while booted to Windows? How about at the internal recovery environment (Shift+Restart)? Then let me see a "BCDEdit /Enum All".

(2) That DVD looks like UEFI alright. Did you boot to it properly? This means not only that BIOS must be in UEFI mode, but, if it offers two options to boot the DVD, you must choose the one that says it's UEFI. Mine precedes the DVD identifier with "UEFI:", but it gives me only that one choice. I just booted to it, & it it did the /Export just fine. If you've got a BIOS that can be in both UEFI & Legacy at once, then I guess you'd get the choice. Mine can only be set to one or the other.

(a) Ensure BIOS is set to UEFI mode (or at least to both at once).

(b) The Boot Menu should be set to the Windows Boot Manager (bootmgr). Don't move the DVD above it.

(c) Insert the DVD, & boot the computer.

(d) At the manufacturer's logo (or shortly before) press the F-Key that gets to the BIOS Boot Menu screen. If you don't know it, look in here...

https://www.sysnative.com/forums/threads/get-access-to-bios-settings-boot-menu-f-keys-hotkeys-by-system-manufacturer-oem.23010/ Get access to BIOS settings & Boot Menu: F-keys/Hotkeys by System Manufacturer (OEM)

Note: That 3rd-party site is knowledgeable, but I know nothing of any downloads or links that are there.

(e) Select the DVD boot item that says it's UEFI.

(f) You will see a "Press any key" message to boot the DVD. If not pressed in time, the boot will go to Windows.

(3) You are right, volume numbers & disk numbers don't necessarily match. Mine didn't either. It was Dell put that label (ESP - EFI System Partition) on my EFI. Your EFI partition has a wrong Attrib. I doubt it caused this problem, but fix it this way...

DiskPart <<<Enter DiskPart

List Vol <<<List the volume numbers

Select Vol 3 <<<Select the EFI volume -- yours likely still is 3

GPT ATTRIBUTES=0x8000000000000000

Detail Part <<<Show partition details

Exit <<<Exit

That will prevent the partition from having a drive letter automatically assigned -- not that I see one had been assigned -- but that Attrib is normal for EFI.

(3) EFI, Windows, & Recovery all do show up in your Disk Management. What doesn't show is the MSR (Microsoft Reserved) which is normal. It looks like it is Disk 0, Partition 1 for you. Try...

DiskPart

Select Disk 0

List Part

Exit

Here's mine. The MSR is partition 2 for me, & it doesn't show up in Disk Management...