How to move non-functioning WinRE partition from start of disk to end and re-install it there?

SIW2 said:

is it offering to fix it ?


You could but why ?

Diskgen boot media could be used to delete the previous esp and msr and then create new ones at the begining of the disk.

Then populate the new esp with the boot critical files using bcdboot command

Click to expand...

DG isn't offering a fix, though it will allow me to scan the volume for bad sectors. Should I do that?

If relocating the EFI and MSR were something I could easily do with DG, then I'd do it so future clones are correct (using DG or some other tool, not Samsung Magician) But it sounds like it's above my pay grade.

try Tools >check partition table

SIW2 said:

try Tools >check partition table

Click to expand...

I get "Warn: The number of sectors in DBR less than actual value" with instructions I don't understand about clicking correct and then manually recreating or reformatting.

Some EF members very frequently use Macrium and may be able to guide you through the software steps.

Macrium can be used for clones as well as backup images.

See if you can make a Macrium backup image instead of a clone.

Then clean install Windows 11 and restore only the C: partition.

This should have the default UEFI / GPT partition: System, Reserved, Data, Recovery

If the backup restoration is successful with or without a startup repair then Macrium can be used for clones.

zbook said:

Some EF members very frequently use Macrium and may be able to guide you through the software steps.

Macrium can be used for clones as well as backup images.

See if you can make a Macrium backup image instead of a clone.

Click to expand...

Thanks, but when I used Macrium to make a backup and restore, although the partitions were in the correct places and Macrium reported no errors on verifying the backup, I had other issues, which is why I resorted to the clone. I'm just interested in fixing this EFI partition issue now; everything else seems to be working, and I'd rather avoid another eight hours of backing up to a hard drive and then restoring, if possible.

I would just click correct. Done it a few times without issue.

Make the boot media first, you should always have it on a usb stick. Do it now and you wont forget.

Please post images or share links displaying commands with results:

SIW2 said:

I would just click correct. Done it a few times without issue.

Make the boot media first, you should always have it on a usb stick. Do it now and you wont forget.

Click to expand...

Okay, I'll try just clicking Correct. I watched few videos on re-creating the EFI partition, and I'd rather not go that route if I don't have to. Thanks again for all your help.

And, I have created the DiskGenius boot media (to go with my growing collection of boot media). Thanks again for all your help. I was a tech writer, long ago, and I'm inclined to write up this move-the-WinRE stuff you've walked me through. I imagine every Samsung Magician user who clones a boot drive will need it, whether they know it or not. If I do, I'll post it in this thread, and if you get a chance, it would be helpful to get feedback on it. Perhaps it could go in the Tutorials section somewhere.

zbook said:

Please post images or share links displaying commands with results:

Code:

bcdedit
bcdedit | find "osdevice"
reagentc /info
shrink querymax

Code:

diskpart
lis dis
lis vol
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par

Click to expand...

Okay, if "Correct" in DiskGenius doesn't fix it, I'll do that. It's after 2am here, so tomorrow or the next day. So far, the computer seems to be booting correctly despite this error.

If it boots please post a new disk management.

And if there are any issues post disk par info results:

zbook said:

If it boots please post a new disk management.

And if there are any issues post disk par info results:

https://www.tenforums.com/attachments/bsod-crashes-debugging/355861d1640707960-batch-files-use-bsod-debugging-diskparinfo.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Click to expand...

It hasn't had any issues with booting, just the repositioning of the WinRE partition, which I've corrected, and the EFI partition marked as "Damaged" by Disk Genius. I'm not seeing any errors in normal use or significant errors in the logs, so far.

This was a google search result:

zbook said:

This was a google search result:

Damaged Partition Recovery: How to Recover Files from Damaged Drives?

In this page you can find an effective way to do damaged partition recovery in Windows 10/8/7 and a solution to repair damaged partition without data loss.

www.diskgenius.com

Click to expand...

Thanks. This is a specific issue with the DBR that Disk Genius may be able to fix. If not, then I'll look into re-creating the EFI. It doesn't seem to be covered on that page.

SIW2 said:

I would just click correct. Done it a few times without issue.

Make the boot media first, you should always have it on a usb stick. Do it now and you wont forget.

Click to expand...

I clicked "Correct" in the Check Partition Errors tool and it reported that it fixed the partition, but the EFI partition is still flagged as Damaged. I see that it contains files from HP and Microsoft, so a simple re-creation won't work. When I look at my Macrium backup, it looks like I can delete the existing EFI and MSR partitions and restore the Macrium EFI and MSR partitions. I could also then reclaim the bit of space left at the front of the drive from the misplaced WinRE partition.

Is this worth doing? Is there any risk to it? Disk Genius doesn't say how the EFI partition is damaged, just that it is, and currently the computer seems to boot normally.

EDIT: I poked around in Macrium and among other things explored the backup files EFI partition, which involved mounting it. When I exited Macrium, it didn't unmount it, which I discovered when I started Disk Genius again. Disk Genius found it and identified it, too, as a System partition that was damaged. So maybe the original SSDs EFI was also damaged in some unclear way?

