locked
2012 - 0x8000FFFF RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Having some issues installing 1803 on Win 10 machines via a 2012 WSUS Server.

    We have 2012R2 and 2016 WSUS Servers which seem to be fine and all clients are updating via these, but a few sites have a 2012 WSUS Server and all appear to fail with 0x8000FFFF.

    I've confirmed the KB is installed that allows 2012 to cater for Win 10 feature upgrades, ran the <g class="gr_ gr_17 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="17" id="17">postinstall</g> /servicing (and restarted WSUS), and added the .esd MIME type to IIS.

    Pointing a machine on this site to update via one of our 2016 servers allows the update to be installed as expected, so this only appears to be an issue with 2012.

    Any ideas?


    • Edited by tecscott Friday, August 3, 2018 9:42 AM
    Friday, August 3, 2018 9:40 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote 
    2018/08/02 09:44:08.9302881 4676  9656  ComApi          * START *   Federated Search ClientId = UpdateOrchestrator (cV: iTHOXF8UbEaasa2Q.0.1.0)
2018/08/02 09:44:08.9304390 4676  9656  IdleTimer       WU operation (SR.UpdateOrchestrator ID 4) started; operation # 40; does use network; is not at background priority
2018/08/02 09:44:08.9557529 4676  9024  IdleTimer       WU operation (SR.UpdateOrchestrator ID 4, operation # 40) stopped; does use network; is not at background priority
2018/08/02 09:44:08.9680989 4676  2528  ComApi          Federated Search: Starting search against 1 service(s) (cV = iTHOXF8UbEaasa2Q.0.1.0)
2018/08/02 09:44:08.9681931 4676  2528  ComApi          * START *   Search ClientId = UpdateOrchestrator, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = iTHOXF8UbEaasa2Q.0.1.0.0)
2018/08/02 09:44:08.9687343 4676  2528  IdleTimer       WU operation (CSearchCall::Init ID 5) started; operation # 43; does use network; is not at background priority
2018/08/02 09:44:09.0727766 4676  2528  Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 5]
2018/08/02 09:44:09.0727812 4676  2528  Agent           Removing service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 from sequential scan list
2018/08/02 09:44:09.0727845 4676  2528  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
2018/08/02 09:44:09.0727881 4676  2528  Agent           Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
2018/08/02 09:44:09.0730571 4676  6152  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
2018/08/02 09:44:09.1151813 4676  8984  Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 5]
2018/08/02 09:44:09.1563876 4676  8984  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 5
2018/08/02 09:44:09.1563903 4676  8984  Agent           Online = Yes; Interactive = Yes; AllowCachedResults = No; Ignore download priority = No
2018/08/02 09:44:09.1563936 4676  8984  Agent           Criteria = IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1""
2018/08/02 09:44:09.1563964 4676  8984  Agent           ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2018/08/02 09:44:09.1563973 4676  8984  Agent           Search Scope = {Machine}
2018/08/02 09:44:09.1564027 4676  8984  Agent           Caller SID for Applicability: S-1-5-21-1029327778-2626596202-74287259-500
2018/08/02 09:44:09.1564039 4676  8984  Agent           ProcessDriverDeferrals is set
2018/08/02 09:44:09.2796837 4676  8984  Misc            Got WSUS Client/Server URL: https://wsus.domain.co.uk:8531/ClientWebService/client.asmx""
2018/08/02 09:44:09.3710893 4676  8984  Driver          Skipping printer driver 2 due to incomplete info or mismatched environment - HWID[(null)] Provider[Microsoft] MfgName[Microsoft] Name[Remote Desktop Easy Print] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
2018/08/02 09:44:09.3710926 4676  8984  Driver          Skipping printer driver 6 due to incomplete info or mismatched environment - HWID[(null)] Provider[HP] MfgName[HP] Name[HP ePrint] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
2018/08/02 09:44:09.3710965 4676  8984  Driver          Skipping printer driver 9 due to incomplete info or mismatched environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft] MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
2018/08/02 09:44:09.7134020 4676  8984  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://wsus.domain.co.uk:8531/ClientWebService/client.asmx
2018/08/02 09:44:09.7135463 4676  8984  ProtocolTalker  OK to reuse existing configuration
2018/08/02 09:44:09.7135497 4676  8984  ProtocolTalker  Existing cookie is valid, just use it
2018/08/02 09:44:09.7135509 4676  8984  ProtocolTalker  PTInfo: Server requested registration
2018/08/02 09:44:11.4716543 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 44; does use network; is at background priority
2018/08/02 09:44:11.4716863 4676  8984  WebServices     Auto proxy settings for this web service call.
2018/08/02 09:44:11.5002822 4676  8984  WebServices     WS error: Fault occurred
2018/08/02 09:44:11.5002840 4676  8984  WebServices     WS Error code: Client
2018/08/02 09:44:11.5003000 4676  8984  WebServices     WS error: <detail><ErrorCode>ConfigChanged</ErrorCode><Message></Message><ID>3f02bbbe-358e-4c5b-87f0-e2ade136272d</ID><Method>http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>"
2018/08/02 09:44:13.5151473 4676  8984  WebServices     Auto proxy settings for this web service call.
2018/08/02 09:44:13.5531033 4676  8984  WebServices     WS error: Fault occurred
2018/08/02 09:44:13.5531105 4676  8984  WebServices     WS Error code: Client
2018/08/02 09:44:13.5531932 4676  8984  WebServices     WS error: <detail><ErrorCode>ConfigChanged</ErrorCode><Message></Message><ID>80449657-8cad-4c52-9a7b-86a23a3bc5ea</ID><Method>http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>"
2018/08/02 09:44:15.5618956 4676  8984  WebServices     Auto proxy settings for this web service call.
2018/08/02 09:44:15.5988274 4676  8984  WebServices     WS error: Fault occurred
2018/08/02 09:44:15.5988346 4676  8984  WebServices     WS Error code: Client
2018/08/02 09:44:15.5989234 4676  8984  WebServices     WS error: <detail><ErrorCode>ConfigChanged</ErrorCode><Message></Message><ID>72fb28ee-e379-49e3-8c43-a058685fa011</ID><Method>http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>"
2018/08/02 09:44:15.5990218 4676  8984  ProtocolTalker  PT: Calling GetConfig on server
2018/08/02 09:44:15.5990483 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 45; does use network; is at background priority
2018/08/02 09:44:15.6037467 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 45) stopped; does use network; is at background priority
2018/08/02 09:44:15.6049892 4676  8984  Misc            Got WSUS SimpleTargeting URL: https://wsus.domain.co.uk:8531""
2018/08/02 09:44:15.6057415 4676  8984  IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 46; does use network; is at background priority
2018/08/02 09:44:15.6057566 4676  8984  ProtocolTalker  Initializing simple targeting cookie, clientId = 2a5914aa-1a4e-499a-9cd0-ea47e5f87afc, target group = Test - Computers, DNS name = compname.domain.local
2018/08/02 09:44:15.6057623 4676  8984  ProtocolTalker    Server URL = https://wsus.domain.co.uk:8531/SimpleAuthWebService/SimpleAuth.asmx
2018/08/02 09:44:15.6058172 4676  8984  WebServices     Auto proxy settings for this web service call.
2018/08/02 09:44:15.6347403 4676  8984  IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 46) stopped; does use network; is at background priority
2018/08/02 09:44:15.6355128 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery) started; operation # 47; does use network; is at background priority
2018/08/02 09:44:15.6420689 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 47) stopped; does use network; is at background priority
2018/08/02 09:44:15.6421144 4676  8984  ProtocolTalker  PTInfo: Server requested registration
2018/08/02 09:44:15.6735675 4676  8984  ProtocolTalker  PTInfo: Calling RegisterComputer
2018/08/02 09:44:15.6735796 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery) started; operation # 48; does use network; is at background priority
2018/08/02 09:44:15.6779848 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery, operation # 48) stopped; does use network; is at background priority
2018/08/02 09:44:15.6957923 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 44) stopped; does use network; is at background priority
2018/08/02 09:44:15.7388360 4676  8984  SLS             *FAILED* [80248007] Method failed [SlsDatastoreLookup:797]
2018/08/02 09:44:15.7388400 4676  8984  SLS             Retrieving SLS response from server...
2018/08/02 09:44:15.8221907 4676  8984  SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}/x64/10.0.16299.0/0?CH=937&L=en-GB&P=&PT=0x30&WUA=10.0.16299.431&MK=Hewlett-Packard&MD=HP+ProDesk+600+G1+SFF
2018/08/02 09:44:16.4048224 4676  8984  SLS             SLS Response is Error response type.  Attempting to extract the HRESULT in the payload...
2018/08/02 09:44:16.4053703 4676  8984  SLS             Succeeded in extracting the HRESULT from the payload => 0x80240042
2018/08/02 09:44:16.4065772 4676  8984  Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfig:793]
2018/08/02 09:44:16.4065850 4676  8984  Metadata        *FAILED* [80245004] GetFragmentSigningConfig (Using default enforcement mode: Audit)
2018/08/02 09:44:16.4065899 4676  8984  Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfigAndUpdateEnforcementPolicy:745]
2018/08/02 09:44:16.4065917 4676  8984  Metadata        Policy-driven service enabled. Using Ignore Policy.
2018/08/02 09:44:16.4066052 4676  8984  ProtocolTalker  SyncUpdates - 0 bad out of 0 metadata signatures checked using Audit enforcement mode.
2018/08/02 09:44:16.6051127 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 49; does use network; is at background priority
2018/08/02 09:44:16.6195473 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 49) stopped; does use network; is at background priority
2018/08/02 09:44:16.6362747 4676  8984  SLS             *FAILED* [80248007] Method failed [SlsDatastoreLookup:797]
2018/08/02 09:44:16.6362786 4676  8984  SLS             Retrieving SLS response from server...
2018/08/02 09:44:16.6365986 4676  8984  SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}/x64/10.0.16299.0/0?CH=937&L=en-GB&P=&PT=0x30&WUA=10.0.16299.431&MK=Hewlett-Packard&MD=HP+ProDesk+600+G1+SFF
2018/08/02 09:44:17.1372854 4676  8984  SLS             SLS Response is Error response type.  Attempting to extract the HRESULT in the payload...
2018/08/02 09:44:17.1378541 4676  8984  SLS             Succeeded in extracting the HRESULT from the payload => 0x80240042
2018/08/02 09:44:17.1378967 4676  8984  Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfig:793]
2018/08/02 09:44:17.1379060 4676  8984  Metadata        *FAILED* [80245004] GetFragmentSigningConfig (Using default enforcement mode: Audit)
2018/08/02 09:44:17.1379181 4676  8984  Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfigAndUpdateEnforcementPolicy:745]
2018/08/02 09:44:17.1379226 4676  8984  Metadata        Policy-driven service enabled. Using Ignore Policy.
2018/08/02 09:44:17.1379398 4676  8984  ProtocolTalker  SyncUpdates - 0 bad out of 0 metadata signatures checked using Audit enforcement mode.
2018/08/02 09:44:17.2219949 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 50; does use network; is at background priority
2018/08/02 09:44:17.2348715 4676  8984  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 50) stopped; does use network; is at background priority
2018/08/02 09:44:17.2348845 4676  8984  ProtocolTalker  SyncUpdates round trips: 3
2018/08/02 09:44:18.5533858 4676  8984  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
2018/08/02 09:44:19.5776299 4676  8984  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
2018/08/02 09:44:20.0474866 4676  8984  Agent           Added update E5B0A42B-46A4-4DCB-8420-AE6570467D65.201 to search result
2018/08/02 09:44:20.0475026 4676  8984  Agent           Found 1 updates and 97 categories in search; evaluated appl. rules of 1108 out of 2172 deployed entities
2018/08/02 09:44:20.1860536 4676  8984  Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 5
2018/08/02 09:44:20.1896440 4676  8984  IdleTimer       WU operation (CSearchCall::Init ID 5, operation # 43) stopped; does use network; is not at background priority
2018/08/02 09:44:20.2024652 4676  2248  ComApi          *RESUMED*   Search ClientId = UpdateOrchestrator, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = iTHOXF8UbEaasa2Q.0.1.0.0)
2018/08/02 09:44:20.2034801 4676  2248  ComApi          * END *   Search ClientId = UpdateOrchestrator, Updates found = 1, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = iTHOXF8UbEaasa2Q.0.1.0.0)
2018/08/02 09:44:20.2037134 4676  2528  ComApi          * END *   All federated searches have completed. Jobs = 1, Succeeded = 1, ClientId = UpdateOrchestrator (cV = iTHOXF8UbEaasa2Q.0.1.0)
2018/08/02 09:44:20.5106599 4676  9656  ComApi          * START *   Federated Download ClientId = UpdateOrchestrator (cV = sczbQdR4BEOe2e34.2.0)
2018/08/02 09:44:20.5109190 4676  788   ComApi          Federated Download: Starting download for 1 service(s) (cV = sczbQdR4BEOe2e34.2.0)
2018/08/02 09:44:20.5109905 4676  788   ComApi          * START *   Download ClientId = UpdateOrchestrator 
2018/08/02 09:44:20.5109923 4676  788   ComApi          Flags: 0X1900C; Download priority: 3; Network Cost Policy: 0
2018/08/02 09:44:20.5109932 4676  788   ComApi          Updates in request: 1
2018/08/02 09:44:20.5110035 4676  788   ComApi          ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2018/08/02 09:44:20.5278531 4676  1724  Agent           Effective power state: AC; IsOnAC: Yes.
2018/08/02 09:44:20.5278567 4676  788   ComApi          *QUEUED* Download ClientId = UpdateOrchestrator
2018/08/02 09:44:20.5278685 4676  1724  IdleTimer       WU operation (DL.UpdateOrchestrator) started; operation # 65; does use network; is not at background priority
2018/08/02 09:44:20.5278718 4676  1724  Agent           Obtained a network PDC reference for callID {EB92BEDD-7C35-43DB-B1E1-FDC81C6AC424} with No-Progress-Timeout set to 4294967295; ActivationID: 65.
2018/08/02 09:44:20.5296574 4676  1724  DownloadManager * START * Begin Downloading Updates [CallerId = UpdateOrchestrator] [Call ID = EB92BEDD-7C35-43DB-B1E1-FDC81C6AC424]
2018/08/02 09:44:20.5296622 4676  1724  DownloadManager Priority = 3, NetworkCostPolicy = 0, Interactive = 1, Download on Battery = 1, Bypass Regulation = 1, Owner is system = 1, Proxy session id = 2, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7.
2018/08/02 09:44:20.5296631 4676  1724  DownloadManager Updates to download = 1
2018/08/02 09:44:20.5296644 4676  1724  Agent             Title = Feature update to Windows 10 (consumer editions), version 1803, en-gb
2018/08/02 09:44:20.5296671 4676  1724  Agent             UpdateId = E5B0A42B-46A4-4DCB-8420-AE6570467D65.201
2018/08/02 09:44:20.5296677 4676  1724  Agent               Bundles 1 updates:
2018/08/02 09:44:20.5296701 4676  1724  Agent                 2F8B209C-F899-4AB7-8502-6154F0FF3821.201
2018/08/02 09:44:20.5297610 4676  1724  DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category PerUpdate.
2018/08/02 09:44:20.5297640 4676  1724  DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category Low.
2018/08/02 09:44:20.5297658 4676  1724  DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category Normal.
2018/08/02 09:44:20.5297676 4676  1724  DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category High.
2018/08/02 09:44:20.5683657 4676  1724  DownloadManager Queueing update 2F8B209C-F899-4AB7-8502-6154F0FF3821.201 for download handler request generation.
2018/08/02 09:44:20.5695834 4676  1724  DownloadManager Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
2018/08/02 09:44:20.5697256 4676  1724  Agent           Effective power state: AC; IsOnAC: Yes.
2018/08/02 09:44:20.5697320 4676  1724  IdleTimer       WU operation (DL.UpdateOrchestrator, operation # 65) stopped; does use network; is not at background priority
2018/08/02 09:44:20.5697350 4676  1724  Agent           Released network PDC reference for callId {EB92BEDD-7C35-43DB-B1E1-FDC81C6AC424}; ActivationID: 65
2018/08/02 09:44:20.5697407 4676  1724  IdleTimer       WU operation (DL.UpdateOrchestrator) started; operation # 66; does use network; is not at background priority
2018/08/02 09:44:20.5697446 4676  1724  Agent           Obtained a network PDC reference for callID {EB92BEDD-7C35-43DB-B1E1-FDC81C6AC424} with No-Progress-Timeout set to 4294967295; ActivationID: 66.
2018/08/02 09:44:20.5698986 4676  1368  Agent           WU client calls back to download call {EB92BEDD-7C35-43DB-B1E1-FDC81C6AC424} with code Call progress and error 0
2018/08/02 09:44:20.5719924 4676  6288  Handler         Loaded state. m_dwState now: WinSetup_DownloadComplete(2)
2018/08/02 09:44:20.5720968 4676  6288  DownloadManager Generating download request for update 2F8B209C-F899-4AB7-8502-6154F0FF3821.201.
2018/08/02 09:44:19.7748114 4676  6288  DownloadManager Calling into handler 0xa to generate download request for update 2F8B209C-F899-4AB7-8502-6154F0FF3821.201.
2018/08/02 09:44:19.7750426 4676  1724  DownloadManager * END * Begin Downloading Updates CallerId = UpdateOrchestrator
2018/08/02 09:44:19.7751634 4676  6288  Handler         Loaded state. m_dwState now: WinSetup_DownloadComplete(2)
2018/08/02 09:44:19.7950967 4676  1724  DownloadManager Avoiding download as update is already marked complete.
2018/08/02 09:44:19.8161586 4676  1724  DownloadManager All files for update 2F8B209C-F899-4AB7-8502-6154F0FF3821.201 were already downloaded and are valid.
2018/08/02 09:44:19.8173510 4676  1724  DownloadManager * END * Download Call Complete Call 6 for caller UpdateOrchestrator has completed; signaling completion.
2018/08/02 09:44:19.8182446 4676  1724  DownloadManager Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
2018/08/02 09:44:19.8190008 4676  1724  Agent           Effective power state: AC; IsOnAC: Yes.
2018/08/02 09:44:19.8190125 4676  1724  IdleTimer       WU operation (DL.UpdateOrchestrator, operation # 66) stopped; does use network; is not at background priority
2018/08/02 09:44:19.8190156 4676  1724  Agent           Released network PDC reference for callId {EB92BEDD-7C35-43DB-B1E1-FDC81C6AC424}; ActivationID: 66
2018/08/02 09:44:19.8191695 4676  1368  ComApi          *RESUMED* Download ClientId = UpdateOrchestrator
2018/08/02 09:44:19.8191743 4676  1368  ComApi          Download call complete (succeeded = 1, succeeded with errors = 0, failed = 0, cancelled = 0, unaccounted = 0)
2018/08/02 09:44:19.8191801 4676  1368  ComApi          * END *   Download ClientId = UpdateOrchestrator
2018/08/02 09:44:19.8191852 4676  1368  Agent           WU client calls back to download call {EB92BEDD-7C35-43DB-B1E1-FDC81C6AC424} with code Call complete and error 0
2018/08/02 09:44:19.8197645 4676  788   ComApi          Download call complete (succeeded = 1, succeeded with errors = 0, failed = 0, cancelled = 0, unaccounted = 0)
2018/08/02 09:44:19.8197733 4676  788   ComApi          * END *   All federated downloads have completed. ClientId = UpdateOrchestrator (cV = sczbQdR4BEOe2e34.2.0)
2018/08/02 09:44:20.2252010 4676  9656  ComApi          * START *   Federated Install   ClientId = UpdateOrchestrator (cV: sczbQdR4BEOe2e34.3.0)
2018/08/02 09:44:20.2255687 4676  5828  ComApi          * START *   Install ClientId = UpdateOrchestrator
2018/08/02 09:44:20.2255738 4676  5828  ComApi          Allow source prompts: Yes; Forced: No; Force quiet: No; Attempt close apps if necessary: No
2018/08/02 09:44:20.2256007 4676  5828  ComApi          Updates in request: 1
2018/08/02 09:44:20.2256115 4676  5828  ComApi          ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2018/08/02 09:44:20.2265519 4676  5828  IdleTimer       WU operation (CInstallCall::Init ID 7) started; operation # 73; does not use network; is not at background priority
2018/08/02 09:44:20.2267505 4676  5828  Agent           Beginning install of conventional work item
2018/08/02 09:44:20.2268033 4676  5828  ComApi          *QUEUED* Updates to install = 1
2018/08/02 09:44:20.2268067 4676  5828  ComApi          Install ClientId = UpdateOrchestrator
2018/08/02 09:44:20.2268251 4676  9784  Agent           *  START  *  Installing updates CallerId = UpdateOrchestrator
2018/08/02 09:44:20.2268290 4676  9784  Agent           Updates to install = 1
2018/08/02 09:44:20.2321948 4676  9784  Agent             Title = Feature update to Windows 10 (consumer editions), version 1803, en-gb
2018/08/02 09:44:20.2322051 4676  9784  Agent             UpdateId = E5B0A42B-46A4-4DCB-8420-AE6570467D65.201
2018/08/02 09:44:20.2322078 4676  9784  Agent               Bundles 1 updates:
2018/08/02 09:44:20.2322156 4676  9784  Agent                 2F8B209C-F899-4AB7-8502-6154F0FF3821.201
2018/08/02 09:44:20.6445541 4676  1368  Agent           WU client calls back to install call {7AAAB89F-9754-46C1-AFD1-163B4DBC2A47} with code Call progress and error 0 
2018/08/02 09:44:21.0998555 4676  1368  Agent           WU client calls back to install call {7AAAB89F-9754-46C1-AFD1-163B4DBC2A47} with code Call progress and error 0 
2018/08/02 09:44:21.4187885 4676  9784  DownloadManager Preparing update for install, updateId = 2F8B209C-F899-4AB7-8502-6154F0FF3821.201.
2018/08/02 09:44:21.4192108 1156  9700  Handler         * START *   Windows Setup Install
2018/08/02 09:44:21.4192129 1156  9700  Handler         Updates to install = 1
2018/08/02 09:44:21.4218652 1156  9700  Handler         Starting Windows Setup with command line = C:\WINDOWS\SoftwareDistribution\Download\38f66963ab91d86049a904b24bf297bc\WindowsUpdateBox.exe" /ClassId ecbb347b-92eb-4d24-9cbc-ac6eb4e190d2 /SessionId 2 /ReportId {2F8B209C-F899-4AB7-8502-6154F0FF3821}.201 "
2018/08/02 09:44:21.4218694 1156  9700  Handler         Registering WinSetup COM server as CLSID {ECBB347B-92EB-4D24-9CBC-AC6EB4E190D2} and APPID {42E97B8B-5D29-4917-A1A6-FD172BBDC876}
2018/08/02 09:44:21.4233039 1156  9700  Handler         Successfully registered WinSetup COM server as CLSID {ECBB347B-92EB-4D24-9CBC-AC6EB4E190D2}
2018/08/02 09:44:21.9070505 1156  9700  Handler         Installer completed. Process return code = 0x8000FFFF, result = 0x8000FFFF, callback pending = False
2018/08/02 09:44:21.9079008 1156  9700  Handler         *FAILED* [8000FFFF] Method failed [CUHWinSetupHandler::Install:775]
2018/08/02 09:44:21.9079081 1156  9700  Handler         * END *   Windows Setup Install
2018/08/02 09:44:22.0942023 4676  9784  Agent           LogHistory called. idUpdate={E5B0A42B-46A4-4DCB-8420-AE6570467D65}.201, resultMapped=8000FFFF, resultUnMapped=0
2018/08/02 09:44:22.1783198 4676  9784  Agent           Install updates CallerId = UpdateOrchestrator
2018/08/02 09:44:22.1783437 4676  1368  ComApi           Install ClientId = UpdateOrchestrator
2018/08/02 09:44:22.1783470 4676  1368  ComApi          Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0
2018/08/02 09:44:22.1784107 4676  1368  ComApi          Reboot required = False
2018/08/02 09:44:22.1784137 4676  1368  ComApi          Exit code = 0x00000000; Call error code = 0x80240022
2018/08/02 09:44:22.1784158 4676  1368  ComApi          * END *   Install ClientId = UpdateOrchestrator
2018/08/02 09:44:22.1784210 4676  1368  Agent           WU client calls back to install call {7AAAB89F-9754-46C1-AFD1-163B4DBC2A47} with code Call complete and error 0 
2018/08/02 09:44:22.1785728 4676  5828  ComApi          Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0
2018/08/02 09:44:22.1786317 4676  5828  ComApi          * END *   All federated installs have completed. ClientId = UpdateOrchestrator (cV = sczbQdR4BEOe2e34.3.0)
2018/08/02 09:44:22.1797187 4676  9784  IdleTimer       WU operation (CInstallCall::Init ID 7, operation # 73) stopped; does not use network; is not at background priority
    The above is the WindowsUpdateLog from one of the clients with the failed install.
    Friday, August 3, 2018 9:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello tecscott, 

     

    Glad to help. 

     

    More details are helpful. Does your 2012 WSUS push other updates correctly? Can your clients report to 2012 WSUS correctly? 

     

    And on your 2012 WSUS server, have you checked if the 1803 upgrade file is downloaded completely? 

     

    Look forward to your feedback and above information would help us to isolate the problem.

     

    Best Regards,

    Ray Jia

     

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 6, 2018 2:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    The 2012 does indeed push all other updates correctly, for example, if I point a PC to use the 2016 WSUS to get 1803, then change it back to the 2012 WSUS server it'll install the 1803 cumulative updates.

    All clients do correctly report to 2012.

    The file is downloaded, I can download the file directly via the .esd link too. During Windows Updates the file is downloaded (from what I understand of the log above, it downloads but fails to install).

    I can only assume this is an issue with 2012 pushing out Win 10 upgrades, however from what I understand 1803 isn't encrypted anymore so shouldn't be an issue, and the necessary changes were already made on this server (wsusutil postinstall /servicing and .esd MIME type added to IIS)

    Thanks.

    It's worth adding, there are 2 2012 servers, both experiencing the exact same issue.
    • Edited by tecscott Monday, August 6, 2018 8:56 AM
    Monday, August 6, 2018 8:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

      

    Thanks for feedback.

     

    I suggest that you recreate the SUSDB on your 2012 servers.

      

    1. Following this guide to recreate SUSDB.

      Recreating the SUSDB and WSUS Content folder for a Windows Server 2012 based WSUS computer
      https://blogs.technet.microsoft.com/sus/2016/10/18/recreating-the-susdb-and-wsus-content-folder-for-a-windows-server-2012-based-wsus-computer/#comment-28755

    2. Before syncing the Upgrades Category to the new WSUS make sure to have KB3095113 and KB3159706 (including manual postinstall steps) installed and configured.

     

    Check if it works. 

     

    Related Case:

    https://social.msdn.microsoft.com/Forums/en-US/1320daa4-efc2-4ae2-a7a5-1f1013da38bb/1703-distributed-clients-now-cannot-contact-wsus-anymore?forum=winserverwsus

     

    Look forward to your feedback.

     

    Best Regards,

    Ray Jia

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 7, 2018 2:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have tried that and had no luck, unfortunately.

    I assume KB3095113 is no longer necessary now, as it's not applicable to the computer when installing this.

    KB3159706 is already installed and the manual postinstall steps have been run.

    It's also worth noting that the clients do check in, attempt to download the update and the install fails. They continue to check in with WSUS stating it has the 1 failed install.


    • Edited by tecscott Tuesday, August 7, 2018 8:19 AM
    Tuesday, August 7, 2018 8:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello tecscott,

     

    I found this.

     

    https://blogs.technet.microsoft.com/wsus/2015/12/03/important-update-for-wsus-4-0-kb-3095113/#pi47623=7#comments%20(

     

    Try the instructions posted by "This Drove me Mad" and "FCW" from this Blog.

     

    Look forward to your feedback.

    Best Regards,

    Ray Jia

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 7, 2018 9:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If you had WSUS Automated Maintenance (Formerly Adamj Clean-WSUS) before it switched to a subscription model you could have run a .\Clean-WSUS.ps1 -DirtyDatabaseCheck

    It's now deprecated but is still included in the package. It runs the equivalent of https://support.microsoft.com/en-ca/help/3194588/0xc1800118-error-when-you-push-windows-10-version-1607-by-using-wsus

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Tuesday, August 7, 2018 7:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Adam, from what I understand the Dirty Database is no longer an issue, as 1803 is not encrypted?

    So the expected output for 1803 would be IsEncrypted = 0 and DecryptionKey = null.

    Thursday, August 9, 2018 9:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Correct. It shouldn't be an issue any longer.

    One thing to make sure of is that the .esd mimetype is setup (there are reports of it going missing).

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-3-windows-as-a-service-waas-and-group-policy-administrative-templates/

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Thursday, August 9, 2018 8:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    So naturally the DirtyDatabaseCheck will return that there's a dirty database, but it won't be any use as it's now irrelevant.

    The IIS MIME type is set up, the log above shows it downloads the file without any issues I don't believe this would be the case if the mime type wasn't set up (it would fail the download).

    Friday, August 10, 2018 8:00 AM