BootMgr Missing after Easus Repart of C - No Repair Tool is Working

I told you to run from command line! Not double click. Did it run successfully form "command prompt at boot"? No menu anymore? If so.... start restoring F,G,H and if running.... go asleep

Kaktussoft said:

C (OS-W764) 100GB
D (Hidden HP Recovery Part 2GB)
E (DVD ROM)
F Pictures 200GB
G Another... 200GB
H Misc.... 500GB

Was the original drive lettering.
So rename the stupid thing called E now to Z for example. After that rename D to E. After restoring F,G,H as well... give them correct drive letters as it was before!

I want to eliminate HP_Recovery which was occupying D and just create an empty partition there of maybe 100GB in case she ever wants to add space to C. Then put the DVD ROM where it belongs after everything else - so maybe create a second empty partition for E, so that FGH maintain the same drive letters... then just restore FGH, Is that OK?

e.g.

C (OS)
D (100GB)
E (100GB)
F (Pictures)
G (Another/Sharlene)
H Misc

EDIT: I actually don't even have to restore the partitions but just create the partitions in Windows with MiniToolWizard then transfer the data over.

EDIT: I did this as stated in a later post.

But want to get the Recovery thing working first so looking into that now.

Kaktussoft said:

System Protection - Turn On or Off
Do step 7 for C To Turn On System Protection for System Settings and Previous Versions of Files

Thanks, done.

And do 9. To Turn Off System Protection for the Selected Disk for any ghost drives (missing).
-----
Also: Give drives the correct drive letter in "disk management" (also DVD drive)

...done.

-----
Also enable the recovery environment so that Advanced Boot Options ->"repair your computer" works. It is disabled now! So do in Elevated Command Prompt

Code:

reagentc/enable

succesfull? if so... reboot and test
=========================

Ran from elevated command prompt... Got error:
REAGENTC.EXE: Operation failed: 57
The parameter is incorrect.

Thought maybe this would help: reagentc /info

Someone fixed this same problem by creating a Recovery folder on C, then a subfolder inside with the numeric ID noted in the /info log as the name of the subfolder, then copied BOOT.SDI and WINRE.WIM in there. I tried that. Got the same error exactly.

Just ran bcdout again and it no longer says the bit about "recovery enabed no":


Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {74c4be10-3600-11e0-8ff1-0018716eb820}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {b4bfce44-d9a0-11e2-ab43-806e6f6e6963}

Resume from Hibernate
---------------------
identifier {b4bfce44-d9a0-11e2-ab43-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device locate=\boot\memtest.exe
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

******************************************
******************************************
But I still get the same error. However when I press F8 at boot I get:

Safe Mode
SM with networking
SM with command prompt

enable boot logging
enable low res
Last know good config
Directory services restore mode
debugging mode
disable auto restart on sys failure
disable driver signature enforcement

Start Windows normally

***************************************
***************************************
So it appears it's enabled unless there is supposed to be an advanced "repair windows" option from here.

remm said:

Ran the bcdfix.cmd from boot command prompt with two errors as seen here.

But it worked - no more boot menu! Starting on the next instructions. Will report back...

from Elevated Command Prompt

Code:

 
bcdedit/set {bootmgr} resumeobject {b4bfce44-d9a0-11e2-ab43-806e6f6e6963}

Do this as well in elevated command prompt:

Code:

bcdedit /set {current} recoveryenabled yes

After that:

Code:

reagentc/disable
reagentc/enable

Still not working? then:

Code:

bcdedit /set {current} recoveryenabled yes

Now do "startup repair" 3 times

remm said:

So I created the partitions in Windows using MiniToolPartitionWizard and resized the C to make it larger (she wanted it larger, that's how this got started).... then created two empty partitions for D and E of 100GB each to take up space where the old D & E were. Then created F, a smaller G and the rest made a smaller H.

Used Paragon to restore the files selectively not checking the System Volume folders or Recycle bins... just the data. Put everything where it belonged and rebooted... and it's working great.

Am downloading Macrium Reflect Free to do a new backup. Meanwhile the only thing left is enabling the reagentc thing... will Google that again, now that I have the data restored.

BTW let's say she wanted to merge the empty D and E partitions into the C (I keep mine small for reasons of defrag and stuff, but she finds it easier to store things in C even with extra partitions for that purpose)... but later if she wanted to do that and FGH became DEF (Pictures could be transferred to the new F to remain in F), that shouldn't cause a problem, should it? Because it's just files and folders.

Rename drive letters of data partitions is not a problem. Moving data files is not a problem as well.

Be sure to update all refereces to those stuff. For example to media player library. And user explorer libraries . I mean libraries as show here