@dbookbinder
Another member in this forum had the sane problem.
To fix the problem, you'd have to format this partition and rebuild the BCD.
Take a look at the link below where I suggested the fix.

Topgundcp said:

@dbookbinder
Another member in this forum had the sane problem.
To fix the problem, you'd have to format this partition and rebuild the BCD.
Take a look at the link below where I suggested the fix.

Is damaged ESP important?

Interesting. I think that Windows typically uses 100 MB unless it is on an Advanced Format 4k Native HDD. On the system where it is 256 MB, is that a factory installation? If so, maybe that's just how the manufacturer created it. In the end, it really doesn't matter. Yes, The 256 MB is how the...

www.elevenforum.com

Click to expand...

Thanks. I saw your post last night. I notice that the EFI partition contains some HP information as well as the Microsoft information. If I follow your instructions, I will just end up with a vanilla Microsoft EFI partition, is that correct? Does it matter? It appears to be mostly BIOS update related information. Possibly related to automatic recovery from a corrupted BIOS, but I don't actually know.

If I follow your instructions, I will just end up with a vanilla Microsoft EFI partition, is that correct?

Click to expand...

Yes.

To make sure, You can open the command prompt and type: bcdedit /enum all then save it to a text file. Go thru the list to see if it contain extra info that need to be saved. If you are unsure, post the result then I'll take a look.

Topgundcp said:

Yes.

To make sure, You can open the command prompt and type: bcdedit /enum all then save it to a text file. Go thru the list to see if it contain extra info that need to be saved. If you are unsure, post the result then I'll take a look.

Click to expand...

Thanks. The attached file has the output of the bcdedit command above. The EFI folder itself contains an HP folder with about 50Mb of data. I'd want to preserve that in a new EFI partition.

dbookbinder said:

Thanks. I saw your post last night. I notice that the EFI partition contains some HP information as well as the Microsoft information. If I follow your instructions, I will just end up with a vanilla Microsoft EFI partition, is that correct? Does it matter? It appears to be mostly BIOS update related information. Possibly related to automatic recovery from a corrupted BIOS, but I don't actually know.

Click to expand...

Because of Microsoft changed the update policy for WinRE , many users (of Win 10) have problems such as errors at Windows update.
The provided solution for these users is to delete and rebuild a larger WinRE. But are at Win 11. As you can see the "solution" is
and for Windows 11. In real at any time a user can play with that , by : put the partition WinRE at the end or start of the System Disk (if i remember OK , MS recommends at the end of) , change name or size WinRE partition.

So i tried for any case to make it 1GB , last partition , and with my own naming.
I made it. But before ............................ check what problems were created. You will found many answers.
Τhanks to SIW2 I succeeded :




-About Disk Genious. In order to find solutions i downloaded and tried.
I realized 2 things. That it has a lot of potential and that it is unreliable. I would tell you not to use it.

-In the other hand i use Mini tool partition wizard. It hasnt the abilities of DG , but is reliable.
-I can't prove it but I believe the error of DG gives you is false.

Whats important and you must check , to understand also if there is problem :
1) You can boot at WinRE via Shift+restart and ensure that major functions like Restore Points and Restore Image work OK.
2) You can boot at WinRE via USB stick and ensure that major functions like Restore Points and Restore Image work OK.
3) You can boot at WinRE by pressing F11 at boot and ensure that major functions like Restore Points and Restore Image work OK.
4) You can boot at HP's UEFI by press the defined key , at my Pavilion thats F2. (i think you have an HP , sorry if i m wrong).

If all these are OK , please post a screenshot of Disk Management and/or Minitool partition wizard ,
to see if there is something looks wrong.

In case that after all these , cant boot at HP's UEFI diagnostics its easy to recreate it.
Just download and run its setup file.

Knoledge about WinRE you could find here.

Looking at the BCD text file, I don't see anything related to the HP entry in esp partition, hence it is invalid, the same as in the other thread where the OP has invalid entries. This cause Diskgenius to complain.
As a precaution, you can copy and save this folder to desktop then proceed with the fix.

OR: better yet, just move this folder out of esp partition, reboot and check again to see if the problem goes away.

@Bug locker
I disagree with you about Diskgenius. I've been using Diskgenius since the beginning when it was called "PartitionGuru" then later renamed to be "DiskGenius". IMO, DiskGenius is way better than Partition Manger, There's a lot more features that Diskgenius offer and Minitool Partition doesn't. With Minitool you can only explore the System partitions (esp, Recovery) but you cannot manipulate as in Diskgenius. If you are using Linux, you can read/copy/transfer files between the 2 filesystems.
With the problem that he is having right now, you cannot reformat the esp partition usng Minitool without having to boot into WinPE.
I am making the statement above because I also own a copy of Minitool Partition Technical Edition.