Can anyone help me with a problem, after updating windows 8.1 pro x64 with kb 2919355, after this I was not synchronized with wsus.
This installed on windows 2012 r2 is all updated.
It already follows all procedures listed in microsoft and others but to no avail.

Thank you

Alan Ferreira Maia

Hi,

i have a WSUS 6.3.9600.18324 on Windows Server 2012 R2

Before installed this server, i apply update KB3095113 and after, i sync WSUS Service (For updating Windows 10 1607 client)

I add a type MIME .esd application/octet-stream on IIS

But, i've always 5 updates on downloading

If i wait, this updates are downloaded completely but, if i click on SYNC NOW, the 5 updates restart download...

I have, on all my client 1607, 3 or 5 updates blocking at 0% of download... all days...

Thanks for your help :)

Paka-7252

Hello everyone,

I am running into an issue, I have a WSUS server setup on W2008 server and some times client computers are going out on the internet and that is consuming my lot of internet bandwidth. It almost works fine and after almost every month I face this problem once/twice. Could you guys please help me out to solve the issue?

Troubleshooting done so far:

1. Crossed checked through rsop.msc that policy has been applied on the computers.

2. Crossed checked that all the option on the my computer settings are showing up as per configured on the WSUS GPO.

Anyone can explain why Windows 10 1607 client can't download WSUS updates ?

WSUS is install on Windows Server 2012 R2 Server.

When a Windows 10 client detect a Windows 10 (1607 only) update on WSUS, client can't download every update ( Windows or other)

If there are only Office update everything works good.

Hi,

In WSUS, i am Unable to install Microsoft Report Viewer Redistributable on Windows server 2016 

When i am click on any system to check its Status Report then it's showing Microsoft Report Viewer Redistributable feature require. 

I have downloaded the files and when try to install it's showing as Microsoft System CLR Type for SQL Server 2012 missing. 

So, please suggest how to install this component and URL to download the file. 

Snapshot-1:

Snapshot-2:

I am trying to use WSUS Powershell module to find all servers that have failed status in WSUS for a specific Update Group. I see 26 servers in the console when I use that to check but when I use the PowerShell Module I get 187. I have tested this on multiple WSUS servers. They are 2012 R2 servers. This happens locally and with remote PowerShell access. Am I missing something?  here is the command I am using:

Get-WsusServer -Name contosowsus02 -PortNumber 8530|Get-WsusComputer -ComputerTargetGroups Kanary  -IncludedInstallationStates Failed

I am getting conflicting reports on how this should be done.

My assumption is that if I clean up the primary of obsolete & superseded updates when the replicas synchronize, they will update themselves to match the primary.

A PowerShell cleanup script I found had a Microsoft response that said otherwise. The rep said you need to clean up the replicas first, then do the primary last.

What is the right way to do this?

I know of the command wuauclt /reportnow /detectnow which is run from the client to prompt a status update to the server. 

Is there also a way to prompt a client status report from the server e.g. is there a command I can run from the WSUS server that will force a particular client to report status?

Hank Vare

1. 
   

   Just a example : If I am updating Monthly rollup, lets say Feb month (first time ) ,In this case the Feb monthly rollup will have the rollup update since OCT ?

   As rollup monthly patches consist of previous month updates as well , in this case won’t it effect network & server performance while downloading huge amount of window update ?

Hello Guys,

We have WSUS server already deployed with computer settings "Use the update service console". In WSUS console, Under "All computers" options, there are all computers appearing which are domain joined which is OK.

Week ago we changed the settings from "Use the update service console" to option "Use group policy or registry settings". For this we also created OU for some specific computers and pushed GP to that OU only.

Now, when I look at "All computers", other then Group policy computers all other systems which were present previously are still there in WSUS console. I also have tried deleting computers which are not in that OU from WSUS console but those computers appears again.

Any solution?

Thanks

Hi,

Since last week our domain machines are getting time out to reach the WSUS server (Version 3.2.7600.226, Windows Server 2008 SP2 fully patched).

Machines already patched contact WSUS normally.

Tried this morning after rebooting the server with a Virtual Machine (all physical machine are getting the same error, fresh installations of the latest Windows 10 ISO available 1607 build 14393.0). This is the error:

The machine appears on WSUS but with no report:

Tried opening http://srv-ad02/ClientWebService/client.asmx on the browser and got this:

Here is the WindowsUpdate.log:

