Windows Server 2012 R2 Boot.wim doesn't load during Boot

I am not sure if this happens under all circumstances but I wasn't able to use the boot.wim file from a Server 2012 R2 setup media. In my WDS server, I added a boot.wim file from the Server 2012 R2 setup ISO as a new Boot Image. I used a vm to boot into the PXE server and try the new boot image but I got the following error;

File: \Windows\System32\winload.exe
Status : 0xc000000f
Info: The selected entry could not be loaded because the application is missing or corrupt.

This is the result I was getting from an untouched boot.wim. I never tried to create a seperate WinPE media to see if that would work but I found this on a Spiceworks forum thread. (btw, the SpiceWorks community is awesome!).

 http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing

A forum member called John Masson sent this solution below and it's pretty solid. I've tested this solution in my lab.

It will sound stupid and non-sense but this is actually working :)

Basically, you have to mount the boot wim file and unmount it while using the "commit" switch even if we are not making any changes. I am just pasting the solution here;

Mount the WIM file with the command
dism /mount-wim /wimfile: /mountdir: /index:1

Unmount the WIM file, committing changes (even though you didn't make any) with the command
dism /unmount-wim /mountdir: /commit


The only thing I can add to that the WIM you need to modify is normally located under the default WDS folder ".\RemoteInstall\Boot\x64\Images\boot.wim".

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more