• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

[SOLVED] MSCONFIG problem

I try to manage the space in the (somewhat limited) SSD. I get what you're saying about removing unused clones. I'll have
to keep that in mind if I start to scramble for SSD space. Is there a safe means to test that out... like temporarily renaming
them or marking them in a way that the O/S doesn't see them so I can see if boot is affected... if it is, I just re-name / re-mark
them back and walk away.
 
If you check volumes and partitions in diskpart (see 117th post) you will see the ESP in disk 1 - your SSD - is already unused and marked as 'healthy' and 'hidden', because the other ESP in disk 0 - your hdd - is marked as 'healthy' but 'system'.
When you launched the bcdboot command (see 98th and 99th posts), it used the ESP in your hdd instead of the one in your SSD.

Instead the cloned recovery partition isn't used because when you (we) launched (used) the bcdedit commands (see 118th and 119th posts), you (we) gave them the parameters to use the recovery partition in disk 0 - your hdd.

<WinreBCD id="{a9e30dc8-1c6a-11e5-923b-f8b156fecaed}"/>
<WinreLocation path="\Recovery\WindowsRE" id="0" offset="701497344" guid="{3f8d2e9a-2795-45c4-a30b-d5d9ff84b6fb}"/>
Click to expand...
{a9e30dc8-1c6a-11e5-923b-f8b156fecaed} is the id for the recoverysequence bcdedit /set {current} recoverysequence {a9e30dc8-1c6a-11e5-923b-f8b156fecaed}.
{3f8d2e9a-2795-45c4-a30b-d5d9ff84b6fb} is the guid of your disk 0 - hdd.
701497344 is the offset of your recovery partition (in disk 0 - your hdd; i.e., where the recovery partition is located. It starts after: 701 497 344 bytes).


Anyway, it's your choice.
If you're not comfortable deleting the two cloned and unused partitions on the ssd, you can quietly leave them. :-)
 
This is all good info; I have about 50% unused on the SSD (it varies), but this is a good way to go if I find more space getting used up.

I try to use junction links when I find something bulky that can get moved to the HDD, but knowing I can snag some more space is good!
 
Just thinking out loud... Knowing now that I have two possible boot records (one on the HDD that is the original as-delivered
config; and one on the SSD that's up-to-date and boots my machine the way I expect it), it seems I have two choices:
  • Leave it that way; if I ever have future problems, I can at least get back to "original"
    OR
  • Clone the "current, good" boot image from the SSD back to the HDD; if I ever have future issues, I could boot to
    EITHER image and get to the same place
Guess I have some thinking to do!
 
Back
Top