Solved Error: "To use System Restore, you must specify which Windows installation to restore...."

Bug locker said:

Could you upload a screenshot of disk management where the Recovery partition is visible.
Also note that many manufacturers like HP use them own Recovery partition. Maybe it is ?
How you know if the visible recovery partition is WinRE or other ?

Click to expand...

Try3 said:

I have.
You were so quick to reply that I had not had time to attach it by then. [I posted the text then went through my archives hunting for that diagram, hence the time lag]
That diagram is of the system as delivered. I had not changed anything.


It is WinRE.


No.
When makers put in a partition it is about 13GB because it contains a full system image of the system.



Denis

Click to expand...

Try3 said:

Where does reagentc /info say your recovery files are?


Denis

Click to expand...

Try3 said:

Αυτό σημαίνει ότι τα αρχεία WinRE βρίσκονται στο φάκελο C:\Recovery.
Φαίνεται λοιπόν ότι τα μετατοπίσατε και διαγράψατε το διαμέρισμα ανάκτησης με τον κανονικό τρόπο***.
Επομένως, δεν υπάρχει μυστήριο σχετικά με το γιατί δεν εμφανίζεται στα διαγράμματα Disk mgmt ή MTPW.


***
reagentc /disable
delete the Recovery partition using MTPW
reagentc /enable



Τα καλύτερα,

Click to expand...

Try3 said:

There is no difference between our results.
Both our WinRE files are within the folder C:\Recovery [as shown in both your results & my results].

Nothing is wrong.

Denis

Click to expand...

Bug locker said:

Last 2 days i tried to set and fix some things. These are enable/disable the WinRe , create missing WinRE.wim , create missing BCD file ,
enable/disable F8 menu. All done.
But sometime i tried to run System Restore (Restore point) from WinRE/WinPE.
So i got a new problem : When i click to choose the "System Restore" , i take an error.
That it not happens if i do that from inside windows. Happens when i boot to WinPE from USB installation disk and reboot to WinRE e.g with Shift+Restart.

Click to expand...

Try3 said:

I think your problem is that you corrupted something in BCD when you were playing around with it.
Nothing indicates any fault within your C:\ drive.
I think that a clean install will fix the BCD-related fault and will create a sound EFI System partition. The computer will boot without any problems.
I think that then restoring your C:\ drive image onto the C:\ drive of the new installation will mean you have all your current settings, applications & files back.

This is a bigger job than working with BCD but I don't know what to do with that.
@NavyLCDR Perhaps you can advise the OP better than I can since you are competent in use of BCD commands.


All the best,
Denis

Click to expand...

Try3 said:

Well it looks the same as mine.

Windows 10 example

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
default {current}
resumeobject {13e3c86c-1dbb-11ee-8ebe-8ee7468b6538}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10
locale en-GB
inherit {bootloadersettings}
recoverysequence {61252ee5-1db6-11ee-99b6-98541b12b3e9}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {13e3c86c-1dbb-11ee-8ebe-8ee7468b6538}
nx OptIn
bootmenupolicy Standard


Windows 11 example [My Windows 11 has an extra entry because I have a boot menu with Safe mode on it]

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
default {current}
resumeobject {91854384-1374-11ee-98ea-a5e178e95a6d}
displayorder {current}
{200c1967-15b1-11ee-890f-f46add8d0a8a}
toolsdisplayorder {memdiag}
timeout 3

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 11
locale en-GB
inherit {bootloadersettings}
recoverysequence {ab3b7483-cc1f-11ee-b45e-f46add8d0a8a}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {91854384-1374-11ee-98ea-a5e178e95a6d}
nx OptIn
bootmenupolicy Legacy

Windows Boot Loader
-------------------
identifier {200c1967-15b1-11ee-890f-f46add8d0a8a}
device partition=C:
path \Windows\system32\winload.efi
description Safe mode
locale en-GB
inherit {bootloadersettings}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {91854384-1374-11ee-98ea-a5e178e95a6d}
nx OptIn
safeboot Minimal
bootmenupolicy Standard


Denis

Click to expand...

Bug locker said:

\Device\HarddiskVolume2

Click to expand...

Try3 said:

That's your EFI System partition,.
View attachment 90423

View attachment 90424


The number 2 makes sense in MTPW. In Disk mgmt, you have to count the 16MB that Disk mgmt does not display [but MTPW does].


All the best,
Denis

Click to expand...

​

Bug locker said:

But yours bootmenupolicy is Legacy , mine is standard.

Click to expand...

Try3 said:

I told you I had a boot menu.
I have mine set to a black & while screen and that's called Legacy.
It is of no significance as far as I am aware.


Denis

Click to expand...

ThrashZone said:

Hi,
To get a new RE partition you can mount 23h2 or which ever you have and keep files and apps and a new one will be created at the end of C

I added mine in front of C and made it larger so it's out of the way and I can use my disk as I want to.
Disk management is a old POS app use third party partition apps and see all partitions not just the ones windows wants you to

View attachment 90448

This will create a new RE partition at the end of C 2gb though so make it what ever you want to later
Anyway everything is on a thread i made a while back

CMD format ssd for install

This is exactly how I set up my drive 0. Like you, I only image backup 1st four partitions (3 hidden and C drive). The data partition is backed up separately. IMO, this is the optimum layout unless you have a second data drive in which case, it is rather optional to have a data drive on drive...

www.elevenforum.com

Code:

REM After creating, shrink by 2 GB to make room for the Recovery Tools partition.
You can change that size to anything.

create partition primary
shrink desired=2048
format fs=ntfs quick label="Windows"

REM Since we shrank the partition by 2 GB, create the Recovery partition without specifying a size.
REM This will cause it to occupy all remaining space (in this case 2 GB).
REM Note that for a recovery partition we have to set a specific ID and attribute.

create partition primary
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
GPT ATTRIBUTES=0x8000000000000001
format FS=NTFS quick label="Recovery Tools"

REM Type exit to exit from diskpart. If you are using these commands in a diskpart script,
REM leave off the exit

exit

Click to expand...

Try3 said:

I told you I had a boot menu.
I have mine set to a black & while screen and that's called Legacy.
It is of no significance as far as I am aware.


Denis

Click to expand...