Following on from an earlier post on using WDS (PS: There’s a good initial guide here on setting up WDS, it should all pretty straight forward really), I encountered a few issues when capturing images. I spent a while setting up a clean build, sysprepped it but then kept getting an error when selecting my capture image from the boot PXE boot screen.:
- Windows failed to start. A recent hardware or software change might be the cause.
- File: \Windows\System32\boot\winload.exe
- Status: 0xc000000f
I then moved onto another recommendation which was to mount and then unmount the boot image. The idea being here that you have a boot image that gives you the error above in WDS already. If you right click on it and go to properties it will who you the file name (.wim) for that image.
You then need to locate that image and mount and then unmount it and it will automagically start to work – trust me.
First you just need to create a local directory to mount it in, i.e. “c:\temp”
Next, open PowerShell and then to mount it run:
dism /mount-wim /wimfile:"d:\remoteinstall\boot\x64\images\YOURWIMNAME.wim" /index:1 /mountdir:"c:\temp"
This won’t take too long and should read “The operation completed successfully”
And then to unmount it run:
dism /unmount-wim /mountdir:"c:\temp" /commit
Once you have done this, boot via your updated capture WIM and everything should be fine.
As far as I’m aware this is still an ongoing issue with WDS on Server 2012 R2 and so after this I’ll probably move on to try MDT 2013 or more likely, SCCM.