Fix Slow Updates/High CPU Usages - Windows 7


Recommended Posts

This is something I have been testing in VM's and with the assistance of a few colleagues, but this has solved the following on clean installs and even some dirty installs:

 

-Checking for updates never finishes

-High CPU usage while Checking for Updates

-Windows Update freezes or locks up the system for periods of time

-Searching for updates can takes hours

 

 

Step 1: Install KB3172605 by downloading the .MSU, expanding the .MSU into a folder, and use DISM to apply the CAB file. In order to do this, enter the following commands in an admin command prompt. Please take note, if your system is 32-bit you would instead use Windows6.1-KB3172605-x86.msu

 

mkdir update
expand -f:* Windows6.1-KB3172605-x64.msu .\update
dism /online /add-package /packagepath:update\Windows6.1-KB3172605-x64.cab

 

Reboot your system and try running Windows Updates, sometimes this is all it takes. On a few of my test VMs, I found this one did the trick, on a few others it did not.

 

If you receive an error stating the manifest file contains a syntax error (0x800736B5) perform the following:

The issue is caused by the Version key under Component Based Servicing in the registry. It is out of date and DISM does not know how to process one of the commands inside the update.  The easiest way to fix this, is to download and install the Windows 7 Roll-up Prerequisite. In order to do this, download the Prerequisite file and perform the following commands from an admin command prompt:

 

mkdir prereq
expand -f:* Windows6.1-KB3020369-x64.msu .\prereq
dism /online /add-package /packagepath:prereq\Windows6.1-KB3020369-x64.cab

if your system is 32-bit you would instead use Windows6.1-KB3020369-x86.msu

 

Restart the machine and you should be able to install KB3172605 at this point, without any errors.

 

**As an additional note, if your Windows 7 system is a fresh-install and was recently upgraded to SP1, or has not done updates for a very very long time, there could possibly be hundreds of applicable updates. In this situation, it is advised to install the Windows 7 Rollup Package, which contains all updates between the launch of SP1 and April 2016.

 

TL;DR Steps

1. Install KB3172605 

2. Install Roll-up Prerequisite

3. Install Roll-up Package

4. Check for updates, which should run much faster now.

 

Download Links:

 

KB3172605

Windows 7 Roll-up Prerequisite (x86)

Windows 7 Roll-up Prerequisite (x64)

Windows 7 Roll-up Update (x86)

Windows 7 Roll-up Update (x64)

Instead of extracting the update and installing it by command, unplugging from the internet and restarting the windows update service before trying to install the update will also make the update install quicker.

 

That being said the command would be useful for remote work.

  • Like 2
  • 3 months later...

Wanted to list another great method.

Very handy on a clean Win7 x64 SP1 install.

Download these hotfixes:

Capture.thumb.JPG.9535221492a882271f6fab6c2b7aa8af.JPG


Do not install them.


Go here:

Use PowerShell to install a list of hotfix all at once.

Follow the simple directions -

PS will install each item silently, without rebooting, and echo each time a hotfix is installed.

Once all are done, reboot.

You should be able to use Windows Updates normally.

UPDATE:

Just tested on a new VM (Win7 x64 SP1) - worked great.
 

____________________________

This is the PS script

$dir = (Get-Item -Path ".\" -Verbose).FullName
 Foreach($item in (ls $dir *.msu -Name))
 {
    echo $item
    $item = $dir + "\" + $item
    wusa $item /quiet /norestart | Out-Null
 }

 

  • Like 2
13 minutes ago, Circaflex said:

I've found on a clean install, today actually, that if you install the pre req listed, then the rollup and then finally the kb 3172605 updates will work without any issues. Very simple process. 

Well... mine's cooler !
(and my post has more colors, so I win)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Yeah, right! /s They've been saying that for two centuries now. Look up "China's final warning" on Wikipedia.
    • I have not verified if any of the fixes mentioned on the below article actually work. Why Claude Code Eats All Your RAM (And How to Fix It) There are at least four separate things that can eat your RAM, and only one of them is your fault. The Four Culprits 1. Bloated Session Logs (The Silent Killer). For 2-4 and more inluding the suggested fixes, see link https://marceloretana.com/blog...aude-code-eats-all-your-ram
    • One of my PC's is Windows 11 Home Edition... and guess what? it supports Hyper-V Disks and Containers, as well as WSL2... which these desktop tools leverage on an as-needed basis. It does not need to be enabled system-wide; it merely needs to exist. Furthermore, I tried something yesterday with Hermes Desktop and their "installer" actually builds everything from source as part of its installer toolchain! The installer (and updater as it were) both go through a roughly 19-step process to prep the system for the tool to be used -- and connectivity to local/remote models, local/remote agent configs, and other steps are not included as part of this process (those are all user config steps post-install). ALSO, the "bug wasn't confirmed to exist" is the weakest argument against a bug. That's literally every flawed product's knee-jerk reaction! Even politicians, lawmakers, murderers, and other violent criminals start with that defense... "I deny everything I'm accused of." The bug is the (shared) experience. Whether it's truly Claude Code's fault, or user error, or some other software package being the ultimate culprit, is not the point. They are experiencing unpleasant side effects and don't like that.
    • Each generaton has its exciting times and I was fortunate enough to be right there at the beginning of the PC industry.   I don't think any of us at that time realized how large it would become I still remember working on a TRS-80 with a green screen monitor that kept overheating and dying.     Also used some TRS-80 PCs with tape cartridge memory.   They worked but boy were they slow with everything being a very slow sequential read or write.  But heh, they worked though it wasn't long before they were repaced by the HDD. 
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      515
    2. 2
      PsYcHoKiLLa
      208
    3. 3
      +Edouard
      160
    4. 4
      Steven P.
      95
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!