[mdt] WSUS updates detected, but errors out on download?

[pete]

So I'm faffing around with MDT (clearing a few things from my list of "things you really should have implemented") and I've hit a snag.

 

I've a basic task sequence entry to install Win 10 1607 then detect and install updates from WSUS after Office 2013 gets installed (and then sysprep/capture). The WSUS check happens in the "State Restore" phase and after applications have been installed and the computer has rebooted once.

 

I've imported the WSUS SSL cert earlier in the task sequence so it doesn't choke on the internal CA. Looking in ZTIWindowsUpdate.log it correctly detects 55 updates pending (mostly Office 2013, a few C++).

 

As soon as it starts the "Begin Downloading" part I get an:

 

ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate:  (-2145091577  0x80248007)

 

for which the Internet has varied theories depending on what you're actually doing. A few threads mention Windows Defender or other particular patches being problematic, but I'd expect it to at least download them and then choke rather than just erroring out as soon as it begins.

 

Any ideas? I've seen mentions of rebooting it too many times breaking the task sequence, but I've only got one reboot beforehand:

 

Edited August 5, 2016 by pete

[pete]

Gah, ignore me - latest build attempt detected and pulled updates (no, I didn't change anything related to WSUS in-between).