Solved bcd/bcdedit problems and others after Acronis DD11

[Kaktussoft]

In the first Windows Boot Loader, description shows (recovered) and the identifier shows a8087bf8...but in device and osdevice they show (9a8087bf9...)
And Device Options, identifier at bottom shows a8087bf9...

View attachment 220654

Could this be causing "repair computer" missing from F8 options at boot?

quite normal

But recovery id is not dedined and not enabled at your computer!

Do the 2 commands I asked you to do!! And post results

Windows-opstartlaadprogramma
----------------------------
id {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale nl-NL
inherit {bootloadersettings}
recoverysequence {c3c471b7-a336-11e1-a60f-bb1c0958a7b3}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {fa1a7f9d-ab26-11df-bc4f-ce7145d50d35}
nx OptIn

 

[Kaktussoft]

if both commands succeed do:
reagentc/info

and try if it works now

 

[front360]

Operation Successful for both reagentc cmds

/info
Extended configuration for the Recovery Environment
Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\a8087bfa-c9b0-11e1-9b9a-96dba092708e
BCD Id: a8087bfa-c9b0-11e1-9b9a-96dba092708e
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful

 

[gregrocker]

Nice work, rep to both of you.

 

[Kaktussoft]

Operation Successful for botb reagentc cmds

post reagentc/info output

and bcedit output again

 

[front360]

bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \bootmgr
description Windows Boot Manager
locale en-US
default {current}
displayorder {current}
timeout 30
Windows Boot Loader
-------------------
identifier {a8087bf8-c9b0-11e1-9b9a-96dba092708e}
device ramdisk=[C:]\Recovery\37f8044b-b1eb-11e1-b46b-ceaaa976d188\Winre.wim,{a8087bf9-c9b0-11e1-9b9a-96dba092708e}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\37f8044b-b1eb-11e1-b46b-ceaaa976d188\Winre.wim,{a8087bf9-c9b0-11e1-9b9a-96dba092708e}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {a8087bfa-c9b0-11e1-9b9a-96dba092708e}
device ramdisk=[C:]\Recovery\a8087bfa-c9b0-11e1-9b9a-96dba092708e\Winre.wim,{a8087bfb-c9b0-11e1-9b9a-96dba092708e}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\a8087bfa-c9b0-11e1-9b9a-96dba092708e\Winre.wim,{a8087bfb-c9b0-11e1-9b9a-96dba092708e}
systemroot \windows
nx OptIn
winpe Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
recoverysequence {a8087bfa-c9b0-11e1-9b9a-96dba092708e}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {2df96044-c997-11e1-b10f-806e6f6e6963}
Resume from Hibernate
---------------------
identifier {2df96044-c997-11e1-b10f-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Premium
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
Debugger Settings
-----------------
identifier {dbgsettings}
Device options
--------------
identifier {a8087bf9-c9b0-11e1-9b9a-96dba092708e}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\37f8044b-b1eb-11e1-b46b-ceaaa976d188\boot.sdi
Device options
--------------
identifier {a8087bfb-c9b0-11e1-9b9a-96dba092708e}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\a8087bfa-c9b0-11e1-9b9a-96dba092708e\boot.sdi

 

[front360]

Why are there 3 Windows Boot Loaders and 2 Device Options now? Is this correct?

 

[Kaktussoft]

bcdedit/delete {a8087bf8-c9b0-11e1-9b9a-96dba092708e}
bcdedit/delete {a8087bf9-c9b0-11e1-9b9a-96dba092708e}

these are old stuff

 

[Kaktussoft]

bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \bootmgr
description Windows Boot Manager
locale en-US
default {current}
displayorder {current}
timeout 30
Windows Boot Loader
-------------------
identifier {a8087bf8-c9b0-11e1-9b9a-96dba092708e}
device ramdisk=[C:]\Recovery\37f8044b-b1eb-11e1-b46b-ceaaa976d188\Winre.wim,{a8087bf9-c9b0-11e1-9b9a-96dba092708e}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\37f8044b-b1eb-11e1-b46b-ceaaa976d188\Winre.wim,{a8087bf9-c9b0-11e1-9b9a-96dba092708e}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {a8087bfa-c9b0-11e1-9b9a-96dba092708e}
device ramdisk=[C:]\Recovery\a8087bfa-c9b0-11e1-9b9a-96dba092708e\Winre.wim,{a8087bfb-c9b0-11e1-9b9a-96dba092708e}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\a8087bfa-c9b0-11e1-9b9a-96dba092708e\Winre.wim,{a8087bfb-c9b0-11e1-9b9a-96dba092708e}
systemroot \windows
nx OptIn
winpe Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
recoverysequence {a8087bfa-c9b0-11e1-9b9a-96dba092708e}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {2df96044-c997-11e1-b10f-806e6f6e6963}
Resume from Hibernate
---------------------
identifier {2df96044-c997-11e1-b10f-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Premium
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
Debugger Settings
-----------------
identifier {dbgsettings}
Device options
--------------
identifier {a8087bf9-c9b0-11e1-9b9a-96dba092708e}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\37f8044b-b1eb-11e1-b46b-ceaaa976d188\boot.sdi
Device options
--------------
identifier {a8087bfb-c9b0-11e1-9b9a-96dba092708e}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\a8087bfa-c9b0-11e1-9b9a-96dba092708e\boot.sdi

Numbers match fine now. Reagentc/disable couldn't remove them bacause....
recovery not enabeled. ID not same as in reagentc/info. don't know.

I think it's working fine now

 

[front360]

okay done, but command only worked when typed bcdedit /delete

should i try reboot with F8 yet?

 

[Kaktussoft]

Why are there 3 Windows Boot Loaders and 2 Device Options now? Is this correct?

Only 2 bootloader now. 1 win7 and 1 win7 recovery environment. now 1 device options is correct.

Winre now working? All problems fixed?

 

[Kaktussoft]

Gonna sleep

 

[Kaktussoft]

okay done, but command only worked when typed bcdedit /delete

should i try reboot with F8 yet?

try to reboot using F8

 

[front360]

You did it, Kaktussoft! Thank you again, I really appreciate it.

 

[front360]

System Repair ran SFC and had an error it couldn't fix, so I ran SFC. Is this possibly an IE or Java(JScript) problem that SFC detects?

CSI 000002dc [SR] Cannot verify component files for Microsoft-Windows-IE-JScriptDebugUI, Version = 9.4.8112.16446, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)

 

[Kaktussoft]

The last issue I saw was from running SFC. Is this possibly an IE or Java(JScript) problem that SFC detects?

CSI 000002dc [SR] Cannot verify component files for Microsoft-Windows-IE-JScriptDebugUI, Version = 9.4.8112.16446, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)

To what/who are you responding? I think you posted in wrong thread(?)

 

[front360]

To anyone. Kaktussoft, you had fixed my bcd issue yesterday and I didn't know if I should start a new thread. thanks

 

[front360]

Kaktussoft, not a big deal but I'd like to know something for future knowledge. After we did all things in this thread to fix my BCD issues, now all my Restore Points are gone and the Restore Disk Usage was changed to 0%. Which command deleted and reset this, was it reagentc /disable or a different one??

 

[Kaktussoft]

Kaktussoft, not a big deal but I'd like to know something for future knowledge. After we did all things in this thread to fix my BCD issues, now all my Restore Points are gone and the Restore Disk Usage was changed to 0%. Which command deleted and reset this, was it reagentc /disable or a different one??

As far as I can remember the only problem was the "system reserved" partition being offline. You did a rebuildbcd which did rebuild the bcd and didn't enable the winre (f8).

startup repair, rebuildbcd, reagentc.... none were actually necessary if you did NOT rebuildbcd. Only what was necessary was the diskpart automount.

Are restore points still enabled? Can you successfuly create a "manual restore point"?

None of the commands mentioned above delete your restore points

 

[Kaktussoft]

Did you or any installation/uninstall or any windows update create a restore point AFTER restoring using acronis?
After restoring they are gone for sure. They will start to be created afterwards.