Estimated reading time: 1 minutes
So today we built a new custom Windows 10 image on a virtual machine and created our new SCCM capture media from the very latest version and every single time we ran the capture it failed at the Sysprep step.
Infuriated by this as we have done captures hundreds of times, we started the annoying method of going through the log files. As the capture was failing at the sysprep part we knew to take a look at the sysprep error logs first which can be found in this location on your machine:
C:WindowsSystem32SysprepPanther
You should see a file called something like setuperr.log – look in here and you should find the reason for the system prep failure.
Amazingly, in our case, it was the pre-installed Twitter and Candy Crush Windows Store Apps that were causing the problem. So, we uninstalled these and tried again – there you go, capture went through without any issues and worked perfectly.
Feedback
If you have any questions or comments, please feel free to leave us a message below using our comments system below.
Share this content:
