Saturday, August 8, 2015

BOOTMGR is missing. How to replace Windows 7 embedded boot files after applying image in WinPE



I have just applied an image of a Windows 7 Embedded system to a HDD using Imagex inside WinPE. I captured the image of the system on the same board and the same drive and cleaned the drive before applying the image so it's the same system I am applying to. Windows is x64 and WinPE and imagex are amd64. This is from Windows Automated Instillation Kit version 2.0.0.0.



I am trying to place the image on a partitioned data drive which was set as active.

After applying the image I know the boot files are not applied as I get the message "BOOTMGR is missing" after rebooting. In WinPE I tried



D:\Windows\System32>bcdboot d:\windows /s c:


The error I get when I try and load the boot files this way is:



BFSVC: Failed to create a new system store. Status = [c000003a]



Additional info: If I look into Windows\Boot\EFI It contains bootmgr.efi and a few other efi files.



Many thanks for reading


Answer



I just discovered after painstakingly researching and pulling hair for a day.
I was booting amd64 WinPE from a USB 3.0. This was not allowing me to copy the boot files. AS I said in my question, the command



bcdboot d:\windows /s c:



Would return



BFSVC: Failed to create a new system store. Status = [c000003a]


I then just burned the WinPE to a disk and rebooted and it was allowed the creation of the boot files. I think it was just the USB 3.0 which was the problem. Even though the port I used was USB 2.0 the USB stick was using was 3.0. Well at least the problem has been narrowed down. No more tears.


No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...