Is there a size limit for a Wim image file (windows XP)in SCCM. We have a Monolithic Engineering image that is just over 30gb's. The image captures fine. We are using unicast and doing a bare metal pxe boot to re-image the target pc. After the image completes Windows XP comes up with " "Windows could not start because the following file is missing or corrupt: <windows Root>\system32.hal.dll." among other errors. we have been able to create and deploy images as large as 25 gb's in the past on the same hardware.

I don't think, this error is something to with size of the file. The same image is working for someother machines?Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

"Windows could not start because the following file is missing or corrupt: <windows Root>\system32.hal.dll." It seems as if you're running into a HAL issue (uniproc vs multiproc). Any chance that the PC where you captured the image is of another HAL type than the one you're now trying to deploy to?Torsten Meringer | http://www.mssccmfaq.de

The Capture PC and the Target PC are identical hardware.