Deployment error on Apply Driver Package (DISM) step

Recently deployment went wrong on a few system types, part of a lot different system types. At every deployment it went wrong on the Apply Driver Package step. At earlier deployments all went fine, but now it stops working. Both were heavy HP workstations with 16GB and 32GB memory onboard. A lot of errors in SMSTS.log and DISM.log were seen.

SMSTS.log
-Dism failed with return code -2147467259
-Failed to add driver to driver store. Code 0x80004005
-Failed to provision driver. Code 0x80004005
-Exiting with return code 0x80004005
-Failed to find a matching version

DISM.log
Failed to find a matching version for servicing stack: E:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
Failed to open the registry root: n/a, key: Microsoft\Windows NT\CurrentVersion\ProfileList. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
Failed to query for path to user profiles directory. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
Failed to load the default user profile registry hive. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
Failed to load offline store from boot directory: '\\?\E:\' and windows directory: '\\?\E:\Windows\' [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
Failed to initialize store parameters with boot drive: E:\ and windows directory: E:\Windows [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

After some digging I found the following solution:
Deployment failures with Precision systems
Win2008R2/Win7: STOP 0xF4 during Task Sequence / OS Deployment
Corrupt Segoe UI font and .NET framework after OSD with 2012 R2 CU1

It mentions:
The issue in this case occurs because WinPE tries to compact the offline registry and fails to commit the registry hives back to disk. This problem only happen when you deploy Windows 7 and use WinPE 5.x 32-bit to deploy the image. Resolution is to set this registry value in the boot.wim using DISM or using a 64-bit boot image.

In my case I changed to use the 64-bit boot image, because of Windows 7 x64 deployment. Otherwise you need to edit the 32-bit boot image with the regkey. Very easy solution and no errors seen anymore :-)

No IP-address set during MDT Sysprep and Capture

Last week I created a Windows 7 SP1 image manually, installed almost 200 updates in it (!) and started the MDT 2013 default task sequence "Sysprep and Capture". The first part went fine (Sysprep), but when in Windows PE there was no IP-address set. Oops! Lucky me you can start a command prompt and start "Retry" later. Let's have a look how to enter a static IP-address within Windows PE.

 
Just start Command Prompt with F8 and type in the following command: "Netsh interface ip show config" > which is showing that my interface is called "Ethernet0"

After that type in the command: "Netsh interface ipv4 set address “Ethernet0” static <IP address> <Subnet mask <Gateway>" 

After that it was possible to capture Windows 7 SP1 successfully!

This simply made my day! ;)

BSOD in VMware 4.1 when booting with WinPE 4.0 images

Last month I did a new ConfigMgr 2012 SP1 installation. When using ConfigMgr boot or capture images on VMware 4.1 a blue screen of death (BSOD) was showed. Because I created the boot images manually, I wasn't sure if it was the WinPE 4.0 boot images or VMware. It turned out it was VMware 4.1 after all. Just use the solution below to make it all functional again.

Shutdown the VM first and copy this BIOS file in it: http://communities.vmware.com/servlet/JiveServlet/download/2139717-98102/bios.440.rom

Then edit the VMware configuration (vmx) file and add the following lines in here:
bios440.filename = "bios.440.rom"
mce.enable = "TRUE"
cpuid.hypervisor.v0 = "FALSE"
vmGenCounter.enable = "FALSE"

That's all needed. WinPE 4.0 (which is Windows 8) will work in a older VMware environment from now on also!

Thanks to Roel Janssens (@roeljanssens) for helping me out!