One drive has messed up my partitions in that I had a drive G called WorkArea (G) that has the one drive folders to sync on it, along with all other files and folders on it. Somehow my G drive WorkArea (G) (partition) was reallocated to drive L WorkArea (L), and a separate partition G now called Local Disk (G). has appeared in the original drive G's place. (not talking about drive Mapping here). In windows explorer I see the following screen shot whereas in disk management, G does NOT show up at all and I cannot change WorkArea (L) back to G. Drive L does show up in windows explorer, but is not in the screen shot. . and trying to re-assign WorkArea to G I cannot, as it is unavailable. how do I fix this? I tried to uninstall OneDrive, and reboot but nothing changed. Can someone please help me fix this as my backup plans are set for G as what is in WorkArea L and now backup of G only shows OneDrive files, that were not part of the backup plan to begin with. Thanks for any help you can offer. Much appreciated. Garry G

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

Anonymous

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

0 comments

Anonymous

Hi PCR... I think an oopsie happened again... My bad...

for the following 2 commands of yours...

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}

I think I did the first one twice and not the second one as they looked very much the same. If that is the case, can I just repeat the whole thing again from the Start?

Sorry about that

0 comments

Anonymous

Hi PCR..

Thanks again for all your help. Looks like a premature Yippee. :-(

I entered the commands as instructed above. All worked except the final Reagent C/Enable ...

I simply copied and pasted your commands above.

For your easy reading, I went back after I pasted the entire CMD results, and bolded the command sequence entered. I also highlighted and bolded in red where the RE image was not found. I stopped at this point an did not reboot for fear I would not be able to.

What to do next?

C:\WINDOWS\system32>ReagentC /Enable

REAGENTC.EXE: The Windows RE image was not found.

here is what it says on the ENum:

Windows RE status: Disabled

**Windows RE location:**

I have included the entire CMD results following....

Microsoft Windows [Version 10.0.19042.1288]

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

Windows Boot Loader

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

device partition=\Device\HarddiskVolume4

path \windows\system32\winload.efi

description Windows Recovery Environment

locale en-US

inherit {bootloadersettings}

displaymessage Recovery

osdevice partition=\Device\HarddiskVolume4

systemroot \windows

nx OptIn

bootmenupolicy Standard

winpe Yes

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

The operation completed successfully.

C:\WINDOWS\system32>

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

The operation completed successfully.

C:\WINDOWS\system32>

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 partition=\Device\HarddiskVolume4

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 Ramdisk Options

ramdisksdidevice partition=C:

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

C:\WINDOWS\system32>BCDEdit /Set {becbfbbc-74c1-11e3-a193-d3e592cc6be4} ramdisksdidevice partition=\Device\HarddiskVolume4

The operation completed successfully.

C:\WINDOWS\system32>

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

The operation completed successfully.

C:\WINDOWS\system32>

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

Device options

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

description Ramdisk Options

ramdisksdidevice partition=\Device\HarddiskVolume4

ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\WINDOWS\system32>ReagentC /Info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:

**Windows RE status:         Disabled** 

**Windows RE location:** 

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.

C:\WINDOWS\system32>ReagentC /Enable

REAGENTC.EXE: The Windows RE image was not found.

C:\WINDOWS\system32>ReagentC /Info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:

Windows RE status:         Disabled 

Windows RE location: 

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.

Here is the final BCDEdit /ENum all

C:\WINDOWS\system32>bcdedit /Enum all

Firmware Boot Manager

identifier {fwbootmgr}

displayorder {bootmgr}

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

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

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

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

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

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 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 partition=\Device\HarddiskVolume4

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=\Device\HarddiskVolume4

ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options

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

description Ramdisk Options

ramdisksdidevice partition=\Device\HarddiskVolume4

ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\WINDOWS\system32>

0 comments

Anonymous

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.

0 comments

Anonymous

Hi PCR...

Bummer... my eyes were probably getting fuzzy when I did this, as they are now as well. I reread the command before hitting enter but missed the second fwbootmgr.

OK so I did the instructions above in Windows at an Administrator Command Prompt...

the commands all seemed to have worked, but I managed to exit before snagging the results.. I went back and redid the following:

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

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

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

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

and captured the results this time as follows:

Microsoft Windows [Version 10.0.19042.1288]

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

Windows Boot Manager

identifier {bootmgr} <===============

device partition=\Device\HarddiskVolume2 <=============== YAY? is good now?

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

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

Firmware Boot Manager

identifier {fwbootmgr}

displayorder {bootmgr}

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

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

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

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

timeout 0

C:\WINDOWS\system32>BCDEDit /Set {fwbootmgr} Displayorder {bootmgr} /Addfirst

The operation completed successfully.

C:\WINDOWS\system32>bcdEdit /Enum {fwbootmgr}

Firmware Boot Manager

identifier {fwbootmgr}

displayorder {bootmgr}

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

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

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

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

timeout 0

C:\WINDOWS\system32>

So does tis mean we are now all good? as in Done!!

If so, then thank you so very much for all your help.

If not.... then what's next?

Cheers!

Garry

0 comments

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

47 answers