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. I have been researching this for days and probably have about 10 hours invested in trying to come to a conclusion and now want some feedback from this group. 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. Wsus Files Too Large' title='Wsus Files Too Large' />Group Policy Preferences allow you to deploy Registry settings. If you have to deploy a large number of complicated Registry settings, you must convert a REG. Recently, weve seen an increase in the number of high CPUHigh Memory usage problems with WSUS, including WSUS in a System Center Configuration Manager. Thank you for a very helpful post, it worked for me, I really needed those extra files, and the stop windows update tip. Win 7 updated with the rollup, but stalled on. The other possible cause is if youve selected too many products andor categories for synchronization to the WSUS server, or if you havent declined enough of the. 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. Forums/getfile/992446' alt='Wsus Files Too Large' title='Wsus Files Too Large' />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. Reduce-PDF-File-Size-Step-23.jpg/670px-Reduce-PDF-File-Size-Step-23.jpg' alt='Wsus Files Too Large' title='Wsus Files Too Large' />Since the release of SCCM 1602 SCCM Office 365 updates management are finally integrated to the standard software update process. 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. Internal. Data. Access. Cache. Get. Core. Update. XmlInt. 32 revision. Ids, Data. Access da, Int. Xml. Per. Request. Microsoft. Update. Services. Internal. Psp Genso Suikoden English Patch. 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. How to solve the windows update error 8. Updated 3. 17. 2. In this article we will guide you through the most complete guide for solving the Windows update error 8. Windows errors are notoriously difficult to solve, especially errors that related to Windows updates, because they all returning a general message without further information. Error 8. 00. 72ee. Windows, starting from Windows 7Windows Server 2. R2 to Windows 1. 0Windows Server 2. R2. This error can appear when you are installing updates via WSUS or when downloading updates from the Windows Update Center over the Internet. First of all, you have to know what causes this error. When you try to connect to the Windows server to download the latest updates, the system is unable to establish a connection, hence the error message that is displayed on your screen. Windows could not search for new updates, An error occurred while checking for new updates for your computer. Errors found Code 8. EE2. Possible solutions for the Windows update error 8. Error code 8. 00. Windows Update error table on the MSFT site is interpreted as follows ERRORINTERNETTIMEOUT 2. The request has timed out. This means that the system cannot access the Microsoft Update or WSUS sites. Solution 1. Check your Internet connection and access to Windows Update web sites. First of all, it is recommended to check that your computer has access to the Internet. Try to open a website http download. If the access to the site is available, the following picture will appear Solution 2. Check Proxy and Firewall settings. Check if you are using a proxy server. If you do, double check the settings in the Internet Explorer and make sure that the proxy does not require a username or password to connect. If it does, the easiest way is to disable the proxy server during the duration of the windows update, although you can also create a workaround by setting your firewall to allow the connection to the Windows Update directly without going through the proxy. If you are connecting to the Internet through a firewall, make sure that the following websites addresses are allowed in its settings HTTP HTTPS update. Solution 3. Reset System Proxy Server Settings. If your computer has been infected with spyware in the past or it is at the moment then the spyware might have modified your Internet Explorer settings to use a proxy server. Open the cmd. exe utility by typing CMD in the Start menu and run the following command netsh winhttp import proxy sourceie. Solution 4. Re register WU dlls. Some dll files might have become unregistered due to a various factors which could trigger the Windows update error 8. In this case, open elevated cmd. Solution 5 Change MTU setting to 1. Wrong MTU setting can also cause 8. This is the rarest occurrence that may cause the 8. MTU setting might be incorrect. In this case, you simply have to set the MTU value to 1. Windows Update again. Solution 6. Fixing error 0x. WSUSIf you receive Windows Updates from internal Windows Server Update Services WSUS server, open the Registry Editor regedit. HKEYLocalMachineSoftwarePoliciesMicrosoftWindowsWindows. Update and check the WUServer and WUStatus. Server. Verify that the correct WSUS server names are specified here. If you dont want to use internal WSUS but you want to receive updates directly from Windows Update, remove these parameters from the registry and restart the Windows Update service with the command net stop wuauserv net start wuauserv. Solution 7. Lack of resources in the App. Pool WSUSIf you are using WSUS server, perhaps the error is due to a lack of resources in the App. Pool WSUS on a server. The solution is to remove the limit on the consumed memory. Open IIS Manager Console Application Pools Wsus. Pool Advanced Settings. Change Private Memory Limit to 0 and restart IIS. Solution 8. Error 8. VM on Hyper VSometimes when using Hyper V, you may encounter a situation where Windows does not want to update inside the virtual machine we ran into this on Windows Server 2. R2. The system gives an error 8. EE2 and does not give any explanation. As it turned out, the error is related to the transmission parameter of large packets in the properties of the host network card. As a host, we have a physical server on which Hyper V is deployed. To solve the problem, run the Device Manager on the Hyper V host and open the properties of the physical network card Then go to the Advanced tab, find and disable 2 settings Large Send Offload V2 IPv. Large Send Offload V2 IPv. These settings are responsible for segmenting the network adapter of large data packets. Save the changes and perform a new update search on the virtual machine. These are all possible solutions to the Windows update error 8. In case you still cannot fix the error, leave a comment below and we will try to assist you.