Problem:

I am trying to build a machine. It gets as far as installing security updates but then fails with the following error:

Task Sequence Error
Task Sequence: <name> has failed with the error code (0×00000004). For more information, please contact your system administrator or helpdesk operator.

If I look in the smsts.log it shows the following lines:

Create Package Item : Package_for_KB2620704
About to run command: expand "\\<server_name>\smspkgf$\SMSPKG\<package_ID>72eb957-6c3a-410b-8dce-1c8ced7712e0\windows6.1-kb2563894-x64.cab" -F:update.mum "E:\_SMSTaskSequence\ZTIPatches.tmp"
Return code from command = 0
Create Package Item : Package_for_KB2563894
About to run command: expand "\\<server_name>\smspkgf$\SMSPKG\<package_ID>7969b60-d3de-4c88-bd0c-fcdaab354601\windows6.1-kb2559049-x64.cab" -F:update.mum "E:\_SMSTaskSequence\ZTIPatches.tmp"
ZTI Heartbeat: command has been running for 6 minutes (process ID 1500)
ZTI Heartbeat: command has been running for 12 minutes (process ID 1500)
ZTI Heartbeat: command has been running for 18 minutes (process ID 1500)
...

It’s like it’s hanging on a particular update.

Resolution:

After having checked everything was okay from the package/ update side it turns out the ConfigMgr servers are Hyper-V VMs. Although the NIC was set correctly on the ConfigMgr server, on the actual Hyper-V host the physical NIC was set to “AUTO” rather than 100 MB/ Full. Changing the NIC speed and rebuilding the machine resolved the issue.