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

That basically looks good. Let's make some adjustments...

(1) Delete one more useless entry, & fix the Windows Memory Tester...

Type "CMD" into Search, & click "Run as Administrator". Then, copy/paste the following into it one line at a time...

BCDEdit /Delete {201ca33d-3744-11eb-ab08-a9da93046d68}

BCDEdit /Set {becbfbbc-74c1-11e3-a193-d3e592cc6be4} Description "Windows Recovery"

BCDEdit /Enum {memdiag} <<<Show old memory tester entry

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

BCDEdit /Set {memdiag} Path \EFI\Microsoft\Boot\memtest.efi

BCDEdit /Enum {memdiag} <<<Show new one

Does the new one have the new Device & Path values? Then all is well.

(2) We did remove H: from the Recovery partition before. We then put R: on it to do a ReagentC, but we removed the R: afterwards. Now, H: has come back -- at least it isn't G: -- remember that? But H: has gotten tangled into the BCD. Well, let's try...

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

DiskPart <<<Enter DiskPart

Select Vol=H <<<Select the Recovery volume

Detail Part <<<Show partition details including the letter & Attrib

Remove Letter=H <<<Remove its letter

Detail Part <<<Show the letter is gone

Exit <<<Exit DiskPart

I'm expecting your second "Detail Part" to look like this...

Partition 4

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

Hidden : Yes

Required: Yes

Attrib : 0X8000000000000001

Use Ctrl-A & Ctrl-C to copy, then past it all here. Then reboot & check in File Explorer to see H: is gone. Finally, let me see...

BCDEdit /Enum {201ca33c-3744-11eb-ab08-a9da93046d68}

BCDEdit /Enum {becbfbbc-74c1-11e3-a193-d3e592cc6be4}

If they still mention the letter H, we can get it back it out.

Well, that sounds great. It boots properly to both Windows & to the recovery environment now. That's right, "Continue" is what gets back to Windows from the recovery environment. You might have traversed the various options first. For instance, "Troubleshoot > Advanced Options > Command Prompt". Then, exit the Command Prompt with its "X" or by typing "Exit", & click "Continue" to get back to Windows. But I suppose all is well. Here is the cleanup...

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

BCDEdit /Export C:\BU\BCD_Backup <<<Overwrite old with new BCD backup

BCDEdit /Delete {c4337ee6-11b0-11ec-ab4f-806e6f6e6963}

BCDEdit /Delete {c4337ee8-11b0-11ec-ab4f-806e6f6e6963}

BCDEdit /Delete {c4337ee7-11b0-11ec-ab4f-806e6f6e6963}

BCDEdit /Delete {c4337ee3-11b0-11ec-ab4f-806e6f6e6963}

That makes a fresh BCD_Backup, then deletes unused & unwanted entries from the BCD. Do a reboot to Windows for certainty all is well. Then...

BCDEdit /Export C:\BU\BCD_Backup <<<One final save of the BCD

BCDEdit /Enum All <<<Show it for a final look

That should do it. Looks like all went well. Good going on your part & mine.

(1) Have you rebooted to Windows since 10/29 when we got {bootmgr} into your BCD? That's an important one. If it won't go to Windows, do the /Import to get back that old rotten BCD. The rest of this is to get Shift+Restart to work. That is a boot to the recovery environment (at the "Choose an Option" screen).

(2) For the recovery environment, Just do the second one...

BCDEdit /Set {201ca33c-3744-11eb-ab08-a9da93046d68} osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{becbfbbc-74c1-11e3-a193-d3e592cc6be4}

All of the other BCDEdit commands went well. Then, try this again...

ReagentC /Enable

ReagentC /Info <<<Does this one say it's enabled?

If it says it's enabled, try a Shift+Restart. Did it work?

(3) If it won't enable or work, then try this...

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

DiskPart <<<Enter DiskPart

Select Disk 0 <<<Focus on Disk 0

List Part <<<List the partitions

Select Part 4 <<<Focus on Recovery partition

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

Exit <<<Exit DiskPart

ReagentC /SetREImage /Path R:\Recovery\WindowsRE /Target C:\Windows