2016/12/09 08:17:55.5320185 808   2356  Shared          * START * Service startup
2016/12/09 08:17:58.1362643 808   2356  Agent           WU client version 10.0.14393.0
2016/12/09 08:17:58.1365191 808   2356  Agent           SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2016/12/09 08:17:58.1366005 808   2356  Agent           Base directory: C:\Windows\SoftwareDistribution
2016/12/09 08:17:58.1373778 808   2356  Agent           Datastore directory: C:\Windows\SoftwareDistribution\DataStore\DataStore.edb
2016/12/09 08:17:59.0805618 808   2356  DataStore       Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 added
2016/12/09 08:17:59.0978707 808   2356  DataStore       Service 9482F4B4-E343-43B6-B170-9A65BC822C77 added
2016/12/09 08:17:59.1060866 808   2356  DataStore       Data store successfully created
2016/12/09 08:17:59.1629132 808   2356  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2016/12/09 08:17:59.1629322 808   2356  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016/12/09 08:17:59.1635234 808   2356  Shared          Network state: Connected
2016/12/09 08:17:59.3679245 808   2356  Misc            LoadHistoryEventFromRegistry completed, hr = 8024000C
2016/12/09 08:17:59.3784513 808   2356  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2016/12/09 08:17:59.3784562 808   2356  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016/12/09 08:17:59.3784612 808   2356  Shared          Power status changed
2016/12/09 08:17:59.4357064 808   2356  Agent           Initializing Windows Update Agent
2016/12/09 08:17:59.4386182 808   1892  Agent           Initializing global settings cache
2016/12/09 08:17:59.4386188 808   1892  Agent           WSUS server: NULL
2016/12/09 08:17:59.4386188 808   1892  Agent           WSUS status server: NULL
2016/12/09 08:17:59.4386194 808   1892  Agent           Target group: (Unassigned Computers)
2016/12/09 08:17:59.4386194 808   1892  Agent           Windows Update access disabled: No
2016/12/09 08:17:59.4386975 808   2356  DownloadManager Download manager restoring 0 downloads
2016/12/09 08:17:59.4611954 808   2356  Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x80248007
2016/12/09 08:17:59.4612191 808   2356  Agent           CPersistentTimeoutEvent | Resubscribe, no existing/cached timer for Id=29A863E7-8609-4D1E-B7CD-5668F857F1DB.
2016/12/09 08:17:59.4612250 808   2356  Agent           Adding timer:
2016/12/09 08:17:59.4612315 808   2356  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-12-10 10:17:59, not idle-only, not network-only
2016/12/09 08:17:59.4681931 808   2612  DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
2016/12/09 08:17:59.4682270 808   2612  DownloadManager PurgeExpiredUpdates::Found 0 non expired updates.
2016/12/09 08:17:59.4682313 808   2612  DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
2016/12/09 08:17:59.4781999 808   2612  Shared          Effective power state: AC
2016/12/09 08:17:59.4782005 808   2612  DownloadManager Power state change detected. Source now: AC
2016/12/09 08:18:00.4106294 304   1052  ComApi          * START *   SLS Discovery
2016/12/09 08:18:00.4276665 304   1052  ComApi          *QUEUED* SLS Discovery
1600/12/31 22:00:00.0000000 808   2648                  Unknown( 38): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
2016/12/09 08:18:00.4540476 808   2648  SLS             Retrieving SLS response from server...
2016/12/09 08:18:00.4540529 808   2648  Misc            Failed to get proxy settings token, not impersonating user. hr=800703f0
2016/12/09 08:18:00.4546158 808   2648  SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.14393.0/0?CH=651&L=pt-BR&P=&PT=0x30&WUA=10.0.14393.0
2016/12/09 08:18:00.4616141 808   2648  Misc            StatusCode for transaction returned from WinHttpQueryHeaders is 403
2016/12/09 08:18:00.4616215 808   2648  Misc            WinHttp: SendRequestToServerForFileInformation failed with 0x80072ef3; retrying with default proxy.
2016/12/09 08:18:01.9179650 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab with dwProvFlags 0x00000080:
2016/12/09 08:18:01.9256998 808   2648  Misc             Microsoft signed: NA
2016/12/09 08:18:01.9257732 808   2648  Misc             Infrastructure signed: Yes
2016/12/09 08:18:01.9279907 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPF464.tmp with dwProvFlags 0x00000080:
2016/12/09 08:18:01.9326968 808   2648  Misc             Microsoft signed: NA
2016/12/09 08:18:01.9327621 808   2648  Misc             Infrastructure signed: Yes
1600/12/31 22:00:00.0000000 808   2648                  Unknown( 38): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
2016/12/09 08:18:01.9351296 808   2648  SLS             Retrieving SLS response from server...
2016/12/09 08:18:01.9351312 808   2648  Misc            Failed to get proxy settings token, not impersonating user. hr=800703f0
2016/12/09 08:18:01.9354503 808   2648  SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{855E8A7C-ECB4-4CA3-B045-1DFA50104289}/x64/10.0.14393.0/0?CH=651&L=pt-BR&P=&PT=0x30&WUA=10.0.14393.0
2016/12/09 08:18:01.9413432 808   2648  Misc            StatusCode for transaction returned from WinHttpQueryHeaders is 403
2016/12/09 08:18:01.9413503 808   2648  Misc            WinHttp: SendRequestToServerForFileInformation failed with 0x80072ef3; retrying with default proxy.
2016/12/09 08:18:03.4162365 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\855E8A7C-ECB4-4CA3-B045-1DFA50104289\sls.cab with dwProvFlags 0x00000080:
2016/12/09 08:18:03.4401291 808   2648  Misc             Microsoft signed: NA
2016/12/09 08:18:03.4403409 808   2648  Misc             Infrastructure signed: Yes
2016/12/09 08:18:03.4478150 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\855E8A7C-ECB4-4CA3-B045-1DFA50104289\TMPFA51.tmp with dwProvFlags 0x00000080:
2016/12/09 08:18:03.4546643 808   2648  Misc             Microsoft signed: NA
2016/12/09 08:18:03.4547480 808   2648  Misc             Infrastructure signed: Yes
2016/12/09 08:18:03.8610691 304   1472  ComApi          *RESUMED* Discovery
2016/12/09 08:18:03.8613201 304   1472  Api             * END *   Discovery ClientId
2016/12/09 08:18:03.8948584 304   1052  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
2016/12/09 08:18:03.9075262 304   1052  ComApi          * START *   SLS Discovery
2016/12/09 08:18:03.9111163 304   1052  ComApi          *QUEUED* SLS Discovery
2016/12/09 08:18:03.9243733 304   1472  ComApi          *RESUMED* Discovery
2016/12/09 08:18:03.9245101 304   1472  Api             * END *   Discovery ClientId
2016/12/09 08:18:03.9261579 304   1052  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
2016/12/09 08:18:12.0489625 808   1892  Agent           Created new random SusClientId c55f4b6a-6fbb-408a-8b27-f553c8278a5e. Old Id: none.
2016/12/09 08:18:12.5521496 808   1892  Agent           * START * Queueing Finding updates [CallerId = OOBE ZDP  Id = 1]
2016/12/09 08:18:12.5521540 808   1892  Agent           Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2016/12/09 08:18:12.5540525 1016  1040  ComApi          Search ClientId = OOBE ZDP
2016/12/09 08:18:12.5570479 808   2860  Agent           * END * Queueing Finding updates [CallerId = OOBE ZDP  Id = 1]
2016/12/09 08:18:12.5590017 808   2860  Agent           * START * Finding updates CallerId = OOBE ZDP  Id = 1
2016/12/09 08:18:12.5590023 808   2860  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
2016/12/09 08:18:12.5590030 808   2860  Agent           Criteria = IsInstalled = 0 AND DeploymentAction = 'Installation' AND CategoryIDs contains 'DD78B8A1-0B20-45C1-ADD6-4DA72E9364CF'""
2016/12/09 08:18:12.5590048 808   2860  Agent           ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2016/12/09 08:18:12.5590051 808   2860  Agent           Search Scope = {Machine}
2016/12/09 08:18:12.5590064 808   2860  Agent           Caller SID for Applicability: S-1-5-18
2016/12/09 08:18:12.5590067 808   2860  Agent           RegisterService is set
2016/12/09 08:18:12.5628929 808   2860  Misc            Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL: https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx""
2016/12/09 08:18:15.1339046 808   2860  ProtocolTalker  PT: Calling GetConfig on server
2016/12/09 08:18:15.1462017 808   2860  WebServices     Auto proxy settings for this web service call.
2016/12/09 08:18:15.2056757 808   2860  WebServices     WS error: Houve um erro na comunicação com o ponto de extremidade em 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.
2016/12/09 08:18:15.2056766 808   2860  WebServices     WS error: O servidor retornou o código de status HTTP '403 (0x193)' com o texto 'Forbidden'.
2016/12/09 08:18:15.2056769 808   2860  WebServices     WS error: O servidor compreendeu a solicitação, mas não pode atendê-la.
2016/12/09 08:18:15.2056772 808   2860  WebServices     WS error: A operação não pôde ser concluída porque o canal foi cancelado.
2016/12/09 08:18:15.2142496 808   2860  WebServices     Web service call failed with hr = 80244017.
2016/12/09 08:18:15.2142502 808   2860  WebServices     Current service auth scheme=0.
2016/12/09 08:18:15.2142505 808   2860  WebServices     Current Proxy auth scheme=0.
2016/12/09 08:18:15.2142564 808   2860  ProtocolTalker  PTError: 0x80244017
2016/12/09 08:18:15.2142574 808   2860  ProtocolTalker  GetConfig_WithRecovery failed 0x80244017
2016/12/09 08:18:15.2142580 808   2860  ProtocolTalker  StartCategoryScan failed  0x80244017
2016/12/09 08:18:15.2620310 808   2860  Agent           Exit code = 0x80244017
2016/12/09 08:18:15.2620320 808   2860  Agent           * END * Finding updates CallerId = OOBE ZDP  Id = 1
2016/12/09 08:18:15.2676319 1016  1108  ComApi          *RESUMED* Search ClientId = OOBE ZDP
2016/12/09 08:18:15.2682623 1016  1108  ComApi          Updates found = 0
2016/12/09 08:18:15.2682629 1016  1108  ComApi          Exit code = 0x00000000, Result code = 0x80244017
2016/12/09 08:18:15.2682633 1016  1108  ComApi          * END *   Search ClientId = OOBE ZDP
2016/12/09 08:18:15.3067946 1016  1040  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

