New
#11
According to @PoulsboMike in post #1 it used to be partition 4, which apparently got its type changed after resizing it....
Here are the results of the reagentc and bcdedit commands.
>>I'd like to see the full text from reagent /info and bcdedit. Can you attach it as a text file please.
Thanks,
It appears that only the path needs to be set. To use partition 4, type this in an elevated command prompt.
Code:reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
You may wish to check first that your partition 4 does indeed contain the recovery environment. You are looking for the folder that contains Winre.wim. Mini Tools Partition Wizard can explore partitions that have no drive letter and/or are hidden.
It probably isn't necessary to mark the partition as 'Recovery' for it to work, but if you wish the Diskpart Set ID command can be used.
Here's some good information on GPT partitions:
UEFI/GPT-based hard drive partitions | Microsoft Docs
Partition 4 has no volume associated with it because it does not have a drive letter assigned. Normally, recovery partitions won't have drive letters assigned, and thus no volume associated with it.
I got this info from my wife's Win 10 machine. I'm not sure what mine showed prior to resizing but assumed it was probably similar.
Partition 4
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 985471647744
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 3 WINRETOOLS NTFS Partition 450 MB Healthy Hidden
Hmmm.... maybe I was mistaken twice in the same thread now.
Further research - no volume associated with it indicates that there is no filesystem on the partition that can be read by Windows. I would go back to what @Bree suggested. Install MiniTool Partition Wizard and try to explore that partition from within MiniTool Partition Wizard and see if it can detect any files and folders there.
A partition is only space set aside on a physical drive for a filesystem - it confines whatever filesystem gets put into that partition to the space set for the partition.
When you format the partition, you create the filesystem in it.
Once the OS recognizes that a filesystem is present, then it assigns a volume to it.
Then, if desired, the OS will assign a drive letter to the volume to make it routinely accessible to the user.
Hmm, it appears that resizing the partition did more damage than just changing its ID. What tool did you use?
Before doing anything else, I'd make sure I had a full image of all partitions. I'm not sure what repair options are available for UEFI/GPT drives, all mine are MBR. Let's hope a GPT guru spots this thread.