Share via

New Microsoft Windows hotfixes to address issues installing and searching for updates

  • Article

DOWNLOAD_thumb2We have a couple recent hotfixes for Windows that you’ll want to be aware of if you install Windows updates by using System Center 2012 Configuration Manager (ConfigMgr 2012 or ConfigMgr 2012 R2). The problems addressed with these hotfixes have the following symptoms:

- When you install Windows updates by using System Center Configuration Manager, the installation takes a long time to complete and Configuration Manager becomes overloaded.

- The Svchost.exe process consumes 100 percent of the CPU usage when you try to upgrade to Windows 10. 

You may also experience issues related to updates installed during a Configuration Manager Task Sequence.

For complete details as well as download and installation instructions, please see the following:

3102810 - Installing and searching for updates is slow and high CPU usage occurs in Windows 7 and Windows Server 2008 R2 (https://support.microsoft.com/en-us/kb/3102810)

3102812 - Installing and searching for updates is slow and high CPU usage occurs in Windows 8.1 and Windows Server 2012 R2 (https://support.microsoft.com/en-us/kb/3102812)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter :

clip_image001 clip_image002

System Center All Up: https://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: https://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: https://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: https://blogs.technet.com/momteam/ 
Service Manager Team blog: https://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: https://blogs.technet.com/scvmm

Microsoft Intune: https://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: https://blogs.technet.com/sus/
The RMS blog: https://blogs.technet.com/b/rms/
App-V Team blog: https://blogs.technet.com/appv/
MED-V Team blog: https://blogs.technet.com/medv/
Server App-V Team blog: https://blogs.technet.com/b/serverappv
The Surface Team blog: https://blogs.technet.com/b/surface/
The Application Proxy blog: https://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/

Comments

  • Anonymous
    November 18, 2015
    Would this issue affect a) update scans and b) deployment of SCEP updates as well as actual update deployment?

    Thanks
  • Anonymous
    November 29, 2015
    212 Microsoft Team blogs searched, 54 blogs have new articles. 154 new articles found searching from
  • Anonymous
    November 30, 2015
    I have the feeling that Microsoft Update on Windows 7 has been slowed down extremely after one of the patch days in this year. Sometimes a new MU client is being released which solves some of this performance issues, but there seem to be some still hidden.

    Today I tried to update IE 9 to IE 11 on Windows 7 x64 (this update was manually hidden before, all other updates were current (at the level of November patch day) - so the above update should have been already applied). It took some time to find IE11 and to install it. A bigger problem arose after reboot when MU should find new updates (patches for IE 11). I told MU (no WSUS) to search for new updates and it took about one hour until MU showed the updates for IE11 (memory was not full ~2GB were free, the computer has an SSD, only the processor might be a bit outdated (some Core 2 Duo) and there surely was no issue with the internet connectivity or bandwidth).

    When there are no new outstanding updates the search for Microsoft Updates is being finished very fast, but after some new updates are being released (patch day) the manual search for new updates is going to take a very long time (10-15 minutes).

    Could something be done to restore MU performance (or to get some insights what it is doing during this time)? WindowsUpdate.log doesn't show much interesting things. Only that search was started, that the cookie has been expired/that there was a new PID, that it found a new driver on WU for some device and about 20 minutes later warnings that some URLs have been tried to be added to the datastore while the files don't exist yet (or something like that - sorry that I don't have the log available now).
  • Anonymous
    December 09, 2015
    Microsoft Update (it is December patch day) took about 40 minutes on Core 2 Duo processors (think they were E4500) with fast SSDs (mostly heating one cpu core during this time) between "Search for updates" and actually showing the updates.

    Maybe it is necessary to take the time to activate Windows Update Tracing registry keys to see in WindowsUpdate.log what is really happening during this time (without them there is only a very long gap).
  • Anonymous
    December 10, 2015
    Using the registry keys from KB902093 I was able to find out that MU spends too much time during "PopulateSupersedenceInfo", unfortunately that was on a computer that probably had not the above update.

    On another computer which had the updates from November patch day installed I tried to use the registry entry for MU from KB2545723 (0x...16 instead of 0x...7). Unfortunately MU seems to truncate logs when it thinks they have grown too large, so there was no useful information during this step available (some time during the update search when it didn't logged for some minutes there was some entry from DtaStor that it is ignoring the shutdown request because there were open references).

    Would be nice when this issue would be fixed (and information how to prevent MU from truncating the tracing logs without having to install a debugger might be helpful as well)