Another log file ReportingEvents.log:

{06524194-C72E-4719-BD26-DCEFA6471B03} 2016-12-09 08:18:15:252-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 OOBE ZDP Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
{F3BE3858-0419-45A7-A760-C97F6634E5A9} 2016-12-09 08:23:36:741-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
{D62C8EE8-A092-4B85-A8DC-45E87D2612BC} 2016-12-09 08:26:24:554-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
{7D4BBB27-B498-4041-9AEF-2B7A8C376D24} 2016-12-09 08:30:56:984-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
{F7E17E09-ABD8-4523-9404-12309945CC61} 2016-12-09 08:42:18:390-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 TrustedInstaller FOD Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
{634ED6ED-D755-47D8-987B-881B8C909AD7} 2016-12-09 08:45:41:325-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
{7299B290-F2BF-4764-83D7-28182A795608} 2016-12-09 08:50:21:278-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
{2DD39B82-6237-43F9-B035-F0E2A2531951} 2016-12-09 08:54:37:498-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
{3751DEC2-1458-4378-9BD4-C9C3AA501C11} 2016-12-09 09:00:38:248-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
{707D7D21-E52B-4607-ACC6-5E7D70F7A2BA} 2016-12-09 09:04:22:247-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
{A95F896A-A357-40B6-AD13-A011C3CEDD4A} 2016-12-09 09:04:22:591-0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 0 updates.
{82AA2F98-B352-49F8-9EEE-AB5713E8C64C} 2016-12-09 09:07:46:216-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
{0BF58FA2-8BE2-4CE0-BA2E-E06B4BBA2840} 2016-12-09 09:07:46:513-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80248014 Update;taskhostw Failure Software Synchronization Windows Update Client failed to detect with error 0x80248014.
{2CFC1DC4-62D3-4DE6-837F-CA7D5781D490} 2016-12-09 09:09:47:685-0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 0 updates.
{AE1AC183-DB92-42F8-A2D6-70BA4DDC952E} 2016-12-09 09:20:48:935-0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 0 updates.
{C0E47BEC-4F18-4A87-A919-54C3BC7554E4} 2016-12-09 09:41:42:248-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.

