Convert MBR to GPT - MBR2GPT fails with error 0x00000000

Megahertz said:

Open a CMD window as administrator and type:

reagentc /enable
reagentc /info

"The windows RE image was not found".

put a copy of winre.wim and reagent.xml in your \windows\system32\recovery folder

if you havent got them to hand you can use these for x64 22h2.zip

if an .xml is already there, overwrite it with the one in the zip

after you have copied those in you can do

reagentc /enable

Megahertz said:

Open a CMD window as administrator and type:

diskpart
select disk 0
list part (take note of the Samsung Recovery partition number)
select part n (replace n with the partition number identified above)
detail part
exit

SIW2 said:

...
too late to check the samsung_rec partition id now. Had to be done before converting, now we will never know what it was. Of course after converting the disk with a 3rd party tool it now shows as ms basic data partition.

Here's the diskpart detail info from the original disk - for the SAMSUNG_REC partition:

Code:

DISKPART> detail part

Partition 4
Type  : 27
Hidden: No
Active: No
Offset in Bytes: 476779118592

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3         SAMSUNG_REC  NTFS   Partition     32 GB  Healthy    Hidden

So I guess the original Samsung_Rec partition was type 27?

- - - Updated - - -

SIW2 said:

put a copy of winre.wim and reagent.xml in your \windows\system32\recovery folder

if you havent got them to hand you can use these for x64 22h2.zip

if an .xml is already there, overwrite it with the one in the zip

after you have copied those in you can do

reagentc /enable

Thanks for the file. Looking at it now, I see only two files; it has winrec.wim and ReAgent.html; no xml file. The folder on my win10 machine that I'm working on has two files in that folder - ReAgent.xml, and ReAgent_Merged.xml1.

Out of curiosity, how does this 'work'; that is, do the contents of \windows\system32\recovery get moved to another partition by some process? I don't see the winrec.wim file anywhere on any system.

Use a third party partitioning program like MiniTool Partition Wizard Free to shrink you C: drive partition by 500 MB with the free space at the right end of the partition. Then try mbr2gpt again. You might have an unmovable file at the end of your C: drive partition which would cause mbr2gpt to not be able to shrink C: drive to make room for the ESP.

Steerpike58 said:

...

Thanks for the file. Looking at it now, I see only two files; it has winrec.wim and ReAgent.html; no xml file. The folder on my win10 machine that I'm working on has two files in that folder - ReAgent.xml, and ReAgent_Merged.xml1.

Out of curiosity, how does this 'work'; that is, do the contents of \windows\system32\recovery get moved to another partition by some process? I don't see the winrec.wim file anywhere on any system.

My apologies - on the temporary machine I was using to do the download, file extensions were turned off and the xml file was being reported as an 'html document'... so the xml file is there. Of course :). I'm still curious to know how the wim file gets used; what process migrates it to another partition. Thanks!

reagentc moves them and adds the recovery sequence to the bcd store. It will probably create %systemdrive%\recovery\windowsre

Looks like my suggestion is being ignored....