Have setup new TS for Windows 10 Enterprise under R2 SP1 CU1. I apply the Software Updates step after installing apps so that it picks up all the updates including Office 2013. On laptops I am enabling Bitlocker. I'm finding the SU step finds about 57 patches, downloads then starts applying and then stops at particular office updates - nothing showing in SMSTS.log other than "Waiting for RefreshUpdates complete notification from Updates Deployment Agent". Strangely a desktop (non bitlocker) works just fine i.e. applies all the patches without fail. So I've had to move the apply SU step higher up so it only applies O/S updates and that is ok. I tried taking specific update it was failing out of the SU group but it hangs at a different Office update, but as I say never a problem with the desktop - same build just no bitlocker. I also tried moving the bitlocker step below the software updates to no avail. The TS never times out - i.e. still sitting there over night hanging at the S
I have similiar issues with my Build and Capture Task-Sequence for Windows 10. The TS just hangs at random Office 2013 Updates with the mentioned message "Waiting for RefreshUpdates complete notification from Updates Deployment Agent" in smsts.log. But i don't use any Bitlocker in my Build and Capture Task-Sequence.
My current Workaround is to Install Office 2013 after the Software Updates step and to deliver the Office 2013 Updates after OSD. Fun part is, that my nearly identical Windows 8.1 Task-Sequence runs without any Problem through the Software Updates step.
Fair point Jason. I was just checking the updatesdeployment.log for both satalled builds and see this
Update (Site_CA9304BF-02E5-43BD-92B6-5143FB41637B/SUM_d3f1b5d8-fbee-4206-863c-88490a070645) Progress: Status = ciStateInstalling, PercentComplete = 0, DownloadSize = 12025, Result = 0x0 UpdatesDeploymentAgent 03/09/2015 16:17:25 4364 (0x110C)
Update (Site_CA9304BF-02E5-43BD-92B6-5143FB41637B/SUM_d3f1b5d8-fbee-4206-863c-88490a070645) Progress: Status = ciStateInstalling, PercentComplete = 10, DownloadSize = 12025, Result = 0x0 UpdatesDeploymentAgent 03/09/2015 16:17:28 3716 (0x0E84)
Update (Site_CA9304BF-02E5-43BD-92B6-5143FB41637B/SUM_d3f1b5d8-fbee-4206-863c-88490a070645) Progress: Status = ciStateInstalling, PercentComplete = 15, DownloadSize = 12025, Result = 0x0 UpdatesDeploymentAgent 03/09/2015 16:17:28 2588 (0x0A1C)
and
Update (Site_CA9304BF-02E5-43BD-92B6-5143FB41637B/SUM_c1eb71e4-9e75-49fa-8631-95d6939974a7) Progress: Status = ciStateVerifying, PercentComplete = 0, DownloadSize = 92524, Result = 0x0 UpdatesDeploymentAgent 03/09/2015 14:47:03 4104 (0x1008)
Update (Site_CA9304BF-02E5-43BD-92B6-5143FB41637B/SUM_cd61d581-0a11-48e4-a2d0-4a3f9743cd17) Progress: Status = ciStateInstalling, PercentComplete = 20, DownloadSize = 3406, Result = 0x0 UpdatesDeploymentAgent 03/09/2015 14:47:04 892 (0x037C)
Update (Site_CA9304BF-02E5-43BD-92B6-5143FB41637B/SUM_cd61d581-0a11-48e4-a2d0-4a3f9743cd17) Progress: Status = ciStateInstalling, PercentComplete = 43, DownloadSize = 3406, Result = 0x0 UpdatesDeploymentAgent 03/09/2015 14:47:04 4968 (0x1368)
Update (Site_CA9304BF-02E5-43BD-92B6-5143FB41637B/SUM_cd61d581-0a11-48e4-a2d0-4a3f9743cd17) Progress: Status = ciStateInstalling, PercentComplete = 50, DownloadSize = 3406, Result = 0x0 UpdatesDeploymentAgent 03/09/2015 14:47:04 2564 (0x0A04)
in other words they were part way through downloading 15 and 50% complete respectively implying it was trying to download content for the specific patch ??
@Simon - most interesting that yours is exactly the same problem
@Ian, My UpdatesDeployment.log file looks exactly the same..
@Jason, that could work as a Workaround. I'll give it a try. Should be not a big deal using this script: http://supportishere.com/how-to-download-microsoft-office-2013-updates-the-easy-way/
I'm not sure if i should open a case to get the root issue, from my Point of view this a Office or Windows 10 Bug.
Let me know if you get a reply Simon - thanks
It looks like the Windows Update Agent and the ConfigMgr Client are both crashing during the Installation of Software Updates. The Crash is probablly triggered by some Office 2013 Update.
Try to open Services.msc when you encounter the Hang and Check the State of "Windows Update" and "SMS Agent Host" Service. They should be both in "Stopping" State.
One you restart those two Services the Task-Sequence should actually continue by itself.
The Case is still open, and i don't have any final Informations yet. It actually looks like a bug in Windows Update Agent or in the ConfigMgr C