Hi,

I am deploying a VHD on a SD card to boot a WIndows 2012 R2 server. I followed this procedure: http://technet.microsoft.com/en-us/library/ee731893(WS.10).aspx

When I boot my VHD I get an error "\Windows\system32\winload.exe" Status 0xc000000e. When I then boot on the repair I notice that the bcdboot command created a second entry in the boot manager with my correct values. But there is also a {default} profile without a partition value in the osdevice parameter. As the {default} profile is assigned to boot per default, it generates this error.

I can resolve this by removing the default entry in the repair on the booted VHD with BCDEDIT. But I would like do prevent this or correct it in my VHD file before it is started. I don't see any way to do so. 

Thank you for your help!

Note: for some reason this behavior changed because I already deployed a server like this about a year ago with exactly the same procedure and then I didn't had the error. The only difference I can think of is the version of Assessment and Deployment Kit I now use (Windows 8.1).

Hi,

I would like to know the reason why "{default}" was created in the first place.

As the BCD was created manually by the command lines you input, a quick solution is to add one more command to set the default boot entry:

bcdedit /default {xxxxxxxxx-xxxx-xxx-xxxx-xxxxxxxxxxxxx}

Hi,

I fully agree, but this is the exact point. I followed the procedure from Technet (link in original post) and this worked about a year ago for the exact same hardware and configuration. The default profile is clearly created by executing one of the following command from the TechNet procedure:

select disk <UFD disk number> 
clean 
create partition primary 
select partition 1 
active 
format quick fs=ntfs 
assign letter=z 
exit
bootsect /nt60 <UFD partition letter> /force /mbr
bcdboot <VHD Partition Letter>\windows /s <UFD Partition Letter>

The question is which one? And how to correct it before the VHD is loaded on the server?

To me it looks like a bug in the Assessment and Deployment Kit for Windows 8.1, the default profile is also named "Windows 8.1", which the OS is "Windows 2012 Server R2".

Thanks

Hi,

Sorry for the delay in reply.

Please run a "bcdedit" after Diskpart to see if there is any entry already existing before the last 2 command lines. I'm thinking if it is the boot information comes from the host system which you are creating the VHD.

If nothing, run bcdedit again after bootsect command.

Ok, but how to target the VHD image with BCDEDIT? I want to do it before I have to start the VHD to allow it to start unattended without intervention. I don't find a method to execute BCDEDIT in that way.

Hi,

I fully agree, but this is the exact point. I followed the procedure from Technet (link in original post) and this worked about a year ago for the exact same hardware and configuration. The default profile is clearly created by executing one of the following command from the TechNet procedure:

select disk <UFD disk number> 
clean 
create partition primary 
select partition 1 
active 
format quick fs=ntfs 
assign letter=z 
exit
bootsect /nt60 <UFD partition letter> /force /mbr
bcdboot <VHD Partition Letter>\windows /s <UFD Partition Letter>

The question is which one? And how to correct it before the VHD is loaded on the server?

To me it looks like a bug in the Assessment and Deployment Kit for Windows 8.1, the default profile is also named "Windows 8.1", which the OS is "Windows 2012 Server R2".

Thanks

Still looking for a solution on this one. Why did it work before with same procedure from Technet? It sounds like a bug in the tools... it is really annoying that I have to first boot the VHD to change the loader configuration with BCDEDIT. I am looking for a way to have this correct before the first boot of the VHD.

Thank you