High CPUHigh Memory in WSUS following Update Tuesdays. Updated 1. 01. 12. Recently, weve seen an increase in the number of high CPUHigh Memory usage problems with WSUS, including WSUS in a System Center Configuration Manager environment  these have mostly corresponded with Update Tuesdays. Microsoft support has determined that the issue is driven primarily by the Windows 1. KB4. 02. 27. 23, KB4. KB4. 02. 53. 39, etc. Wsus The Server Is Failing To Updates' title='Wsus The Server Is Failing To Updates' />See here for the list of Windows 1. These updates have large metadata payloads for the dependent child packages because they roll up a large number of binaries. Slow Microsoft update downloads from the WSUS server. Party Application Patching with SCCM and SolarWinds Patch Manager Video 502 Bad Gateway Unable to Sync. Windows 1. 0, versions 1. Windows 1. 0 RTM and 1. Windows 1. 0, version 1. Symptom. The symptoms include. High CPU on your WSUS server 7. CPU in w. 3wp. exe hosting Wsus. Pool. High memory in the w. Wsus. Pool customers have reported memory usage approach 2. GBConstant recycling of the W3wp. Wsus. Pool identifiable by the PID changingClients failing to scan with 8. Windows. Update. log. Mostly 5. 00 errors for the Client. Web. ServiceClient. IIS logs. Cause. Microsoft support has determined that the issue is driven primarily by the Windows 1. KB4. 02. 27. 23, KB4. KB4. 02. 53. 39, etc. See here for the list of Windows 1. These updates have large metadata payloads for the dependent child packages because they roll up a large number of binaries. Windows 1. 0, versions 1. Windows 1. 0 RTM and 1. Windows 1. 0, version 1. How to determine if the 1. Updates are the cause. To determine if WSUS is affected by this problem, decline the Windows 1. If both CPU and memory quickly drop back to normal, then the issue is likely the result of metadata size from the Windows 1. They can be reapproved after you have determined if the updates are causing this issue, assuming you want to deploy them. If declining the Windows 1. WSUS server. Take the steps outlined in The Complete Guide to Microsoft WSUS and Configuration Manager SUP maintenance to decline the superseded updates. Hello, I have SCCM SP1 R2 with Software Update Point SUP, WSUS SP1 all on same machine OS Windows 2003 SP2 All English ver. I have problem with. Hello Spiceheads Im trying to catch the last train we have 1511 Win 10 pro client and we want to push 1703 through 2012 WSUS server we have it setup to download. If, after doing this you are still having problems, read on. This blog post may help alleviate some of these problems, but is not a magic bullet. After these changes are made, you will still see high CPU and memory until the system stabilizes as I explain further down. WSUS Caching. WSUS has a caching mechanism whereby the first time update metadata is requested by any client WSUS will store it in memory. Further requests for the same update revision will retrieve the update metadata from memory instead of reading it from the database. Some of the metadata in the database is compressed, so not only must it be retrieved, it must be decompressed into memory, which is an expensive operation. You can monitor the current number of updates stored in the cache via Performance Monitor with the counter WSUS Client Web ServiceCache size and instance spgetcorexml. Keep in mind that this counter provides the number of cached items, not the amount of memory consumed by cached metadata. The Problem. For large metadata packages and many simultaneous requests, it can take longer than ASP. NETs default timeout of 1. When the timeout is hit, ASP. NET disconnects the client and aborts the thread doing the metadata retrieval. If you look at Program FilesUpdate ServicesLog. FilesSoftware. Distribution. System. Threading. Thread. Abort. Exception Thread was being aborted. System. Buffer. MemcpyByte dest, Bytesrc, Int. System. Buffer. MemcpyBytedest, Bytesrc, Int. System. Buffer. MemcpyBytedest, Bytesrc, Int. System. String. Ctor. Char. Ptr. Start. LengthCharptr, Int. Index, Int. 32 length. Microsoft. Update. Services. Internal. Cab. Utilities. Expand. Memory. Cab. To. StringByte src. Microsoft. Update. Services. Internal. Data. Access. Execute. Sp. Get. Core. Update. XmlInt. 32 revision. Ids. at Microsoft. Update. Services. Turbo Net Manager Crack Of Idm more. Internal. Data. Access. Cache. Get. Core. Update. XmlInt. 32 revision. Ids, Data. Access da, Int. Xml. Per. Request. Microsoft. Update. Services. Internal. Client. Implementation. Get. Sync. InfoVersion client. Protocol. Version, Data. Access data. Access, Hashtable state. Table, Hashtable deployment. Table, Boolean have. Groups. Changed, Boolean driver. Sync. Needed, Boolean do. Chunking. at Microsoft. Update. Services. Internal. Client. Implementation. Software. SyncData. Access data. Access, Unencrypted. Cookie. Data cookie. Data, Int. 32 installed. Non. Leaf. Update. Ids, Int. 32 leaf. Update. Ids, Boolean have. Groups. Changed, Boolean express. Query, Guid filter. Category. Ids, Boolean need. Two. Group. Out. Of. Scope. Updates. at Microsoft. Update. Services. Internal. Client. Implementation. Sync. UpdatesCookie cookie, Sync. Update. Parameters parameters. Microsoft. Update. Services. Internal. Client. Implementation. Sync. UpdatesCookie cookie, Sync. Update. Parameters parametersNote What you are looking for is a Thread. Abort. Exception with Execute. Sp. Get. Core. Update. Xml on the stack Thread. Abort. Exceptions could happen for other reasons as well we are concerned with this specific scenario. When the thread abort happens, all of the metadata that has been retrieved to that point is discarded and is not cached. As a result, WSUS enters a continuous cycle where the data isnt cached, the clients can never complete the scan and continue to rescan. Another issue that can occur is the WSUS application pool keeps recycling because it exceeds the private memory threshold which it is very likely to do if the limit is still the default of 1. This recycles the app pool, and thus the cached updates, and forces WSUS to go back through retrieving updates from the database and caching them. Solution. A WSUS update is now available that includes improvements for update metadata processing. This update should be applied to all WSUS servers in your environment. Windows Server 2. KB4. 03. 93. 96Windows Server 2. R2 KB4. 04. 16. 93Windows Server 2. KB4. 04. 16. 90WSUS 3. SP2 KB4. 03. 99. In addition to applying the applicable updates noted above, it is recommended that routine maintenance of WSUS be performed. See The Complete Guide to Microsoft WSUS and Configuration Manager SUP maintenance for more info. If you still occasionally experience thread abort exceptions, you can increase ASP. NETs default timeout. Increase the ASP. NET timeout. Make a copy of Program FilesUpdate ServicesWeb. ServicesClient. Web. ServiceWeb. Config. Open Program FilesUpdate ServicesWeb. ServicesClient. Web. ServiceWeb. Config. Find the element lt http. Run. Time. It will look like this in an unmodified web. Runtime max. Request. Length4. 09. 6 Modify http. Run. Time by adding an execution. Timeout attribute lt http. Runtime max. Request. Length4. 09. 6 execution. Timeout3. 60. 0 Save the web. From an elevated command prompt, run IISReset to restart IIS. Monitoring WSUS Metadata Caching. Open Windows Performance monitor and add the following counters. WSUS Client Web Service Cache Size counter for spgetcorexml instance. Process Private Memory counters. If there is more than one w. WSUSPool, but you can also add Process ID Process to determine which worker process should be monitored. Monitor the cache size counter it should increase and eventually reach a peak value that does not change. This indicates all metadata that clients need is cached. It can take several hours for this to stabilize, so be patient.