none
Install Updates TimeOut (After upgrade SCCM 1806)

    Question

  • Hi ,

    Not sure if its related to the upgrade but before it worked (and our not yet to 1806 updated prd environment doesn't have the issue)

    Problem:

    Updates wont install, the Install Updates task will eventually fail after a time out.

    OS: Windows 10 1607 LTSB (I know never use LTSB but its healthcare)

    SMTSTS:

    Waiting for RefreshUpdates complete notification from Updates Deployment Agent    InstallSWUpdate    05/09/2018 08:25:21    3776 (0x0EC0)
    FALSE, HRESULT=800705b4 (installswupdate.cpp,1359)    InstallSWUpdate    05/09/2018 09:25:21    3776 (0x0EC0)
    Time-out expired waiting for updates refresh complete notification.    InstallSWUpdate    05/09/2018 09:25:21    3776 (0x0EC0)
    WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (installswupdate.cpp,1492)    InstallSWUpdate    05/09/2018 09:25:21    3776 (0x0EC0)
    RefreshUpdates(bForceOnlineScan), HRESULT=800705b4 (installswupdate.cpp,1001)    InstallSWUpdate    05/09/2018 09:25:21    3776 (0x0EC0)
    InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle), HRESULT=800705b4 (main.cpp,248)    InstallSWUpdate    05/09/2018 09:25:21    3776 (0x0EC0)

    WUHandler:

    Restarting WU Agent service...    WUAHandler    05/09/2018 08:27:36    1392 (0x0570)
    Stopped the service 'wuauserv' successfully    WUAHandler    05/09/2018 08:27:36    1392 (0x0570)
    Waiting for 30 secs for policy to take effect on WU Agent.    WUAHandler    05/09/2018 08:27:37    1392 (0x0570)
    Added Update Source ({C8337872-4E0A-4554-A5E4-CC19EF8F06C5}) of content type: 2    WUAHandler    05/09/2018 08:28:07    1392 (0x0570)
    CWUAHandler - Scan(), old SupersedenceMode=0, new SupersedenceMode=1. Need update and save to SourceManager.    WUAHandler    05/09/2018 08:28:07    1392 (0x0570)
    Modified Update Source ({C8337872-4E0A-4554-A5E4-CC19EF8F06C5}) to new SupersedenceMode: 1    WUAHandler    05/09/2018 08:28:07    1392 (0x0570)
    Scan results will include all superseded updates.    WUAHandler    05/09/2018 08:28:07    1392 (0x0570)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')    WUAHandler    05/09/2018 08:28:07    1392 (0x0570)
    Async searching of updates using WUAgent started.    WUAHandler    05/09/2018 08:28:07    1392 (0x0570)
    Async searching completed.    WUAHandler    05/09/2018 08:28:59    676 (0x02A4)
    Successfully completed scan.    WUAHandler    05/09/2018 08:29:00    3956 (0x0F74)
    Its a WSUS Update Source type ({C8337872-4E0A-4554-A5E4-CC19EF8F06C5}), adding it.    WUAHandler    05/09/2018 08:29:00    3892 (0x0F34)
    Not RS3+, this device is SCCM managed.    WUAHandler    05/09/2018 08:29:00    536 (0x0218)
    SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr    WUAHandler    05/09/2018 08:29:00    536 (0x0218)
    Existing WUA Managed server was already set (https://AXXXXX.X.XXX:8531), skipping Group Policy registration.    WUAHandler    05/09/2018 08:29:00    3892 (0x0F34)
    Added Update Source ({C8337872-4E0A-4554-A5E4-CC19EF8F06C5}) of content type: 2    WUAHandler    05/09/2018 08:29:00    3892 (0x0F34)
    Scan results will include all superseded updates.    WUAHandler    05/09/2018 08:29:00    3892 (0x0F34)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')    WUAHandler    05/09/2018 08:29:00    3892 (0x0F34)
    Async searching of updates using WUAgent started.    WUAHandler    05/09/2018 08:29:00    3892 (0x0F34)
    Async searching completed.    WUAHandler    05/09/2018 08:29:04    2912 (0x0B60)
    Successfully completed scan.    WUAHandler    05/09/2018 08:29:05    3892 (0x0F34)

    ScanAgent

    ScanJob({3696A025-8B64-4399-B2BA-74A4C7FE6202}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    05/09/2018 08:29:05    1380 (0x0564)
    ScanJob({3696A025-8B64-4399-B2BA-74A4C7FE6202}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    05/09/2018 08:29:05    1380 (0x0564)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:05    1380 (0x0564)
    - - Calling back to client on Scan request complete...    ScanAgent    05/09/2018 08:29:05    1380 (0x0564)
    ScanJob({8E7CEE95-0A95-46D9-9EFA-2302A02530B1}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    05/09/2018 08:29:06    1256 (0x04E8)
    ScanJob({8E7CEE95-0A95-46D9-9EFA-2302A02530B1}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    05/09/2018 08:29:06    1256 (0x04E8)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    - - Calling back to client on Scan request complete...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    ScanJob({03761DEE-6D2A-4A0C-883E-B529837D13DE}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    05/09/2018 08:29:06    3956 (0x0F74)
    ScanJob({03761DEE-6D2A-4A0C-883E-B529837D13DE}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    05/09/2018 08:29:06    3956 (0x0F74)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    - - Calling back to client on Scan request complete...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    ScanJob({4BE9D76A-DA7B-45E5-8BF8-DEAEC2ABC190}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    05/09/2018 08:29:06    1220 (0x04C4)
    ScanJob({4BE9D76A-DA7B-45E5-8BF8-DEAEC2ABC190}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    05/09/2018 08:29:06    1220 (0x04C4)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    - - Calling back to client on Scan request complete...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    ScanJob({FD11A867-F580-45CE-B166-6EED587C0505}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    05/09/2018 08:29:06    3644 (0x0E3C)
    ScanJob({FD11A867-F580-45CE-B166-6EED587C0505}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    05/09/2018 08:29:06    3644 (0x0E3C)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    - - Calling back to client on Scan request complete...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    ScanJob({C6F3BABA-66E2-4F52-A87A-0F3DC67CC94B}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    05/09/2018 08:29:06    1392 (0x0570)
    ScanJob({C6F3BABA-66E2-4F52-A87A-0F3DC67CC94B}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    05/09/2018 08:29:06    1392 (0x0570)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    - - Calling back to client on Scan request complete...    ScanAgent    05/09/2018 08:29:06    1380 (0x0564)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    3344 (0x0D10)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    1220 (0x04C4)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:06    4032 (0x0FC0)
    - - -Evaluating Update Status...    ScanAgent    05/09/2018 08:29:07    3920 (0x0F50)

    UpdateHandler:

    Successfully initiated scan.    UpdatesHandler    05/09/2018 08:28:08    3920 (0x0F50)
    Successfully initiated scan.    UpdatesHandler    05/09/2018 08:28:08    1384 (0x0568)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:00    3876 (0x0F24)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    3956 (0x0F74)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    3876 (0x0F24)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    3344 (0x0D10)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    3892 (0x0F34)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    3088 (0x0C10)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    3852 (0x0F0C)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    1384 (0x0568)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    4036 (0x0FC4)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    3920 (0x0F50)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:05    1380 (0x0564)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:06    1380 (0x0564)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:06    1380 (0x0564)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:06    1380 (0x0564)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:06    1380 (0x0564)
    Updates scan completion received, result = 0x0.    UpdatesHandler    05/09/2018 08:29:06    1380 (0x0564)

    UpdatesDeployment:

    Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_ec23bd30-6b50-4935-9208-d2314db5c761", actionType 12l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Update (Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_ec23bd30-6b50-4935-9208-d2314db5c761) added to the targeted list of deployment ({7331B19C-0889-41BE-80AF-CA0965758D8E})    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_9ae38a26-59a8-44d7-8524-fd750a9092b8", actionType 12l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Update (Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_9ae38a26-59a8-44d7-8524-fd750a9092b8) added to the targeted list of deployment ({7331B19C-0889-41BE-80AF-CA0965758D8E})    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_3691827b-92e2-4f18-acfa-8e42b48119e7", actionType 12l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Update (Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_3691827b-92e2-4f18-acfa-8e42b48119e7) added to the targeted list of deployment ({7331B19C-0889-41BE-80AF-CA0965758D8E})    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_3f23889e-6a30-41ed-981b-c61eeca84d01", actionType 12l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Update (Site_C8337872-4E0A-4554-A5E4-CC19EF8F06C5/SUM_3f23889e-6a30-41ed-981b-c61eeca84d01) added to the targeted list of deployment ({7331B19C-0889-41BE-80AF-CA0965758D8E})    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    Trigger detect - no further action needed.    UpdatesDeploymentAgent    05/09/2018 08:29:08    3892 (0x0F34)
    CEvalO365ManagementTask::Execute()    UpdatesDeploymentAgent    05/09/2018 08:36:56    3692 (0x0E6C)
    Not RS3+, this device is SCCM managed.    UpdatesDeploymentAgent    05/09/2018 08:36:56    3692 (0x0E6C)

    Wsus seems to be fine, the machines can communicate with WSUS. Packages and SUP are Ok.

    Anyone an idea where to look?


    • Edited by Tim NL Wednesday, September 5, 2018 8:22 AM typo
    Wednesday, September 5, 2018 8:21 AM

Answers

  • I created a new Software Update Deployment (of the same SUG) and deployed it again to the same collection. I seems that that solved the problem. (Not sure why, so still waiting for an explanation) Install Updates in OSD is working again.
    • Marked as answer by Tim NL Thursday, September 6, 2018 7:10 AM
    Thursday, September 6, 2018 7:03 AM

All replies

  • Hi Tim NL,

    I read the log fragment which you provided.

    "Time-out expired waiting for updates refresh complete notification. InstallSWUpdate 05/09/2018 09:25:21 3776 (0x0EC0)"

    Error code: 0x0EC0
    The dynamic-link library %1 could not be loaded, or an error
    Occasion while trying to use it.
    Source: Windows

    I have not used Windows 10 1607 LTSB, but I have not encountered similar issue with other version of Windows. Maybe the windows OS has corruption, or updates are damaged.

    Is this problem for one machine or multiple?

    If it's for one machine, I suggest you repair your OS system files using DISM first, then re-download the update and distribute it, deploy it.

    How to repair your system files using DISM:
    https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install-insiderplat_pc/how-to-repair-your-system-files-using-dism-and-sfc/1021b42a-09ff-41a0-a95a-48f3ee3ae699

    Best regards,

    Yuxiang


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 6, 2018 5:43 AM
  • Hello Yuxiang,

    Thanks for you reply. It's not on one machine but all. (image worked before)

    I used a vanilla install.wim and I used a serviced image with SSU of may. All the same behavior. The strange thing is that in FULL OS. (So Install Updates task disbaled during TS) after a long time the updates are installing. (same image, same machine).

    I have a case open at MSFT so hopefully a quick fix.

    Thursday, September 6, 2018 6:28 AM
  • I created a new Software Update Deployment (of the same SUG) and deployed it again to the same collection. I seems that that solved the problem. (Not sure why, so still waiting for an explanation) Install Updates in OSD is working again.
    • Marked as answer by Tim NL Thursday, September 6, 2018 7:10 AM
    Thursday, September 6, 2018 7:03 AM
  • Hi Tim Nl,

    Error code: 0x0EC0
    The dynamic-link library %1 could not be loaded, or an error
    Occasion while trying to use it.
    Source: Windows

    As this error code said, it may be that the SUG is corrupted, not clients OS, thank you for sharing.



    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 6, 2018 7:25 AM
  • We're having the same issue, after the upgrade to 1806 + Hotfix.

    I tried to re-deploy the SUG, but no luck. This hangs when using Task Sequence Install Software Updates task. 

    Looking at the smsts.log

    Successfully initiated RefreshUpdates operation. For troubleshooting, please refer to logs: UpdatesDeployment.log, UpdatesHandler.log, UpdatesStore.log, wuahandler.log, WindowsUpdate.log
    InstallSWUpdate 10/5/2018 3:49:27 PM 4080 (0x0FF0)
    Waiting for RefreshUpdates complete notification from Updates Deployment Agent
    InstallSWUpdate 10/5/2018 3:49:27 PM 4080 (0x0FF0)
    FALSE, HRESULT=800705b4 (installswupdate.cpp,1359)
    InstallSWUpdate 10/5/2018 4:49:27 PM 4080 (0x0FF0)
    Time-out expired waiting for updates refresh complete notification.
    InstallSWUpdate 10/5/2018 4:49:27 PM 4080 (0x0FF0)
    WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (installswupdate.cpp,1492)
    InstallSWUpdate 10/5/2018 4:49:27 PM 4080 (0x0FF0)
    RefreshUpdates(bForceOnlineScan), HRESULT=800705b4 (installswupdate.cpp,1001)
    InstallSWUpdate 10/5/2018 4:49:27 PM 4080 (0x0FF0)
    InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle), HRESULT=800705b4 (main.cpp,248)
    InstallSWUpdate 10/5/2018 4:49:27 PM 4080 (0x0FF0)
    Tuesday, October 9, 2018 3:23 PM
  • I'm seeing the same issue here, with the same log entries (timeout/800705b4). Have not tried to create a new software update deployment yet, will do that as soon as possible.

    @Yuxiang Shi: That "error code" you keep referring to is not an error code, that's the thread id as listed in Tim's smsts.log. 
    Wednesday, November 28, 2018 1:08 PM
  • I'm thinking to create new SU deployment because of this. Heppends in OSD now.

    MCSE Mobility 2018. Expert on SCCM, Windows 10 and MBAM.

    Wednesday, November 28, 2018 4:32 PM
  • i have exactly the same errors as above on Win 10 1809.

    Updates install fine for all clients where deployed via non-TS means.

    Wednesday, January 2, 2019 10:35 PM