Ugh…should have waited to try the CU before I ran my mouth.
https://support.microsoft.com/en-us/kb/3176934 So far, it seems like this fixed our issue. We captured a new WIM, and it did apply additional updates with this CU injected. We are putting it in the build now, if the Office 2016 updates apply from WSUS, then I think we are good to go. On Fri, Aug 26, 2016 at 10:37 AM, Jay Marsett <jmars...@gmail.com> wrote: > Seeing issues downloading/installing updates on 1607 builds pulling > updates from WSUS using the ztiwindowsupdate.wsf process with MDT (2013 > update 1 build 8298) integrated task sequences in SCCM CB (1606). Looks > and acts the same as this. > > https://social.technet.microsoft.com/Forums/en-US/9941646e-648d-49e2-97a4- > 088e5cc0d917/windows-10-1607-stuck-when-downloading- > updates-from-wsus-in-mdt-windows-update-task-sequence? > forum=win10itprosetup > > and > > https://community.spiceworks.com/topic/1749367-windows-10- > ver-1607-having-difficulty-with-getting-updates-from-wsus?page=1 > > Anyone know of a solution, is this something that MDT 2013 update 2 might > address? > > We are going the route of applying the latest CU as a command line and > hoping for the best. Seems that others have tried that and still see the > issue, but we aren't sure what else to try. > > Also, does this issue appear if the CU/additional updates are applied via > a SUP instead? > > Please and thank you. > > >
