Windows 7: Recovery Partition - Create

it doesnt matter what you name it, the actual bootloader entry will still read the same, mine is called recovery, it still reads as NST winPE image in bootloader, sorry if i came across as touchy, i didnt mean to lol and yes i see what you mean now, i will change it

whs- system image is good admittedly, but what happens if you havent disabled automatic backups and when it does its backup whatever is wrong is backed up too?

It's also not impossible the backup image is corrupted.

The naming works ok for me:

D:\windows\system32>bcdedit /enum /v

Windows Boot Loader
-------------------
identifier {c41cd56f-296a-11df-8efe-001966657855}
device ramdisk=[D:]\BOOT.WIM,{c41cd56e-296a-11df-8efe-001966657
855}
path \Windows\System32\Boot\winload.exe
description Rename here before click Add
locale en-US
osdevice ramdisk=[D:]\BOOT.WIM,{c41cd56e-296a-11df-8efe-001966657
855}
systemroot \Windows
detecthal Yes
winpe Yes



D:\windows\system32>

We sometimes provide our customers with tailor made and assembled computers, too, although we are absolutely not a PC vendor. Each customer has own needs, different 'bloatware'.

I am really interested to find out if this approach would allow us to create a standard recovery partition. Removing ei.cfg would make it universal; some customers are happy with Professional, even HP, when most want / need Ultimate, so the customers key would decide the version.

IMO this could be something really good!

Kari

sorry should have been clearer there, when you reboot, your name will not appear on the dual boot menu, every entry points to it having the right name, but at the OS selection screen there is no change

Well, I would make a one time image and delete the xml definition file. Thus I am sure it will not be repeated and accidently write over the original.

Ther's something wrong then.

The last entry on my boot menu reads:

Rename Here before click add

I have done it hundreds of times - may be a glitch in the version of Easy you are using.

Try d/l ing build 82.

EasyBCD 2.0 Beta Builds - The NeoSmart Forums

Hi Kari,

If you are interested in that kind of thing , it is pretty easy to add extra functions and apps. to the boot.wim , to access extra recovery tools - such as the free versions of Paragon PM and Backup and recover , Partition Wizard, Nir Sofer's free apps, like Produkey , password blanker, there are lots of nice open source apps. and so on.

It's a lot easier than it appears.

For example, if you are on Win 7 , this little app. will add some in automatically for you ( Paragon Pm 2010 Free and Backup and Recovery 10 free as long as you have them installed ).

pe - Windows Live

If it's for customers , obviously need to check the licenses allow it.

Hi all,

First up, thanks for this great tutorial. The instructions are very clear and concise and I was able to follow them without any problems whatsoever!

I've been having issues with my Recovery Partition, and was wondering if you could help.

I have a 120GB Backup Disk. On this I created a 4GB Recovery Partition (Z:\) with the Windows 7 Pro 64-Bit DVD contents on it, and on the same disk I also created a second partition (G:\) with my System Image on it, plus an export of my Registry.

I have used EasyBCD to create a boot menu, and as long as my Primary Boot Disk is functioning, I am able to select the Recovery Partition from the boot menu and load it.

All OK so far!

However, I my Primary Boot Disk recently failed. Now when I try to boot the Recovery Partition, I get told that the disk is not bootable. I have changed the boot disk priorities in the BIOS so that the disk that the Recovery Partition is on is the primary boot device, but it still isn't bootable.

I understand that the boot menu was on the failed disk, but I would have thought that the Recovery Partition would be bootable, seeing as the Windows 7 DVD is.

Can anyone tell me what I'm doing wrong?

Did you try marking the recovery partition Active?

Hmmm... I have a feeling you may be on to something there..

I'll see if I can get my dead HDD (it occasionally still works for random periods of time!) to work for long enough for me to check.

I'll post back here with the results.