New
#81
Thanks topgundcp, but this machine is new from an OEM (HP).
Yep, I've seen Windows punt during an upgrade ... "resizing" the "Recovery" part by creating a new part (every freaking time an upgrade is performed!) I've seen some machines with 4 or more 450 MB Recovery parts all stuck on the end. It makes it quick and dirty for MS, but a pain for the user
The 1+ GB Recovery as the 1st part threw me off, but I'm not surprised that HP does it "their way". I suspect that "their way" is to put their bloat in that recovery and tell you to create your own recovery drive (or buy one from them). Not really certain about that though.
I'm not sure If I posted it in this thread, but these Technet pages are what I reference (even though they're Win8)
I adjust the WinRE part to 450 MB for UEFI | GPT (or combined System Reserved + WinRE to 500 MB for BIOS | MBR).
NavyLCDR and I worked on one thread that was a strange Hybrid (BIOS with UEFI | GPT partitioning) - the solution was to grow the EFI System part to 363 MB (member's choice on size, I suggested 450 MB). What these OEMs do and why is beyond my comprehension !
Configure UEFI/GPT-Based Hard Drive Partitions
Sample: Configure UEFI/GPT-Based Hard Drive Partitions by Using Windows PE and DiskPart
I recently set up a fresh Win10 Hyper-V machine (to get UEFI) and the default partition sizes do not match the Technet documentation, so I fed MS and asked for those pages to accurately reflect Win10. It's actually pretty cool how Win10 sets up the pars and vols (they don't match 1-to-1 (par1=vol2 - I had a text doc, but can't locate it now).
Anyway ... I've been wrestling with the latest round of AMD drop on my insider build for the past two days .. so this post is well past the expiration date
OldMike,
I apologize for the diskpart command omission, I forgot to put the partition parameter on the detail cmd.
I corrected that post, but there's no sense in you revisiting the commands at this point.