jaclaz, on 22 October 2012 - 09:59 AM, said:
Tripredacus, on 22 October 2012 - 09:11 AM, said:
You only need to use BCDBoot.exe if your HDD has more than one partition. If it is a single OS partition, you don't need it.
And the files that are missing in the "source" will appear, materializing from thin air?
Well lets put it this way. I can do an install with a System Reserved partition (where the boot files are located), then capture just the OS partition, redploy it as single partition and it will boot. Have there been any documented cases of where NOT using BCDBoot.exe on a single partition disk causes Windows not to boot? From my experiences, BCDBoot.exe is only needed when you have multiple partitions with bootable OSes.
@OP, you don't mention what made this image. Is it Imagex, DISM or something else? You also don't mention what OS the image is of, and if you are deploying to MBR or GPT disks.
There are some conflicting documentation as to how to run BCDBoot.exe. Some may say run it from the WinPE ramdisk (x:\windows\system32\bcdboot.exe) but I have seen other documentation saying to run it from the deployed OS path (e:\windows\system32\bcdboot.exe) which I've never gotten to work. You could alternatively copy it from the deployed OS to the ramdisk... or just keep it in your WinPE image.
I've also run into problems with the C: being take up already when booting into PE for imaging (except Windows 8) which I solve by using a diskpart script. It basically takes whatever is assigned to C: and changes it to something else that isn't taken. This way there is no problem with your deployed OS being installed to a partition assigned with C:\.