Question Nightmare System drive expansion
Question Nightmare System drive expansion
Display a screenshot of Disk Management once the recovery process completes, showing you boot from the newly recovered drive in Windows.
I have already given my response to you on that. Check your message for my reply. If I remember correctly (because I was working with it in diskpart earlier), there were four partitions: first the EFI partition, then the hidden MS partition, followed by the system C partition, then the recovery partition, and finally a lot of space.
I notice no images attached.
It seems the details provided aren't sufficient in text alone.
You might be remembering something incorrectly or referencing a different topic.
A visual capture would help resolve any confusion.
Which part of "Sorry.. too late, I have rebuilt the machine now." do you think you don’t grasp?
That ship has sailed... I’m curious about understanding this again, should I encounter something similar in the future.
What situation are you imagining? A functioning drive that breaks after what I did—using two separate commercial tools or manually as described?
In theory, I still have a backup, so I could recover again and take a screenshot, etc... but I’d destroy the rebuild (unless I back up the new build first, then restore the old one for the screenshot... which is a hassle). That’s really frustrating.
I would really benefit from a solid plan to help solve this issue.
If you had recorded your steps with photos, someone might have noticed the mistakes. Otherwise, it seems less important now. Hope you solve it.
I adjusted my reply as you did, so you might not have noticed... It’s uncertain if this will influence your decision.
In theory, I still have the backup, which means I could recover again and take a screenshot, but I would destroy the rebuild (unless I create a new build and restore the old backup for the screenshot—this is quite inconvenient).
I really need a solid explanation of how it could help resolve this issue.
It failed four times, so I’m pretty sure if I try again I could recreate the problem.
However, as I suspect, I would benefit from someone proposing a reasonable working hypothesis on what might have gone wrong, to justify the effort, especially since we currently only have a "clutching at straws" screenshot.
Partitions may receive a distinct id (guids/identifiers). If your system was configured to boot from a particular id and the partition tool altered it to the default, you might no longer be able to boot. This issue can be resolved by reverting the id or updating the boot settings to reflect the new id.
For more details, see: https://learn.microsoft.com/en-us/window...dentifiers
Regarding manual GUID changes – how severe are the risks? Is altering a generated GUID safely acceptable? The chance of collision remains low, but manipulating GUIDs can still pose dangers. Often, only minor adjustments are made, which doesn’t significantly increase risk.
I know what you mean, and I’d probably want to verify if it didn’t fail to start after the restore.
However, it did start up properly right after the restore.
It’s hard to believe that two commercial tools wouldn’t recognize this and switch IDs during partition changes—especially since moving or expanding partitions would have had to be handled differently.
Also, remember I also performed a move (deleting and recreating the recovery partition per MS instructions) and adjusted the size in the MS disk management tool; both of those steps also led to it not booting, and the tools should follow these procedures.
Is it even a prebuild?!
If it is, then the company responsible is the one that didn't "follow the rules," although anyone can change the IDs.
Partition tools and diskpart don't understand the need to preserve the ID, if you delete a partition—especially when expanding it—the old ID is lost.
Since the default ID relies on partition details, it would shift whenever those details change.
Cloning the disk maintains everything consistent, including IDs, so restarting after the restore should work fine.
It's just a theory at the end.