locked
Software Updates hand - W10 Task sequence with Bitlocker RRS feed

  • Question

  • 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 SU step


    Ian Burnell, London (UK)

    Friday, September 4, 2015 8:37 AM

All replies

  • 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.

    https://social.technet.microsoft.com/Forums/en-US/3855ce64-585e-4172-b008-1979f282fb36/windows-10-bac-hangs-at-install-software-updates

    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.


    Best regards, Simon

    Friday, September 4, 2015 9:13 AM
  • Not a solution for this root issue, but why not add the Office updates directly to your Office package/application by simply adding the MSPs to the Updates folder? Yes, this will be a little bit of initial work, but works very well and requires nothing more than dropping the MSPs into the Updates folder (and updating your DPs of course).

    Jason | http://blog.configmgrftw.com | @jasonsandys


    Friday, September 4, 2015 11:43 AM
  • 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 Burnell, London (UK)

    Friday, September 4, 2015 12:10 PM
  • @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.


    Best regards, Simon







    Friday, September 4, 2015 12:47 PM
  • Always open a bug with CSS if you have the opportunity to do so please. There is no way for Microsoft to know about and (hopefully) work on fixing it unless someone does.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, September 4, 2015 2:04 PM
  • I opened a case for this issue. If someone does the same and wants to exchange case numbers, feel free to contact me.

    Best regards, Simon


    Monday, September 7, 2015 6:44 AM
  • Let me know if you get a reply Simon - thanks


    Ian Burnell, London (UK)

    Thursday, September 10, 2015 2:39 PM
  • 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 Client.


    Best regards, Simon


    • Edited by Simon Dettling Friday, September 11, 2015 3:04 PM
    • Proposed as answer by Joyce L Monday, September 28, 2015 1:59 AM
    Friday, September 11, 2015 3:04 PM
  • I'm definitely experiencing this issue as well, in a build & capture sequence with no bitlocker. The hang always occurs on an Office 2010 update, but which one seems to vary between runs. This was an issue with Win10 RTM and with build 1511. I'm currently running 2012 R2 SP1 CU2 (what a mouthful!). I will try checking the services and restarting them as mentioned below.

    Wednesday, November 25, 2015 7:28 PM
  • Hi Simon,

    I was just wondering if you were ever able to get any resolution to your issue as I've started encountering the exact same symptoms with Office 2013 during the TS after upgrading to v1511. When the services enter that "Stopping" state I can't do anything in services.msc except kill ccmexec.exe, and that just crashes the TS completely.

    Regards,

    -Chris

    Friday, January 22, 2016 4:54 AM
  •  after upgrading to v1511.


    Please use the CM Current Branch forums next time. This one is for 2012 only.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, January 22, 2016 7:08 AM
  • I was just wondering if you were ever able to get any resolution to your issue

    Nope.

    We ran a PoC with Windows 10 and Office 2013 back in Q3 2015. When Office 2016 came out, we dropped Office 2013. With Office 2016 the Error actually never occured.


    Simon Dettling | msitproblog.com | @SimonDettling

    Friday, January 22, 2016 10:27 AM
  • Hey Everyone,

    Just thought I'd add to this thread as I am running into the same issue installing Office 2013 in Windows 10 during regular OSD builds. As others have noted doesn't seem related to a specific update. We also see it in scenarios with and without BitLocker so that isn't it either.

    No solution yet that we are aware of to this issue.

    John

    Wednesday, March 16, 2016 12:15 AM
  • Hi Simon,

    I was just wondering if you were ever able to get any resolution to your issue as I've started encountering the exact same symptoms with Office 2013 during the TS after upgrading to v1511. When the services enter that "Stopping" state I can't do anything in services.msc except kill ccmexec.exe, and that just crashes the TS completely.

    Regards,

    -Chris

    Hi,

    In the command prompt, get the PID for both services using the commands :

    sc queryex wuauserv

    sc queryex ccmexec

    Then kill both services using :

    taskkill /f /pid YOURPID

    You will then be able to start the services :

    net start wuauserv

    net start ccmexec

    The TS will continue as expected. We have the same problem using SCCM 2012 R2 CU1 and Windows 10 1511 Build and capture TS


    MVP Enterprise Mobility | MCSE | MCSA | MCTS | MCITP | Microsoft Certified Trainer


    Thursday, April 14, 2016 4:56 PM
  • Hi all,

    I had this issue as well (SCCM 2012 R2 SP1 CU3, Win10 1511, Office 2013 32bit). I've written a powershell script to automate Maxime's fix and it seems to be working OK. Download and instructions here if you want it: 

    https://20road.com/2016/05/22/windows-10-1511-software-update-work-around/

    I've got a call open with MS. Will let you know if I get anywhere. 

    Cheers,

    Mike



    • Edited by MikePohatu Tuesday, May 24, 2016 7:26 AM
    Tuesday, May 24, 2016 7:25 AM
  • I would just chime in and say, thanks for creating the script. I also made a call to microsoft 3 weeks ago. We closed the case because thay said they were working on a solution, which we have seen nothing of so far. They havent even said anything official.
    Wednesday, June 1, 2016 7:03 PM
  • Any solution to this?
    Friday, June 3, 2016 9:54 AM
  • Have sent a few sets of logs off, but nothing yet. 
    Tuesday, June 28, 2016 9:08 AM
  • Hey Everyone,

    Just thought I'd add to this thread as I am running into the same issue installing Office 2013 in Windows 10 during regular OSD builds. As others have noted doesn't seem related to a specific update. We also see it in scenarios with and without BitLocker so that isn't it either.

    No solution yet that we are aware of to this issue.

    John


    We were having an issue installing Office 2013 with Updates - but our fiks was to stop the printspooler (strange enough) and install O2013 afterwards - now it works like charm

    Maybe that will work for your updateerror as well?

    Tuesday, July 12, 2016 9:12 AM
  • There was a recent hotfix, that fixed things related to this. Not sure what it was called though.
    Wednesday, August 24, 2016 8:31 AM
  • This is the hotfix: https://support.microsoft.com/en-us/kb/3174008

    We're moving to 1606 soon anyway so we'll probably just skip this and go straight to the new version. 

    Wednesday, September 7, 2016 9:16 PM