MDT WSUS Windows 10 Updates Failing 0x8024401C

Had an issue with MDT failing to install Windows 10 via WSUS. I kept getting the 0x8024401C error.

I upgraded my WSUS on the Windows Server 2012R2 to version 4.0. Then upgraded the host to Windows Server 2016. Still receiving the same error.

After some more googling and trial and error I made the following changes to the IIS server for the WSUS  Application Pool:

  • Queue Length: From 10000 to 25000
  • Limit Interval (minutes): From 5 to 15
  • “Service Unavailable” Response: From HttpLevel to TcpLevel
  • Private Memory Limit (KB): From 18342456 to 0

Build is now receiving updates from the WSUS server.

Advertisements

MDT 2013 – Windows 10 – KB2267602 Freeze during build

Had this issue during the building of a Windows 10 reference image using build 1607.

During the Windows Update Pre-Application Installation the build would stop and progress no further. The update was the Definition Update for Windows Defender – KB2267602 (Definition 1.63…)

Capture2

Looking at the ZTIWIndowsUpdate.log the download did not start and the progress was at 0%.

I have included the update KB######### to allow the Windows 10 1607 build to communicate with the local WSUS server.

I have added the Definition Update to the exclusion list in the customsettings.ini property using WUMU_ExcludeKB as shown below:

WUMU_ExcludeKB001=2267602

After kicking off a new reference build the task sequence continued on with no issues.

Adding Internet Explorer 11 to your Windows 7 SP1 reference image

Here is an article from Johan Arwidmark regarding adding IE11 to your reference image.

Don’t forget to update the unattend.xml.

Also here are the KB Articles not to deploy to the WIndows 7 reference image:

WUMU_ExcludeKB01=976002
WUMU_ExcludeKB02=2267621
WUMU_ExcludeKB03=2434419
WUMU_ExcludeKB04=2506143
WUMU_ExcludeKB05=2533552
WUMU_ExcludeKB06=2819745

If you get a DISM error, this is usually associated with the updates being added to the OS via offline servicing.

Check the DISM.log folder for the update that is affecting your build. X:\Windows\Logs\DISM.log