All,
Windows 7 SP1 and WSUS on Server 2012.

I have an issue where some clients are updating but others seem to be stuck and are not progressing with downloading and installing updates.

I have set the scheduled install time to 1700 and I expect the clients to pull down updates that have been assigned in WSUS. 
I have selected the option to Use the update service console and created appropriate groups under 'All Computers'.
Extract from WindowsUpdate log below:

Is the following client still pulling updates down? It completes with a 'fault: 0x00012c'.
Any insight would be great!

2016-12-0904:24:06:3401228384Agent * Added update {81D78420-DEFD-4425-81C1-CAD24AFAA647}.201 to search result
2016-12-0904:24:06:3401228384Agent * Added update {D782BF08-27FB-40F9-8318-5188C7B690A6}.201 to search result
2016-12-0904:24:06:3401228384Agent * Added update {E502C0A7-9CD8-480A-ABEA-BF5DA5D10914}.201 to search result
2016-12-0904:24:06:3401228384Agent * Added update {14B2992C-B408-4D5E-A2EC-CAB506CB1AE4}.203 to search result
2016-12-0904:24:06:3401228384Agent * Added update {1059C8AC-4568-4146-B02C-370D486787B3}.203 to search result
2016-12-0904:24:06:3401228384Agent * Added update {8FD03E33-55CE-46B3-BEC0-0AEBA9745DBC}.204 to search result
2016-12-0904:24:06:3401228384Agent * Added update {AC2D1F27-4E54-41D1-95BB-5DE4F631B83C}.202 to search result
2016-12-0904:24:06:3401228384Agent * Added update {56989B34-704B-4A90-8C28-B432C53E54BC}.202 to search result
2016-12-0904:24:06:3401228384Agent * Added update {D21BCA57-2381-47F0-8973-75F3EC5B8E63}.202 to search result
2016-12-0904:24:06:3401228384Agent * Added update {D9ECA4D5-9F4E-44C6-83CF-396E9C709CBC}.201 to search result
2016-12-0904:24:06:3401228384Agent * Added update {54D9D0B1-EC0A-4C67-B477-D42E3BA4AFDA}.202 to search result
2016-12-0904:24:06:3401228384Agent * Added update {C19FE2F6-5B9D-4C73-92ED-5CA9A1BC4955}.201 to search result
2016-12-0904:24:06:3401228384Agent * Added update {E3C83C7E-55EE-49A4-A8E6-66DF82119E89}.202 to search result
2016-12-0904:24:06:3401228384Agent * Added update {16740A04-DF6D-4BE3-B27F-F7CDB287EBF2}.205 to search result
2016-12-0904:24:06:3401228384Agent * Added update {DB79590E-38A6-4180-B6D2-900EEB061AC4}.202 to search result
2016-12-0904:24:06:3401228384Agent * Added update {A48BE556-3CA3-4452-9651-7B1F74DF6A32}.201 to search result
2016-12-0904:24:06:3401228384Agent * Added update {7B6B1929-1F54-47A9-B3AD-EAEC4B2B377D}.223 to search result
2016-12-0904:24:06:3401228384Agent * Found 85 updates and 81 categories in search; evaluated appl. rules of 2099 out of 4663 deployed entities
2016-12-0904:24:06:6991228384Agent*********
2016-12-0904:24:06:6991228384Agent**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-12-0904:24:06:6991228384Agent*************
2016-12-0904:24:07:85312281168AU>>##  RESUMED  ## AU: Search for updates [CallId = {3CF45D21-7F18-4006-99CF-ADCD0C7F46E4}]
2016-12-0904:24:07:85312281168AU # 85 updates detected
2016-12-0904:24:08:25912281168AU#########
2016-12-0904:24:08:25912281168AU##  END  ##  AU: Search for updates [CallId = {3CF45D21-7F18-4006-99CF-ADCD0C7F46E4}]
2016-12-0904:24:08:25912281168AU#############
2016-12-0904:24:08:27412281168AUSuccessfully wrote event for AU health state:0
2016-12-0904:24:08:27412281168AUFeatured notifications is disabled.
2016-12-0904:24:08:27412281168AUAU setting next detection timeout to 2016-12-10 01:33:15
2016-12-0904:24:08:27412281168AUSetting AU scheduled install time to 2016-12-09 11:00:00
2016-12-0904:24:08:27412281168AUSuccessfully wrote event for AU health state:0
2016-12-0904:24:08:3061228384ReportREPORT EVENT: {0D009CC2-D7A4-45B6-AD7A-7EB6282916CC}2016-12-08 08:40:44:992-00001188102{00000000-0000-0000-0000-000000000000} 00AutomaticUpdatesSuccessContent InstallInstallation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ‎08 ‎December ‎2016 at 11:00:  - Security Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB954430)
2016-12-0904:24:08:3061228384ReportREPORT EVENT: {44F3E1BA-122F-4365-A019-D5F3F0943BDD}2016-12-08 08:40:45:007-00001188102{00000000-0000-0000-0000-000000000000} 00AutomaticUpdatesSuccessContent InstallInstallation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ‎08 ‎December ‎2016 at 11:00:  - Security Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB954430) - Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB973688)
2016-12-0904:24:08:3061228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3061228384ReportREPORT EVENT: {E2BF5236-0617-41D5-9C08-885523B3F2E6}2016-12-08 11:00:10:416-00001188102{00000000-0000-0000-0000-000000000000} 00AutomaticUpdatesSuccessContent InstallInstallation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ‎09 ‎December ‎2016 at 11:00:  - Update for Windows 7 for x64-based Systems (KB3177467)
2016-12-0904:24:08:3061228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:30612281168AUSuccessfully wrote event for AU health state:0

2016-12-0904:24:08:3061228384ReportREPORT EVENT: {10E4BEC5-148D-4EE8-AC98-61C7A456C26D}2016-12-09 04:24:06:543-00001147101{00000000-0000-0000-0000-000000000000} 00AutomaticUpdatesSuccessSoftware SynchronizationWindows Update Client successfully detected 85 updates.
2016-12-0904:24:08:3061228384ReportREPORT EVENT: {C5F1F361-9945-4ABA-B45B-ECF64884062C}2016-12-09 04:24:06:636-00001156101{00000000-0000-0000-0000-000000000000} 00AutomaticUpdatesSuccessPre-Deployment CheckReporting client status.
2016-12-0904:24:08:3521228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:24:08:3681228384ReportCWERReporter finishing event handling. (00000000)
2016-12-0904:36:54:0691228384PTWARNING: Cached cookie has expired or new PID is available
2016-12-0904:36:54:0691228384PTInitializing simple targeting cookie, clientId = 4ca83683-9b59-4a4a-bb63-1437e51bed04, target group = , DNS name = XXXXXXXXX
2016-12-0904:36:54:0691228384PT Server URL = http://XXXXXXXXXXXXXXXXX:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-12-0904:36:56:8451228384PTWARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2016-12-0904:36:56:8451228384PTWARNING: SOAP Fault: 0x00012c
2016-12-0904:36:56:8451228384PTWARNING:     faultstring:Fault occurred
2016-12-0904:36:56:8451228384PTWARNING:     ErrorCode:ConfigChanged(2)
2016-12-0904:36:56:8451228384PTWARNING:     Message:(null)
2016-12-0904:36:56:8451228384PTWARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2016-12-0904:36:56:8451228384PTWARNING:     ID:d91d6723-fbe1-4492-badf-3b7e2b8c66b0
2016-12-0904:36:56:8921228384PTWARNING: Cached cookie has expired or new PID is available
2016-12-0904:36:56:8921228384PTInitializing simple targeting cookie, clientId = 4ca83683-9b59-4a4a-bb63-1437e51bed04, target group = , DNS name = client.ad.slough.gov.uk
2016-12-0904:36:56:8921228384PT Server URL = http://XXXXXXXXXXXXXXXXX:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-12-0904:36:56:9081228384ReportUploading 2 events using cached cookie, reporting URL = http://XXXXXXXXXXXXXXXXX:8530/ReportingWebService/ReportingWebService.asmx
2016-12-0904:36:56:9231228384ReportReporter successfully uploaded 2 events.
2016-12-0908:55:45:5131228934AUAU setting next sqm report timeout to 2016-12-10 08:55:45
Thanks,
Ash

Hello,

I have a few targeted server groups in on our WSUS server.  However not all servers are showing for example:

Production (70%)

Development (80%)

Domain Controllers (3/4 servers)

Skype Servers (none)

If I go onto the servers that are missing from WSUS and into their GPO and check:

HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU

All the settings look ok, it will show the correct targeted from etc.

I can have 2 servers on the same GPO and only 1 will be on WSUS.

The Windowsupdate log file will list the correct WSUS server too.  This is one that was there the other day and now missing:

We are having issue with a Windows Server 2012 update where windowsupdate.log says below errors which is trying to get the updates from SCCM server. I checked the proxy its proper.

Can you please suggest.

2016-12-09 15:14:40:337  816 fa8 Misc WARNING:     IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 3, GetLastError=2250
2016-12-09 15:15:24:870  816 1244 WS WARNING: Nws Failure: errorCode=0x803d0006
2016-12-09 15:15:24:870  816 1244 WS WARNING: Original error code: 0x80072ee2
2016-12-09 15:15:24:870  816 1244 WS WARNING: There was an error communicating with the endpoint at 'http://SCCM12:8530/ClientWebService/client.asmx'.
2016-12-09 15:15:24:870  816 1244 WS WARNING: There was an error receiving the HTTP reply.
2016-12-09 15:15:24:870  816 1244 WS WARNING: The operation did not complete within the time allotted.
2016-12-09 15:15:24:870  816 1244 WS WARNING: The operation timed out
2016-12-09 15:15:24:871  816 1244 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
2016-12-09 15:15:24:871  816 1244 WS WARNING: Web service call failed with hr = 8024401c.
2016-12-09 15:15:24:871  816 1244 WS WARNING: Current service auth scheme='None'.
2016-12-09 15:15:24:871  816 1244 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2016-12-09 15:15:24:871  816 1244 WS FATAL: OnCallFailure failed with hr=0X8024401C
2016-12-09 15:15:24:871  816 1244 WS WARNING: NWS retry 1 for transient error 0x8024401C
2016-12-09 15:16:28:869  816 1244 WS WARNING: Nws Failure: errorCode=0x803d0006
2016-12-09 15:16:28:869  816 1244 WS WARNING: Original error code: 0x80072ee2
2016-12-09 15:16:28:869  816 1244 WS WARNING: There was an error communicating with the endpoint at 'http://SCCM:8530/ClientWebService/client.asmx'.
2016-12-09 15:16:28:869  816 1244 WS WARNING: There was an error receiving the HTTP reply.
2016-12-09 15:16:28:869  816 1244 WS WARNING: The operation did not complete within the time allotted.
2016-12-09 15:16:28:869  816 1244 WS WARNING: There was an error communicating with the endpoint at 'http://SCCM:8530/ClientWebService/client.asmx'.
2016-12-09 15:16:28:869  816 1244 WS WARNING: There was an error receiving the HTTP reply.
2016-12-09 15:16:28:869  816 1244 WS WARNING: The operation did not complete within the time allotted.
2016-12-09 15:16:28:869  816 1244 WS WARNING: The operation timed out
2016-12-09 15:16:28:869  816 1244 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
2016-12-09 15:16:28:869  816 1244 WS WARNING: Web service call failed with hr = 8024401c.
2016-12-09 15:16:28:869  816 1244 WS WARNING: Current service auth scheme='None'.
2016-12-09 15:16:28:869  816 1244 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2016-12-09 15:16:28:869  816 1244 WS FATAL: OnCallFailure failed with hr=0X8024401C
2016-12-09 15:16:28:869  816 1244 WS WARNING: NWS retry 2 for transient error 0x8024401C
2016-12-09 15:17:34:760  816 1244 WS WARNING: Nws Failure: errorCode=0x803d0006
2016-12-09 15:17:34:760  816 1244 WS WARNING: Original error code: 0x80072ee2
2016-12-09 15:17:34:760  816 1244 WS WARNING: There was an error communicating with the endpoint at 'http://SCCM:8530/ClientWebService/client.asmx'.
2016-12-09 15:17:34:760  816 1244 WS WARNING: There was an error receiving the HTTP reply.
2016-12-09 15:17:34:760  816 1244 WS WARNING: The operation did not complete within the time allotted.
2016-12-09 15:17:34:760  816 1244 WS WARNING: There was an error communicating with the endpoint at 'http://SCCM:8530/ClientWebService/client.asmx'.
2016-12-09 15:17:34:760  816 1244 WS WARNING: There was an error receiving the HTTP reply.
2016-12-09 15:17:34:760  816 1244 WS WARNING: The operation did not complete within the time allotted.
2016-12-09 15:17:34:760  816 1244 WS WARNING: There was an error communicating with the endpoint at 'http://ATLEISSCCM12P1.eis.equifax.com:8530/ClientWebService/client.asmx'.
2016-12-09 15:17:34:760  816 1244 WS WARNING: There was an error receiving the HTTP reply.
2016-12-09 15:17:34:760  816 1244 WS WARNING: The operation did not complete within the time allotted.
2016-12-09 15:17:34:760  816 1244 WS WARNING: The operation timed out
2016-12-09 15:17:34:760  816 1244 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
2016-12-09 15:17:34:760  816 1244 WS WARNING: Web service call failed with hr = 8024401c.
2016-12-09 15:17:34:760  816 1244 WS WARNING: Current service auth scheme='None'.
2016-12-09 15:17:34:760  816 1244 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2016-12-09 15:17:34:760  816 1244 WS FATAL: OnCallFailure failed with hr=0X8024401C
2016-12-09 15:17:34:760  816 1244 IdleTmr WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 7) stopped; does use network; is at background priority
2016-12-09 15:17:34:760  816 1244 PT WARNING: PTError: 0x8024401c
2016-12-09 15:17:34:760  816 1244 PT WARNING: GetCookie_WithRecovery failed : 0x8024401c
2016-12-09 15:17:34:760  816 1244 PT WARNING: RefreshCookie failed: 0x8024401c
2016-12-09 15:17:34:760  816 1244 PT WARNING: RefreshPTState failed: 0x8024401c
2016-12-09 15:17:34:760  816 1244 PT   + SyncUpdates round trips: 0
2016-12-09 15:17:34:760  816 1244 PT WARNING: Sync of Updates: 0x8024401c
2016-12-09 15:17:34:760  816 1244 PT WARNING: SyncServerUpdatesInternal failed: 0x8024401c
2016-12-09 15:17:34:760  816 1244 Agent   * WARNING: Failed to synchronize, error = 0x8024401C
2016-12-09 15:17:34:760  816 1244 Agent   * WARNING: Exit code = 0x8024401C
2016-12-09 15:17:34:760  816 1244 Agent *********
2016-12-09 15:17:34:760  816 1244 Agent **  END  **  Agent: Finding updates [CallerId = CcmExec  Id = 1]
2016-12-09 15:17:34:760  816 1244 Agent *************
2016-12-09 15:17:34:760  816 1244 Agent WARNING: WU client failed Searching for update with error 0x8024401c
2016-12-09 15:17:34:760  816 1244 IdleTmr WU operation (CSearchCall::Init ID 1, operation # 5) stopped; does use network; is not at background priority
2016-12-09 15:17:34:760  816 1244 IdleTmr Decremented idle timer priority operation counter to 1
2016-12-09 15:17:34:760  816 13b8 Agent ***  END  ***  Queueing Finding updates [CallerId = Device Driver Retrieval Client  Id = 2]
2016-12-09 15:17:34:760 3940 d80 COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = CcmExec]
2016-12-09 15:17:34:760  816 13b8 Agent *************
2016-12-09 15:17:34:760  816 13b8 Agent ** START **  Agent: Finding updates [CallerId = Device Driver Retrieval Client  Id = 2]
2016-12-09 15:17:34:760  816 13b8 Agent *********
2016-12-09 15:17:34:760  816 13b8 Agent   * Online = Yes; Ignore download priority = No
2016-12-09 15:17:34:760  816 13b8 Agent   * Criteria = "Type='Driver'"
2016-12-09 15:17:34:760  816 13b8 Agent   * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2016-12-09 15:17:34:760  816 13b8 Agent   * Search Scope = {Machine}
2016-12-09 15:17:34:760  816 13b8 Agent   * Caller SID for Applicability: S-1-5-18
2016-12-09 15:17:34:760  816 13b8 Agent   * RegisterService is set
2016-12-09 15:17:34:760 3940 d80 COMAPI   - Updates found = 0
2016-12-09 15:17:34:760 3940 d80 COMAPI   - WARNING: Exit code = 0x00000000, Result code = 0x8024401C
2016-12-09 15:17:34:760 3940 d80 COMAPI ---------
2016-12-09 15:17:34:760 3940 d80 COMAPI --  END  --  COMAPI: Search [ClientId = CcmExec]
2016-12-09 15:17:34:760 3940 d80 COMAPI -------------
2016-12-09 15:17:34:760 3940 d80 COMAPI WARNING: Operation failed due to earlier error, hr=8024401C
2016-12-09 15:17:34:760 3940 d80 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024401C)
2016-12-09 15:17:34:760  816 13b8 SLS Retrieving SLS response from server...
2016-12-09 15:17:34:760  816 13b8 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=538&L=en-US&P=&PT=0x7&WUA=7.9.9600.17489
2016-12-09 15:17:39:772  816 c38 Report REPORT EVENT: {6E7787F6-F7B0-483F-B541-8817A05ABF2D} 2016-12-09 15:17:34:760-0500 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
2016-12-09 15:17:39:772  816 c38 Report CWERReporter::HandleEvents - WER report upload completed with WER status 0x8 (hr=0)
2016-12-09 15:17:39:772  816 c38 Report WER Report sent: 7.9.9600.17489 0x8024401c(0) 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2016-12-09 15:17:39:772  816 c38 Report CWERReporter finished handling 1 events. (00000000)
2016-12-09 15:17:55:786  816 13b8 Misc WARNING: Send failed with hr = 80072ee2.
2016-12-09 15:17:55:786  816 13b8 Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
2016-12-09 15:17:55:786  816 13b8 Misc WARNING: Send request failed, hr:0x80072ee2
2016-12-09 15:17:55:786  816 13b8 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=538&L=en-US&P=&PT=0x7&WUA=7.9.9600.17489>. error 0x80072ee2
2016-12-09 15:17:55:786  816 13b8 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2016-12-09 15:17:55:786  816 13b8 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2016-12-09 15:17:55:786  816 13b8 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2016-12-09 15:17:55:786  816 13b8 SLS FATAL: SLS:CSLSDownloader::GetUrlContent: DoFileDownload failed with 0x80072ee2.
2016-12-09 15:17:55:786  816 13b8 SLS FATAL: GetResponse failed with hresult 0x80072ee2...
2016-12-09 15:17:55:786  816 13b8 EP FATAL: EP: CSLSEndpointProvider::GetWUClientData - failed to get SLS data, error = 0x80072EE2
2016-12-09 15:17:55:786  816 13b8 EP FATAL: EP: CSLSEndpointProvider::GetEndpointFromSLS - Failed to get client data, error = 0x80072EE2
2016-12-09 15:17:55:786  816 13b8 EP FATAL: Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x80072EE2
2016-12-09 15:17:55:786  816 13b8 PT WARNING: PTError: 0x80072ee2
2016-12-09 15:17:55:786  816 13b8 PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee2
2016-12-09 15:17:55:786  816 13b8 Agent   * WARNING: Exit code = 0x80072EE2
2016-12-09 15:17:55:786  816 13b8 Agent *********
2016-12-09 15:17:55:786  816 13b8 Agent **  END  **  Agent: Finding updates [CallerId = Device Driver Retrieval Client  Id = 2]
2016-12-09 15:17:55:786  816 13b8 Agent *************
2016-12-09 15:17:55:786  816 13b8 Agent WARNING: WU client failed Searching for update with error 0x80072ee2

Hi, everybody:

 I set up a WSUS in my LAN, however it's HardDrive is too small to store ALL update files(total space: 250GB) , I only have to choose some important update, and the rest of updates such as drivers is not saved in local WSUS.

However, once the client in my LAN need to update those files which is not in local WSUS, the client seems to get them from microsoft WSUS, and the download progress slow down again.

Is it possible or can be set WHEN a client download a update file which is not exist in local WSUS, it will also save a copy in local WSUS, and next time when another client also need this update, it just can download from local WSUS, need no download from microsoft again??

We provide VM hosting for development groups and we have a customer who wishes to review all Microsoft updates before they are applied.  Right now, we are just using WSUS and applying all updates to all machines every Sunday night.

This customer wants to be able to review updates and approve or deny them to be installed.  What is the best way for us to do this?  I guess I could approve all needed/failed updates and then let the customer decide if they want to install it or not, but I think the customer will want us to handle that for them.

I One of my customers is running Windows 2008 Small Business Server. Windows Update Contant folders had been correctly moved away from C drive soon after installation of the server (WSUS Content). That folder is about 8 GB big (small network, 8 computers). The susdb.mdf file however, is still on the C drive and is a whopping 15.1 GB big. I believe this is not according to plan. I have done some server cleanup through the specific WSUS interface, but the biggest chunk just hangs. What can I do? None of the suggestions I found have worked.

Kind regards,

Wouter Pinkhof

Wouter Pinkhof PINKH bvba, PC-Hulp.com