New
#11
I think startup repair was a little bit confused! Disk0 is the first disk to try to boot from. RECOVERY is marked active. I think windows did try to repair that partition instead of SSD. But not sure about that
Attached is the bcd.txt file.
I did clone disk 0 to disk 1, yes. Does this mean I can delete the second and second last partitions, as seen in my screenshot of disk management?
bcdmenu is realy a mess!! Some things point to harddiskvolume5 , some to D and one to unknown.
Do in elevated command prompt:
dir/ahs \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0
post output
reagentc/info
post output
Hi Kaktussoft,
I really appreciate you staying with me on this.
The first part of your instruction there doesn't seem to work for me - it says it could not find path specified.
The second part, reagentc/info :
Extended configuration for the Recovery Environment
Windows RE enabled: 1
Windows RE staged: 1
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory: \\?\GLOBALROOT\device\harddisk0\partition2\recovery\windowsre
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE
BCD Id: 7596ba67-735a-11e1-8282-848f69c777b3
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful
These are the strange identifiers in bcd.txt
identifier {07288cf1-a1e2-11e1-b319-91d364d3f396}
identifier {07288cf2-a1e2-11e1-b319-91d364d3f396}
identifier {07288cf3-a1e2-11e1-b319-91d364d3f396}
identifier {07288cf4-a1e2-11e1-b319-91d364d3f396}
identifier {1f8184a5-14de-11df-9734-f08c6d8c50b0}
First disable WINRE, delete unneeded stuff and enable WINRE
All done from elevated command promptCode:reagentc/disable (only proceed if command is succeful!) maybe some entries are gone now bcdedit/delete {07288cf1-a1e2-11e1-b319-91d364d3f396} bcdedit/delete {07288cf2-a1e2-11e1-b319-91d364d3f396} bcdedit/delete {07288cf3-a1e2-11e1-b319-91d364d3f396} bcdedit/delete {07288cf4-a1e2-11e1-b319-91d364d3f396} bcdedit/delete {1f8184a5-14de-11df-9734-f08c6d8c50b0} reagentc/enable
Post bcd output again
Last edited by Kaktussoft; 19 May 2012 at 07:48.
Hi again,
I've done as you instructed, and attached is the new bcd.txt file.
I had to change bcdedit/del to bcdedit/delete, but I presume it has the same effect!!
yes it should be bcdedit/delete
Everything has been cleared and sholuld work now. Does F8 on boot work and starts WINRE?
It's still runing from D: we will fix that later
identifier {f38191ca-a1a9-11e1-8b23-848f69c777b3}
device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{f38191cb-a1a9-11e1-8b23-848f69c777b3}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{f38191cb-a1a9-11e1-8b23-848f69c777b3}
systemroot \windows
nx OptIn
winpe Yes
identifier {f38191cb-a1a9-11e1-8b23-848f69c777b3}
description Ramdisk Options
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\WindowsRE\boot.sdi
in elevated command prompt
Code:dir/ahs /s c:\winre.wimare these files on C:?Code:dir/ahs /s c:\boot.sdi