New
#31
Look at my post, I already tried that.
C:\Users\rrkurtz>reagentc /enable
REAGENTC.EXE: The Windows RE image was not found.
Look at my post, I already tried that.
C:\Users\rrkurtz>reagentc /enable
REAGENTC.EXE: The Windows RE image was not found.
Hi,
Not without some trickery you won't.I should be able to merge the two un-allocated partitions into C: and get back to just 3 partitions (I hope).
When I look at the partition table of disk 0 I go aaarghhhhhhhh.
200+ gig for that C:\ partition? Really ? I know it's common practice but it's no good practice to mix data and OS related stuff and I blame most OEMs for it but it's really asking for trouble.
Maybe I'm one of those rare examples that shoe horns the OS into a 30gig partition and points all the personal stuff to a DATA partition but that's what I've always done. I come from an industrial environment where safety first rules.
You know, all this RAID stuff, scsi, mainframes etc.
Anyway, if you're interested I can show how to shrink that C: drive and create a data partition etc.
Microsoft Reserved Partition. And no, you can't touch partitions to the left of your system partition (C:\).What is this 16MB other it shows? Can I use Aomei to merge it and the 1.48GB partitions into C:?
Cheers,
I do not want to fiddle with drive space problems. I much prefer to keep all the basic stuff on my 250GB SSD. All programs, all data. Why not take advantage of the SSD speed wherever possible.
If I were a gamer or installed programs that required a large drive space use then I would install it to one of my other drives, but I'm not so I don't see the point.
I also have 3.5TB of additional disk storage where I keep other things, including file backups via Mirror Folder and image backup via Macrium reflect Pro.
My system is fast and reliable asis.
Edit: If I need more space, I'll get a bigger SSD but so far I've only used about 70GB on the SSD so there is lots of space left.
Hi,
I was talking same drive but new partition to store data. SSD or anything you fancy Sir.I do not want to fiddle with drive space problems. I much prefer to keep all the basic stuff on my 250GB SSD. All programs, all data. Why not take advantage of the SSD speed wherever possible.
As said, not good practice to mix user data and OS. That's all.
Cheers,
I understand what you meant and at one time I used to do that, but as I said, I now prefer to keep it all on the SSD in a single partition.
I know how to move user stuff off to another partition and how to redirect other things to a different partition, I just have no interest in doing so.
I do appreciate the offer but it's just not something I care to do. I'm happy the way it's setup now, especially if I can get rid of the annoying 16MB and 1.48GB partitions or un-allocated space. Even if not, I'm happy asis.
Hi,
Fair enough.I do appreciate the offer but it's just not something I care to do. I'm happy the way it's setup now, especially if I can get rid of the annoying 16MB and 1.48GB partitions or un-allocated space. Even if not, I'm happy asis.
Just trying to help out as I've seen too many people struggling with EFI partition schemes.
All the best,
Still trying to figure out how to enable Windows RE.
I found this xml file in the 450MB partition. Is the information I need to fix this in there, like the GUID?
<?xml version='1.0' encoding='utf-8'?>
<WindowsRE version="2.0">
<WinreBCD id="{4b087f93-8cd7-11e5-987b-b318410213b4}"/>
<WinreLocation path="\Recovery\WindowsRE" id="0" offset="1048576" guid="{e4bf3c3a-b75d-48a2-a7c0-2860dee59991}"/>
<ImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
<PBRImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
<PBRCustomImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
<InstallState state="1"/>
<OsInstallAvailable state="0"/>
<CustomImageAvailable state="0"/>
<IsAutoRepairOn state="1"/>
<WinREStaged state="0"/>
<OperationParam path=""/>
<OsBuildVersion path="10240.16384.amd64fre.th1.150709-1700"/>
<OemTool state="0"/>
<IsServer state="0"/>
<DownlevelWinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
<IsWimBoot state="0"/>
<ScheduledOperation state="5"/>
</WindowsRE>
Use MiniTool Partition Wizard Free to assign a drive letter to the recovery partition. Say R:. Then from an elevated command prompt the command would be:
REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE
Once you have the location of the WindowsRE set, you can remove the drive letter from the recovery partition.
That worked, thanks. After running reagentc as you showed, I was able to do a reagentc /enable and now it's useable:
Code:C:\Users\rrkurtz>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: 3bd199af-8cab-11e5-9737-448a5b06acdb Recovery image location: \\?\GLOBALROOT\device\harddisk1\partition2\Recimage Recovery image index: 1 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful.