I have installed a new Windows 2019 server with the WSUS feature. My environment is mostly Windows 7 with a handful of Windows 10 PC's. Most of the Windows 10 PC's are communicating with WSUS and getting updates. About a third of the Windows 7 PC's are failing - (if I pull updates from Microsoft online updates install without issue). Please see attached screen shot. I have tried multiple fixes to no avail. 

Thanks, 

Milty 

Win 7 update error

milty60

I have an offline Windows Server 2016 WSUS server patched to the current February 2019 SSU and CU.  It has a set of approved updates on it for Windows Server 2016.

None of my Windows Server 2016 clients are reporting to it, however they are able to check and download updates without issue.  The client on the WSUS server can't report to itself either.

WSUS server and statistics location is set via GPO to http://FQDN:8530. Automatic update mode is set to 3.  Registry values are confirmed to be set by the GPO.  The Windows Update diagnostic tool has been run against both server and clients without effect.  I have rebooted both server and clients without effect.

I have tried manual scan: usoclient refreshsettings startscan

I have tried manual reporting: wuauclt /reportnow

I have tried manually stopping wuauserv and clearing out the SoftwareDistribution folder.

Nothing I have done makes any difference.  I cannot work out why the clients won't check in.

Examination of the WindowsUpdate log shows that the "Report" component on the client never logs anything:

2019/03/08 03:30:24.5819798 940   1092  Shared          * START * Service startup
2019/03/08 03:30:24.6036711 940   1092  Agent           WU client version 10.0.14393.2608
2019/03/08 03:30:24.6039172 940   1092  Agent           SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2019/03/08 03:30:24.6040146 940   1092  Agent           Base directory: C:\windows\SoftwareDistribution
2019/03/08 03:30:24.6044155 940   1092  Agent           Datastore directory: C:\windows\SoftwareDistribution\DataStore\DataStore.edb
2019/03/08 03:30:24.6230313 940   1092  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2019/03/08 03:30:24.6230516 940   1092  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019/03/08 03:30:24.6234764 940   1092  Shared          Network state: Connected
2019/03/08 03:30:24.6256422 940   1092  Misc            LoadHistoryEventFromRegistry completed, hr = 8024000C
2019/03/08 03:30:24.6268401 940   1092  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2019/03/08 03:30:24.6268469 940   1092  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019/03/08 03:30:24.6268528 940   1092  Shared          Power status changed
2019/03/08 03:30:24.6298602 940   1092  Agent           Initializing global settings cache
2019/03/08 03:30:24.6298612 940   1092  Agent           WSUS server: http://updates.REDACTED:8530
2019/03/08 03:30:24.6298619 940   1092  Agent           WSUS status server: http://updates.REDACTED:8530
2019/03/08 03:30:24.6298625 940   1092  Agent           Alternate Download Server: NULL
2019/03/08 03:30:24.6298632 940   1092  Agent           Fill Empty Content Urls: No
2019/03/08 03:30:24.6298638 940   1092  Agent           Target group: (Unassigned Computers)
2019/03/08 03:30:24.6298645 940   1092  Agent           Windows Update access disabled: No
2019/03/08 03:30:24.6302243 940   1092  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-03-08 04:31:32, not idle-only, not network-only
2019/03/08 03:30:24.6324420 940   1092  Agent           Initializing Windows Update Agent
2019/03/08 03:30:24.6325035 940   1092  DownloadManager Download manager restoring 0 downloads
2019/03/08 03:30:24.6325431 940   1092  Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2019/03/08 03:30:24.6336617 940   3372  Shared          Effective power state: AC
2019/03/08 03:30:24.6336627 940   3372  DownloadManager Power state change detected. Source now: AC
2019/03/08 03:30:43.6510824 940   664   ComApi          * START *   Init Search ClientId = UpdateOrchestrator
2019/03/08 03:30:43.6510859 940   664   ComApi          * START *   Search ClientId = UpdateOrchestrator
2019/03/08 03:30:43.7129808 940   664   Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 1]
2019/03/08 03:30:43.7129860 940   664   Agent           Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2019/03/08 03:30:43.7130257 940   664   ComApi          Search ClientId = UpdateOrchestrator
2019/03/08 03:30:43.7181437 940   4928  Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 1]
2019/03/08 03:30:43.7228157 940   4928  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 1
2019/03/08 03:30:43.7228173 940   4928  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
2019/03/08 03:30:43.7228183 940   4928  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""
2019/03/08 03:30:43.7228215 940   4928  Agent           ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2019/03/08 03:30:43.7228221 940   4928  Agent           Search Scope = {Machine}
2019/03/08 03:30:43.7228252 940   4928  Agent           Caller SID for Applicability: S-1-5-21-3731600443-1732068735-1633618523-500
2019/03/08 03:30:43.7228260 940   4928  Agent           ProcessDriverDeferrals is set
2019/03/08 03:30:43.7228265 940   4928  Agent           RegisterService is set
2019/03/08 03:30:43.7259109 940   4928  Misc            EP: error: 0x8024500C : - failed to get SLS data
2019/03/08 03:30:43.7259119 940   4928  Misc            EP: error: 0x8024500C: GetSecondaryServicesEnabledState failed
2019/03/08 03:30:43.7259151 940   4928  Agent           AutoRecovery: DetectAndToggleServiceState failed 0x8024500c
2019/03/08 03:30:43.7291641 940   4928  Misc            Got WSUS Client/Server URL: http://updates.REDACTED:8530/ClientWebService/client.asmx""
2019/03/08 03:30:43.9371533 940   4928  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://updates.REDACTED:8530/ClientWebService/client.asmx
2019/03/08 03:30:43.9373102 940   4928  ProtocolTalker  OK to reuse existing configuration
2019/03/08 03:30:43.9373142 940   4928  ProtocolTalker  Existing cookie is valid, just use it
2019/03/08 03:30:43.9373279 940   4928  ProtocolTalker  PTInfo: Server requested registration
2019/03/08 03:30:44.5053826 940   4928  WebServices     Auto proxy settings for this web service call.
2019/03/08 03:30:44.5278535 940   4928  ProtocolTalker  PTInfo: syncing with server using normal query
2019/03/08 03:30:44.5337456 940   4928  ProtocolTalker  SyncUpdates round trips: 2
2019/03/08 03:30:45.5174394 940   4928  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://updates.REDACTED:8530/ClientWebService/client.asmx
2019/03/08 03:30:45.5174410 940   4928  ProtocolTalker  OK to reuse existing configuration
2019/03/08 03:30:45.5174442 940   4928  ProtocolTalker  Existing cookie is valid, just use it
2019/03/08 03:30:45.5174455 940   4928  ProtocolTalker  PTInfo: Server requested registration
2019/03/08 03:30:45.6010503 940   4928  Agent           Policy driven service does not support additional filtering on feature updates.
2019/03/08 03:30:45.6010537 940   4928  Agent           Found 0 updates and 84 categories in search; evaluated appl. rules of 442 out of 736 deployed entities
2019/03/08 03:30:45.6228588 940   4928  Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 1
2019/03/08 03:30:45.6234951 940   3088  ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
2019/03/08 03:30:45.6239361 940   3088  ComApi          Updates found = 0
2019/03/08 03:30:45.6239370 940   3088  ComApi          * END *   Search ClientId = UpdateOrchestrator
2019/03/08 03:30:45.6248565 940   664   ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
2019/03/08 03:35:32.4174453 940   784   ComApi          * START *   Init Search ClientId = UpdateOrchestrator
2019/03/08 03:35:32.4174517 940   784   ComApi          * START *   Search ClientId = UpdateOrchestrator
2019/03/08 03:35:32.4348552 940   784   Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 2]
2019/03/08 03:35:32.4348596 940   784   Agent           Removing service 00000000-0000-0000-0000-000000000000 from sequential scan list
2019/03/08 03:35:32.4348627 940   784   Agent           Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2019/03/08 03:35:32.4348905 940   784   ComApi          Search ClientId = UpdateOrchestrator
2019/03/08 03:35:32.4395500 940   1956  Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 2]
2019/03/08 03:35:32.4441996 940   1956  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 2
2019/03/08 03:35:32.4442009 940   1956  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
2019/03/08 03:35:32.4442021 940   1956  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""
2019/03/08 03:35:32.4442054 940   1956  Agent           ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2019/03/08 03:35:32.4442061 940   1956  Agent           Search Scope = {Machine}
2019/03/08 03:35:32.4442092 940   1956  Agent           Caller SID for Applicability: S-1-5-21-3731600443-1732068735-1633618523-500
2019/03/08 03:35:32.4442099 940   1956  Agent           ProcessDriverDeferrals is set
2019/03/08 03:35:32.4442104 940   1956  Agent           RegisterService is set
2019/03/08 03:35:32.4470435 940   1956  Misc            EP: error: 0x8024500C : - failed to get SLS data
2019/03/08 03:35:32.4470444 940   1956  Misc            EP: error: 0x8024500C: GetSecondaryServicesEnabledState failed
2019/03/08 03:35:32.4470473 940   1956  Agent           AutoRecovery: DetectAndToggleServiceState failed 0x8024500c
2019/03/08 03:35:32.4501433 940   1956  Misc            Got WSUS Client/Server URL: http://updates.REDACTED:8530/ClientWebService/client.asmx""
2019/03/08 03:35:32.6071937 940   1956  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://updates.REDACTED:8530/ClientWebService/client.asmx
2019/03/08 03:35:32.6073465 940   1956  ProtocolTalker  OK to reuse existing configuration
2019/03/08 03:35:32.6073547 940   1956  ProtocolTalker  OK to reuse existing configuration
2019/03/08 03:35:32.6073801 940   1956  Misc            Got WSUS SimpleTargeting URL: http://updates.REDACTED:8530""
2019/03/08 03:35:32.6075945 940   1956  ProtocolTalker  Initializing simple targeting cookie, clientId = 263f9e73-42ab-4b7a-adf3-9590311f3c77, target group = <NULL>, DNS name = ednsbar001.REDACTED
2019/03/08 03:35:32.6075957 940   1956  ProtocolTalker    Server URL = http://updates.REDACTED:8530/SimpleAuthWebService/SimpleAuth.asmx

I'm wondering what is the best way to remove a patch, KB4487017, from WSUS but not my clients just yet?  We've ran into some problems with Chrome and BSODs on our Windows 10 1803 clients which look very similar to what's reported here. 

In that article he says uninstalling and reinstalling KB4487017 on his clients seems to have fixed the issue, so what I'd like to do is remove the patch from WSUS so that it gets redownloaded, as I know MS sometimes re-releases updates with "fixes" but does not documented this.  I'll then locally uninstall the update from a couple clients where the issue has been reported, scan for updates and have them pull the new, hopefully "fixed" update.

Thanks.

Hi IT Pro's,

I am looking forward tp hearing your opinion.

Which RAID is best for WSUS.

We are preparing new (old) server  (HPE DL360p Gen8) for that purpose and I wonder which option is the best.

Do you think that RAID 5 will be OK?

Thank you

Hello Guys,

Dont know why but just checked all computers status on wsus server and found that all computers not reposted to wsus server since 30 days 

can you please tell me step to fix this issue 

Thanks,

Madhukar  

I need to reinstall WSUS to clear some 3rd party updates from it and start over

Everything seemed to work okay and it started to download over 300GB afterward.

Once that was completed, it still said there was 2 files that needed to be downloaded.

The event viewer has an error message "file cert verification failure", event id 364, for a Windows 10 update cab.

I've looked online but can't find anything that fixes this. I even ran the wsus reset and re-downloaded everything but still stuck at 2 files needed to be downloaded.

Don't think its a firewall issue since I re-installed on the same server.

Don't think it is a Windows 2012 R2 patch since again its from the same server that was functioning normally.

SSL issue? Application Pool? IIS?

Does removing the WSUS role and re-adding it wipe out some sort of patch?

Heath

This situation started a few months ago.

When ever new updates emerge, they stuck at pending install, forever (I usually don't turn off my PC at all for days). In the mean time, my system start to be hogged by a process called the svhcost.exe (netsvc-p) which takes half my CPU and my disk activity alike. 

Windows 10 Pro 1803 OS build 17134.472 under domain environment. Update is automatically approved by WSUS.

I have a PC at home which auto updates just fine but most computer in my domain that are 1803, has this hiccup.

The process keeps reading the files I do not know detail of. But apparently it's related to Windows Update.

In the mean time the system get laggy coz all the CPU eaten up. The settings windows is ridiculously slow in response and often shows up white. Until I finally I found out that I can go to "Advanced options" and flip the option "Allow metered network". After I flip the options, update start to show 0% and then start installing.

Mind this: I need to FLIP this option every time new updates come and the system is acting up. Letting it stay on or off just do not make a different.

Does any one experience this? I can't think of a valid explanation. 

Hi Team,

We have Windows systems scattered in 5 regions.

Country 1            7000 Systems

Country 2            700 Systems

Country 3             4800

Country 4           6000

Country 5            2000

We are trying to plan the WSUS environment.

Environment:

Server - Windows Server 2008, 2012 & 2016 (Approx 4500 servers)

Desktop - Windows 7/8.1/10 (Approx 16,000 clients)

SQL - Server 2012R2 Express

WSUS Setup:

WSUS Central server has 5 Upstream Servers, Each Upstream server has max 10 downstream servers

All servers are in replica mode of WSUS Central.

We are planning to setup a Upstream Server in Country 1 and one Replica Servers.

For the rest of the countries Keeping 2 Replica servers for each country, I mean Country 2,3,4,5.

To Provide High availability we are using the F5 Load Balancer GTM, so that wsus clients can connect the nearest WSUS server.

Please review and suggest about this design. would like to understand having 9 Replica servers is okay or we will face any issues. 

Ravi Ch

Hi,

Does anyone tried using a WSUS 2016 server in a Server 2003 AD? Trying to get a WSUS 2016 push updates to Server 2003 AD.

Hi team,

We are facing one issue in installing KB4486563.Getting below error can some one please advice how to fix the issue.

Windows update "Security Update for Windows (KB4486563)" could not be installed because of error 2147956481 "The referenced assembly could not be found." (Command line: ""C:\Windows\system32\wusa.exe" "D:\Temp\kb4486563-x64.msu"       ")

os:2008 r2 sp1

I ran sfc /scan now and result is pass

Is database backup a viable method to move metadata between WSUS instances?

I've tried the "accepted" method using wsusutil export/import but the import takes way too long to be viable (~7 hours) and doesn't contain approvals.

Obviously the version of WSUS would have to match, but other than that does anyone know if the WSUS database contains installation-specific data? The collected computer data is not a concern as it would be discarded anyway.

I have a newly built WSUS server on Windows Server 2012 R2. I am able to add and see over 60 machines however, wsus only displays a maximum of 33 machines. I have a few different groups and I am only adding the QA and DEV boxes right now. If I run check for updates on the client it will show up in the WSUS group and that happens for all but once the number reaches 33, it will add the new one and drop an existing machine that was already there. 

Does anyone know why that is happening. 

Hi everyone,

just to make sure that i have to add this manually and it is not a problem with my WSUS server.

I cannot find this update for Win2016 on my WSUS. Other updates / patches (e.g. for the last tuesday) are synced and downloaded. Is it just not available for WSUS for now?

And what are the rules which updates make it? 

<h3>Regards Stephan</h3>

We are using Windows Server 2016 Essentials and provide updates via WSUS for 6 laptops with Windows 10 Pro. The server was installed in April 2018 and the 6th laptop was purchased and joined to the domain in February 2019. With this 6th laptop we're not able to get updates from WSUS. While trying to fix this we also noticed that our Windows server has the same problem itself, however everything works as expected for the other 5 laptops:

The "checking for updates..." screen loads forever and the event viewer shows this exception after a few minutes:

Name der fehlerhaften Anwendung: svchost.exe_wuauserv, Version: 10.0.14393.0, Zeitstempel: 0x57899b1c
Name des fehlerhaften Moduls: wuaueng.dll, Version: 10.0.14393.2608, Zeitstempel: 0x5bd1346f
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x000000000005a70c
ID des fehlerhaften Prozesses: 0xb70
Startzeit der fehlerhaften Anwendung: 0x01d4d7e36980242a
Pfad der fehlerhaften Anwendung: C:\Windows\system32\svchost.exe
Pfad des fehlerhaften Moduls: c:\windows\system32\wuaueng.dll
Berichtskennung: 9485e301-f9aa-4133-8e34-d2e286c37421
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

0xc00000fd is a stack overflow exception, as far as I know.

We've been trying to fix this now for weeks. Here is what we did:

• this troubleshooter-tool (https://support.microsoft.com/de-de/help/4027322/windows-update-troubleshooter) - it requires a restart. In the end the tool has the same problem like the Windows Update GUI, it loads forever
• Reset Windows Update components (https://support.microsoft.com/de-de/help/971058/how-do-i-reset-windows-update-components) - we did that multiple times
• wsusutil.exe usecustomwebsite true
• wsusutil.exe checkhealth - the event view contains a warning that one of the clients didn't connect within 30 days, which is true
• DISM + sfc /scannow (https://support.microsoft.com/de-de/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness) - all files seem to be good
• cleaned WSUS
• re-installed WSUS via Server Manager
• disabled the WSUS-GPO so that all clients connect to Microsoft Update directly. This allowed us to update the new laptop and the server itself.

We noticed that someone had the same problem here:

https://social.technet.microsoft.com/Forums/en-US/ba8bb1ad-ea2f-4b2b-9c68-c7cf8c8f1acb/windows-10-windows-update-crash-with-wuauengdll-exception-code-0xc00000fd?forum=win10itprogeneral

...But the solution didn't work for us. Also we don't have access to the mentioned wsus-clean-script.

wuaueng.dll versions:

• 10.0.17763.292 - working laptops and non working laptop
• 10.0.14393.2608 - windows server 2016 essentials = wsus server

Hey guys,

I'm having an issue with a few of my windows servers. They are all Windows Server 2012 R2. I have configured my windows server to automatically download updates, but install them on a scheduled date. However, when a new update is ready to be installed, I monitored the server at the time of its scheduled installation time, but the automatic update did not start at all. In my group policy editor, Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update, I have "Configure Automatic Updates" enabled with the option of 4 (Auto download and schedule the install). As far as I know, I don't think there are any other settings I need to touch here.

Checking inside the event viewer, I filtered the logs to view if the automatic update service started at all, but it was not found anywhere.

Any help would be very appreciated on this.

I've built an offline wsus server, followed MS recommended path and imported updates but 'Installed' hangs up at 96% for majority of updates and 'File Status' says 'update is downloading' (for 5 days now).  Initially I had imported 297GB but declined the superseded; mirrored my export server settings, approved updates and disabled firewall but no love.  When I run the bitstransfer report see transient errors but not sure why.  I've run wsusutil.exe reset, rebooted but still no joy.   Bitstransfer report below and any help appreciated, thanks.

Get-BitsTransfer -AllUsers | Select -ExpandProperty FileList: 

RemoteName         : http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10 wi
                     rtm_fr-fr.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt
LocalName          : E:\Updates\WsusContent\7B\D295A466F37BEA4ADC76E5A6DC66AC40D88F4D7B.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10 wi
                     rtm_cs-cz.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt
LocalName          : E:\Updates\WsusContent\8C\E33F368B8B4EC16440A7A3CE7B23CDF74F0FE68C.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10 wi
                     rtm_uk-ua.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt
LocalName          : E:\Updates\WsusContent\14\F18069CC699724F9B43576B5B0E7957BB39ABE14.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10 wi
                     rtm_it-it.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt
LocalName          : E:\Updates\WsusContent\39\FA5CF62819F54FD7E076F2E3369B28AE06381D39.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10 wi
                     rtm_da-dk.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt
LocalName          : E:\Updates\WsusContent\75\FB4E0A894D8688638B97237E3E44C52341EB8675.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10 wi
                     rtm_ru-ru.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt
LocalName          : E:\Updates\WsusContent\95\F69588F2793ECC3737AFB8FE0AE508743E343595.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                     _hindi_hi-in-a4b8d698-7531-4af6-868d-e144c0dc9631.txt
LocalName          : E:\Updates\WsusContent\54\02F693452E242AD82636B4C589385A586F931B54.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                     _romanian_ro-ro-a4b8d698-7531-4af6-868d-e144c0dc9631.txt
LocalName          : E:\Updates\WsusContent\95\241B583BCB3D6637FF131EDFD80D52ABCDDF4595.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                     _norwegian (bokmal)_nb-no-a4b8d698-7531-4af6-868d-e144c0dc9631.txt
LocalName          : E:\Updates\WsusContent\E3\16D75AB586DCE5E5E685113D8CC14ECB249F4DE3.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0

RemoteName         : http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                     _japanese_ja-jp-a4b8d698-7531-4af6-868d-e144c0dc9631.txt
LocalName          : E:\Updates\WsusContent\E1\2C3493C9BBB8AB5861BD3035D8DC05A1ED24C6E1.txt
IsTransferComplete : False
BytesTotal         : -1
BytesTransferred   : 0
***************************************************************************************************************************************

PS C:\windows\system32> Get-BitsTransfer -AllUsers | Select *


JobId                   : 6e975877-1d5f-4198-bc3c-41fa6dda74e1
DisplayName             : 93fa78c8-d070-4e1e-a149-ae724f6f6d56
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:18 PM
ModificationTime        : 3/11/2019 11:55:24 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10
                          win7 rtm_fr-fr.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 0e45ef91-5fe5-4668-810a-d25b5de58cb4
DisplayName             : 718a5cbc-940c-4908-ad99-f3ac71a7dfbe
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:33 PM
ModificationTime        : 3/11/2019 11:55:31 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10
                          win7 rtm_cs-cz.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 8655d13c-53d9-4603-a25b-a4ebef19f345
DisplayName             : cd616634-3049-43f2-9dcf-986553026e13
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:33 PM
ModificationTime        : 3/11/2019 11:55:31 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10
                          win7 rtm_uk-ua.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 147c3c81-acae-4878-b0bb-6a2471b0e616
DisplayName             : c8cf740b-af34-41c5-856c-af851b15d6d9
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:43 PM
ModificationTime        : 3/11/2019 11:55:43 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10
                          win7 rtm_it-it.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 5d6c9e19-4738-4192-981a-d2d169d9aedd
DisplayName             : b2a3d580-1a50-4da4-b9bb-32caf217299c
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:43 PM
ModificationTime        : 3/11/2019 11:55:43 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10
                          win7 rtm_da-dk.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 6ae1e0e2-ad5d-474f-b0da-93b585bd1432
DisplayName             : ef4924f5-9d4e-45a2-bbb6-8f9a3f0ac06c
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:43 PM
ModificationTime        : 3/11/2019 11:55:43 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/msdownload/update/v5/eula/use terms_supp_ie10
                          win7 rtm_ru-ru.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 7d90ce23-8405-4f08-99ca-c35c0000af24
DisplayName             : aa365c3b-e87d-4245-8e29-c5ab427a7e25
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:53 PM
ModificationTime        : 3/11/2019 11:55:59 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                          _hindi_hi-in-a4b8d698-7531-4af6-868d-e144c0dc9631.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 9ab700a1-1a90-4384-9cbf-d94e08958800
DisplayName             : d5846742-9784-4f2a-b1b0-d609ab22f62b
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:53 PM
ModificationTime        : 3/11/2019 11:55:59 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                          _romanian_ro-ro-a4b8d698-7531-4af6-868d-e144c0dc9631.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : 4f28a773-744b-42e9-b7b5-16b32b4cce72
DisplayName             : 7e8f0301-12e2-4615-94bc-05ba0da34ae1
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:29:53 PM
ModificationTime        : 3/11/2019 11:55:59 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                          _norwegian (bokmal)_nb-no-a4b8d698-7531-4af6-868d-e144c0dc9631.txt}
ProxyList               :
ProxyBypassList         :

JobId                   : be20ccd5-a8d4-46eb-98ee-d7f540a8dd69
DisplayName             : 87b781e9-38c9-4c85-92db-6e48aac0979c
Description             : SUSFile
TransferType            : Download
JobState                : TransientError
TransferPolicy          : Always
OwnerAccount            : NT AUTHORITY\NETWORK SERVICE
Priority                : Foreground
RetryInterval           : 600
RetryTimeout            : 86400
TransientErrorCount     : 99
ProxyUsage              : NoProxy
ErrorContext            : RemoteFile
ErrorCondition          :
InternalErrorCode       : -2147012889
ErrorDescription        : The server name or address could not be resolved

ErrorContextDescription : The error occurred while the remote file was being processed.

BytesTotal              : -1
BytesTransferred        : 0
FilesTotal              : 1
FilesTransferred        : 0
CreationTime            : 3/10/2019 7:30:14 PM
ModificationTime        : 3/11/2019 11:56:18 AM
TransferCompletionTime  : 1/1/0001 12:00:00 AM
FileList                : {http://wsus.ds.download.windowsupdate.com/d/msdownload/eula/unicodeuse terms_supp_ie11 rtw
                          _japanese_ja-jp-a4b8d698-7531-4af6-868d-e144c0dc9631.txt}
ProxyList               :
ProxyBypassList         :

Hi,

I have Update Rollups node that I usually don't touch.

It was added when I run upgrade to IE11 (was necessary for getting IE11).

Today I clicked on it and found bunch of not approved updates.

If I remember correctly they are not must to install as critical or security.

Can somebody confirm?

I guess Security Monthly Rollup should cover "holes" in OS...

Thx.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Standard problem with WSUS Cleanup Wizard timing out without removing any unnecessary updates. SBS2K8. WSUS 3. 6000+ unnecessary updates awaiting approval. Huge database. Unresponsive SQL server. Lot of people have this problem:
http://social.technet.microsoft.com/Forums/en-US/9724778f-c1a0-4d24-82e4-8b2d054257d6/wsus-hangs-on-cleanup-wizard-for-unused-updates-then-disconnects-from-console?forum=winserverwsus

Drives are regularly defragged in the background. Not gonna shut down the server and have down time just to fix this.

Tried the reindexing script from
http://technet.microsoft.com/en-us/library/dd939795(WS.10).aspx
, (don't copy the command line, it has weird characters in it, just type it in manually.) and it completes but it didn't improve anything.

Found this:
http://wsus.codeplex.com/releases/view/17612
and it also times out.

Found this comment:
For anyone who is getting Timeout Expired with obsolete updates. I have a solution! Use server name : "
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
" to connect with SQL managment studio. Once connected manually run "
exec spGetObsoleteUpdatesToCleanup
". This will return a list of obsolete ID's. For each one run "
exec spDeleteUpdate @localUpdateID=000000
", where 000000 is the ID. For myself I found the first ID in the list took a full 37 minutes to delete and then after that I could run the cleanup through the GUI as per usual.

by jjdacl on Apr 23 at 12:55 PM 

Found that you actually need to do:
USE SUSDB
GO
exec spGetObsoleteUpdatesToCleanup

And to connect in the first place, I had to hit Options, and select named pipe from the middle pull down. 

First delete took 6 minutes and memory has spiked up to almost 15GB in use out of 16GB physical. But the WSUS console (Update Services) still shows the same number of old updates. Failure? I don't think so: I'm running the cleanup wizard again and so far it isn't timing out... It has run over night, and has made some progress; the bar has moved perhaps 5%. 

So... My take is that the SQL server causes this problem when there is to much data, because the indexes are poorly designed (not because the indexes need to be re-indexed) causing the first query to time out, which causes the cleanup to fail. Once you get past that first deletion, and have everything loaded into memory, the cleanup tool can stay connected long enough to delete each unneeded update.

Next step will be to find a command line method, such as:
http://wsus.codeplex.com/releases/view/17612
and put it into the task scheduler like Microsoft should have done at the beginning to keep this from getting out of hand.

P.S. Lawrence Garvin, please do NOT reply to this; I have no need of your arrogance.

Hello,

I'm having difficulty establishing a connection in the WSUS  console.  When I start WSUS, I can see my WSUS server listed, but when I select it, the connection seems to time out and I'm face with the error message: Error: Connection Error. I'm giving the option to 'reset server node'.

Event ID 7053 is shown (see below).  The services are running and I've tried deleting the MMC file as suggested.  

Anyone got any advice on this, or is there any other Logs I can look at/post in relation to this?  The server is running On 2008 R2.

Many thanks