Windows 10: 2 recovery partitions

after performing an upgrade, I have 2 recovery partitions, the same size, one at the beginning of the disk and the new one at the end of the disk
I only need one, right?
Two ideas came to mind:
1 boot into linux, copy the contents of the second partition to the first partition, and then delete the second partition.
2 use EaseUs partition master to delete the first partition and then move the second partition to its place.

Feedback, please.

:)

 

2 Recovery Partitions On Windows 10

Thanks for the Quick Reply,

As I said earlier, converting my disk to dynamic will result in an error message and somewhat corruption of my BOOTMGR file, whether inderectly from a prompt or directly from the mmc console.

 

2 Recovery Partitions On Windows 10

Hi Kian,

Sorry for the inconvenience.

You have to right click on the device and select the option convert to dynamic disk
in disk management and then check if it helps.

A recovery partition is a separate partition on a computer hard drive that contains all the system files, drivers, applications, and default settings that a computer shipped with from the factory. It can sometimes be hidden from view, only revealing itself
to very low-level processes, such as disk formatting utilities, operating system installations, DOS, and boot processes. They are designed to be write-protected, ensuring that the data on it remains in pristine condition and no tampering from outside sources
can occur. Upon activation, they boot into a separate, bare-bones operating system designed specifically for operating system repair or recovery and sometimes data backup.

System partition and boot partition are computing terms for disk partitions of a hard disk drive that must exist and be properly configured for a system to operate correctly. There are two
different definitions for these terms: One that developed from the simple firmware on PC's allowing Operating Systems to manage their own Boot Loader's location and one, common in servers, for Firmware that manages the location and selection of Boot Loader.
The difference comes from the differing view that the partition is intended to hold a single Operating Systems "boot" code and that the "system" firmware controls the partition with the boot code.

No, I would recommend you to not remove either of the partitions as it may result in computer malfunction.

Do get back to us for any issues pertaining to Windows in the future. We will be happy to help.

 

Need to see a full screenshot of your disk management window first. Also from an elevated command prompt type
reagentc /info
and post the result. Then we can give you an informed answer.

Disk Management - How to Post a Screenshot of - Windows 10 Forums

 

Yes, you can do this. However, the Recovery environment will be broken. So after copy the last partition to the first position, you'd need to assign a letter R to it then run from Admin command:
reagentc /setreimage /path R:\Recovery\WindowsRE

Once done, remove the letter R
Re-run: reagentc /info to confirm that the Recovery environment is working
NOTE: If the status shows: Disabled then run: reagentc /enable

EDIT:You should also swap the sata cables to make your Windows OS to be disk 0. In addition, mark your data disk as "Inactive"

 

I did it, but windows RE status is disabled. I went through the process twice, but same results.

Also, I could not change the active status of the data disk, because the option is greyed out in disk management






EDIT:
I got the RE status to enable by following the directions here:
https://www.winhelp.us/restore-windows-re.html
I think that all I really needed to do was the last step: reagentc /enable but who knows?

I still can't mark my data disk as inactive, not sure how important that is...

 

Yep, that's all you need to do. If run again, the status should be: enabled

To mark inactive, from Admin command:

• diskpart
• select disk 1
• select par 1
• inactive
• exit

For MBR disk.During POST, will search for Boot info if the disk is marked ACTIVE. Since the disk is a Data disk, no boot info can be found hence will delay the boot time.

 

okay, that worked. The data disk no longer shows active.
But neither does the C partition on the primary disk (which is now 0, since I switched the SATA cables as recommended)
I tried the reverse command, but I got an error message saying it only works on MBR.
My primary disk is GPT.

 

That's normal. Your disk 0 is GPT disk, no such thing as "Active" with GPT disk, only with MBR disk that needs to mark as "Active" in order to boot. You are all set.
You can now mark it "SOLVED"