win7 repair and recovery not accessible after resizing partitions

Page 3 of 4 FirstFirst 1234 LastLast

  1. 5ggggg
    Posts : 43
    win7_home_64
    Thread Starter
       New #21

    - F11 starts hp environment like "Ramdisk Options" does now
    - post #15 shows the output of original BCD C:\Users\Administrator>bcdedit /store C:\sources\acronis111209\Laufwerk(C)\Boot\bcd /enum all
    - if I use reagentc /disable the store looks different afterwards
    diabled:
    Code:
    C:\Users\Administrator>bcdedit /enum all
Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=H:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
extendedinput           Yes
default                 {current}
resumeobject            {158181c0-9a00-11db-8a1d-b11d19fd3102}
displayorder            {current}
                        {6d9f7130-2281-11e1-8857-2c41385e3f8f}
toolsdisplayorder       {memdiag}
timeout                 30
Windows-Startladeprogramm
-------------------------
Bezeichner              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  de-DE
inherit                 {bootloadersettings}
recoveryenabled         No
osdevice                partition=C:
systemroot              \Windows
resumeobject            {158181c0-9a00-11db-8a1d-b11d19fd3102}
nx                      OptIn
Windows-Startladeprogramm
-------------------------
Bezeichner              {572bcd60-ffa7-11d9-aae0-0007e994107d}
device                  ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
path                    \windows\system32\boot\winload.exe
description             Microsoft Windows PE 2.0
osdevice                ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
systemroot              \windows
detecthal               Yes
winpe                   Yes
ems                     Yes
Windows-Startladeprogramm
-------------------------
Bezeichner              {6d9f7130-2281-11e1-8857-2c41385e3f8f}
device                  ramdisk=[G:]\Recovery\WindowsRE\Winre.wim,{6d9f7131-2281-11e1-8857-2c41385e3f8f}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[G:]\Recovery\WindowsRE\Winre.wim,{6d9f7131-2281-11e1-8857-2c41385e3f8f}
systemroot              \windows
nx                      OptIn
winpe                   Yes
Wiederaufnahme aus dem Ruhezustand
----------------------------------
Bezeichner              {158181c0-9a00-11db-8a1d-b11d19fd3102}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  de-DE
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No
Windows-Speichertestprogramm
----------------------------
Bezeichner              {memdiag}
device                  partition=H:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  de-DE
inherit                 {globalsettings}
badmemoryaccess         Yes
EMS-Einstellungen
-----------------
Bezeichner              {emssettings}
bootems                 Yes
Debuggereinstellungen
---------------------
Bezeichner              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200
RAM-Defekte
-----------
Bezeichner              {badmemory}
Globale Einstellungen
---------------------
Bezeichner              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}
Startladeprogramm-Einstellungen
-------------------------------
Bezeichner              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}
Hypervisoreinstellungen
-------------------
Bezeichner              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200
Einstellungen zur Ladeprogrammfortsetzung
-----------------------------------------
Bezeichner              {resumeloadersettings}
inherit                 {globalsettings}
Geräteoptionen
--------------
Bezeichner              {4cbd1d8e-2250-11e1-85fc-2c41385e3f8f}
description             Ramdisk Options orig
ramdisksdidevice        unknown
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Geräteoptionen
--------------
Bezeichner              {6d9f7131-2281-11e1-8857-2c41385e3f8f}
description             Ramdisk Options
ramdisksdidevice        partition=G:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Optionen zum RAM-Datenträgersetup
---------------------------------
Bezeichner              {ramdiskoptions}
description             Ramdisk Options
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi
    enable (4 loaders, 3 ramdisk, HP recov and ramdisk have been doubled with new guid):
    Code:
    C:\Users\Administrator>ReAgentC /enable
REAGENTC.EXE: Vorgang erfolgreich ausgeführt
C:\Users\Administrator>bcdedit /enum all
Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=H:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
extendedinput           Yes
default                 {current}
resumeobject            {158181c0-9a00-11db-8a1d-b11d19fd3102}
displayorder            {current}
                        {6d9f7130-2281-11e1-8857-2c41385e3f8f}
toolsdisplayorder       {memdiag}
timeout                 30
customactions           0x1000085000001
                        0x5400000f
