Re: CBS mum missing and error 800b0100 in Server Manager

(cross-post added to Server Setup)
"Mek" <> wrote in message news:C5A9DC3E-8116-492E-9B03-...
> First of all, I'm running Windows Server 2008 x64 Edition. I was trying to
> add role features and the Roles and Services boxes were unable to load ther
> info. I checked the event log and found error 800b0100, which apparently
> involves a store corruption usually because of a failed update.
>
> Long story short, I've done a lot of diagnostics and I've tracked down the
> issue to a single missing .mum file called
> Package_for_KB961260~31bf3856ad364e35~amd64~~6.0.1 .3.mum.

> The file is listed
> as missing in the log when I run the System Update Readiness Tool.


I thought CheckSUR was supposed to repair stuff too?
FWIW it did for me when I had a problem with Vista SP1
for x86. The only unexpected thing for me was that it
didn't run automatically but still fixed the things that were
wrong.


>
> I've downloaded the KB961260 update and extracted it to get the files. Two
> files were originally listed as missing but I found them in the update,
> copied them over, and the errors for those files went away. However, the
> file listed above isn't in the update. What I need to know is whether anyone
> knows why it isn't there, how to get it, and what the source of the original
> problem might be. If there's any info that might help, just ask and I'll
> post it. Thanks in advance, everyone.


Cross-posting to a newsgroup where there may be more
visibility for other AMD64 server users. ; )


Good luck

Robert Aldwinckle
---

> > The file is listed
> > as missing in the log when I run the System Update Readiness Tool.
>
>
> I thought CheckSUR was supposed to repair stuff too?
> FWIW it did for me when I had a problem with Vista SP1
> for x86. The only unexpected thing for me was that it
> didn't run automatically but still fixed the things that were
> wrong.

Well, in my case at least, it didn't fix the problem. I thought it was
supposed to, based on what I had read, but I ran it twice and it reported the
same problem both times. After I found and copied two of the three files,
those errors disappeared but the third error remained. My conclusion: it's
telling me what's wrong but not fixing it. Maybe I'm missing a command line
switch or something.

Hello Mek,
Checksur replaces manifest files it finds as corrupt as well as few other
files. It doesn't contain all the files in the OS or the download would
have to pretty large.
It has to contain each of the versions for the manifests as well.

Checksur is not on the system by default, it is on Windows update and runs
after problems are detected the next time you attempt to download updates
from Windows update.

Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| >Thread-Topic: CBS mum missing and error 800b0100 in Server Manager
| >thread-index: Acmh+sdNdQtjHH9ISmSIEi7Oso3yEA==
| >X-WBNR-Posting-Host: 207.46.19.229
| >From: =?Utf-8?B?TWVr?= <>
| >References: <C5A9DC3E-8116-492E-9B03->
<>
| >Subject: Re: CBS mum missing and error 800b0100 in Server Manager
| >Date: Tue, 10 Mar 2009 20:38:01 -0700
| >Lines: 16
| >Message-ID: <8D78EFEB-D370-4B6D-A419->
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > charset="Utf-8"
| >Content-Transfer-Encoding: 7bit
| >X-Newsreader: Microsoft CDO for Windows 2000
| >Content-Class: urn:content-classes:message
| >Importance: normal
| >Priority: normal
| >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3168
| >Newsgroups:
microsoft.public.windowsupdate,microsoft.public.wi ndows.server.setup
| >Path: TK2MSFTNGHUB02.phx.gbl
| >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:6192
microsoft.public.windowsupdate:80190
| >NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| >X-Tomcat-NG: microsoft.public.windows.server.setup
| >
| >> > The file is listed
| >> > as missing in the log when I run the System Update Readiness Tool.
| >>
| >>
| >> I thought CheckSUR was supposed to repair stuff too?
| >> FWIW it did for me when I had a problem with Vista SP1
| >> for x86. The only unexpected thing for me was that it
| >> didn't run automatically but still fixed the things that were
| >> wrong.
| >
| >Well, in my case at least, it didn't fix the problem. I thought it was
| >supposed to, based on what I had read, but I ran it twice and it
reported the
| >same problem both times. After I found and copied two of the three
files,
| >those errors disappeared but the third error remained. My conclusion:
it's
| >telling me what's wrong but not fixing it. Maybe I'm missing a command
line
| >switch or something.
| >