WSUS 3.0 SP2 troubles after installing KB2938066 (0xC000000D)

Hi everyone,

I ran into a problem in our WSUS environment after installing the latest hotfix KB2938066.

We have WS2008R2 SP1 (fully patched) for WSUS-Upstream server and couple of the same servers for WSUS-Downstream.

Previous functional version of WSUS was 3.2.7600.256.

After installing KB2938066 (v3.2.7600.274) the WU/MU clients updated, but on some machines, mostly on servers with WS2008R2 SP1 (RADIUS and Domain Controllers), they now have problems installing updates.

The error I see in '0xC000000D', which is something peculiar and not well searchable on the internet.

Here is part of the WindowsUpdate log.

I would appreciate any advice. Thx, John.

 

Agent *************
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
Agent *********
Agent * Online = Yes; Ignore download priority = No
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"
Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
Agent * Search Scope = {Machine}
Setup Checking for agent SelfUpdate
Setup Client version: Core: 7.6.7600.320 Aux: 7.6.7600.320
Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
Misc Microsoft signed: NA
Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPC435.tmp with dwProvFlags 0x00000080:
Misc FATAL: Error: 0xc000000d when verifying trust for C:\Windows\SoftwareDistribution\SelfUpdate\TMPC435.tmp
Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\TMPC435.tmp are not trusted: Error 0xc000000d
Setup FATAL: Ident cab verification failed with error 0XC000000D
Setup WARNING: SelfUpdate check failed to download package information, error = 0xC000000D
Setup FATAL: SelfUpdate check failed, err = 0xC000000D
Agent * WARNING: Skipping scan, self-update check returned 0xC000000D
Agent * WARNING: Exit code = 0xC000000D
Agent *********
Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
Agent *************
Agent WARNING: WU client failed Searching for update with error 0xc000000d
AU >>## RESUMED ## AU: Search for updates [CallId = {9CD5DB56-3B59-4481-90D0-FD1E34D65233}]
AU # WARNING: Search callback failed, result = 0xC000000D
AU # WARNING: Failed to find updates with error code C000000D
AU #########
AU ## END ## AU: Search for updates [CallId = {9CD5DB56-3B59-4481-90D0-FD1E34D65233}]
AU #############

Here is the WER file, which appeared in the application event log as information:

Version=1
EventType=WindowsUpdateFailure
EventTime=130498849873184095
Consent=1
ReportIdentifier=73f3eedf-0bf6-11e4-8540-005056960b89
Response.type=4
Sig[0].Name=ClientVersion
Sig[0].Value=7.6.7600.320
Sig[1].Name=Win32HResult
Sig[1].Value=c000000d
Sig[2].Name=UpdateId
Sig[2].Value=D67661EB-2423-451D-BF5D-13199E37DF28
Sig[3].Name=Scenario
Sig[3].Value=Scan
Sig[4].Name=SourceId
Sig[4].Value=101
Sig[5].Name=Environment
Sig[5].Value=Managed
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
FriendlyEventName=Windows Update installation problem
ConsentKey=WindowsUpdateFailure
AppName=Host Process for Windows Services
AppPath=C:\Windows\System32\svchost.exe
ReportDescription=A Windows update did not install properly. Sending the following information to Microsoft can help improve the software.