custom:5400000f         {06c30f27-229f-11e1-81c2-2c41385e3f8f}
Windows-Startladeprogramm
-------------------------
Bezeichner              {06c30f27-229f-11e1-81c2-2c41385e3f8f}
device                  ramdisk=[G:]\Recovery\WindowsRE\Winre.wim,{06c30f28-229f-11e1-81c2-2c41385e3f8f}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[G:]\Recovery\WindowsRE\Winre.wim,{06c30f28-229f-11e1-81c2-2c41385e3f8f}
systemroot              \windows
nx                      OptIn
winpe                   Yes
Windows-Startladeprogramm
-------------------------
Bezeichner              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {06c30f27-229f-11e1-81c2-2c41385e3f8f}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {158181c0-9a00-11db-8a1d-b11d19fd3102}
nx                      OptIn
Windows-Startladeprogramm
-------------------------
Bezeichner              {572bcd60-ffa7-11d9-aae0-0007e994107d}
device                  ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
path                    \windows\system32\boot\winload.exe
description             Microsoft Windows PE 2.0
osdevice                ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
systemroot              \windows
detecthal               Yes
winpe                   Yes
ems                     Yes
Windows-Startladeprogramm
-------------------------
Bezeichner              {6d9f7130-2281-11e1-8857-2c41385e3f8f}
device                  ramdisk=[G:]\Recovery\WindowsRE\Winre.wim,{6d9f7131-2281-11e1-8857-2c41385e3f8f}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[G:]\Recovery\WindowsRE\Winre.wim,{6d9f7131-2281-11e1-8857-2c41385e3f8f}
systemroot              \windows
nx                      OptIn
winpe                   Yes
Wiederaufnahme aus dem Ruhezustand
----------------------------------
Bezeichner              {158181c0-9a00-11db-8a1d-b11d19fd3102}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  de-DE
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No
Windows-Speichertestprogramm
----------------------------
Bezeichner              {memdiag}
device                  partition=H:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  de-DE
inherit                 {globalsettings}
badmemoryaccess         Yes
EMS-Einstellungen
-----------------
Bezeichner              {emssettings}
bootems                 Yes
Debuggereinstellungen
---------------------
Bezeichner              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200
RAM-Defekte
-----------
Bezeichner              {badmemory}
Globale Einstellungen
---------------------
Bezeichner              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}
Startladeprogramm-Einstellungen
-------------------------------
Bezeichner              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}
Hypervisoreinstellungen
-------------------
Bezeichner              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200
Einstellungen zur Ladeprogrammfortsetzung
-----------------------------------------
Bezeichner              {resumeloadersettings}
inherit                 {globalsettings}
Geräteoptionen
--------------
Bezeichner              {06c30f28-229f-11e1-81c2-2c41385e3f8f}
description             Ramdisk Options
ramdisksdidevice        partition=G:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Geräteoptionen
--------------
Bezeichner              {4cbd1d8e-2250-11e1-85fc-2c41385e3f8f}
description             Ramdisk Options orig
ramdisksdidevice        unknown
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Geräteoptionen
--------------
Bezeichner              {6d9f7131-2281-11e1-8857-2c41385e3f8f}
description             Ramdisk Options
ramdisksdidevice        partition=G:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Optionen zum RAM-Datenträgersetup
---------------------------------
Bezeichner              {ramdiskoptions}
description             Ramdisk Options
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi
      My Computer
    Quote Quote

  3. boyans
    Posts : 240
    Win 8 RP, Win 7, XP
       New #22

    The difference between the two BCD outputs is exactly as expected.

    reagentc /disable = delete one recovery loader + its device options + removing customactions pointing to deleted recovery loader + amend basic Windows 7 loader (to not recovery enabled).


    So you can now start Windows 7 and start Recovery - anything else ?
      My Computer
    Quote Quote

  4. 5ggggg
    Posts : 43
    win7_home_64
    Thread Starter
       New #23

    only F11 is not working
      My Computer
    Quote Quote

  6. gregrocker
    Posts : 50,642
       New #24

    If the manual bcd edits won't do it, I would run HP Factory Recovery disks which should have been made at Setup or can be ordered from Tech Support, possibly for little cost if PC is new. This should restore everything as before. Recover Windows 7 Operating System Using HP Recovery - HP Klantenondersteuning (Nederland - Nederlands)

    You can try first running any full HD image backup but it may not restore the hotkeys.

    I've not seen resizing C cause this problem on HP, even after conversion to Logical to add more subpartitions. It's Recovery Partition is pretty resilient and normally survives even after doing a clean reinstall to C.

    Check also your ESC menu at boot to see what you find.
      My Computer
    Quote Quote

  7. 5ggggg
    Posts : 43
    win7_home_64
    Thread Starter
       New #25

    I burned those disks of course, but boyans got to 90% alreaedy ... so still hoping for the last kick ;-)
      My Computer
    Quote Quote

  8. 5ggggg
    Posts : 43
    win7_home_64
    Thread Starter
       New #26

    gregrocker said:
    ...I've not seen resizing C cause this problem on HP, even after conversion to Logical to add more subpartitions.
    Maybe it was the fact, that I had to move the recovery partition after shrínking C.

    How could I achieve my wished structure from within w7 ?? .. structure see post #17
      My Computer
    Quote Quote

  10. gregrocker
    Posts : 50,642
       New #27

    What we've helped do in the past which seems to work fine is convert C to logical, shrink it and use that space to add any other needed Logical sub-partitions.

    This doesn't move the Recovery partition which can be problematic as we're seeing in two other threads here today.

    I'd consider backing up, run Factory Recovery disks to set it back to factory condition, then do the above using Disk Mgmt or if necessary free Partition Wizard bootable CD, then set it up once you know it works.

    Save a Win7 backup image so you have path back.
    Last edited by gregrocker; 10 Dec 2011 at 11:35.
      My Computer
    Quote Quote

  11. boyans
    Posts : 240
    Win 8 RP, Win 7, XP
       New #28

    5ggggg said:
    I burned those disks of course, but boyans got to 90% alreaedy ... so still hoping for the last kick ;-)
    1. Create Custom Bootstrap Action - give it "Recovery loader" and say F10 as parameters. (two selections and confirm.). The tool implements over 100 key codes but not F11 and F12 .

    2. Edit "customactions" element in {bootmgr} - replace the value(F10) with the value(F11) you should have written down on paper (see begin of thread).

    You can delete the id of recovery loader from boot menu (bootmgr->DisplayOrder element) so it will not be visible. This would give the final touch to the exercise.
      My Computer
    Quote Quote

  12. 5ggggg
    Posts : 43
    win7_home_64
    Thread Starter
       New #29

    THX to both of you ...
    0. but Partition magic has gparted built into it. Does it have any further advantage over it (most time it will have anolder version of gp)

    1 is done

    2. I restored C:\boot undera folder c:\acronis. Now I am not allowed do delete this folder, because it has elements like bootmgr within it ... What to do ??

    3. boyans
    a) I tried custom action. F11 does not work in Biossetup , but works on the boot menue. Then I deleted the OEM custom type action from bootloader, so just custom action is left. Now F11 is not even working in bootmenue. reagentc /disable /enable brings back OEM_custom type.
    Maybe the following reagentc options regarding image and bootkey might help...your suggestion, how should it be used ? which code ? 0x1000085000001 0x5400000f ?
    Code:
    REAGENTC.EXE [Optionen]
  Folgende Optionen können angegeben werden:
  /setreimage /path  <Verzeichnisname> [/target <Verzeichnisname>]
  [/bootkey <Abfragecode>]
             Legt den Speicherort des vom Benutzer bereitgestellten
             Windows RE-Abbilds fest.
             Die optionale Option "/target" gibt den Pfad des Speicherorts
             der Windows-Installation an.
             Die optionale Option "/bootkey" gibt den Abfragecode für
             eine OEM-spezifische Starttaste an.
  /setosimage [/path <Verzeichnisname> [/target <Verzeichnisname>]]
  [/customtool]
             "/path" legt den Speicherort der vom Benutzer bereitgestellten
             Setupdateien für das Betriebssystem fest.
             Alternativ gibt "/customtool" an, dass in Windows RE ein Abbild-
             tool angegeben wurde.
    b)
    5ggggg said:
    ... maybe it has something to do with the different ramdisks. look at the ramdisk from hp (first on the left, I left it in the store but it is not used). I looked on a backup I made from the new PC and also there it says unknown device Data = byte[72]. maybe we should copy the old id to a new id and use this ???
    Can you please explain this unknow device data .. is it a hp special ?
    Last edited by 5ggggg; 10 Dec 2011 at 12:50.
      My Computer
    Quote Quote

  13. 5ggggg
    Posts : 43
    win7_home_64
    Thread Starter
       New #30

    are you guys with your families today I am just about restoring waiting for final comands
      My Computer
    Quote Quote

 
Page 3 of 4 FirstFirst 1234 LastLast

  Related Discussions
I'm running Windows 7 Ultimate SP1 64-bit and looking for suggestions for a program that can manage partitions and resize them without data loss. Similar to Partition Magic from years ago. Thanks
Resizing Disk Partitions
in Hardware & Devices

Trying to help a friend resize the partitions on the hard disk drive on his laptop running Windows Vista.When I did the same on my laptop I used "Easus" which performed great but when we tried to download the same program again for his computer we received the message that it was...
To anyone who might know a solution to this quandary: As a fresh user of Windows 7 Home Premium 64-bit that came installed with my new desktop computer, I am now and then confronted with issues I never encountered before. I have been relatively proficient in using XP for years on my older...
Hi i am in a deadlock I shrunk my boot partition and extended my data partition with gparted. Then at boot time windows started checkdisk and repaired a lot of errors (ie all the errors it found). So far so good. The problem now is that I can only reach one internet site namely my internet...
My laptop's disk is divided into two partitions. One for the usual office stuff etc, and the other for digital audio. Both selected at boot via Boot Magic. However, when I set it it up, I should have made the music partition much bigger than the office, as some drum sample libraries are pretty...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 12:58.
Find Us