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

Deleted & reposted as I recalled Bootrec exists only in the recovery environment.

You are welcome. Bootrec only exists in the recovery environment. It's really best to have a Recovery drive or Installation media to get there in this circumstance. Do you have one? Those have an external recovery environment onboard. Otherwise...

(a) Hold Shift as you click Restart to get to the internal recovery environment.

(b) Click "Troubleshoot > Advanced Options > Command Prompt".

(c) Enter the following commands...

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 commands ===

MD X:\BU <<<Make a folder on "C:" named BU

BCDEdit /Export X:\BU\BCD_Backup <<<Backup the BCD into it

DiskPart <<<Enter DiskPart

Select Disk 0 <<<Focus on disk 0

List Part <<<List the partitions

Select Part 2 <<<Focus on partition 2 (EFI System)

Assign Letter=S <<<Give it letter S:

Exit <<<Exit DiskPart

REN S:\efi\microsoft\boot\bcd bcd_old <<<Rename current BCD

Bootrec /RebuildBCD <<<Create fresh BCD

DiskPart <<<Enter DiskPart

Select Vol=S <<<Focus on EFI

Remove Letter=S <<<Remove the letter

Exit <<<Exit DiskPart

That should do it. Close the Command Prompt, & click "Continue" to return to Windows. At an Admin Command Prompt, enter...

BCDEdit /Enum All <<<Show the new BCD

Use Ctrl-A & Ctrl-C to copy, then post it here. I'm unsure the Recovery partition will have activated so that Shift+Restart will continue to work. If not, we can then activate it manually.

If it won't reboot, get into the recovery environment...

(a) An error message may have an "Advanced Options" button that gets there.

(b) Shut the computer 2 times as it tries to boot. On the 3rd attempt to boot it should go there.

(c) Use a Recovery drive or Installation media to get there. Need instructions?

Then, at the "Choose an Option" screen...

(a) Click "Troubleshoot > Advanced Options > Command Prompt".

(b) Enter the following commands...

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.

Hi PCR....

Am trying to follow what your are saying about the BCD?

"I don't know, maybe we should let it be, but I'm inclined to want to regenerate your BCD. Here is what mine looks like...

(a) {bootmgr} is on top in the Firmware Boot Manager.

(b) There are no duplicate, malformed or unused sections.

Microsoft Windows [Version 10.0.19043.1288]

(c) Microsoft Corporation. All rights reserved.

*C:\Windows\system32>*bcdedit /enum all

Firmware Boot Manager "

there is a lot of information after this that I have no idea what it is all about or where or how it is produced.

If I am to create a new BCD can you walk me through the steps please, as you did withthe previous part. Where to start and what to do.

thansk again.

Garry

You are welcome. That looks like a big success so far. Disk Management is showing the Recovery partitions appropriately in both its upper (disk 0 partition 4) & lower pane. DiskPart shows the letter is gone. You are free to use G: elsewhere. Hopefully, the mishap will not recur. I'm unsure what caused it in the first place. I do know, in these later versions of Windows, a letter gets automatically put onto the Recovery partition when you boot into the recovery environment. Also, the letters may scramble & be different there. But it all should be back to normal when rebooted back to Windows. Matbe it was that Attrib value at fault. It wanted Windows to keep the letter on Recovery.

I think your BCD needs a lot of work. I'm inclined to suggest we generate a new one altogether. You've got a {bootmgr} section in there, but it is malformed & unused. There are other unused sections. Instead, from fiirmware (fwbootmgr), there is a jump to this thing...

Firmware Application (101fffff)

---

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

device partition=\Device\HarddiskVolume2

path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

description Windows Boot Manager

That Device & Path belong in your {bootmgr}, & the firmware should be going there. But yours does appear to get the job done. If you hold Shift & click "Restart", does Windows reboot to the recovery environment at the "Choose an Option" screen? And does it have the full panoply of options, including Troubleshoot & Advanced Options buttons? I don't know, maybe we should let it be, but I'm inclined to want to regenerate your BCD. Here is what mine looks like...

(a) {bootmgr} is on top in the Firmware Boot Manager.

(b) There are no duplicate, malformed or unused sections.

Microsoft Windows [Version 10.0.19043.1288]

