Windows 10: Configuring System Image on Recovery Partition

Hello - I have just done a fresh install of Windows 10 Pro to my reasonably old hardware.

I am running a boot loader called Clover which emulates EFI and Windows 10 has therefore been installed to a GPT disk.

I manually configured the partitions according to this:

Sample: Configure UEFI/GPT-Based Hard Drive Partitions by Using Windows PE and DiskPart

Giving me this:





I understand that the 1st 300 MB partition is to hold the recovery environment which I think is configured since the following is returned:

Code: C:\Windows\system32>REAGENTC.EXE /Info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition5\Recove ry\WindowsRE Boot Configuration Data (BCD) identifier: ca5cef0b-45f1-11e5-9e89-ac5f2b72bb e9 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful.[/quote] Am I on the right track when I say that I now need to create the recovery image in to the 14.65GB partition ?

Can Windows 10 do this or must I use a tool such as AOMEI OneKey Recovery ?

:)

 

Multiple drive o recovery and EFI partitions

These extra partitions have probably been created over time from upgrading your system. If the update process sees there is not enough space in a recovery partition for the upgrade a new partition is created.

The only real way to remove all these partitions is to perform a clean install, while this is not ideal, there is no way for you to know which recovery partition is the latest and therefore it would be dangerous to start deleting partitions

Default HDD Configuration:





Recommended HDD Configuration:

 

Duplicate Recovery partition in Disk Management

The default partition layout for UEFI-based PCs is: a system partition, an MSR, a Windows partition, and a recovery tools partition.



UEFI/GPT-based hard drive partitions

Keith

 

I booted in to Windows PE and ran disk part to find out the drive letters and this has shown that the Windows drive is mounted under Windows PE as C: and the 15 GB as K:
I then ran:

Code: dism /capture-image /image-file:k:\windows10_pro.wim /capturedir:C:\ /name:"Windows 10 Pro"[/quote] The image file got create ok however the system restore is unable find the drive and hence also not the wim file.

 

several issues..
I assume you are running windows 10 OS

Windows 10 does not use a recovery image or recovery image partition - it uses the component store..

The reagentc info you posted shows winre on partition 5 > 14.65GB < not 300MB partition
the reason for this is because windows 10 uses a 450MB recovery tools partition

 

Thanks Kyhi for the reply.

Yes I am running Windows 10 Pro - a fresh install using the "upgrade key"

Point 6 under Option 1 here:

DISM - Repair Windows 10 Image - Windows 10 Forums

indicates that a wim image can be used for repair as an alternative to the online DISM actions.

If I reinstalled I assume the Windows RE 450 MB partition would get created. However do you know if there is a recommended partitioning scheme to allow wim file to be kept on the local disk in order to use :
Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1 /limitaccess[/quote] Thanks again !

 

I'm assisting a small company with a migration to Windows 10. Like many, upgrades take a lot of research and time; however they're pretty easy to work with, so I want to make them happy. Because the people I work with are often in the professional community, I always default to past methods that have worked well, and while there's some time to address the issues, I'm just putting my feelers out there to anyone that might have some input.

In short, I'm having the exact same problem with a new unit. The CEO of the company was very happy with having used Windows 10 on a separate system, so it's important that they get what they need to move forward and have it work reliably.

Here's the architecture they're going to be following per my design and MS' recommended architecture as so well noted in this post by David74:

Attachment 82742

It is hoped that the picture allows many people to understand this problem, and hopefully we all get the opportunity to team up by sharing our knowledge in order to mutually benefit from what is a great way to deploy an OS.

"Knowing the specifics of a problem does not always mean the implement of solution is readily at hand."