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

Anonymous

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

47 answers

Anonymous

2021-11-02T01:24:13+00:00

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.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-11-02T17:35:11+00:00

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! ??
Was this answer helpful?

0 comments No comments
Anonymous

2021-11-02T18:46:56+00:00

Yep -- woohoo! It's a job well done on both our parts. And good of Windows to self-adjust the BCD after the removal of H: & a reboot. Victory is ours at last. I studied the BCDEdit help screens & practiced on my own BCD to be able to do all that. Also, there are sites & threads that discuss it. I guess do one really final: "BCDEdit /Export C:\BU\BCD_Backup".

And that's the glorious end of it. Good luck.
Was this answer helpful?

0 comments No comments
Anonymous

2021-11-02T19:30:00+00:00

Hi PCR....

Thank you so very much for all your help. I cannot thank you enough for all your time and effort.

This was a big learning experience for me considering I do not still, even know what BCD acronym means, or how to have even thought about this as problem,

You are a great community resource and I hope everyone to whom you have ever helped here appreciates you as much as I do.

Thanks again, and stay safe.

Best Regards,

Garry
Was this answer helpful?

0 comments No comments
Anonymous

2021-11-02T19:47:51+00:00

You are welcome. BCD stands for Boot Configuration Data. Glad to have helped. I too am happy to have learned a thing/two in this thread. May there be many happy boots & reboots to you & me. Good luck, & keep us informed.
Was this answer helpful?

0 comments No comments