Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Francesco

Microsoft update causes 100% cpu usage

Recommended Posts

I install every Hotfix for Office and Windows on every patchday ;)

I can't I have too much PCs at home to install updates on all of them every time. Also I can't leave the PCs i've repaired without MU.

Share this post


Link to post
Share on other sites

I've found a better idea. You know the MS baseline analyzer? If I run it with a schedule now it automatically makes automatic updates get the updates even for office! This should finally fix the problem.

Share this post


Link to post
Share on other sites

I solve this issue.

The update Hotfix KB916089 Version 5 ( http://support.microsoft.com/kb/916089/en-us ) (Msi.dll 3.1.4000.2805) solve the issue. I don't have 100% cpuusage and I still have a GUI when installing programs through a msi-file. The GUI wasn't shown while installing, so that programs which have 2 or more cds fails to install, when I installed other patches who had a never msi.dll than MSI 3.1V2.

I'm so happy :thumbup:wub:

Share this post


Link to post
Share on other sites

Scan for viruses and malware. Then go to Start > Run > cmd

Enter this:

sfc /purgecache

When complete, enter:

sfc /scannow

This may ask for your Windows install cd.

Share this post


Link to post
Share on other sites
I solve this issue.

The update Hotfix KB916089 Version 5 ( http://support.microsoft.com/kb/916089/en-us ) (Msi.dll 3.1.4000.2805) solve the issue. I don't have 100% cpuusage and I still have a GUI when installing programs through a msi-file. The GUI wasn't shown while installing, so that programs which have 2 or more cds fails to install, when I installed other patches who had a never msi.dll than MSI 3.1V2.

I'm so happy :thumbup:wub:

Yeah, ran in to that last week trying to install Street and Trips 2006.. Took me a few minutes to track down the the probelm and then the hotfix that updated msi.dll.. Going to try this new one out so I can have the fix and still run MSI installers correctly.. :lol:

Tarun, not spyware in this case.. Seen it on 2 machines that are completely clean.. (1 doesnt even get connected to the net actively).. Before 916089 v5 there was another hotfix (I dont remember the number now, the one I removed earlier) that also updated msi.dll but didnt cut it for this bug..

Update: Found it..

Actually there were a couple updates that replaced msi.dll

http://support.microsoft.com/kb/906219

Never installed that one.. (Oldest update I can find that is newer then the MSI 3.1 base install)

And

http://support.microsoft.com/kb/914810

Which happens to deal with a problem with Automatic Updates too.. It is the one that caused my installer for Streets and Trips to fail..

Msi.dll version 3.1.4000.2648

It didnt do anything to resolve the slow or dead stop updating I ran in to occasionally. It would still take forever to scan..

Edited by bilemke

Share this post


Link to post
Share on other sites
Tarun, not spyware in this case.. Seen it on 2 machines that are completely clean.. (1 doesnt even get connected to the net actively)..

yes, thats right. Tarun you are wrong, this is a strange Bug in the Microsoft Installer, but now, every thing is ok :):wub:

Share this post


Link to post
Share on other sites

Ooh, harsh! ;)

I just cover the most common possibilities, including that of which I just recently had to resolve at the shop. Those just turned out to be virus/malware related. Glad yours isn't though. :P

Share this post


Link to post
Share on other sites

:huh:

:rolleyes:

You are both wrong.. Wrong wrong wrong!!!! :realmad:

:lol:

Just a very annoying problem to encounter.. ;)

(And, end smiley face mod)

Share this post


Link to post
Share on other sites

ok an update to this going back to windows update speeds it up a lot but seems doesnt completely fix it. On a pwoerful pc its not as bad but on a amd 900mhz its still a looooong wait waiting for windows update to load and for updates to install.

This is a very stupid bug to leave unpatched and I cant believe ms have not had reports about it.

If googling this many people are blaming it on viruses and spyware.

Edited by Chrysalis

Share this post


Link to post
Share on other sites
This is a very stupid bug to leave unpatched and I cant believe ms have not had reports about it.

the patch is avaiblibe at support ;)

If googling this many people are blaming it on viruses and spyware.

thats right. most people think it is a virus or spyware :rolleyes:

Share this post


Link to post
Share on other sites

Because newer versions of the msi.dll that contains the MSI function invariably break certain installers, and programs fail to install. Although this happens with almost all incremental msi updates, most people only install a new version of the msi engine when a new major version is released (1.0, 2.0, 3.0, 3.1, 4.0, etc), and these versions are better tested and supported by both Microsoft and third-party vendors that write .msi packages - meaning less impact on users and more stability in the engine. I think the ultimate factor in why this has not been released en-masse is that the problem, while an annoyance, is not necessarily a critical update to an actual broken, non-functioning component (things still work with the current non-patched version, for the most part, unless you leave your box up for weeks without rebooting after multiple patch installations). Therefore, the harm is quite possibly worse than the good the update brings, and vendors really only write .msi packages to the major versions.

Ultimately, the bug isn't a major issue, it's an annoyance, and the possibilities to break things by releasing a fix for something that's not technically broken means the change will not be rolled out publicly - it'll simply be rolled into the next major msi engine release (4.0, with Vista).

Edited by cluberti

Share this post


Link to post
Share on other sites

disagree, if I left winupdates to auto then on every bootup their is a 7 minute worth of 100% cpu usage on svchost.exe on my older pc as auto updates checks for updates.

if it finds any it then takes 5-10 minutes to install them.

if this was a production pc it would be very disturbing and more then a minor annoyance.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...