Windows update scan takes hours? Speed up Windows 7 scans for updates

An unlikely combination of two Windows updates can reduce scan times from hours to minutes

An unlikely combination of two Windows updates can reduce scan times from hours to minutes

If you’re experiencing Windows 7 update scans measured in hours — if not days — as I described last week, a newly discovered trick may reduce scan times to minutes. It’s an unlikely combination of two updates that has worked wonders on my Win7 PCs. Try it and see how it works on yours.


Install a COMBINATION of the following updates on Win7 SP1 — KB3138612 AND KB3145739. I found out that patching KB3145739 alone without patching the WU Client for Win7 SP1 is not enough.


KB 3138612, you may recall, is the March “Windows Update Client for Windows 7” —  exactly the kind of patch you’d expect to solve the Win7 update slowdown.

KB 3145739, on the other hand, is this month’s “security update for Windows Graphics Component” — otherwise known as MS 16-039, the security patch that (once again) fixes the way Windows handles fonts inside the kernel.

I know that sounds like combining beer and cement to make a cheesecake, but there you have it. KB 3138612 installs a new program to handle Windows Updates; KB 3145739 has a new Windows kernel. Either patch installed by itself leads to hours and hours of waiting for Windows 7 update. Installing both patches together brings wait times (on the systems I’ve checked, anyway) back to sane levels.

KB 3145739 is superseding KB 3139852 which was made famous by Noel Carboni about a month ago. That patch was fixing slow update for a lot of people. As such it supersedes a ton of other older patches and from this point of view is like a Cumulative Update.

The issue which creates slowing down of WU is that all those old patches are not removed by Microsoft after releasing the new ones and create problems for those who try to patch new installations.

To see if you have KB 3138612 (remember, this is only for Windows 7), click Start > Control Panel > System and Security > View installed updates. Click on Name to sort your vast collection of updates by name. Look under the heading Microsoft Windows for “Update for Microsoft Windows (KB3138612).” If you don’t have it, go to the KB article and download the appropriate version (32-bit versions are identified as x86; 64-bit versions are x64), then double-click on the download to install it.

To see if you have KB 3145739, follow the same procedure but look for “Security Update for Microsoft Windows (KB3145739).” If you don’t have it, you’ll need to fire up Internet Explorer (I kept getting spurious errors with Chrome and Firefox) and go to the appropriate site for the 32-bit version or the 64-bit version.

More info here:

Understanding and troubleshooting Microsoft Configuration Manager OSD PXE boot

There is a new blog post:

Understanding and troubleshooting Microsoft Configuration Manager OSD PXE boot

Are you wanting to setup PXE boot for operating system deployment in your Configuration Manager environment? Or maybe you already have but are running into some issues that are preventing it from working quite the way you want? If so then we have the perfect guide for you. If you want to understand how PXE support works and is configured in ConfigMgr, and/or troubleshoot any of the most common problems you may run into, this guide is a great place to start. The topics covered include the following:

  • PXE Service Point Installation
  • Adding Boot Images to a PXE Enabled DP
  • The PXE Boot Process
  • Downloading The Boot Files
  • WinPE Boot
  • Troubleshooting common issues

You can get started with the guide here.

Known Issues with KB3148812

Known Issues with KB3148812

Hi WSUS admins, just a quick post to let you know that we’ve received word of some issues happening (e.g., WSUS admin console is inaccessible, clients can’t contact WSUS) in the wild after installing KB3148812.  It is critical functionality; however, you don’t lose anything by skipping installation until we publish media that leverages this scenario, which will not be happening this month.  For now, feel free to remove the patch if it’s causing you problems, and we’ll get to the bottom of the issues that have been reported.  If you’d like to assist in resolving this, then please Email Blog Author and we’ll follow up with you.

What you need to know about KB3148812