In this video I will talk about the error message that says "Failed to update reagent.xml" while executing MBR2GPT command to convert windows 10 from Legacy BIOS to UEFI.
If anyone is wondering about the commands he's talking about at 5:21, they are "reagentc /disable" and "reagentc /enable" for disabling and re-enabling Windows Recovery Environment (WinRE) respectively.
This is perfect for me. I've struggled with trying to get my Win10 computer ready for Win11 and I finally found that changing from MBR to GPT was the problem. So when I made the change I had the exact error issue showed at the end of this video. Thanks
I thought I had to perform some extra steps if I get that error and was worrying about it. Thanks for clearing the doubt. It was enabled as soon as i rebooted.
Whilst updating extg 1TB SATA 2.5" SSD to larger NVMe M.2 my disk clone s/w was warning me that my MBR setting would be replicated on the new drive and there was a 2TB limitation. I needed to change extg drive to GPT before cloning (don't know why I didn't before, GPT is much to be preferred for stability). I was getting this error and was concerned. Your video was a much needed very clear and easy to follow instruction. I am very grateful.
After watching 5 of your videos and each one getting me closer to my solution I finally got it all to work. Thanks for all of you hard work and willingness to help others. Truly appreciative
Just perfect. While converting the disk this same error appeared and I thought something serious had happened, but everything worked correctly. Thanks!
Thank you so much for this video! I spent so long searching Google for instructions and CZcams! Finally found your video which actually live shows the process of doing It In CMD step by step! You've saved me so much grief. I was doing exactly what you showed in your video before I found your video.. But I was doing the commands without a space before the /"command" 😂😂😂 You're my hero dude! Thank you so much for this video! I've liked and subscribed 👍 keep up the good the amazing work!
It doesn't work for me, my local disk is disk 4, also if I try it with programs it tells me: invalid configure file or the system partition and boot are on different disks, I don't understand anything.
For me the mbr2gpt conversion was successful but its not booting, it says "reboot and select proper boot device ... a key_" Changed boot mode to UEFI. Please help.
Because CZcams disabled dislikes it is hard to know if the video is good or not, so I will leave this comment here to inform people that this video is indeed good and helpful!
It was super super hard for me to figure out what was going on and why I couldn't boot up in uefi mode well i foundout that my main drive was mbr not gpt and thought I wonder if that is the problem. Now I can install windows 11
Alright this actually works, but for people who cant even log in to windows in the first place can actually do this from a bootable windows installer, by clicking on Repaire, Troubleshoot then Command Prompt.
after converting from mbr to gpt in disk management the system reserved partition is still there along with the UEFI (100mb). should i just leave the system reserved there??
Please help me; I am getting operating system not found error. When I restarted my system and convert into uefi. Note: I have got same error and mbr to gpt conversation was successful.
Hey man. I followed someone elses guide to convert to uefi and didnt read the failed to part and restarted anyways. Now im stuck at reboot and select proper boot device. What should i do to fix it now?
Could the message "Failed to update reagent.xml" be an indicator for future problems with REAGENTC ? I have taken my computer through a large set of drive and partition changes recently. It is a home-build that had an older motherboard and CPU, with all drives as MBR. I installed a new motherboard, CPU, and 2 NVME "drives". The goal is Windows 11 compatibility. After watching one of your videos, I used MBR2GPT on my Windows 10 disk soon after I got all the hardware reassembled. I moved and copied partitions to migrate from a multibooting MBR/Legacy environment to GPT/UEFI, and moved the boot and OS environment to one of NVME SSDs. Along the way I "broke" my Recovery Environment partition, probably with REAGENTC /enabled. I didn't know about REAGENTC.EXE or the WinRE.wim file. Possibly related: I had to create a new BCD to get all partitions working smoothly on one drive and drop an old multiboot. I used simple BCDEDIT commands from Internet research to direct the EFI System partition to the correct Windows Boot Manager and to (C:) Windows, so if something is needed there for the RE partition, I might have missed it. Regarding the "break", I found that I had a Recovery partition according to DISKPART, but Disk Management displayed it without the (Recovery Environment) designation, and Create a System Image no longer included it. I have recreated the Recovery Environment partition properly, as the next (DISKPART show its Type as Recovery, and Disk Management shows the designation (Healthy, Recovery Environment). When I couldn't find WinRE.wim anywhere, I obtained a copy from my Microsoft Surface Pro -which is also Windows 10 Pro. I copied that WinRE.wim file into the C:\WindowSystem32\Recovery folder. Problem is that the REAGENTC /ENABLE comma still reports the error "The Windows RE image was not found. Unlike your demo system, mine has files in addition to ReAgent.xml in the folder: $PBR_Diskpart.txt, $PBR_ResetConfig.xml, and ReAgent_Merged.xml1.
@@itarmy2778Thank you for responding. I will abandom the WinRE.wim file that I copied from the Surface Pro; it is plausible that Microsoft did their own customization. The Windows 10 on the target system is Microsoft's retail version, not an OEM version. I have no idea why the additional files are in the folder at this point. I have access to another system on which I installed retail Windows 10 Pro to bare metal several years ago, so I think the WinRE.wim on that system should be identical to the one I lost. I wish I understood what role Reagent.xml plays, because I still suspect it. I read somewhere that one solution to the error message to the "Wiindows RE Image was not found." when the (correct) WinRE.wim is to "delete" reagent.xml (actually renaming it to something notable as a rollback option). Reagentc /enable would alledgedly not find it and create a new, suitable one. Your reccomendation to do a reinstallation of Windows may be wise, but if I were ready to do that, I wouldn't have used MBR2GPT in the first place.
So for me I finally got it not to fail but I did get the reagent error now when I went to bios to change from csm to uefi it still won’t boot into windows even tho I set my boot configuration..
need your help i found an errot on validating that is too many partion found error, but i have only two main partion and another two is recovery and system received how to convert gpt..please help me brother...
If anyone is wondering about the commands he's talking about at 5:21, they are "reagentc /disable" and "reagentc /enable" for disabling and re-enabling Windows Recovery Environment (WinRE) respectively.
Ty for this because ya I did not catch it.
Wow. You're the best 🙏 MS' own support here is useless, as always. So many thanks for this!
You are welcome
This is perfect for me. I've struggled with trying to get my Win10 computer ready for Win11 and I finally found that changing from MBR to GPT was the problem. So when I made the change I had the exact error issue showed at the end of this video. Thanks
Glad it helped!
You, sir, are friggin brilliant. Your tutorial was straight forward and simple. THANK YOU!
I thought I had to perform some extra steps if I get that error and was worrying about it. Thanks for clearing the doubt. It was enabled as soon as i rebooted.
I love that I am following you along this string of all the errors I am coming across. THANK you for making these.
You are so welcome!
Whilst updating extg 1TB SATA 2.5" SSD to larger NVMe M.2 my disk clone s/w was warning me that my MBR setting would be replicated on the new drive and there was a 2TB limitation. I needed to change extg drive to GPT before cloning (don't know why I didn't before, GPT is much to be preferred for stability). I was getting this error and was concerned. Your video was a much needed very clear and easy to follow instruction. I am very grateful.
Excellent. Helped solve the mbr2gpt conversion reagent.xml issue I had perfectly. Thank you.
You're welcome!
After watching 5 of your videos and each one getting me closer to my solution I finally got it all to work. Thanks for all of you hard work and willingness to help others. Truly appreciative
Glad to help
Excellent. Thank you for this no-nonsense, well-crafted video!
You're welcome!
thank you so much for this saved me from having a heart attack! just subbed thank you!!!!!!!!
Same here mate😅
Legendary man, thank you for a straight forward, on point tutorial :)
Thanks Nathan!
Every Indain guy is the best guy to make tutorials, thnak you so much bro, it helped
Thank you my friend, your video was so much easier to follow to get my PC up and running than other people's instructions.
Thank you so much, this tutorial saved my PC to be able to update to Windows 11!
Glad it helped!
This was soooo helpful thank you! I had that exact error when trying to go from MBR to GPT.
Glad it helped!
Thank you. This was very helpful and now I don't have to worry.
Glad it helped!
Just perfect. While converting the disk this same error appeared and I thought something serious had happened, but everything worked correctly. Thanks!
Thank you so much for this video! I spent so long searching Google for instructions and CZcams! Finally found your video which actually live shows the process of doing It In CMD step by step!
You've saved me so much grief.
I was doing exactly what you showed in your video before I found your video.. But I was doing the commands without a space before the /"command" 😂😂😂
You're my hero dude!
Thank you so much for this video!
I've liked and subscribed 👍 keep up the good the amazing work!
Glad I could help!
Many thanks for your help. I thought I'd broken Windows when I saw the "Failed to update .." message. I'm now at peace!!
You are welcome!
Well explained. Keep up the good work👍🏼
Glad you liked it!
Dude, this saved me! THanks for sharing!
Bro thank for the clean and short tutorial, very appreciate.
Thanks! I got this exact error and this vid gave me the peace of mind to continue.
You're welcome! Cheers!
It doesn't work for me, my local disk is disk 4, also if I try it with programs it tells me: invalid configure file or the system partition and boot are on different disks, I don't understand anything.
Absolutely Amazing watched many other videos!! Worked perfectly now I can use SAM!!
Glad it helped!
man you are a genius and a life saver, thank you SO much
Than you so much. I spent lot of hour to understand that I need to convert to gpt and you solved my problem when converting
I have a question I have 2 disk and I have converted only one. Does i need to convert booth? How can I do it?
Thanks a lot, bro. For non-native speakers, just slow down speed a bit, and you'll see how clear it is.
You're welcome!
Command Prompt is now called "Terminal" in Windows 11 just in case anyone was wondering.
Dear IT Army! Thanks a lot for this clarification!!!
It worked, thank u!
Glad it helped
Thanks for the clear explanation, I wanted to be sure I got it done right
Glad I could help
Thanks for the great video. This provided a very simple solution for this error.
Thank you so much for taking the time to help others - including me - with this issue. I am grateful.
Happy to help!
Gold!. Exactly what I was looking for. Good explanation. and it worked for me exaclty like in the video shown.
Glad it helped!
YOU SAVED MY LIFE, THE BEST!
Thank you. Very thoroughly explained.
Glad it was helpful!
Very helpful, thank you.
Thank you so much buddy ... It helped me to upgrade my PC..... Saviour🤩 ....
Subscribed 🤘
That was really helpful. Thanks a million 👍
Glad it was helpful and thanks for subscribing
This was truly helpful. Thank you very much.
Glad it was helpful!
Great info but please put the commands and steps in your description text for people to follow easily. Thanks for posting this content.
Sure
For me the mbr2gpt conversion was successful but its not booting, it says "reboot and select proper boot device ... a key_"
Changed boot mode to UEFI.
Please help.
Thank you for the video, was changing setting to get Win11 to install and this error came up for me.
Welcome!!!
Thank you very much for the video, exactly the issue I had. Problem solved :)
You're welcome!
Thanks. I got this same error at the convertion to UEFI, but had no need to disable and enable reagentc, since it was enabled after the restart.
Enjoy!
Hey, do you have any idea on how to do it on a gigabyte motherboard z390? i can't seem to change the boot mode on mine?
thanks dude - very helpful - put my mind at rest!
Glad I could help!
This was excellent. Very thorough.
Much appreciated!
Because CZcams disabled dislikes it is hard to know if the video is good or not, so I will leave this comment here to inform people that this video is indeed good and helpful!
Thanks GodShake for taking the time to comment. Really appreciate it!
Thank you! That put my mind at ease.
Glad I could help!
Dude you are a master!
just....the best ! thx man
It was super super hard for me to figure out what was going on and why I couldn't boot up in uefi mode well i foundout that my main drive was mbr not gpt and thought I wonder if that is the problem. Now I can install windows 11
Alright this actually works, but for people who cant even log in to windows in the first place can actually do this from a bootable windows installer, by clicking on Repaire, Troubleshoot then Command Prompt.
Thank you for this amazing tutorial!
You're very welcome!
thanks for the video. very clear instructions. I thought i might break my windows.
Glad it helped
to the point! Thanks, very helpfull for win11 upgrades that require secure boot, CSM is gone for good
Glad it helped!
Thank you.
Best regards from Germany
Thank you too!
Thanks for the video, it fixed a totally different problem for me, but the video lead me to it.
Glad it helped
Wonderful. Thank you!
Thank you. It was really helpful.
Dear I have problem with hp recovery partition. there is all files in recovery partition but didnot working on startup pressing the f11 key.
after converting from mbr to gpt in disk management the system reserved partition is still there along with the UEFI (100mb). should i just leave the system reserved there??
Thank you! This helped a lot!
Please help me; I am getting operating system not found error. When I restarted my system and convert into uefi.
Note: I have got same error and mbr to gpt conversation was successful.
Thank you, sir! This worked for me!
You're welcome!
Hey man. I followed someone elses guide to convert to uefi and didnt read the failed to part and restarted anyways. Now im stuck at reboot and select proper boot device. What should i do to fix it now?
I cant access bios with f1-f12 or esc or ctrl alt delete
Thank you very much for your videos! 🙏🙏
it refuses to let me restart reagent
thank you very much for saving my day! (probably not just one :) )
Disk layout validation failed for disk 0 what is theproblem
Thank you for this brother ❤
2 lk... Thanks for sharing.. Sir 👍
So nice of you
Gracias por el video!!!! me salvo con una solución práctica
Could the message "Failed to update reagent.xml" be an indicator for future problems with REAGENTC ? I have taken my computer through a large set of drive and partition changes recently. It is a home-build that had an older motherboard and CPU, with all drives as MBR. I installed a new motherboard, CPU, and 2 NVME "drives". The goal is Windows 11 compatibility. After watching one of your videos, I used MBR2GPT on my Windows 10 disk soon after I got all the hardware reassembled. I moved and copied partitions to migrate from a multibooting MBR/Legacy environment to GPT/UEFI, and moved the boot and OS environment to one of NVME SSDs. Along the way I "broke" my Recovery Environment partition, probably with REAGENTC /enabled. I didn't know about REAGENTC.EXE or the WinRE.wim file. Possibly related: I had to create a new BCD to get all partitions working smoothly on one drive and drop an old multiboot. I used simple BCDEDIT commands from Internet research to direct the EFI System partition to the correct Windows Boot Manager and to (C:) Windows, so if something is needed there for the RE partition, I might have missed it. Regarding the "break", I found that I had a Recovery partition according to DISKPART, but Disk Management displayed it without the (Recovery Environment) designation, and Create a System Image no longer included it. I have recreated the Recovery Environment partition properly, as the next (DISKPART show its Type as Recovery, and Disk Management shows the designation (Healthy, Recovery Environment). When I couldn't find WinRE.wim anywhere, I obtained a copy from my Microsoft Surface Pro -which is also Windows 10 Pro. I copied that WinRE.wim file into the C:\WindowSystem32\Recovery folder. Problem is that the REAGENTC /ENABLE comma still reports the error "The Windows RE image was not found. Unlike your demo system, mine has files in addition to ReAgent.xml in the folder: $PBR_Diskpart.txt, $PBR_ResetConfig.xml, and ReAgent_Merged.xml1.
There files provide the manufacturer specific recovery options in the recovery environment. Better perform a fresh install next time.
@@itarmy2778Thank you for responding. I will abandom the WinRE.wim file that I copied from the Surface Pro; it is plausible that Microsoft did their own customization. The Windows 10 on the target system is Microsoft's retail version, not an OEM version. I have no idea why the additional files are in the folder at this point. I have access to another system on which I installed retail Windows 10 Pro to bare metal several years ago, so I think the WinRE.wim on that system should be identical to the one I lost. I wish I understood what role Reagent.xml plays, because I still suspect it. I read somewhere that one solution to the error message to the "Wiindows RE Image was not found." when the (correct) WinRE.wim is to "delete" reagent.xml (actually renaming it to something notable as a rollback option). Reagentc /enable would alledgedly not find it and create a new, suitable one. Your reccomendation to do a reinstallation of Windows may be wise, but if I were ready to do that, I wouldn't have used MBR2GPT in the first place.
You're welcome. Yes, get the winre.wim from retail Windows machine or Windows 10 iso.
Thank you, simplest tutorial
Welcome!!!
Really helpful. Thanks a ton
Glad it helped!
Nice but now i have 2 recovery partition on my HD?
Unable to update Boot Configuration Data. facing this problem
thank you so much for this video
What do I do with the legacy partition?
Impressive explanation.. 👍
Thanks 🙂
switch to GPT worked but reagentc.exe still says disabled
Many many thanks!!
So for me I finally got it not to fail but I did get the reagent error now when I went to bios to change from csm to uefi it still won’t boot into windows even tho I set my boot configuration..
my computer is not supported uffi who to convert mbr to gpt partion my computer model is hp 6005 pro please help me
Works as a charm! Thanks a ton mate
No problem 👍
ur the best ty soooooo much
Thank you very much, this really help
Glad it helped!
Life saver.
Thanks for ensuring that's fine!
No worries!
Thank you for saving mee!!!
You're welcome!
Thank you for explaining in english dude 👍
Happy to help
need your help i found an errot on validating that is too many partion found error, but i have only two main partion and another two is recovery and system received how to convert gpt..please help me brother...
Please check my videos on deleting old recovery partition
thanks, no worry anymore , good job
excellent video, thank you!
Glad it was helpful!
thanks, but i think you should mention that it doesn't matter in the description.
Ohh Got it Now thanks Man😊😊
Welcome 😊