Restoring HP Recovery Boot Info


Thx for the awesome software.

I am trying to restore a boot entry for the HP Recovery partition on a niotebook on which a new version of Win7 was installed without deleting the Recovery partition. However, I did create both C: and D: volumes on the space that was previously only C:, so the Recovery partition is no longer on D:, but E:.

I created a new WinPE boot record pointing to E:\system.sav\FactoryUpdate\boot.wim (only other *.wim record on partition is called base.wim and that seems to be for creating a RAM disk). I have tried checking and unchecking the force portable (no good) and EMS enabled options, and the best I get is a boot into the PE environ with a cmd window showing an error "upDrvLtr: unKnown," and then a second cmd windows giving me a command prompt on "X:\Windows\system32".

My best and ignorant guess is that somehow I need to edit a configuration file on the recovery partition telling it to look at E: and not D:, but I may also not be using EasyBCD correctly.

Any and all help appreciated.


Mostly Harmless
Staff member
Hi Hlafordlaes, welcome to NST.

Please post the contents of EasyBCD's "Detailed Mode" here.
Hi Hlafordlaes, welcome to NST.
Please post the contents of EasyBCD's "Detailed Mode" here.
Thx; here it is:

Windows Boot Manager
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {da04765f-b407-11df-9acd-b4c83173373c}
resumeobject {da04765e-b407-11df-9acd-b4c83173373c}
displayorder {da04765f-b407-11df-9acd-b4c83173373c}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes
Windows Boot Loader
identifier {da04765f-b407-11df-9acd-b4c83173373c}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {da047660-b407-11df-9acd-b4c83173373c}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {da04765e-b407-11df-9acd-b4c83173373c}
nx OptIn
Windows Boot Loader
identifier {da047670-b407-11df-9acd-b4c83173373c}
device ramdisk=[E:]\system.sav\FactoryUpdate\boot.wim,{da04766f-b407-11df-9acd-b4c83173373c}
path \Windows\System32\Boot\winload.exe
description NST WinPE Image
locale en-US
osdevice ramdisk=[E:]\system.sav\FactoryUpdate\boot.wim,{da04766f-b407-11df-9acd-b4c83173373c}
systemroot \Windows
detecthal Yes
winpe Yes
ems Yes


Super Moderator
Staff member
Browse the contents of the recovery partition. If there is a .wim you can add a new .wim entry to boot from it.


New Member
Can you point me at how to boot from a wim from a non-booting installation (ie command line from recovery CD) please.

Current situation is that I applied the large windows WIM to C: (/dev/sda1) using imagex, it boots into vista but the partition with OS is allocated the letter D: for some reason hence none of the apps and most of the system functions don't work 'cos they're coded to look at C:\blahblah but the relevant file is actually at D:\blahblah


Knows where his towel is.
Staff member


New Member
Unfortunately the vista boots into a dysfunctional form and regedit won't run. Notepad does, but little else !

I did actually manage to make progress with a WinPE boot CD that had a remote registry editing tool, and deleted the registry items that were messing up the drive letters.

It now boots into a much more workable form, the only current problem being the "can't load user profile" nonsense which I've fixed on other systems previously.