win7 repair and recovery not accessible after resizing partitions

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
-------------------------------------------------------------------------------------------------------------------------

You must check that all paths in lines above exist.

Also check "\boot\boot.sdi" on [boot] device exists.

And all {GUID}'s as in my previous explanation point in right direction starting from "Recovery loader".

I am sorry but I can't see from here whats on your computer hard disk.:)

where should this be "=[boot]\sources\boot.wim". Does it mean on system partitions h:\sources... or c:\sources.

But there has never been a directory "sources" on the original PC... Wheired because this path also appears in the h:\boot\bcd (system) on the very first acronis backup I made...

Later on I made a dir c:\sources (for copying purposes), but it never had a boot.wim on it ....

You do not have to "delete drive letters" in BCD.
There are no drive letters in BCD !

In BCD there is only a "object" for a concrete device element (which is mapped to a drive letter eventually if there is a mapping in Windows NT object space for it).

It is a little more than complicated - if interested go to MSDN and search for "BCD objects".

===================

Have you checked the paths exist for loader for PE2 ?

[boot] is active partition.

thx, but is active = boot partition (would be system=H) or active = where \windows resides (c:)

I restored the acronis files once more - it also says "\sources\boot.wim" ... but originally there was only the win7 loader in the "display order":

Code:

C:\Users\Administrator>bcdedit /store C:\sources\acronis111209\Laufwerk(C)\Boot\bcd /enum all
Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=H:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
extendedinput           Yes
default                 {default}
resumeobject            {158181c0-9a00-11db-8a1d-b11d19fd3102}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30
customactions           0x1000085000001
                        0x5400000f
custom:5400000f         {9d8711c8-f4b3-11e0-bdd6-fe10d78c86f8}
Windows-Startladeprogramm
-------------------------
Bezeichner              {default}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {9d8711c8-f4b3-11e0-bdd6-fe10d78c86f8}
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              {9d8711c8-f4b3-11e0-bdd6-fe10d78c86f8}
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              {9d8711c9-f4b3-11e0-bdd6-fe10d78c86f8}
description             Ramdisk Options
ramdisksdidevice        unknown
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
Optionen zum RAM-Datenträgersetup
---------------------------------
Bezeichner              {ramdiskoptions}
description             Ramdisk Options
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi

can you explain your suggestion what to do now more in detail please .... THX very much
richard

PS:
- I still have no idea why the displayed boot manger entries look different to the system bcd store ...
- and the only boot.wim on the computer is in g:\FactotoryUpdate\ on hp recovery partition.
- and even beeing logged in as Administrator I cant access some recovery drectory in explorer (it can be accessed via CMD)

To be displayed in boot menu the id of the loader has to be in element "DisplayOrder" of bootmgr object.

This PE2 loader is activated only by keyboard shortcut - there is customactions element in bootmgr object for it.

Do you remember which partition was active when "all was functioning OK" ?


ON A SINGLE DISK THERE SHOULD BE ONLY ONE ACTIVE PARTITION !!
And usually is.
If you use Microsoft Software there is no way of marking 2 partitions as active at the same time on a single disk. It has no meaning.

Back to Problem.

You can scan your manifacturer DVD for .wim files.
If you can find some - post name and size.

The boot.wim - 257 MB listed in your previous post is non-standard so it must be OEM recovery or whatever OEM supa-dupa.
Usual recovery .wim is about 150-160 MB.

257 MB cannot be placed on 199 MB - size of your System(H:) partition. So OEM whatever was never placed on System(H:)

Have you ever started whatever software system back in time with F11 during boot ?
It seems that this is a leftover from OEM install just pointing to nowhere.

----------------------
You have a starting Windows 7 + access to recovery now. Do you need anything more at the moment ?
If no - just delete the loader entry for PE2 and corresponding device options.


!! C: partition is pretty full - this can very soon lead to problems !! Try to move unnecessary contents away.
It is good practice to have at least 10 GB free on Windows partition or say 20% free.

On next Windows update or if you install new software - aufpassen !

5ggggg said:

The PC is brand new ... I started with acronis backup and gparted then ... 3 days ago

C is full because of the acronis file restores sitting under path /sources ... I am about deleting it
Yes Bios F11 was woking ... I still think it could have something to do with this special unkanown device here:
https://www.sevenforums.com/1693485-post10.html

Using gparted or any disk editor is not without risks.
People say - always make backups before serious interventions.

Descriptions of device options seem to have precedence over descriptions of attached loaders. So you see in boot menu corresponding device options description.

1. What did F11 do - start normal Windows Recovery or OEM Recovery ?

2. List same BCD from quote with bcdedit and post output.