(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>bcdedit /enum all

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {bootmgr}

                    {140ab3f9-3491-11e7-a4a0-952787f57a8e} 

                    {140ab3fa-3491-11e7-a4a0-952787f57a8e} 

timeout 1

Windows Boot Manager

---

identifier {bootmgr}

device partition=\Device\HarddiskVolume1

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

resumeobject {140ab3fc-3491-11e7-a4a0-952787f57a8e}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Firmware Application (101fffff)

---

identifier {140ab3f9-3491-11e7-a4a0-952787f57a8e}

description Onboard NIC(IPV4)

Firmware Application (101fffff)

---

identifier {140ab3fa-3491-11e7-a4a0-952787f57a8e}

description Onboard NIC(IPV6)

Windows Boot Loader

---

identifier {current}

device partition=C:

path \Windows\system32\winload.efi

description Windows 10

locale en-US

inherit {bootloadersettings}

recoverysequence {140ab3fe-3491-11e7-a4a0-952787f57a8e}

displaymessageoverride CommandPrompt

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \Windows

resumeobject {140ab3fc-3491-11e7-a4a0-952787f57a8e}

nx OptIn

bootmenupolicy Standard

Windows Boot Loader

---

identifier {140ab3fe-3491-11e7-a4a0-952787f57a8e}

device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{140ab3ff-3491-11e7-a4a0-952787f57a8e}

path \windows\system32\winload.efi

description Windows Recovery Environment

locale en-us

inherit {bootloadersettings}

displaymessage Recovery

osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{140ab3ff-3491-11e7-a4a0-952787f57a8e}

systemroot \windows

nx OptIn

bootmenupolicy Standard

winpe Yes

Resume from Hibernate

---

identifier {140ab3fc-3491-11e7-a4a0-952787f57a8e}

device partition=C:

path \Windows\system32\winresume.efi

description Windows Resume Application

locale en-US

inherit {resumeloadersettings}

recoverysequence {140ab3fe-3491-11e7-a4a0-952787f57a8e}

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

filedevice partition=C:

filepath \hiberfil.sys

bootmenupolicy Standard

debugoptionenabled No

Windows Memory Tester

---

identifier {memdiag}

device partition=\Device\HarddiskVolume1

path \EFI\Microsoft\Boot\memtest.efi

description Windows Memory Diagnostic

locale en-US

inherit {globalsettings}

badmemoryaccess Yes

EMS Settings

---

identifier {emssettings}

bootems No

Debugger Settings

---

identifier {dbgsettings}

debugtype Local

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 {140ab3ff-3491-11e7-a4a0-952787f57a8e}

description Windows Recovery

ramdisksdidevice partition=\Device\HarddiskVolume4

ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\Windows\system32>

Hi PCR ....

Here is the latest as per your instructions. Thank you for your reply once again. Most appreciated.

The disk management screen shot is at the end of the cmd information.

In your last reply after the instructions, you said: the following, but I do not know what this means or what needs to be done next if anything. Can you please explain / clarify further ?

"(2) The Firmware Boot Manager in the BCD is a window to the BIOS Boot menu screen. Yours isn't set normally for a UEFI installation.,,

Firmware Boot Manager

---------------------

identifier {fwbootmgr}

displayorder

{c4337ee6-11b0-11ec-ab4f-806e6f6e6963} <<<Direct boot to EFI

{c4337ee7-11b0-11ec-ab4f-806e6f6e6963} <<<Direct to a hard drive

{c4337ee8-11b0-11ec-ab4f-806e6f6e6963} <<<Also direct boot to EFI

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

timeout 0

It should instead boot to the Windows Boot Manager ({bootmgr}). You do have one in the BCD, but it is missing its device & path values. There is a lot amiss in your BCD. I'm thinking we should generate a new one altogether instead of tinkering with this one.

-----------------------------------------------------------------------------------

cmd details follow here:

Microsoft Windows [Version 10.0.19042.1237]

(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> select disk 0

Disk 0 is now the selected disk.

DISKPART> select part 4

Partition 4 is now the selected partition.

DISKPART> detail part

Partition 4

Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

Hidden : Yes

Required: No

Attrib : 0000000000000000

Offset in Bytes: 999546683392

Volume ### Ltr Label Fs Type Size Status Info

---

* Volume 4 G NTFS Partition 627 MB Healthy Hidden

DISKPART> remove Letter=G

DiskPart successfully removed the drive letter or mount point.

DISKPART> GPT ATTRIBUTES=0x8000000000000001

DiskPart successfully assigned the attributes to the selected GPT partition.

DISKPART> detail part

Partition 4

Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

Hidden : Yes

Required: Yes

Attrib : 0X8000000000000001

Offset in Bytes: 999546683392

Volume ### Ltr Label Fs Type Size Status Info

---

* Volume 4 NTFS Partition 627 MB Healthy Hidden

DISKPART> exit

and the view in file explorer now looks like this and note that there is no longer a drive G showing. I will now rename L: to G: so that my backups work again.

Once again, thank you very much for your help so far. Nice to know that there is knowledgeable community help available, and that there are those like yourself willing to help. so grateful.

Cheers!

Garry