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

Hi PCR...

Ran commands above and all executed successfully. The following is the results of the first set BCDEdit commands. The last 2 follow behind them.

By the looks of things, all seems OK but can you verify that, and that we are finished with the fixing please.

If all good, thank you so very much for all your time and wisdom.

If you don't mind me asking, how do you know about all this stuff? I don't think even the average Microsoft tech would know about all this. I am impressed for sure.

Cheers!

Garry

---

Microsoft Windows [Version 10.0.19042.1288]

(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>BCDEdit /Delete {201ca33d-3744-11eb-ab08-a9da93046d68}

The operation completed successfully.

C:\WINDOWS\system32>BCDEdit /Set {becbfbbc-74c1-11e3-a193-d3e592cc6be4} Description "Windows Recovery"

The operation completed successfully.

C:\WINDOWS\system32>BCDEdit /Enum {memdiag}

Windows Memory Tester

---

identifier {memdiag}

device unknown

path \boot\memtest.exe

description Windows Memory Diagnostic

locale en-US

inherit {globalsettings}

badmemoryaccess Yes

C:\WINDOWS\system32>BCDEdit /Set {memdiag} Device partition=\Device\HarddiskVolume2

The operation completed successfully.

C:\WINDOWS\system32>BCDEdit /Set {memdiag} Path \EFI\Microsoft\Boot\memtest.efi

The operation completed successfully.

C:\WINDOWS\system32>BCDEdit /Enum {memdiag}

Windows Memory Tester

---

identifier {memdiag}

device partition=\Device\HarddiskVolume2

path \EFI\Microsoft\Boot\memtest.efi

description Windows Memory Diagnostic

locale en-US

inherit {globalsettings}

badmemoryaccess Yes

C:\WINDOWS\system32>DiskPart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.

On computer: GARRY-INTEL1

DISKPART> Select Vol=H

Volume 4 is the selected volume.

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 H NTFS Partition 627 MB Healthy Hidden

DISKPART> Remove Letter=H

DiskPart successfully removed the drive letter or mount point.

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>

The final 2 commands follow here

C:\WINDOWS\system32>BCDEdit /Enum {201ca33c-3744-11eb-ab08-a9da93046d68}

---

Windows Boot Loader

---

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

device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{becbfbbc-74c1-11e3-a193-d3e592cc6be4}

path \windows\system32\winload.efi

description Windows Recovery Environment

locale en-US

inherit {bootloadersettings}

displaymessage Recovery

osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{becbfbbc-74c1-11e3-a193-d3e592cc6be4}

systemroot \windows

nx OptIn

bootmenupolicy Standard

winpe Yes

C:\WINDOWS\system32>BCDEdit /Enum {becbfbbc-74c1-11e3-a193-d3e592cc6be4}

Device options

---

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

description Windows Recovery

ramdisksdidevice partition=\Device\HarddiskVolume4

ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\WINDOWS\system32>

C:\WINDOWS\system32>

WooHoo.. likes like we are done! ??

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.

Hi PCR,,,

OK... followed the instructions above in your last replay.

All good except for the first delete. came back with a not found. All the others worked as well.

Forgot to capture the scree details before I rebooted though.

Rebooted using shift + restart, saw all the options then did just a continue to Windows. Windows started successfully.

here is the results of the last 2 commands:

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

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

Note at the bottom that I now have a new partition H in windows explorer but not in Disk Management. Can that be removed?

I think so but not sure.

Microsoft Windows [Version 10.0.19042.1288]

(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>BCDEdit /Export C:\BU\BCD_Backup

The operation completed successfully.

C:\WINDOWS\system32>BCDEdit /Enum All

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {bootmgr}

timeout 0

Windows Boot Manager

---

identifier {bootmgr}

device partition=\Device\HarddiskVolume2

path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

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

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

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 ramdisk=[H:]\Recovery\WindowsRE\Winre.wim,{becbfbbc-74c1-11e3-a193-d3e592cc6be4}

path \windows\system32\winload.efi

description Windows Recovery Environment

locale en-US

inherit {bootloadersettings}

displaymessage Recovery

osdevice ramdisk=[H:]\Recovery\WindowsRE\Winre.wim,{becbfbbc-74c1-11e3-a193-d3e592cc6be4}

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=H:

ramdisksdipath \Recovery\WindowsRE\boot.sdi

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.

Hi PCR,,,

I had started a reply after doing all above and when I did the Shift restart of course I was planning to answer the question of if it worked and yes it seemed to give me all the advanced options OK, but when I said to continue to windows, it rebooted and lost my original reply.

so to answer your first question:

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).

Yes I rebooted just now before starting the instructions above. Ran the instruction in CMD prompt and looks like all worked OK, although when I invoked the CMD instruction it popped up the window twice, so closed one then exited and restarted it. OK this time only once.

After doing the above did the ReagentC /Info... and =got the following result:

C:\WINDOWS\system32>ReagentC /Info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:

**Windows RE status:         Enabled** 

**Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE** 

**Boot Configuration Data (BCD) identifier: 201ca33c-3744-11eb-ab08-a9da93046d68** 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0 

REAGENTC.EXE: Operation Successful.

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.

Did this and as mentioned it seemed to work. when the options showed up I just said to continue to windows. Was that the right thing or should it have been a different option? I was just going for the view of all the options being there.

If all good so far, what cleanup is there left to do?

Thanks so much for your help here and sticking with me even thru all the mis-steps I made.

Cheers!

Garry