ReagentC /Enable

ReagentC /Info <<<Does it say it's enabled now?

DiskPart <<<Enter DiskPart

Select Vol=R <<<Focus on Recovery partition

Remove Letter=R <<<Remove the letter

Exit <<<Exit DiskPart

If it says it's enabled, try the Shift+Restart for the recovery environment. Did it get there, & did it have all its buttons, like Troubleshoot & Advanced Options? If so, we are done except maybe for a little cleanup.

Yippee, indeed! Well, do a reboot to test whether it works (if you haven't already). If it boots, do the following while in Windows. These are eight BCDEdit commands of one line each & three ReagentC. Copy/paste them into the Command Prompt...

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

BCDEdit /Enum {201ca33c-3744-11eb-ab08-a9da93046d68} <<<Show old Windows RE

BCDEdit /Set {201ca33c-3744-11eb-ab08-a9da93046d68} Device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{becbfbbc-74c1-11e3-a193-d3e592cc6be4}

BCDEdit /Set {201ca33c-3744-11eb-ab08-a9da93046d68} osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{becbfbbc-74c1-11e3-a193-d3e592cc6be4}

BCDEdit /Enum {201ca33c-3744-11eb-ab08-a9da93046d68} <<<Show new Windows RE

BCDEdit /Enum {becbfbbc-74c1-11e3-a193-d3e592cc6be4} <<<Show old Ramdisk Options

BCDEdit /Set {becbfbbc-74c1-11e3-a193-d3e592cc6be4} ramdisksdidevice partition=\Device\HarddiskVolume4

BCDEdit /Set {becbfbbc-74c1-11e3-a193-d3e592cc6be4} ramdisksdipath \Recovery\WindowsRE\boot.sdi

BCDEdit /Enum {becbfbbc-74c1-11e3-a193-d3e592cc6be4} <<<Show new Ramdisk Options

ReagentC /Info <<<Is it enabled?

ReagentC /Enable <<<Enable the Recovery Environment (if not already)

ReagentC /Info <<<Is it enabled now? ****

Let me see the output of that. If ReagentC won't enable, just post a new "BCDEdit /Enum All".

But -- if it is enabled -- click a Power icon, then hold Shift as you click Restart. The computer should reboot to the internal recovery environment (the Recovery partition). Does it seem to have all of its tools? Click "Continue" to return to Windows, & post a final "BCDEdit /Enum All". That should be the end of it.

Hi BG. I'm Greg, 10 years awarded Windows MVP, specializing in Installation, Performance, Troubleshooting and Activation, here to help you.

Please post a screenshot of Disk Management, which I read like a doctor reads X-rays. Follow the steps here so I can see everything needed to advise you: http://answers.microsoft.com/en-us/windows/foru...

The contents of G which I can see show that it's the Recovey partition containing the bootable WinRE tools which are used when Windows won't start, shown here:

https://www.tenforums.com/tutorials/2294-advanc...

A Recovery partition should not have a Drive letter so you can remove that.

But before you try to move the OneDrive folder partition back I would unlink OneDrive because it could mess up it's linkages which have apparently somehow changed from where you originally assigned them.

So the way to do this is go into OneDrive Settings > Backup tab to disable Backup Folder protection so the User folders syncing with OneDrive are set back to default location for the time being.

Next go into OneDrive Settings > Accounts tab > to Unlink OneDrive as shown here: https://www.tenforums.com/tutorials/36246-link-...

Now go into Disk Management, remove the drive letter from G, move it to the partition where you want the OneDrive folder.

Now go into Start Menu, open Microsoft OneDrive, go through the steps here to set it up: https://www.windowscentral.com/how-get-started-....

At the step for where you want to move the OneDrive folder, choose Drive G and the existing OneDrive folder.

If you still want Folder Protection Backup, enable it again on OneDrive Settings > Backup tab.

Make sure Files On Demand is not checked on the Settings tab or the files will only stay in the cloud, not on the hard drive where they'll be replaced by links.

I hope this helps. Feel free to ask back any questions. Please report back results for all steps given so I know what else to suggest if necessary.

______________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.