Quantcast
Channel: OS|DC
Viewing all articles
Browse latest Browse all 64

MDT 2013U1/U2: Failure (5627): Run DISM.exe

$
0
0

constrTETRIS_by_polaus_thumb9

If you've recently updated you deployment solution (MDT+ADK) you’ve probably noticed some regression in Hyper-V compared to the previous releases. One of them may occur if you try to deploy packages during your deployment. It will miserably fail with the following error:

FAILURE (5627): 14: Rum DISM.exe

Litetouch deployment failed, Return Code = – 2147467259 0x80004005

2016-02-13_19h44_12_thumb2

A deeper look in the BDD.log seams to point to a storage space limitation problem:

image_thumb4

but the message is misleading as the issue does not comes from the disk, but form the memory (thanks to Niall Brady for clarifying)

Ok, now we have a clue :  DISM is unable to apply the unattend.xml because of a memory limitation under Windows PE. Sounds familiar to you ? Yes it is, WinPE 5 introduced a similar kind of bug with Hyper-v Dynamic memory. If you don’t remember, Rens Hollenders perfectly described the case in this blog post.

So how to fix this: pretty simple… increasing the memory should be enough, but unfortunately without taking advantage of the Hyper-v’s dynamic memory: as my testing shows, memory request from DISM are not processed fast enough by Hyper-V and the process fail a few seconds after launching. So we will need to use an heavy amount of 2000 MB or RAM to make the process run flawlessly, Dynamic memory can be used again once the PE phase is finished.

the setting in Hyper-v should be set like this:

2016-02-15_13h36_05_thumb[2]

Now that RAM is set correctly, DISM will be able to do his mammoth works without failing:

2016-02-15_18h19_22_thumb[2]

Hope you’ll find this helpful. 


Viewing all articles
Browse latest Browse all 64

Trending Articles