Office 2007 SP1 update error, I've tried eveything...

Well, this is what CheckSUR reported:

=================================
Checking System Update Readiness.
Version 6.0.6000.2
2008-04-01 18:30:59 PM

Checking Deployment Packages

Checking Package Manifests and catalogs.

Checking package watchlist.

Checking component watchlist.

Checking packages.
Checking component registry

Checking component store

Scanned 6882 components, 10483 component payload files
Summary:
Milliseconds: 652139
No errors detected
Customer Experience report successfuly uploaded. Thank you for
participating. For more information, see the Microsoft Customer Experience
Improvement Program on the Microsoft web site.

Nothing appears to be wrong according to the log. Despite this, I tried
restarting my laptop and re-installing Office 2007 SP1 anyway. No luck.
Tobias, you said something about sending you the log files? There is the one
from verbose logging. There is also one that the event viewer references:
C:\MAINWWsp1.log. Do you want this one as well?

"Tobias Nunberger" wrote:

> Hi
>
> greentiger wrote:
> > Ok, so what is the recommended course of action here? Looking this error up:
> > ERROR_SXS_COMPONENT_STORE_CORRUPT there are many tech articles referencing a
> > MS KB article that no longer exists and other possible solutions like
> > re-installing Windows Update, etc.
>
> Yes, I've found the same information. it seems this can happen when the
> Vista component store has been corrupted. I found a recommendation to
> check for event ID 4375 in the event logs and to locate a file named
> "pending.xml" in %WinDir%\WinSXS and to remove it. However this
> information seems to be inaccurate! o:
>
> There's an article available which guides through troubleshooting
> Windows Update related issues using a support tool written for this
> purpose. It seems to also handle the ERROR_SXS_COMPONENT_STORE_CORRUPT
> issue. You probably may want to try this ...
>
> Q947821: Description of the CheckSUR update for Windows Vista
> http://support.microsoft.com/kb/947821/en-us
>
> Good look!
> Toby
>

Did Microsoft release a patch to fix this problem yesterday? I turned on my
laptop yesterday morning and it installed about 20 updates including MS
Office 2007 SP1 to my surprise.

If not, the only thing I changed on my system recently was I turned off the
Windows Error Reporting manager service on Saturday. I had noticed the
wermgr.exe process was consuming between 25-50% of my CPU resources at a near
constant basis. This was causing my laptop to overheat when I used other
moderately CPU intensive programs. After I turned it off, my laptop CPU was
running as expected and Vista was running a LOT smoother.

It could be coincidence but I wanted to know if MS fixed the problem or
wermgr.exe was the source of all my headaches.

-gt

"greentiger" wrote:

> Well, this is what CheckSUR reported:
>
> =================================
> Checking System Update Readiness.
> Version 6.0.6000.2
> 2008-04-01 18:30:59 PM
>
> Checking Deployment Packages
>
> Checking Package Manifests and catalogs.
>
> Checking package watchlist.
>
> Checking component watchlist.
>
> Checking packages.
> Checking component registry
>
> Checking component store
>
> Scanned 6882 components, 10483 component payload files
> Summary:
> Milliseconds: 652139
> No errors detected
> Customer Experience report successfuly uploaded. Thank you for
> participating. For more information, see the Microsoft Customer Experience
> Improvement Program on the Microsoft web site.
>
> Nothing appears to be wrong according to the log. Despite this, I tried
> restarting my laptop and re-installing Office 2007 SP1 anyway. No luck.
> Tobias, you said something about sending you the log files? There is the one
> from verbose logging. There is also one that the event viewer references:
> C:\MAINWWsp1.log. Do you want this one as well?
>
> "Tobias Nunberger" wrote:
>
> > Hi
> >
> > greentiger wrote:
> > > Ok, so what is the recommended course of action here? Looking this error up:
> > > ERROR_SXS_COMPONENT_STORE_CORRUPT there are many tech articles referencing a
> > > MS KB article that no longer exists and other possible solutions like
> > > re-installing Windows Update, etc.
> >
> > Yes, I've found the same information. it seems this can happen when the
> > Vista component store has been corrupted. I found a recommendation to
> > check for event ID 4375 in the event logs and to locate a file named
> > "pending.xml" in %WinDir%\WinSXS and to remove it. However this
> > information seems to be inaccurate! o:
> >
> > There's an article available which guides through troubleshooting
> > Windows Update related issues using a support tool written for this
> > purpose. It seems to also handle the ERROR_SXS_COMPONENT_STORE_CORRUPT
> > issue. You probably may want to try this ...
> >
> > Q947821: Description of the CheckSUR update for Windows Vista
> > http://support.microsoft.com/kb/947821/en-us
> >
> > Good look!
> > Toby
> >