none
Vista SP1 installation stalls at error 800B0100

    質問


  • I've tried all available SP1 downloads and always end up with the installation process stalling with an 0x800B0100 error.

    I'm referred to http://go.microsoft.com/fwlink/?linkID=101139 which doesn't appear to offer any insight into the problem.

     

    P.S.

    Thanks for resolving a previous problem where I couldn't even get SP1 to start loading... I installed the missing Segoe UI font and was able to get as far as this 800B0100 error.

    2007年12月20日 19:15

回答

すべての返信

  • I know how to fix this form of corruption!  Please send an email to vistasp1logs@hotmail.com with a link to this thread and your nickname (so I can identify you) and I'll give you instructions

    2007年12月20日 20:45
  •  

    I am having the exact same issue, I will contact you as well.

     

    Thank you

    2007年12月21日 23:31
  • Same problem here.  Contacting you.
    2007年12月22日 15:02
  •  George Hilios [MSFT] wrote:

    I know how to fix this form of corruption!  Please send an email to vistasp1logs@hotmail.com with a link to this thread and your nickname (so I can identify you) and I'll give you instructions



    Hi George:

    I'd like to find out more about your solution to my 800B0100 problem that is stalling the installation of Vista SP1.
    I've emailed you directly before (via Thunderbird) at the address provided but I don't know how to link the email to this thread.

    Thanks ... Nuffyfluts
    2007年12月22日 16:09
  • I have the same issue with standalone SP1 as well as going through Windows Update. On this particular machine, most updates work. The monthly Windows Mail junk filetr updates croak (not needed with Outlook) and, alas, so does SP1. Error code 800B0100.

     

    I've tried some of the fixes found on the newsgroups (the lack of official KB info is troubling) to no avail. I will contact you as well.

     

    Regards,

    Lloyd

     

    2007年12月27日 4:53
  • George:

    I'm still waiting for you to respond with advice on how to get around the 800B0100 problem.

    Nuffyfluts

    2007年12月27日 12:45
  • Same issue here. I've tried just about everything anyone has suggested. I'll send you my log files George. Thanks!

     

    2008年1月10日 18:37
  •  

    I have sent George a note, and have not gotten response.  I have tried the lastest download of the lastest RC of SP1.. and I still get the same message.  Has anyone solved this problem?
    2008年1月16日 17:12
  • I've been waiting for a long time for a response from "George"... to no avail.

    I suspect that his claim to having a solution was simply a ruse.


    2008年1月16日 17:36
  • Sorry for the delay.  I was out of town on holiday and have been busy with SP development.

     

    Please go to https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=492aab30-c810-4121-a626-3cd7799837f2, select receive files from microsoft, and use password "e!fSzWmBQjz0gB" with no quotes.  Run the tool (cbscheckstore.exe) from an elevated commandline (theres 2, use the x64 one if appropriate).  Please post the results and I will try and get you replacement files for what it tells you is corrupt/missing.

    2008年1月16日 17:47
  • Here's the results I got...

    Checking Package Manifests and catalogs...
    Error: Invalid Catalog. Error:0x800b0100.
    Name: C:\Windows\servicing\packages\Microsoft-Windows-Shell-HoldEm-Package-KB932925-TopLevel~31bf3856ad364e35~x86~~6.0.6000.17034.cat
    Failed to get File information, last error is 2

    Error: Invalid Catalog. Error:0x800b0100.
    Name: C:\Windows\servicing\packages\Package_1_for_KB928089~31bf3856ad364e35~x86~~6.0.1.1.cat
    Failed to get File information, last error is 2


    Checking package watchlist...

    Checking component watchlist...

    Checking packages...
    Error: Cannot find package manifest in store for package: Microsoft-Windows-DreamScene-Package-Preview.16455-MiniLP~31bf3856ad364e35~x86~en-US~6.0.6000.16455.
    Error: Cannot find package manifest in store for package: Microsoft-Windows-DreamScene-Package-Preview.16455-TopLevel~31bf3856ad364e35~x86~~6.0.6000.16455.
    Error: Cannot find package manifest in store for package: Microsoft-Windows-DreamScene-Package-Preview.16455~31bf3856ad364e35~x86~~6.0.6000.16455.

    Errors found.
    2008年1月16日 23:21
  •  

    0x800B0100 -2146762496 TRUST_E_NOSIGNATURE No signature was present in the subject
    2008年1月16日 23:38
  • George,

     

    Thank you.. Here is my output:

     

    Checking Package Manifests and catalogs...

    Error: Invalid Catalog. Error:0x800b0100.

    Name: C:\Windows\servicing\packages\Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.cat

    Size: 24861 bytes.

     

    Error: Failed to parse: C:\Windows\servicing\packages\Package_1_for_KB935807~31bf3856ad364e35~x86~~6.0.1.6.mum

    Line 1:

     

    ™hÚéø|»k߬SJû÷Ù– vÔªÍb3ãoq¦ƒ©9Ym¼Zh&Ž¹ß[3ö)¼N4FÛQ£>=5¯&

     

    Error: Failed to parse: C:\Windows\servicing\packages\Package_2_for_KB935807~31bf3856ad364e35~x86~~6.0.1.6.mum

    Line 1:

     

    µðÂ`

     

    Error: Invalid Catalog. Error:0x800b0100.

    Name: C:\Windows\servicing\packages\Package_3_for_KB938194~31bf3856ad364e35~x86~~6.0.1.2.cat

    Size: 28371 bytes.

     

     

    Checking package watchlist...

     

    Checking component watchlist...

     

    Checking packages...

     

    Errors found.

     

     

    Michael

     

    2008年1月17日 23:14
  • Michael, please go to that link provided earlier and grab the files mentioned in your output (I've uploaded them).  Open an elevated command prompt, cd into c:\windows\servicing\packages, and take ownership of each of them *if they are present*.  You can use the command line tool "takeown", which is already present on your machine.  The command will look something like

     

    takeown C:\Windows\servicing\packages\Package_3_for_KB938194~31bf3856ad364e35~x86~~6.0.1.2.cat

     

    Then copy the files you downloaded from the earlier link over these ones.  Please note that some of the files *may* be missing, which is the same problem as if they were corrupt.  Just copy the correct files here.  Then run the tool again to make sure everything is fine, and try the installation once more!

     

    As for WickedP, the files that are giving you a problem are proving to be quite a pain to find.  I'm trying to track down where to find them, but it is hard since they are related to Ultimate Extras.  I'll let you know when I find them and upload them so you can follow the same steps.

    2008年1月17日 23:38
  • George,

     

    After Taking ownership, I get an access is denied when I try and copy.  Do I need to do this from safe mode? 

     

    Also the Takeown command should be takeown /F "etc...

     

    Michael

     

    2008年1月18日 3:01
  • George:

    I finally got around to downloading and running the cbscheckstore.exe program as you recommended.
    When run, it yields the following....

    Checking Package Manifests and catalogs
    Error: Invalid Catalog. Error:0x800b0100
    C:\Windows|servicing\packages\Package_2_for_KB942624~31bf3856ad364e35~x86~6.0.1.1.cat
    Size: 14442 bytes

    Checking package watchlist...

    Checking component watchlist...

    Checking packages...

    Errors found.




    Looking forward to your response... Nuffyfluts
    2008年1月18日 16:54
  • Michael, sorry I think I left a step out!  Can you run "net stop trustedinstaller" from an elevated command prompt?  That may help.  Also, if takeown doesn't seem to do the trick, can you try taking ownership of the file using the security tabs in properties when you right click the file?

     

    Nuffyfluts, I've uploaded that file to the workspace as well.  Could you follow the same steps and try the install again?

    2008年1月18日 18:15
  •  

    George,

     

    Tried Net Stop Trustedinstaller - tells me service is not running.  So I did the security tabs and changed owners.  I still get access denied when I try to copy.  Going to try Safemode now and let you know how it goes.

     

    Michael

    2008年1月18日 21:45
  •  

    No go on the Safe mode.. Still tells me I don't have permissions.  My account is the Adminstrator account.  So not sure why it is not giving me permissions to overlay the files.  Any other suggestions?

     

    Michael

    2008年1月18日 22:09
  • George,

     

    I found this newsgroup as I too am having a similar problem.  Here are the results of cbscheckstore for me:

     

    C:\Users\Steven\Downloads>x64CbsCheckStore
    Checking Package Manifests and catalogs...
    Error: Invalid Catalog. Error:0x800b0100.
    Name: C:\Windows\servicing\packages\Package_2_for_KB935280~31bf3856ad364e35~amd6
    4~~6.0.1.2.cat
    Size: 25085 bytes.


    Checking package watchlist...

    Checking component watchlist...

    Checking packages...

    Errors found.

     

     

    Any chance you could upload the relevant package for me as well?

     

    Thanks

    2008年1月19日 6:37
  • George,

    If you want to contact me directly just drop me an email at michaelrowe01 AT gmail DOT com . 

    Michael
    2008年1月19日 17:50
  • I fixed my problem by upgrading from the vista DVD to replace everything with default system files.  Then went through the whole update process and everything worked great - am now running SP1.

    2008年1月20日 6:28
  • Anon, I uploaded the file and then just saw your reply... glad the DVD upgrade worked for you!

     

    Michael, I'm not sure what else we can do to claim ownership of the file and replace it.  If all else fails, you can always boot the machine using the Vista DVD, go to a recovery console (I think Shift-F10 or something would do it also from the install screen), and copy the file using the command line.  We are in the process of making a tool that will do this all for you and hope to have it out sometime soon

    2008年1月21日 17:56
  • I get the same Error 0x800B0100 when trying to install Vista sp1 RC, is it possible to find a solution?
    2008年1月22日 21:57
  • Well my problem is the same but the log in the command line program says:
    Error: cannot find package manifest in store for package: package_for_kb935509~31bf3856ad364e35~x86~6.0.1.9.
    please helpme, im the only with that "version" of the same problem.

    thanks.
    2008年1月23日 2:27
  •  George Hilios [MSFT] wrote:

    Anon, I uploaded the file and then just saw your reply... glad the DVD upgrade worked for you!

     

    Michael, I'm not sure what else we can do to claim ownership of the file and replace it.  If all else fails, you can always boot the machine using the Vista DVD, go to a recovery console (I think Shift-F10 or something would do it also from the install screen), and copy the file using the command line.  We are in the process of making a tool that will do this all for you and hope to have it out sometime soon



    I gave that a try, and it allowed me to make the replacements, however Same error on the install.. re-ran the CbsCheck tool, same errors.  I will wait for the tool.  Thanks I am really looking forward to SP1.

    Michael
    2008年1月24日 0:53
  • George, I tried the link / password you posted. This is what I got: https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=492aab30-c810-4121-a626-3cd7799837f2

    There are no files available to download.

    Help.

    2008年2月7日 21:08
  • .....Reference : Post #11

     

    Nuffyfluts, I've uploaded that file to the workspace as well.  Could you follow the same steps and try the install again?



    Following a hardware crash, I'm up and running again and tried to access the file you left for me.
    It , and the other files, appear to have been deleted... there are no files in the directory anymore.
    Can you help?
    Thanks, Nuffyfluts  >>> computerz@cogeco.ca
    2008年2月7日 23:29
  •  George Hilios [MSFT] wrote:

    Sorry for the delay.  I was out of town on holiday and have been busy with SP development.

     

    Please go to https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=492aab30-c810-4121-a626-3cd7799837f2, select receive files from microsoft, and use password "e!fSzWmBQjz0gB" with no quotes.  Run the tool (cbscheckstore.exe) from an elevated commandline (theres 2, use the x64 one if appropriate).  Please post the results and I will try and get you replacement files for what it tells you is corrupt/missing.

    George, I have emailed you as you reequest at the beginning of this thread. 

    Also https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=492aab30-c810-4121-a626-3cd7799837f2 says "No workspace was found corresponding to the supplied password. The password or web page address (URL) may be incorrect. "
     
     
    I am having Vista X64. please help thanks in advance!

    2008年2月16日 19:22
  • Hi,

    I am geeting the error 800B0100 for one of the SP1 prerequisite updates (KB938371). Any ideas how to fix this?

     

    Greetings Marco

    2008年2月17日 10:25
  • I'm getting this same error and also tried the download from sftus.one.microsoft.com but no files were available. Any additional help would be great.

     

    BTW, I'm curious how MS will handle this error when SP1 goes to the world. I don't think "normal" users will be able/willing to follow the instructions presented here.

    2008年2月19日 9:27
  • I found a fix to this issue. I had another Vista machine tha upgraded fine so I just copied all of the files from the good machines C:\Windows\servicing\Packages folder to the problem machine. I did have to take ownership and change some permissions first. After doing the the upgrade was fine.

     

    2008年2月20日 2:48
  • @  George Hilios: Can you please help us?  I have also sent you an email...

    @  Qythyx: Your soution didn't work either sicne a friend did send me the folder and files?

    @  Anon: The Update from the original DVD doesn't work for me, it aborts with a 700er error saying: "Missing files for performing the update.".

    Thanks in advance!

    2008年2月23日 18:22
  • I a

    m sure I am having this problem since rthe Event logger doesn't wprk for me

    http://forums.microsoft.com/msdn/showpost.aspx?postid=1280359&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=1

    and I cannot install Vbista X64 SP1 however the reset.CMD printout doesn't worj for me, it says the command has a syntax error and I shall check /h for  syntax.

    Any help anybody please? I want to know this fixed, thanks in advance!

    Here is what I see: 
    Resetting ACLs...
    (this may take several minutes to complete)

    ==========================================================================


    LookupAccountName : HKEY_LOCAL_MACHINE:administrators 1337 Die Struktur der Sich
    erheitskennung ist unzulässig.

    Current object HKEY_LOCAL_MACHINE will not be processed


    Elapsed Time: 00 00:00:00
    Done: 0, Modified 0, Failed 0, Syntax errors 1
    Last Syntax Error:WARNING : /grant=administrators=f : Error when checking argume
    nts - HKEY_LOCAL_MACHINE


    LookupAccountName : HKEY_CURRENT_USER:administrators 1337 Die Struktur der Siche
    rheitskennung ist unzulässig.

    Current object HKEY_CURRENT_USER will not be processed


    Elapsed Time: 00 00:00:00
    Done: 0, Modified 0, Failed 0, Syntax errors 1
    Last Syntax Error:WARNING : /grant=administrators=f : Error when checking argume
    nts - HKEY_CURRENT_USER


    LookupAccountName : HKEY_CLASSES_ROOT:administrators 1337 Die Struktur der Siche
    rheitskennung ist unzulässig.

    Current object HKEY_CLASSES_ROOT will not be processed


    Elapsed Time: 00 00:00:00
    Done: 0, Modified 0, Failed 0, Syntax errors 1
    Last Syntax Error:WARNING : /grant=administrators=f : Error when checking argume
    nts - HKEY_CLASSES_ROOT


    System Drive...
    WARNING : /grant : Invalid option : C:\Program Files (x86)\Windows Resource Kits
    \Tools
    Use :
    SubInacl /help to get the usage information
    or
    SubInAcl /help syntax to understand SubInAcl syntax.
    Current object C:\Program Files (x86)\Windows Resource Kits\Tools will not be pr
    ocessed


    Elapsed Time: 00 00:00:00
    Done: 0, Modified 0, Failed 0, Syntax errors 1
    Last Syntax Error:WARNING : /grant : Invalid option : C:\Program Files (x86)\Win
    dows Resource Kits\Tools


    Windows Directory...
    LookupAccountName : C:\Windows\*.*:administrators 1337 Die Struktur der Sicherhe
    itskennung ist unzulässig.

    Current object C:\Windows\*.* will not be processed


    Elapsed Time: 00 00:00:00
    Done: 0, Modified 0, Failed 0, Syntax errors 1
    Last Syntax Error:WARNING : /grant=administrators=f : Error when checking argume
    nts - C:\Windows\*.*


    ==========================================================================

    FINISHED.
    Press any key to exit . . .
    Drücken Sie eine beliebige Taste . . .

    2008年2月27日 22:24
  • George,

    I tried to fetch the files you mentioned and I'm getting the following error:

    "No workspace was found corresponding to the supplied password. The password or web page address (URL) may be incorrect. Please verify the password with a Microsoft Support Professional."

    I also have the 800B0100 error while trying to install SP1.  One thing; I've been getting that exact same error trying to install the recent IE7 security update as well - was kind of hoping that SP1 would get me past the other thing.

    Thanks,
    Andy
    2008年3月7日 4:33
  • You're right! I am a "normal" user and don't get any of this, but I am so frustrated by this error code. Is there some way to correct this error using layman's terms? Smile

     

    HELP!! Thanks!

     

    2008年3月15日 3:06
  • George,
    I tried the link you posted, but I am not able to download the files.  I will send you an email as well.  Thanks for any help you can provide.
    2008年3月20日 18:03
  • Please my good George,..

    Can You help me out here with the Vista SP1 corrupt error stuff ???

     

    Thank You

    SUNSHINE

     

     

    2008年3月21日 7:44
  • I need some help with this as well. I just got back from break and tried to install service pack 1 and I get the same error. hopefully someone will have an answer soon.
    2008年3月24日 0:41
  • I have the same problem as the others on this list  . . . please let me know when you have a tool available . . . getting too close to tax time for me to mess with this now.

    Thansk!
    2008年3月25日 13:08
  •  George Hilios [MSFT] wrote:

    I know how to fix this form of corruption!  Please send an email to vistasp1logs@hotmail.com with a link to this thread and your nickname (so I can identify you) and I'll give you instructions

     

    George, I've been getting consistent error the same as the others when trying to get wuauclt to download/install Vista SP1. 

     

    Nick name is Net_Vet

     

    In events, its only a 31 error--Failure download, no other errors, and I can see it time out at 0% downloaded and issue a fail.

     

    Error is 800B0100. Windows Vista Service Pack 1 (KB936330).

    Tried multiple times, there are no other updates showing as available EXCEPT, one hidden update for Office 2003 Service Pack 3 (SP#) which I hid since I'm running Office 2007 and didn't want to risk overwriting files.

     

    Does the 2003 need to install first?

     

    One other thing. I did install the Svc Pk for Office 2007.

    When the machine rebooted it dropped into diagnostics at the dos prompt and reindexed everything and it did report a number of corrupted or missing files.

     

    So the I wonder if the 2007 MS Office Suite Svc Pk 1 (SP1) might have glitched, although it reports as having a success.

    When I first started office Word wouldn't open and Outlook would, but not open email giving an error saying the format command was miissing. But that all cleared up when I ran a Repair from the Office 2007 orginal disks.

     

    Any suggestions.

    While I wait I'll try the close the sidebar thing. If succesful I come back and repost.

    Thanks.

    Remi

     

    2008年4月16日 17:15
  • I have a fresh recovery of VHP 32bit on a Compaq Presario.  I also get error 800B0100 when running fresh download of "Windows6.0-KB936330-X86-wave0.exe".

    The link and pwd above results in "No workspace was found corresponding to the supplied password. The password or web page address (URL) may be incorrect. Please verify the password with a Microsoft Support Professional."

    What now?

    A search for "cbscheckstore.exe" only finds this forum.

    2008年5月3日 13:17
  • Hi George, I am getting the same error code "800B0100" when trying to install SP1 . I tried to use the link that you have posted "https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=492aab30-c810-4121-a626-3cd7799837f2" and use password "e!fSzWmBQjz0gB", however I received the following message:

    {No workspace was found corresponding to the supplied password. The password or web page address (URL) may be incorrect. Please verify the password with a Microsoft Support Professional.}

     

    Kindly advise what to do to fix this error.

     

    Regards

    2008年5月4日 15:35
  • George –

     

    I have exactly the same problem others have reported on Technet.

     

    I have downloaded and read KB 947366 and executed all the resolution steps. All were normal except for the System File Checker. It finished but reported errors that it could not correct. I was directed to the CB.log file which I can view but haven’t the slightest idea how to read or act upon. I also have experienced problems in attempting to install the monthly Junk File Filter update that others have reported (with the same error number>

     

    I really don’t want to go back and reinstall Vista and all my applications from scratch – do I have an out?

     

    Jim Gaffney

     

    2008年5月14日 23:13
  •  

    I am experiencing this problem as well and I have tried everything listed on the link Microsoft provides.  What was the final solution to this problem short of reinstalling everything which is not an option at this time?

     

    Thanks,

     

    Adam

    2008年5月15日 0:45
  • Having same problem. I just emailed you.

     

    Thanks,

    TagUrIt

     

    2008年5月16日 15:36
  • Please help me I cannot install Vista SP1 stalls at error 800B0100.

    I have plenty of disk space.

    I use F-Secure fire and virus.

    I have all other updates.

     

    Thanks

    Joeljohn66

     

    2008年5月21日 18:24
  • I have the same problem. Can anyone who knows how to fix this, please email me at
    josephlamberti@sbcglobal.net
    2008年6月5日 11:47
  •  

    I have the same problem too. I emailed you, George.

     

    I'm getting the same code but according to the update history, it's failing on the junk e-mail filter (KB905866)

    2008年6月12日 14:13
  •  

    Please go to https://sftus.one.microsoft.com/choosetransfer.aspx?key=5607543d-be9d-44dc-87aa-95b75b45ad1b.  Click Reveive Files from Microsoft, and use password iIG9!C8GqMb4U.  Download cbscheckstore.exe, and run the following from an elevated command prompt:

     

    cbscheckstore.exe > output.txt

     

    Then paste the contents of output.txt here and we will see which certificates have been corrupted on your system

    2008年6月12日 17:46
  • George,

    Here's the output from my machine:

    Checking Package Manifests and catalogs...
    Error: Failed to parse: C:\Windows\servicing\packages\Package_1_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1.mum
    Line 1:

    (

    Error: Failed to parse: C:\Windows\servicing\packages\Package_2_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1.mum
    Line 1:

    regf

    Checking package watchlist...

    Checking component watchlist...

    Checking packages...
    Warning: Failed to open owner key for package: Package_1_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002
    Warning: Failed to open owner key for package: Package_2_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Errors found.


    Any help on getting past this update error would be most appreciated.

    Thanks,
    Andy
    2008年6月12日 18:09
  • I've uploaded ak732-fix.zip to the workspace, so please download that in the same way you did cbscheckstore.exe.  Then, you should replace the files in c:\windows\servicing\packages with the ones contained in the zip file, regardless of whether or not they are there.  Doing so is a bit tricky because of the heavy permissions on them, so here are some instructions:

     

    Right click each file, go to properties, security tab, Advanced, Owner tab, Edit (will prompt for elevation), and then change owner to yourself (it is probably set to Trusted Installer).  Then run the following from an elevated command prompt:

     

    net stop trustedinstaller

     

    If it succeeds or trustedinstaller is not already running, you can proceed.  If it fails, there is probably a package waiting reboot, so do that, and try again after.

     

    Then you can replace the files from within the cab and run cbscheckstore again.  If it doesn't find any problems, try the install again!

    2008年6月12日 18:21
  • George,

    Thanks for helping out.  I adjusted the ownership, copied the files contained in the zip file.  Two of the files required overwriting existing files, two were new to the packages folder.

    Unfortunately, I'm still getting errors from cbscheckstore:

    ~~~~~~~~~~~~~~~~~

    Checking Package Manifests and catalogs...
    Error: Failed to parse: C:\Windows\servicing\packages\Package_2_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1.mum
    Line 1:

    regf

    Checking package watchlist...

    Checking component watchlist...

    Checking packages...

    Warning: Failed to open owner key for package: Package_1_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002
    Warning: Failed to open owner key for package: Package_2_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Errors found.

    ~~~~~~~~~~~~~~~~~

    I even went back and re-copied the files, individually, just to be sure.

    Thanks,
    Andy
    2008年6月12日 19:02
  • Hi George

     

    I have the same problem as Andy (AK732) and run the cbscheckstore.exe command on my Laptop and received the following output file

     

    ______________________

    Checking Package Manifests and catalogs...
    Error: Package manifest cannot be validated by the corresponding catalog.
    Error:0x800b0100Name:
    C:\Windows\servicing\packages\Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.13.0.mum
    Size: 2452 bytes.

    Name: C:\Windows\servicing\packages\Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.13.0.cat
    Size: 12686 bytes.

    Error: Failed to parse: C:\Windows\servicing\packages\Package_for_KB938194~31bf3856ad364e35~x86~~6.0.1.2.mum
    Line 1:

    QdEءu©ط“‍غحب‰,i±‌گن„­n©¥‚لا²،¥«·ں•5کUکـ{„X $ô‘8ٍw5³‎z¢—o»ڑ

    Checking package watchlist...

    Checking component watchlist...

    Checking packages...
    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.14.0, possibly an orphaned package.error: 0x80070002
    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.15.0, possibly an orphaned package. error: 0x80070002
    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.16.0, possibly an orphaned package. error: 0x80070002

    Errors found.

    ________________________

     

    Kindly Advise

    2008年6月13日 6:30
  • SamerJ, can you try the same instructions with SamerJ-Fix.zip that I have uploaded to the workspace?

     

    ak732, could you open C:\Windows\servicing\packages\Package_2_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1.mum and see if it looks corrupt to you?  Should be pretty basic XML.  In fact, if you copy it to another location on your hard drive, change the file extension to .xml and open in internet explorer, it should open with no errors.  Just to double check, C:\Windows\servicing\packages\Package_2_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1.mum was one of the files you replaced, correct?

    2008年6月13日 17:21
  • George,

    The zip file you sent me did not have any files starting with "Package_2".  They were all "Package_1" files.  So now, I didn't copy in the Package_2 file.

    The contents of the zip file you sent me are:

      package_1_for_kb944533_bf~31bf3856ad364e35~x86~~6.0.1.1.cat
      package_1_for_kb944533_bf~31bf3856ad364e35~x86~~6.0.1.1.mum
      package_1_for_kb944533~31bf3856ad364e35~x86~~6.0.1.1.cat
      package_1_for_kb944533~31bf3856ad364e35~x86~~6.0.1.1.mum

    I guess I still need replacements for the two problematic packages?

    Thanks,
    Andy
    2008年6月13日 18:45
  • George,

    Also, the file below does appear corrupt.  It's certainly not XML - looks like a binary file of some sort.

       Package_2_for_KB944533~31bf3856ad364e35~x86~~6.0.1.1.mum

    Thanks,
    Andy


    2008年6月13日 18:54
  • Is the version of that file in the .cab corrupt as well?

    2008年6月13日 19:18
  • George,

    That file doesn't exist in the CAB file you sent.

    Thanks,
    Andy
    2008年6月13日 19:37
  • You are right, sorry good sir!  Bad George.  Please try ak732-fix2.cab on the workspace.  I included this file in there as well

     

    2008年6月13日 19:57
  • Dear George,

    Thanks for the fix, I have copied and replaced the files you have sent. However after running "cbscheckstore.exe > output.txt" again I received the following output:

    {

    Checking Package Manifests and catalogs...

     

    Checking package watchlist...

     

    Checking component watchlist...

     

    Checking packages...

    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.14.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.15.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.16.0, possibly an orphaned package. error: 0x80070002

     

    Errors found.

    }

     

    Kindly advise

    2008年6月13日 21:00
  • Great!  Try SP1 install now.  You can ignore those warnings.  We don't care too much about orphaned packages, but its good info we want to collect to improve servicing in the future

     

    2008年6月13日 21:06
  • Hi George,

    Emailed you today, same problem as others. SP1 in my case is Failed to Download.

    Will running cbscheck exe help to identify a missing/corrupted file that causes this 800b0100 error reporting?

     

    thanks.

    NV

     

    2008年6月14日 1:05
  • The email address doesn't really work...

     

    Could you run cbscheckstore.exe from that workspace so we can figure out what is corrupt?

     

    As an FYI to anyone hitting this issue, a newer version of a package is coming out soon to be offered over Windows Update which fixes corruption issues like this one.  So don't be worried about having to come here if it hits you again!

    2008年6月14日 1:26
  • I'd like to run cbscheckstore.exe but I don't have the executable. Can you provide a link?

    Tried the link you gave others to a space but it wouldn't let me enter the password.

     

    Thanks.

    nv

     

     George Hilios [MSFT] wrote:

    The email address doesn't really work...

     

    Could you run cbscheckstore.exe from that workspace so we can figure out what is corrupt?

     

    As an FYI to anyone hitting this issue, a newer version of a package is coming out soon to be offered over Windows Update which fixes corruption issues like this one.  So don't be worried about having to come here if it hits you again!

    2008年6月14日 1:50
  • George,

    Just wanted to loop back and thank you for your help with this issue.  The latest fix you posted worked and I've got SP1 up and running.

    I've noticed one post-SP1-update problem.  My browser home page, which is a custom ASP.NET application that runs off IIS7 on localhost, is no longer working.  It's been working fine forever prior to the SP1 update.  But now, for some reason, I cannot connect to the website on localhost.  I've republished it (from VS.NET 2008).  But it just won't connect in either IE7 or FF2.

    Does that issue ring a bell by any chance?  Is it maybe a permissions problem?  Does the SP1 update modify IIS permissions?

    Anyway, thanks again for your help.

    Andy


    2008年6月14日 2:03
  • Thanks a lot George, I was able to install SP1. The SP1 also resolved a problem that I was experincing before when updating windows :

    "Windows could not search for new updates, Error Code 8024400D"

     

    Best Regards

     

     

    2008年6月14日 10:19
  • Hi George,

    I too am having a problem installing Vista SP1. The error code returned is 800B0100.

     

    I have run the command CBSCheckStore.exe as instructed and it returned the following output:

     

    Checking Package Manifests and catalogs...

    Error: Invalid Catalog. Error:0x800b0100.

    Name: C:\Windows\servicing\packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.cat

    Size: 15461 bytes.

     

     

    Checking package watchlist...

     

    Checking component watchlist...

     

    Checking packages...

     

    Errors found.

     

    If you could instruct me on what i need to do to repair the corrupt package that would greatly appreciated.

     

    Regards,

     

    NTM

     

    2008年6月14日 12:09
  •  

    Hi George...

     

    I initiated this string way back in December.

     

    For several months I tried unsuccessfully to install SP1 following various solutions you had recommended.

     

    Nothing worked for me, so I decided to wait for the official release from Microsoft.

     

    When it was made available to the masses, only once did I get access to the upgrade using the Windows Update route. It failed then, and I've never seen the upgrade since.

     

    I've recently downloaded the upgrade via another route but I still can't get SP1 to install.

     

    Have the previous incompatibilities with some drivers been resolved (Nvidia, Zone Alarm, Realtek AC'97, ...)?

     

    Is there a comprehensive list of drivers that SP1 has trouble with and where can I find it? 

     

    I'm looking to give the SP1 upgrade another try but need your most current advice on how to proceed.

     

    Thanks... Nuffyfluts

    2008年6月14日 12:41
  • George, I am having the same problem with installing Vista Service PAck 1. I am getting th eerror 0X800B0100. Could you please help me.

    Regards, Richard

     

    2008年6月15日 3:49
  • George,

    I am completely stuck with this.

     

    VISTA sp1 ran from the windows update site automatically.

    Once ran, I had lost all my admin privs on my basic account so I chose a system restore point and went back.

    I then noticed that I could not install sp1 due to this error; I subsequently noticed that no windows updates would install because of this error.

    I then contact microsoft support and have spent 5 hours with them.  I now have no virus software, no firewall etc and still cannot install any windows update or sp1 because of this error.

     

    I have all the services you have listed running.

     

    I tried to go to the link but it would not let me enter a password.

     

    Thanks in advance

    2008年6月15日 18:03
  • It appears the workspace expired.  I've created a new one here:

     

    https://sftus.one.microsoft.com/choosetransfer.aspx?key=54e2a332-5eab-495c-a4ae-31e13fa2b006

     

    Password: d1NL3Sw)Gv[]UP%@

     

    I put cbscheckstore.exe back there.

     

    Ntm79, I've uploaded ntm79.zip there as well with the file you need.  Can you follow the previous instructions to put this into c:\windows\servicing\packages?
    Trhepbur, can you try the new workspace link?
    Nuffyfluts, are you getting this error code?  If so, please follow the instructions I just provided.

    2008年6月17日 17:50
  •  

    It seems the workspace link changed a bit after I created it.  Try https://sftus.one.microsoft.com/choosetransfer.aspx?key=54e2a332-5eab-495c-a4ae-31e13fa2b006 with the same password

    2008年6月17日 20:21
  • Dear George,

     

    I have run the cbscheckstore.exe, I got the following :

     

    Error: Invalid Catalog. Error:0x800b0100

    Name: C:\Windows\servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad36

    4e35~x86~~7.0.6000.381.cat

    Size: 11639 bytes.

     

    Checking package watchlist...

     

    Checking component watchlist...

     

    Checking packages...

     

    Error found

     

    While I was running cbscheckstore.exe, the program was closing very rapidly at the end, is this normal? I have been able to copy those doing a print screen.

     

    I hope you can help me with the error I just found.

     

    Best regards,

     

    Reynald

     

     

    2008年6月17日 20:39
  • Yes that is expected, it is meant to be run from the command line so I'm sorry for not clarifying.

     

    I've uploaded raytigger.zip which has this missing file!

    2008年6月17日 20:44
  • George,

    I was able to access this and ran cbsstore

    Output is

     

     

    C:\Users\Magshepburn\Documents\My Downloads>cbscheckstore
    Checking Package Manifests and catalogs...
    Error: Failed to parse: C:\Windows\servicing\packages\Package_30_for_KB936330~31bf3856ad364e35~x86~~6.0.1.18000.mum
    Line 1:

    put type="hidden" name="stAmbiguous" id="stAmbiguous" value="" /


    Checking package watchlist...

    Checking component watchlist...

    Checking packages...

    Errors found.

    C:\Users\Magshepburn\Documents\My Downloads>

     

    Thoughts?

    Thx

    Tony

    2008年6月17日 21:24
  •  

    Wow.  That one in particular is weird.  Maybe there was power loss in the middle of the install, or you have a bad hard drive?

     

    I've uploaded trhepbur.zip which should have a replacement for that corrupt file which will unblock you for the time being.  At some point though, I'd suggest running "chkdsk /r" from an elevated command prompt to check the state of your disk.

    2008年6月17日 21:35
  • George,

    system will not let me do it either from within explorer or from and CMD prompt opened as administrator.  I suspect the core of what is wrong here is that somehow my profile has been corrupted.  When I did the original SP1 install I could do no system commands at all; when I used a restore point I got back what seemed to be close to all my privs.  But windows update no longer functioned.  Dont know if this helps or not.

    Tony

     

    2008年6月17日 22:27
  •  

    Yeah there are instructions earlier in the thread about taking ownership of the file through the explorer UI.  Can you try those?  I think its on page 4

    2008年6月17日 22:37
  • Am also having alot of problems with this error. I have downloaded the trhepbur.zip file, but am having problems with permissions. Have followed the instructions on page 4 but not sure how to run

    the following from an elevated command prompt:

     

    net stop trustedinstaller



    What does elevated cmd mean?



    When I run CbsCheckStore I get the following:



    Checking Package Manifests and catalogs...
    Error: Invalid Catalog. Error:0x800b0100.
    Name: C:\Windows\servicing\packages\Package_30_for_KB936330~31bf3856ad364e35~x86
    ~~6.0.1.18000.cat
    Size: 2149036 bytes.


    I cant seem to get any successful updates since this error has materialised.

    Sorry for hijacking this thread bye the way.

    Leonard
    2008年6月18日 0:52
  • Getting the following after running cbscheckstore:

     

    Checking Package Manifests and catalogs...

    Error: Failed to parse: C:\Windows\servicing\packages\Microsoft-Windows-Secure-Key-Backup-Package-KB932926-MiniLP~31bf3856ad364e35~x86~en-US~6.0.6000.16442.mum

    Line 3:

     

    [100003]

    ;CA- AntiSpam

    ProductVersion=2,0,1,0

     

    [40003]

    ;Zon

     

     

    Checking package watchlist...

     

    Checking component watchlist...

     

    Checking packages...

     

    Errors found.

     

    Help is appreciated.

    2008年6月18日 5:20
  • Hello
    I am getting the following errors ??? any pointers would be good....regards

     

    Checking packages...

    Error: Cannot find package manifest in store for package: Package_1_for_KB905866

    ~31bf3856ad364e35~x86~~6.0.12.0.

    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad

    364e35~x86~~6.0.13.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad

    364e35~x86~~6.0.14.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad

    364e35~x86~~6.0.15.0, possibly an orphaned package. error: 0x80070002

    Error: Cannot find package manifest in store for package: Package_1_for_KB933729

    ~31bf3856ad364e35~x86~~6.0.1.1.

    Error: Cannot find package manifest in store for package: Package_1_for_KB939653

    ~31bf3856ad364e35~x86~~6.0.1.0.

    Error: Cannot find package manifest in store for package: Package_1_for_KB941202

    ~31bf3856ad364e35~x86~~6.0.1.0.

    Error: Cannot find package manifest in store for package: Package_2_for_KB939653

    ~31bf3856ad364e35~x86~~6.0.1.0.

    Error: Cannot find package manifest in store for package: Package_2_for_KB941651

    ~31bf3856ad364e35~x86~~6.0.1.0.

    Error: Cannot find package manifest in store for package: Package_3_for_KB939653

    ~31bf3856ad364e35~x86~~6.0.1.0.

    Error: Cannot find package manifest in store for package: Package_for_KB939653~3

    1bf3856ad364e35~x86~~6.0.1.0.

    Error: Cannot find package manifest in store for package: Package_for_KB941651~3

    1bf3856ad364e35~x86~~6.0.1.0.

     

    Errors found.


    2008年6月18日 14:43
  •  Net_Vet wrote:

    I'd like to run cbscheckstore.exe but I don't have the executable. Can you provide a link?

    Tried the link you gave others to a space but it wouldn't let me enter the password.

     

    Thanks.

    nv

     

     George Hilios [MSFT] wrote:

    The email address doesn't really work...

     

    Could you run cbscheckstore.exe from that workspace so we can figure out what is corrupt?

     

    As an FYI to anyone hitting this issue, a newer version of a package is coming out soon to be offered over Windows Update which fixes corruption issues like this one.  So don't be worried about having to come here if it hits you again!

     

     

    Hi George,

    I finally managed to get ahold of cbscheckstore.exe at a time when the library was active and ran the checker.

     

    It listed a package 16 catalog error (0 bytes) which was an invalid file.

    I have another Vista system so I copied over the file to windows\servicing\packages after changing ownership of the folder successfully.

     

    Ran the checker again and it reported no errors so I'll try the SP1 update now and see if it will download now and will post back.

     

    cbschecker results -

     

    Checking Package Manifests and catalogs...

    Error: Invalid Catalog. Error:0x800b0100. Name: C:\Windows\servicing\packages\Package_16_for_KB938371~31bf3856ad364e35~x86~~6.0.2.27.cat Size: 0 bytes.

    Checking package watchlist... Checking component watchlist... Checking packages... Errors found.

     

     

    . . . and after copying over the file in error from another vista machine:

     

    Checking Package Manifests and catalogs...

    Checking package watchlist...

    Checking component watchlist... Checking packages...

    No Errors are found.

     

    Thanks.

     

    Net_Vet

     

     

    2008年6月18日 15:11
  • George,

    file shows that I am the owner of the package file and that I have full control of both the unzipped file and the one in the packages folder, but I still have a security conflict.

    Tony

     

    2008年6月18日 18:07
  • Hi George,

    I too am seeing this error and would be grateful for your assistance.  I've posted the output of cbscheckstore below.

    Thanks

    Checking Package Manifests and catalogs...

    Checking package watchlist...

    Checking component watchlist...

    Checking packages...

    Warning: Failed to open owner key for package: Package_18_for_KB933928~31bf3856ad364e35~x86~~6.0.1.6, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_19_for_KB933928~31bf3856ad364e35~x86~~6.0.1.6, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.21.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB929123~31bf3856ad364e35~x86~~6.0.1.4, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB929399~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB929735~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB929916~31bf3856ad364e35~x86~~6.0.1.7, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB930857~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB931099~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB933729~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB933928~31bf3856ad364e35~x86~~6.0.1.6, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB936357~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB936782~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB936825~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB938127~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB938979~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB939159~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB941202~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB941569~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB941600~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB941649~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB943055~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB943078~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB943899~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB945553~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB946026~31bf3856ad364e35~x86~~6.0.1.3, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB946041~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB950126~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB951376~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_1_for_KB951698~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB929123~31bf3856ad364e35~x86~~6.0.1.4, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB933928~31bf3856ad364e35~x86~~6.0.1.6, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB936824~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB938979~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB941649~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB941651~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB941693~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB943899~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB946041~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB950126~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_2_for_KB950759~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_36_for_KB942763~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_36_for_KB943411~31bf3856ad364e35~x86~~6.0.1.5, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_37_for_KB942763~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_37_for_KB943411~31bf3856ad364e35~x86~~6.0.1.5, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_38_for_KB943411~31bf3856ad364e35~x86~~6.0.1.5, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB905866~31bf3856ad364e35~x86~~6.0.21.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB929123~31bf3856ad364e35~x86~~6.0.1.4, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB929916~31bf3856ad364e35~x86~~6.0.1.7, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB933928~31bf3856ad364e35~x86~~6.0.1.6, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB938979~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB941649~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB950126~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB951376~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_3_for_KB951698~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_4_for_KB938979~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_4_for_KB941649~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_4_for_KB950126~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_5_for_KB933928~31bf3856ad364e35~x86~~6.0.1.6, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_5_for_KB938979~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_5_for_KB941649~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_5_for_KB941693~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_5_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_5_for_KB950759~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_6_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_7_for_KB938123~31bf3856ad364e35~x86~~6.0.1.5, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_7_for_KB942763~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_7_for_KB943411~31bf3856ad364e35~x86~~6.0.1.5, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB905866_client_0~31bf3856ad364e35~x86~~6.0.21.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB905866_client_1~31bf3856ad364e35~x86~~6.0.21.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB905866_client~31bf3856ad364e35~x86~~6.0.21.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB905866~31bf3856ad364e35~x86~~6.0.21.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB929123~31bf3856ad364e35~x86~~6.0.1.4, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB929916~31bf3856ad364e35~x86~~6.0.1.7, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB933928~31bf3856ad364e35~x86~~6.0.1.6, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB936824~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB938123~31bf3856ad364e35~x86~~6.0.1.5, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB938979~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB941649~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB941651~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB941693_client_0~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB941693_client_1~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB941693_client~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB941693~31bf3856ad364e35~x86~~6.0.1.2, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB942763~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB943411~31bf3856ad364e35~x86~~6.0.1.5, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB943899~31bf3856ad364e35~x86~~6.0.2.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB946041~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB947562_client_0~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB947562_client_1~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB947562_client~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950126_client_0~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950126_client_1~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950126_client~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950126~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950759_client_0~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950759_client_1~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950759_client~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB950759~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951376_client_0~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951376_client_1~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951376_client~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951376~31bf3856ad364e35~x86~~6.0.1.1, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951698_client_0~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951698_client_1~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951698_client~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Warning: Failed to open owner key for package: Package_for_KB951698~31bf3856ad364e35~x86~~6.0.1.0, possibly an orphaned package. error: 0x80070002

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~x86~~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.0.6000.381.

    Error: Cannot find package manifest in store for package: WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.0.6000.381.

    Errors found.


    2008年6月18日 22:08
  • George, you have to be thinking by now 'leave me alone' so your a Saint in continuing your efforts in resolving this issue for others (all of us less computer savy types).

     

    If this error can be resolved by doing a clean install of Vista, I am considering doing it to resolve some issues including -but not limited to - that for about a month now, I can't print from IE (it goes through the motions but '0 documents to print' is basically what the printer icon shows when I pass over it).

     

    Not the thing I'd rather do since it is such a time consuming headache but sometimes a necessary evil.

     

    Anyway, as of today, the 2nd link has no files available to download.

     

    I too have had the same problem with SP1 and I do have Vista Ultimate, which in some of your posts, I believe had something to do with this problem.

     

    I downloaded my file on 4/11/08 (6.0.6001.17028) so if there's a newer file available, let me know.

     

    Updates has tried to install SP1 7+ times, each time claiming it successfully installed - which installs very quickly w/o needing a reboot - though I remember it rebooting after the 1st attempt - which is why I suppose it has installed so many times since.

     

    Please restate your instructions so I, and any others following, are up to speed with what your doing to help so I (we) don't have to read posting after posting trying to keep it all straight in what you need from us and such.

     

    Looking forward to resolving this issue.

    2008年6月24日 13:31
  • I have been reluctant to post for fear of stepping on someone's toes, but I have successfully overcome the 800B0100 problem using instructions given to me by a support tech.

     

    The solution lay in downloading and running a System Update readiness tool (which told me I needed to uninstall Acronis Disk Director Suite before preceeding) and then doing a In-Place Upgrade using the original Vista Installation disk. The In-Place Upgrade is apparently akin to the XP Non-destructive install; the OS files were replaced with fresh copies, but the registry was not overwritten so I didn't have to reinstall all my applications. I DID have to reinstall many device drivers - sound, mouse, and others and my two-panel display configuration somehow was disturbed, but was easily corrected. After the install, auto-updated went back and picked up some 50 plus updates to get the system up to date.

     

    I am reluctant to post the instruction message here, but if anyone is interested, I'll be happy to forward a copy of the instruction message to you. I make no guarantees; I'm not a tech, but the solution worked for me. As always, do a fresh backup before you do anything else - just in case.

     

    jim@jgaffney.net

    2008年6月24日 14:34
  • Funny, I was just about to mention that Smile  A tool we've been working on called the System Update Readiness tool can be downloaded at http://www.microsoft.com/downloads/details.aspx?FamilyId=D22AF4E2-1AAF-4672-8951-4B7920F982E9&displaylang=en

     

    It has the ability to replace a large number of the files/registry keys that can get corrupted, so could you all try running this?  We will be releasing a newer version within the next month or two with the ability to fix an even larger number of issues.

    2008年6月24日 16:39
  • Hi George,

    Thank you for your continued help with this.

    Have downloaded the system readiness tool - it fails to run with the following error -

    Installer encountered an error: 0x80004002
    No such interface supported

    I'd be really grateful for any other suggested solution you're able to offer.

    Thanks
    2008年6月24日 21:00
  • Folks,

    I finally gave up.

    I spent 5 hours on the phone with microsoft support.

    I used the system readiness tool

    I ran cbs*(_* that George recommended.

    I switched off all non-microsoft services

    I uninstalled all virus checkers and firewalls

    I now have a PhD in frustration.....

    Nothing worked.

     

    I did a complete new Vista install; cut out all the Dell *** that they loaded.

    Then discovered that Vista Windows Update does not work with installed memory > ~ 3GB (3.2?)

     

    Found a post on a site [http://www.petri.co.il/cannot_install_update_windows_vista_kb929777.htm] that indicated using

     

    bcdedit /set removememory 2000      (that took me down to ~ 2GB)

     

    to set your 'active' memory to < 3GB would fool the install system.  You need to use this command with real care; once done you have to reboot and depending on what happens after the windows update you may need to reverse the instruction (bcdedit /deletevalue removememory); read up on this before you try it.

     

    When I did that windows update miraculously worked, all updates installed and SP1 installed cleanly.

     

    Now I am just a victim of my own ignorance as I did not realise that Dell had installed Vista on Disk 1 instead of Disk 0 so I now have a 30Gb partition on a hard disk that I cannot reclaim because Vista will not allow you to remove a partition that once had a vista operating system there.  Still thats a problem for another day.

     

    2008年6月24日 21:41
  •  

    Fritz--

     

    Can you please check if there is a %windir%\logs\CBS\CheckSUR.log (C:\Windows\logs\CBS\CheckSUR.log) file?

     

    If there is, please open it up in Notepad and paste the contents here. If it isn't present, I'd also like to know.

     

    Thanks.

    2008年6月25日 0:10
  •  George Hilios [MSFT] wrote:

    I know how to fix this form of corruption!  Please send an email to vistasp1logs@hotmail.com with a link to this thread and your nickname (so I can identify you) and I'll give you instructions

    2008年6月25日 4:22
  • That email address doesn't work anymore... please don't use it

    2008年6月25日 18:57
  • Hi Erik,

    The only files in this location are CBS.log and FilterList.log.  There is no file called CheckSUR.log.

    Thanks
    2008年6月25日 20:17
  •  

    Tried sending an email and got a delivery failure notice so already knew though you were not responding to me.

     

    I’ve tried the System Update Readiness tool at http://www.microsoft.com/downloads/details.aspx?FamilyId=D22AF4E2-1AAF-4672-8951-4B7920F982E9&displaylang=en and it installed just fine but changed nothing.

     

    I still can't get SP1 to install via Updates or the install program.

     

    Reading the post mentioning the memory issue makes me wonder if my having 3GB of RAM somehow is affecting things.

     

    Any thoughts about that?

     

    Is anyone else having trouble have over 2GB of RAM?

    2008年6月26日 2:20
  • Can you please paste the contents of your %windir%\logs\CBS\CheckSUR.log file to this thread?

     

    Thanks.

    2008年6月26日 3:59
  •  


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-06-24 21:08:53 PM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.19.0.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\Package_3_for_KB905866~31bf3856ad364e35~x86~~6.0.19.0.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\Package_for_KB905866_client_0~31bf3856ad364e35~x86~~6.0.19.0.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\Package_for_KB905866_client_1~31bf3856ad364e35~x86~~6.0.19.0.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\Package_for_KB905866_client~31bf3856ad364e35~x86~~6.0.19.0.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\Package_for_KB905866~31bf3856ad364e35~x86~~6.0.19.0.mum  
    Checking component registry
    (w) Warning CSI 0x00000002 COMPONENTS\DerivedData\Components\x86_microsoft-windows-f..client-applications_31bf3856ad364e35_6.0.6000.16386_none_76c2ea6b2b7b540d  Missing: Failed to open component key.  This is not expected, but not catastrophic.  Information gathering.
    (w) Warning CSI 0x00000002 COMPONENTS\DerivedData\Components\x86_microsoft-windows-f..lications.resources_31bf3856ad364e35_6.0.6000.16386_en-us_122307d77f1dd3f4  Missing: Failed to open component key.  This is not expected, but not catastrophic.  Information gathering.

    Checking component store

    Scanned 10045 components, 12972 component payload files
    Summary:
    Milliseconds: 803547
     Found 6 errors
      CSI Warning Total Count: 2
      CBS Missing Manifest Total Count: 6
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

     

    2008年6月26日 4:10
  •  

    Atomic04--

     

    Based on your log, I can tell you that your SP1 install is definitely failing due to registry data going missing. It looks at though you may also have some disk inconsistencies; you might try running chkdsk to confirm that. I would also advise you to run the Memory Diagnostics Tool that is included with Vista.

     

    That said, I can say with absolute certainty that your problems are not related to the amount of RAM in your computer.

     

    You may be wondering why, exactly, these things are in this state. It could be due to any number of problems, including bad hardware or buggy drivers. However, in the majority of these cases, it tends to get traced back to a hard reboot of the machine at some point (not properly shutting down). I obviously can't say for sure.

     

    We are working towards being able to help repair some of these inconsistencies, but unfortunately the current version of the CheckSUR tool that is available in unable to fix these. I can't comment on when a better tool may be available, but rest assured that we are trying to help our customers as much as possible.

     

    For now, the only immediate advice I can give is that a fresh installation of Vista should resolve this issue for you. I know that's not ideal, but unfortunately, when we're dealing with data going missing, we're in uncharted waters.

     

    Sorry that I can't be of more immediate help.

    2008年6月26日 4:32
  • Here is my log.  Thanks in advance.


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-06-25 21:53:13 PM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.
    (f) Corrupt Manifest CBS 0x800F0900 \servicing\packages\Package_2_for_KB938979~31bf3856ad364e35~x86~~6.0.1.2.mum  Line 1: INDX(

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    Checking component registry

    Checking component store

    Scanned 8044 components, 11667 component payload files
    Summary:
    Milliseconds: 379755
     Found 1 errors
      CBS Corrupt Manifest Total Count: 1
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

     

    2008年6月26日 5:06
  • First, I'll do a check disk as soon as possible but not today - it's too late here for it's just past midnight.

     

    Not at all suprised you brought up improper shutdowns for something - at times - will not allow me to properly reboot or shutdown and it just sits there 'shutting down'.

     

    Don't mind the 5+/- minute waits but once I let it go for over 14 hours before I got fed up waiting.

     

    Figured a clean install was coming but I just hate taking the time for all that 'fun'.

     

    Guess I'd better get it over with.

     

     

    2008年6月26日 5:26
  • I have worked two days with tech support who acts like this a new problem. Now they are saying this is not a VISTA problem and I will need to pay a fee. This thread started over 6 months ago???

     

    I know a bit, but am in no way an expert. I know enough to say that I have wasted untold hours on this. Each time I contact tech support they refuse to read the case file and we proceed on a goose chance.

     

    Usually I just give up on Microsoft and do a complete reinstall which takes me three days since I am on a slower DSL, which is the only service available to me. From reading this thread, it does not appear even that will help me.

     

    Please help!

     

     

    2008年6月28日 17:24
  • Please run http://www.microsoft.com/downloads/details.aspx?FamilyId=D22AF4E2-1AAF-4672-8951-4B7920F982E9&displaylang=en and try the install again.  If that does not help, paste the contents of C:\Windows\logs\CBS\CheckSUR.log here.
    2008年6月28日 17:33
  • OK I did as you equested even though I had done this process multiple times before. Again it errored out. Here is the information you requested: BTW thank you.

     

     


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-06-28 13:52:03 PM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.
    (f) Corrupt Catalog CBS 0x800B0100 \servicing\packages\Microsoft-Windows-Help-CoreClientUAPS-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.cat  
    C:\Windows\servicing\packages\Microsoft-Windows-Help-CoreClientUAPS-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.cat
     Size: 39183 bytes.
    (f) Corrupt Catalog CBS 0x800B0100 \servicing\packages\Package_1_for_KB938127~31bf3856ad364e35~x86~~6.0.1.0.cat  
    C:\Windows\servicing\packages\Package_1_for_KB938127~31bf3856ad364e35~x86~~6.0.1.0.cat
     Size: 12809 bytes.
    (f) Corrupt Catalog CBS 0x800B0100 \servicing\packages\Package_2_for_KB937143~31bf3856ad364e35~x86~~6.0.1.4.cat  
    C:\Windows\servicing\packages\Package_2_for_KB937143~31bf3856ad364e35~x86~~6.0.1.4.cat
     Size: 43348 bytes.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    Checking component registry

    Checking component store

    Scanned 8171 components, 11818 component payload files
    Summary:
    Milliseconds: 262269
     Found 3 errors
      CBS Corrupt Catalog Total Count: 3
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

     

    2008年6月28日 21:16
  • I've been reading this thread for a couple of days because my laptop seems to have the same issue.

    I have now run the readiness tool, and cannot find a log where you suggested.  I do have a manifest file, but no *.log file.

    Am I missing something?

    Same 800B0100 issue.

    I've already tried taking ownership, but am unsure as where to go from here.

    Please let me know what you need to see and I would be happy to provide to fix this issue.

    Thanks!


    2008年6月29日 21:34
  • After spending three days with tech support, finally got someone who knew what they were doing.

     

    It amazes me how had it is to get them to just look at what has been done. They just want to start over and re-do the same things. Over and over, and over and over.

     

    The end result. had to do an operating system reboot after deleting all spam and virus protection. Took me about four hours. Will know in about another two if I am out of the woods.

     

    One weird thing was it refused to recognize my copy as valid. Tech guy said once SP1 finishes this will eliminate the problem.

     

    IMHO - don't fight it - do an operating system re-install - not a clean install.

     

    2008年6月29日 22:00
  • Dear George,

     

    I have tried several times to paste the file you send me under raytigger.zip. I always get a reply that you need permission to perform this action. I must have not set up the permission properly. Could you tell me what am I doing wrong or is there a link where I will find the info how to set up the permission as required.

     

    Thank you

     

    Rey

     

    2008年6月30日 21:04
  • Finally had success downloading and installing SP1.

    You don't need to do a Vista reinstall or slick your disk and start from scratch.

    A methodical search of the literature and fixing each thing as it comes up, repeating the procedures as each different error is listed will get you there, at least it did for me.

     

    Below is some info I managed to save and document which might be helpful for others.

    I avoided a reinstall and SP1 installed giving me much improved system performance and stability.

     

    Lots of cold reboots after Vista freezeups was probably the cause of a lot of my systems corruptions and lost files,etc.

     

    After fixing 800B0100 via cbschecker I got new errors.

     

    I had 3 corrupt files after getting rid of Corrupt Catalog CBS 0x800B0100 and hr=0x80070002 (missing file), Corrupt Manifest CSI 0x00000000,

     

     

     


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-06-29 4:35:53 AM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    Checking component registry


    Checking component store
    (f) Corrupt Manifest CSI 0x00000000 
    \winsxs\Manifests\x86_3f81913969a668a202fb070bef83af3b_31bf3856ad364e35_6.0.6000.20734_none_17c8906a06220183.manifest 
    3f81913969a668a202fb070bef83af3b, Culture=neutral, Version=6.0.6000.20734, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS 
    Manifest: Empty file

    (f) Corrupt Manifest CSI 0x00000000 
    \winsxs\Manifests\x86_5736fb1534f4d37c26b504dd97d6cde2_31bf3856ad364e35_6.0.6000.16609_none_85e1098d3a34103b.manifest 
    5736fb1534f4d37c26b504dd97d6cde2, Culture=neutral, Version=6.0.6000.16609, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS 
    Manifest: Empty file

    (f) Corrupt Manifest CSI 0x00000000 
    \winsxs\Manifests\x86_microsoft-windows-s..stack-msg.resources_31bf3856ad364e35_6.0.6000.20782_zh-cn_c01ad85296ab5d3c.manifest 
    Microsoft-Windows-ServicingStack-Msg.Resources, Culture=zh-CN, Version=6.0.6000.20782, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS 
    Manifest: Empty file


    Scanned 7878 components, 11692 component payload files
    Summary:
    Milliseconds: 455406
     Found 3 errors
      CSI Corrupt Manifest Total Count: 3
    Customer Experience report successfuly uploaded.  Thank you for participating. 
    For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

    ======================================

     

    So, diving in after finding a ppt in the previous posts about error managment I downloaded some of the guides, etc.

     

    This one was VERY helpful. So, download the

    Windows Vista Deployment Error Diagnostic Guide

     

     

    https://www.microsoft.com/downloads/details.aspx?FamilyID=461fc2e9-c500-48dc-a5f8-7deb1a9b6f03&displaylang=en

     

    Here's an excerpt:

     

    Contents

    Contents .............................................................................................................................. 3

    Introduction ......................................................................................................................... 4

    Logging Process ................................................................................................................. 4

    Error Types ......................................................................................................................... 4

    Component-Based Servicing (CBS) Errors ......................................................................... 5

    Syntax of CBS Error Messages ...................................................................................... 5

    Versions and Elevation Values ....................................................................................... 6

    Install State ..................................................................................................................... 7

    Message Types .............................................................................................................. 7

    CBS Error Codes............................................................................................................... 15

    CBS Event Messages ....................................................................................................... 21

    Description of Events .................................................................................................... 21

    Description of Detailed Information............................................................................... 22

    Component-Servicing Infrastructure (CSI) Errors .............................................................. 25

    CSI Error Codes ........................................................................................................... 26

    Settings Management Infrastructure (SMI) Errors ............................................................. 38

    Format of SMI Error Messages/Warning ...................................................................... 39

    SMI Error Messages ..................................................................................................... 40

    Windows Update Errors .................................................................................................... 42

    Device Management Infrastructure (DMI) Errors ............................................................... 43

    Generating a separate driver log file ............................................................................. 43

    DMI Error Messages ..................................................................................................... 43

    Additional Information ........................................................................................................ 44

     

     

    .... Introduction

    This document describes how to diagnose error logs related to deploying Windows Vista®, specifically how to interpret errors related to Windows Setup (Setup.exe) and Package Manager (Pkgmgr.exe).

    Logging Process

    If an error occurs during Windows Setup, then the following .log files are automatically created: %WINDIR%\panther\setupact.log \\ Full Log %WINDIR%\panther\setuperr.log \\ Errors only If an error occurs when you run Package Manager manually with the logging option (/l), a log file is created in the specified location. For example, Start /w pkgmgr.exe /ip /m:\\myserver\share\myfix.cab /s:c:\sandbox /l:c:\logs\mylog.log If a location is not specified, then a default Component-Based Servicing (CBS) log file is created at the following location. %WINDIR%\logs\cbs\cbs.log If the CBS log becomes more than 50 megabytes (MB) in size, it is truncated. The truncated portion is stored at the following location. %WINDIR%\logs\cbs.persist.log The Windows Update log also contains CBS errors as well as Windows update errors. This log file is created at the following location. %WINDIR%\windowsupdate.log Important If you attempt to service an offline Windows image and Package Manager returns an error, the Windows image may be corrupt. The Windows image you are attempting to service should be discarded. This is necessary because if the Windows image is corrupt, subsequent attempts to service the image may not return an error, and you may ship a Windows image that is corrupt. Servicing operations for corrupt images may result in the failure to apply subsequent critical patches. As a best practice, when you receive an error using Package Manager, discard the current Windows image and start again with the last known valid Windows image. When servicing your offline Windows image, ensure that all offline servicing actions are successful. If there are any failures, discard the potentially corrupt Windows image.

    Error Types

    Log files can contain the following error types:

    Component-Based Servicing (CBS) Errors – Errors related to servicing Windows Vista packages and applicability.

    Component-Servicing Infrastructure (CSI) Errors – Errors related to servicing Windows Vista component sets within a package.

    Settings Management Infrastructure (SMI) Errors – Errors related to setting configuration, such as in an answer file.

    Windows Vista Deployment Error Diagnostic Guide 5 © 2007 Microsoft Corporation. All rights reserved.

    Device Management Infrastructure (DMI) Errors – Errors related to offline installation of out-of-box drivers.

    Windows Update (WU) Errors – Errors related to servicing of the operating system through Windows Update.

    Log files can also contain system errors in the hexadecimal format 0x8007nnnn. To find additional error information, perform the following procedure:

    1. Click Start, click Run, and then type Calc.exe.

    2. Ensure that the calculator is in Scientific view, click Hex (for hexidecimal), enter the last four numbers in hexadecimal form, and then click Dec to convert the number to decimal.

    3. At this Microsoft Web site, search ―System Error Codes‖on the MSDN Web site (http://go.microsoft.com/fwlink/?LinkId=83027) for the decimal code.

    For example, for error 0X80070490, convert 0490 to a decimal (1168), and then search System Error Codes for 1168.

    Component-Based Servicing (CBS) Errors

    To find CBS-related errors, search the log file for the word ―Error.‖CBS errors can be either:

     CBS related errors with the format 0x800fnnnn

    System error codes with the format 0x8007nnnn (as discussed in the previous section)

    Important If you open a CBS log file and it is missing CBS-related information, you might need to enable logging by setting the following registry key: [HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing] EnableLog=dword:00000001 This ensures that the CBS log contains all possible information about what occurred.

    When you find a CBS error, use the following information about the syntax, versions, elevation levels, and common errors to diagnose the problem.

    Syntax of CBS Error Messages

    The basic syntax of CBS logged entries is: <TimeStamp> <Severity> <Component> <Type>: <Description>

    Parameter

    Description

    <TimeStamp>

    Specifies the date and time that the error occurred.

    <Severity>

    Specifies the severity of the event. Values are Info, Warning, and Error.

    <Component>

    Specifies the component that logged the message. For the CBS log, this is either CBS or CSI.

     

    Additional Information

     Package Manager Technical Reference ( http://go.microsoft.com/fwlink/?LinkId=91915 )

     OCSetup Log Diagnoser (http://go.microsoft.com/fwlink/?LinkId=84909 ).

     System Error Codes (http://go.microsoft.com/fwlink/?LinkId=83027 )

     

    as well as these (there may be duplicates in the list):

     

    http://www.microsoft.com/downloads/thankyou.aspx?familyId=461fc2e9-c500-48dc-a5f8-7deb1a9b6f03&displayLang=en

    http://technet2.microsoft.com/windowsserver2008/en/library/1020fd57-fd6e-40ff-bb04-e639da37b96e1033.mspx?mfr=true

    http://technet2.microsoft.com/windowsserver2008/en/library/1020fd57-fd6e-40ff-bb04-e639da37b96e1033.mspx?mfr=true

    http://msdn.microsoft.com/en-us/library/aa385229(VS.85).aspx

    http://www.microsoft.com/technet/support/ee/ee_advanced.aspx

    http://support.microsoft.com/kb/836941/en-us

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

    http://technet2.microsoft.com/windowsserver2008/en/library/ba7a187c-1ead-4459-829b-614a6428721f1033.mspx?mfr=true

    http://technet2.microsoft.com/windowsserver2008/en/library/ba7a187c-1ead-4459-829b-614a6428721f1033.mspx?mfr=true

    http://forums.microsoft.com/technet/ShowPost.aspx?siteid=17&postid=3188399

    http://technet.microsoft.com/en-us/windowsvista/bb968859.aspx

    http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=1992&SiteID=17

    http://technet.microsoft.com/en-us/windowsvista/bb738089.aspx

     

    Look in windows subfolders \winsxs, \logs, software distribution, \servicing\packages, etc. you may find .cat, .mum, mui, .manifest files etc. that are corrupt, i.e. show as 0 bytes in size. And use the tools checksur and cbschecker to get the error numbers too, and use the guide to help lead you to the right type of error and what to do in each case.

     

    These bad files can be replaced with good copies from another Vista system or extracted from \windows\CheckSur\v.1.0\base.cab or other .cab files (depending on which files are bad of course) on your system since it seems using Checksur or other tools don't always automatically fix and replace all the corrupt files.

     

    The key for me was CheckSur. It stipulated the corrupt files and I replaced them manually. You'll have to change permissions first. Change the ownership and then add Full Control as the the permission level (doesn't seem to cause any problems).

     

    Doing such should eliminate the most recent errors to getting SP1 to install or download. You might encounter additional errors, but follow the same procedures for each that show up.

     

    Read the diagnostic manuals and you'll find ideas to solve the problems. Learn about identifying the error types.

     

    It seems that MS doesn't widely link to all of these resources since they're for IT professionals and I guess it's more cost effective to support the supporters rather than end users.

     

    It's a learning curve but it seems all is fixable using the right steps and information (once you find it. It took me since mid April to gather and try and error to finally follow the right steps after getting the right documentation, etc. (Like many here, I'm no tech pro, but self trained through trial and error and slow since I jump all over the place and try a lot, but eventually get it somehow).

     

    In addition there is the windowsupdate log, cbs log, checksur log etc. to check. Don't neglect the persist version of the log since there is an overflow once the logs get over a certain size. These logs will show the missing/corrupt manifests, security and or catalog files that need attention before SP1 will install.

     

    Also use the event reporter tool, type event view after clicking start. Run the event vierwer and look in Windows Logs- System for errors reported for getting event IDs, error numbers, etc. that you can use to search tech forums on MS for addtional help.

     

    Good luck

     

    Net_Vet

     

    2008年7月5日 14:48
  • I try running this program and it stalls on the verifying portion.  Can't get it to run at all.  And, I am having the same 800B0100 error as everyone else.  The odd thing is, my laptop upgraded to it without a glitch.  Any ideas?

     

     

    2008年7月12日 13:56
  • Hello George,

     

    I received the same 800B0100 error, so I manually downloaded SP1 from Microsoft, now I am getting the 0x800B0100 error.  I've tried downloading the files you've mentioned; however, the given password gives me a message that there are no files to download.

     

    Can you please send me an updated download link and password so I can attempt to get this problem resolved?

     

    Thank you!

    arthur2142

     

    2008年7月12日 23:55
  • I can't get Vista SP1 to install.  Here is the contents of my CheckSUR log:

     


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-07-12 23:35:06 PM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.10.0.mum  
    Checking component registry

    Checking component store

    Scanned 8365 components, 12550 component payload files
    Summary:
    Milliseconds: 868388
     Found 1 errors
      CBS Missing Manifest Total Count: 1
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

    =======================================

     

    I cant find the Package_1_for_KB905866~31bf3856ad364e35~x86~~6.0.10.0.mum  file anywhere.  Can you help me?

     

     

    2008年7月13日 4:45
  • Hi George, or anyone else.
    I am having trouble installing SP1 and would like help.
    Could you please tell me how to get past error 0x800B0100
    Thanks
    John
    2008年7月14日 0:36
  • Hello all, my apologies but I am out of the country at the moment and won't be returning for at least a month.  If you could try the tool at http://www.microsoft.com/downloadS/details.aspx?familyid=D22AF4E2-1AAF-4672-8951-4B7920F982E9&displaylang=en, you might be able to get fixed to the point where SP1 will install.  Expect an update to this tool in the month or 2 with additional repair capabilities

    2008年7月14日 1:46
  • thanks for letting us know ahead of time, George.

     

    2008年7月14日 2:35
  •  George Hilios [MSFT] wrote:

    Hello all, my apologies but I am out of the country at the moment and won't be returning for at least a month.  If you could try the tool at http://www.microsoft.com/downloadS/details.aspx?familyid=D22AF4E2-1AAF-4672-8951-4B7920F982E9&displaylang=en, you might be able to get fixed to the point where SP1 will install.  Expect an update to this tool in the month or 2 with additional repair capabilities



    SUCCESS!!!

    Hi George...
    I initiated this string in December.
    I used the tool you cited above.
    After its installation, I was able to install Vista SP1.

    Thanks loads... Nuffyfluts



    2008年7月14日 16:05
  •  

     

    Unfortunately it appears that the System Update Readiness Tool doesn't fix all instances of this problem; I have pretty much the same symptoms except that catalog that is causing the problems is WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.cat for me.

     

    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-07-20 12:57:24 p.m.

    Checking Deployment Packages

    Checking Package Manifests and catalogs.
    (f) Corrupt Catalog CBS 0x800B0100 \servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.cat  
    C:\Windows\servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.cat
     Size: 10761 bytes.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    Checking component registry

    Checking component store

    Scanned 10048 components, 13248 component payload files
    Summary:
    Milliseconds: 703761
     Found 1 errors
      CBS Corrupt Catalog Total Count: 1
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

     

     

     

    Is there a way to refresh all of these correctly at once?

    2008年7月20日 2:27
  •  

    Dear Georges,

     

    I have finally succeed to install the file you send me. I deleted the old file saving it as a precaution, and passed the file I received. I ran the cbs.checkstore.exe and had no faults found. I then run the windows update and it works no more error message 800B0100. I will run the Vista SP1 shortly and let you know if it works as well.

     

    However, I was unable to just replace the file, it worked only by deleting the corrupted file.

     

    Thanks for you support,

     

    Rey

    2008年7月27日 20:24
  • Hello, George and Eric!

    Thanks for all the helpful things you have already written in this thread!
    I've got the same 800B0100 error code when trying to install SP1 (x64). Sad
    I have installed 947821 CheckSUR Utility, but it finds no error:

    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-07-31 01:02:00

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    Checking component registry

    Checking component store

    Scanned 17169 components, 21819 component payload files
    Summary:
    Milliseconds: 463456
     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.


    I have also found an empty folder in my C:\ with 24-hex-digit name,
    probably temp for one of updates.

    Thanks in advance for any help!

    2008年7月31日 8:53
  •  

    Dear George,

     

    I have finally succeed in replacing the corrupted file. To replace it, after checking all kind of permissions required....and still having the message "You need permission to perform this action". I decide to delete the concerned file and save it in another folder. I then install the one you send me, it just went fine. As the icon for Windows update was telling me in the taskbar that some updates were available and this was also not working, I clicked on it and was able to install the updates this way. I then started installation of Vista SP1 and this worked fine also.

     

    Everythnig seems to be running normally since.

     

    Thanks for your support and time.

     

    Best regards,

     

    Rey

    2008年8月1日 9:10
  • To resolve the installation / corruption problem I was directed to perform "in place upgrade" wich consisted of putting in the Vista DVD and reinstalling Vista. After the process was completed I manually downloaded the SP1 update and it installed without error.

    2008年8月7日 3:34
  • Hi George,

    I am also having the same problem. I am using Vista Ultimate.

    I am not able to access the link with the password provided.

     

    And could you please give the location of the cbscheckstore.exe.

     

    Thanks

    Suneel

     

    2008年8月7日 3:55
  • here is my checkSUR log:

     


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-04-20 3:05:56 AM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    Checking component registry

    Checking component store

    Scanned 8148 components, 11935 component payload files
    Summary:
    Milliseconds: 585177
     Found 15 errors
      CBS Missing Manifest Total Count: 15
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-08-16 9:18:52 AM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    Checking component registry

    Checking component store

    Scanned 8453 components, 12568 component payload files
    Summary:
    Milliseconds: 561732
     Found 15 errors
      CBS Missing Manifest Total Count: 15
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.


    =================================
    Checking System Update Readiness.
    Version 6.0.6000.2
    2008-08-16 9:34:04 AM

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) Missing Manifest CBS 0x00000002 \servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    Checking component registry

    Checking component store

    Scanned 8453 components, 12568 component payload files
    Summary:
    Milliseconds: 579406
     Found 15 errors
      CBS Missing Manifest Total Count: 15
    Customer Experience report successfuly uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

     

     

    thanks in advance

     

    2008年8月16日 15:24
  •  

    All of the functionality in CBSCheckStore.exe is in CheckSUR.

     

    I'd like to make everyone on this thread aware of the fact that a new version of CheckSUR was released last week. We are still working on updating the KB article to point to the new release. In the meantime, here are the links to the new version:

     

    Vista
    • X86: http://www.microsoft.com/downloads/details.aspx?FamilyID=2889489c-ee87-4607-8aa5-812e8078ab27&DisplayLang=en
    • X64: http://www.microsoft.com/downloads/details.aspx?FamilyID=14f76773-007c-493f-bece-243bc21ac73d&DisplayLang=en

     

    Windows Server 2008
    • X86: http://www.microsoft.com/downloads/details.aspx?FamilyID=6d9ece65-3820-4583-85f5-7e2a5799b3ba&DisplayLang=en
    • Ia64: http://www.microsoft.com/downloads/details.aspx?FamilyID=c1faaf23-1b60-458e-916d-ec835fc8955e&DisplayLang=en
    • X64: http://www.microsoft.com/downloads/details.aspx?FamilyID=32978546-8108-408f-b78e-0e95eff14c92&DisplayLang=en

     

    This new version is capable of fixing additional problems with the servicing store that the previous version could not.

    2008年8月18日 16:44
  •  

    hello,

    i tried the new release. didnt fix my update, but my logs changed:


    =================================
    Checking System Update Readiness.
    Version 6.0.6001.22201
    2008-08-18 14:07

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~en-US~7.0.6000.381.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.0.6000.381.mum  

    Checking component store

    Checking SMI Store
    (f) SMI Missing Registry Key 0x00000000  wcm://Microsoft-Windows-WindowsUpdateClient-Core?version=7.0.6000.374&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (f) SMI Missing Registry Key 0x00000000  wcm://Microsoft-Windows-WindowsUpdateClient-UI?version=7.0.6000.374&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-WindowsUpdateClient-Core?version=7.0.6000.381&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-WindowsUpdateClient-UI?version=7.0.6000.381&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    Summary:
    Milliseconds: 930360
     Found 17 errors
      CBS MUM Missing Total Count: 15
      SMI Missing Registry Key Total Count: 2
      SMI Extra Registry Key Total Count: 2

     

     

     

    thanks

    2008年8月18日 19:35
  • I am happy to report that The newest system update readiness tool posted above me has resloved my issue. After installing the particular update I tried installing SP1 through windows update and it completed succesfully. After 6 months of trying to find a solution it has been finally solved, at least for me. Hopefully this helps others that are having this same problem as well. Hopefully i never have to come back here.
    2008年8月21日 22:26
  • Same Problem here, the system update readiness tool (August) is unable to fix 20 Errors:

    =================================
    Checking System Update Readiness.
    Version 6.0.6001.22201
    2008-08-24 01:24

    Checking Deployment Packages

    Checking Package Manifests and catalogs.
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\packages\Package_1_for_KB929399~31bf3856ad364e35~amd64~~6.0.1.1.cat       

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.

    Checking component store
    (f)    CSI Payload File Missing    0x00000000    IMJP10.IME    amd64_microsoft-windows-d..panese-imejpimm32if_31bf3856ad364e35_6.0.6000.16386_none_5713ae0be504c1fe   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_7be7aaed41157917   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_dd262d0a8beeb0e0   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_34cdc87e8f1e7da8   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_1a027adc4a1d6da2   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_eb574af0ad971215   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_4e829729a7421bd7   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_d8b3cdb8ffed9996   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_db04377b5a205ad3   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_3cf6b0e7eb4cf60f   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_1a598d99dd4b00c0   
    (f)    CSI Payload File Missing    0x00000000    ieapfltr.dll    amd64_microsoft-windows-ie-antiphishfilter_31bf3856ad364e35_6.0.6000.16546_none_55a5335b27107725   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_104a1e07a2e31f01   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_f61cdf6ad643e09f   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_cc47586dbe49229a   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_b25310e88d9c54fc   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_d2299c3473a801be   
    (f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\2eb73259f9a3cbfd0ef0ada90032605969358d3b99df948dc30fdbf3d4cee7d6.cat    microsoft-w..-deployment_31bf3856ad364e35_6.0.6000.16386_defc82685fa1f31f   
    (f)    CSI Payload File Missing    0x00000000    inetcpl.cpl    x86_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_6.0.6000.16575_none_8d0cb78254e644a9   

    Checking SMI Store
    Summary:
    Milliseconds: 3825460
     Found 20 errors
      CSI Catalog Corrupt Total Count: 16
      CSI Payload File Missing Total Count: 3
      CBS Catalog Corrupt Total Count: 1
    2008年8月24日 14:29
  •  

    i copied the missing .mum files off my mother in laws computer. seems update is working now.thanks.

    may i also mention an unrelated issue: i cant seem to find a way to easily go the the last page/post in this forum; its really annoying to have to click four times to get to the last post. could someone do a go to page or go to last post link?

    thanks.

    2008年8月25日 9:26
  • I am having the same issues and running the updated system readiness tool was not succesful in allowing me to check for updates or install SP1..... any help is greatly appreciated

     


    =================================
    Checking System Update Readiness.
    Version 6.0.6001.22201
    2008-08-27 09:03

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-DFSR-ClientEdition-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-DFSR-ClientEdition-Package~31bf3856ad364e35~amd64~en-US~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-ParentalControls-Package~31bf3856ad364e35~amd64~~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-MobilePC-Client-SideShow-Package~31bf3856ad364e35~amd64~~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-OfflineFiles-Package~31bf3856ad364e35~amd64~~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-DFSR-ClientEdition-Package~31bf3856ad364e35~amd64~~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-MobilePC-Client-SideShow-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-MobilePC-Client-SideShow-Package~31bf3856ad364e35~amd64~en-US~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-OfflineFiles-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-OfflineFiles-Package~31bf3856ad364e35~amd64~en-US~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-ParentalControls-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-ParentalControls-Package~31bf3856ad364e35~amd64~en-US~6.0.6000.16386 Package registry presence failed, possibly an orphaned package on package watchlist

    Checking component watchlist.

    Checking packages.
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.0.6000.374.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.0.6000.374.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~en-US~7.0.6000.374.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~en-US~7.0.6000.374.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.0.6000.374.mum  

    Checking component store

    Checking SMI Store
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-Desktop_Technologies-Text_Input_Services-IME-Japanese-Core?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-Desktop_Technologies-Text_Input_Services-IME-Japanese-Core?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-DFSR-Core-ClientOnly?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-IME-Korean-TIPProfile?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-IME-Korean-TIPProfile?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-IME-Simplified-Chinese-Core?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-IME-Simplified-Chinese-Core?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-IME-Traditional-Chinese-Core?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-IME-Traditional-Chinese-Core?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10001?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10001?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10002?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10002?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10003?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10003?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10008?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-10008?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-1361?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-1361?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20000?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20000?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20001?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20001?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20002?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20002?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20003?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20003?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20004?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20004?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20005?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20005?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20261?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20261?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20290?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20290?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20833?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20833?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20936?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20936?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20949?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-20949?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-50225?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-50225?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-50227?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-50227?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-50229?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-50229?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-51949?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-51949?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-52936?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-52936?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-54936?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-54936?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-932?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-932?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-936?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-936?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-949?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-949?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-950?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-CodePage-950?version=6.0.6000.16386&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000404?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000404?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000411?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000411?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000412?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000412?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000804?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-00000804?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_106_key?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_106_key?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_AX2_keyboard?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_AX2_keyboard?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_DEC_LK411-AJ?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_DEC_LK411-AJ?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_DEC_LK411-J?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_DEC_LK411-J?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_Fujitsu_thumb-shift_keyboard?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_Fujitsu_thumb-shift_keyboard?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_IBM02?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_IBM02?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_NEC-AT?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_NEC-AT?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_NEC98-NT?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_NEC98-NT?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_NEC_Win95?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_NEC_Win95?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_standard_101_key?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Japanese_standard_101_key?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_101a?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_101a?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_101b?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_101b?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_101c?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_101c?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_103?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-International-Keyboard-Korean_103?version=6.0.6000.16386&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-OfflineFiles-Core?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    (w) SMI Extra Registry Key 0x00000000  wcm://Microsoft-Windows-OfflineFiles-Service?version=6.0.6000.16386&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers 
    Summary:
    Milliseconds: 702089
     Found 13 errors
      CBS MUM Missing Total Count: 5
      CBS Watchlist Package Missing Total Count: 8
      SMI Extra Registry Key Total Count: 99

    2008年8月27日 13:42
  • Cant upgrade to Vista SP1. Done so much to try and get it to work. Tech help from microsoft tells me theres nothing I can do, so I hope someone can help me.

    Here's my CheckSUR.log:

    =================================
    Checking System Update Readiness.
    Version 6.0.6001.22201
    2008-09-14 02:16

    Checking Deployment Packages

    Checking Package Manifests and catalogs.

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.
    (f)    CBS MUM Missing    0x00000002    servicing\packages\Package_1_for_KB937143~31bf3856ad364e35~x86~~6.0.1.4.mum       
    (f)    CBS MUM Missing    0x00000002    servicing\packages\Package_2_for_KB937143~31bf3856ad364e35~x86~~6.0.1.4.mum       
    (f)    CBS MUM Missing    0x00000002    servicing\packages\Package_3_for_KB937143~31bf3856ad364e35~x86~~6.0.1.4.mum       
    (f)    CBS MUM Missing    0x00000002    servicing\packages\Package_for_KB937143~31bf3856ad364e35~x86~~6.0.1.4.mum       

    Checking component store

    Checking SMI Store
    Summary:
    Milliseconds: 1374905
     Found 4 errors
      CBS MUM Missing Total Count: 4

    2008年9月18日 0:36
  • Here is a copy of my checksur.log I hope somebody can give me an idea of where to go from here. Thanks all.



    =================================
    Checking System Update Readiness.
    Version 6.0.6001.22201
    2008-09-20 23:21

    Checking Deployment Packages

    Checking Package Manifests and catalogs.
    (f)    CBS MUM Corrupt    0x800F080D    servicing\packages\Package_1_for_KB950974~31bf3856ad364e35~x86~~6.0.1.0.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\packages\Package_1_for_KB950974~31bf3856ad364e35~x86~~6.0.1.0.cat       
    (f)    CBS MUM Corrupt    0x800F080D    servicing\packages\Package_4_for_KB950974~31bf3856ad364e35~x86~~6.0.1.0.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\packages\Package_4_for_KB950974~31bf3856ad364e35~x86~~6.0.1.0.cat       
    (f)    CBS MUM Corrupt    0x800F080D    servicing\packages\Package_for_KB950974_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\packages\Package_for_KB950974_client_0~31bf3856ad364e35~x86~~6.0.1.0.cat       
    (f)    CBS MUM Corrupt    0x800F080D    servicing\packages\Package_for_KB950974_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\packages\Package_for_KB950974_client_1~31bf3856ad364e35~x86~~6.0.1.0.cat       
    (f)    CBS MUM Corrupt    0x800F080D    servicing\packages\Package_for_KB950974_client~31bf3856ad364e35~x86~~6.0.1.0.mum        Line 1:
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\packages\Package_for_KB950974_client~31bf3856ad364e35~x86~~6.0.1.0.cat       
    (f)    CBS MUM Corrupt    0x80070026    servicing\packages\Package_for_KB950974~31bf3856ad364e35~x86~~6.0.1.0.mum        Line 1: Ä
    (f)    CBS Catalog Corrupt    0x800B0100    servicing\packages\Package_for_KB950974~31bf3856ad364e35~x86~~6.0.1.0.cat       

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.

    Checking component store
    (f)    CSI Catalog Missing    0x80092003    winsxs\Catalogs\2c6ca58d6d793d7749fec47716f6289946817fd00162bebc9d7fbd1d80cc0895.cat    ea019e783f0..3f19d6794ba_31bf3856ad364e35_6.0.6001.22162_27883b602c16bf38    Missing catalog or invalid CatalogThumprint
    (f)    CSI Manifest Missing    0x00000002    x86_ea019e783f0aea92f42b03f19d6794ba_31bf3856ad364e35_6.0.6001.22162_none_27883b602c16bf38.manifest    x86_ea019e783f0aea92f42b03f19d6794ba_31bf3856ad364e35_6.0.6001.22162_none_27883b602c16bf38   
    (f)    CSI Catalog Missing    0x80092003    winsxs\Catalogs\2c6ca58d6d793d7749fec47716f6289946817fd00162bebc9d7fbd1d80cc0895.cat    88cd20da13f..ae0a4b66778_31bf3856ad364e35_6.0.6001.18057_522651bea46de6cb    Missing catalog or invalid CatalogThumprint
    (f)    CSI Manifest Missing    0x00000002    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6001.18057_none_0cbe918751dfdd3f.manifest    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6001.18057_none_0cbe918751dfdd3f   
    (f)    CSI Catalog Missing    0x80092003    winsxs\Catalogs\64cff67bd29f87f6b279a36779c1f94d505e72b96d02a7825fbec4147f97d690.cat    04294e32f5d..4050ee16913_31bf3856ad364e35_6.0.6000.16677_a99c03a85f132aa9    Missing catalog or invalid CatalogThumprint
    (f)    CSI Manifest Missing    0x00000002    x86_04294e32f5df770bb5d234050ee16913_31bf3856ad364e35_6.0.6000.16677_none_a99c03a85f132aa9.manifest    x86_04294e32f5df770bb5d234050ee16913_31bf3856ad364e35_6.0.6000.16677_none_a99c03a85f132aa9   
    (f)    CSI Catalog Missing    0x80092003    winsxs\Catalogs\64cff67bd29f87f6b279a36779c1f94d505e72b96d02a7825fbec4147f97d690.cat    cda929e44c8..f767f1ddc1d_31bf3856ad364e35_6.0.6000.20818_6e030692cc670470    Missing catalog or invalid CatalogThumprint
    (f)    CSI Manifest Missing    0x00000002    x86_cda929e44c8209b0e90ecf767f1ddc1d_31bf3856ad364e35_6.0.6000.20818_none_6e030692cc670470.manifest    x86_cda929e44c8209b0e90ecf767f1ddc1d_31bf3856ad364e35_6.0.6000.20818_none_6e030692cc670470   
    (f)    CSI Manifest Missing    0x00000002    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6001.22162_none_0d385cf46b0a1a47.manifest    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6001.22162_none_0d385cf46b0a1a47   
    (f)    CSI Manifest Missing    0x00000002    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6000.16677_none_0ac2b30954c98430.manifest    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6000.16677_none_0ac2b30954c98430   
    (f)    CSI Manifest Missing    0x00000002    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6000.20818_none_0b8e318c6db592d2.manifest    x86_microsoft-windows-c..complus-eventsystem_31bf3856ad364e35_6.0.6000.20818_none_0b8e318c6db592d2   

    Checking SMI Store
    Summary:
    Milliseconds: 749480
     Found 23 errors
      CSI Manifest Missing Total Count: 7
      CSI Catalog Missing Total Count: 4
      CBS MUM Corrupt Total Count: 6
      CBS Catalog Corrupt Total Count: 6


    2008年9月21日 5:05
  • Here's a copy of my checksur log.  What's next?

     


    =================================
    Checking System Update Readiness.
    Version 6.0.6001.22201
    2008-10-06 12:01

    Checking Deployment Packages

    Checking Package Manifests and catalogs.
    (f) CBS Catalog Corrupt 0x800B0100 servicing\packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~x86~en-US~7.0.6000.381.cat  

    Checking package watchlist.

    Checking component watchlist.

    Checking packages.

    Checking component store
    (f) CSI Manifest Bad XML 0xC0150006 WinSxS\Manifests\x86_microsoft-windows-ieinstal_31bf3856ad364e35_6.0.6000.20583_none_e6ebb4f5add79d99.manifest x86_microsoft-windows-ieinstal_31bf3856ad364e35_6.0.6000.20583_none_e6ebb4f5add79d99 
    (f) CSI Manifest Zero Length 0x00000000 WinSxS\Manifests\x86_6cf0868198157ef917eec6d80ab110ae_31bf3856ad364e35_6.0.6000.20710_none_1ab44bc240315697.manifest x86_6cf0868198157ef917eec6d80ab110ae_31bf3856ad364e35_6.0.6000.20710_none_1ab44bc240315697 
    (f) CSI Manifest Bad XML 0xC0150006 WinSxS\Manifests\x86_microsoft-windows-ie-antiphishfilter_31bf3856ad364e35_6.0.6000.16473_none_f963254f6ece1096.manifest x86_microsoft-windows-ie-antiphishfilter_31bf3856ad364e35_6.0.6000.16473_none_f963254f6ece1096 

    Checking SMI Store
    Summary:
    Milliseconds: 435377
     Found 4 errors
      CSI Manifest Zero Length Total Count: 1
      CSI Manifest Bad XML Total Count: 2
      CBS Catalog Corrupt Total Count: 1

     

    2008年10月6日 16:27
  • HI GEORGE. PLZ EMAIL ME AT TELE_VOE@yahoo.com I CAN'T INSTALL VISTA SERVICE PK 1. I KEEP GETTING ERROR MSJ 800b0100 ty

    2008年10月24日 11:32
  • I have been waiting for an answer for months and MS doesn't seem to have one.  I think you as well as myself are better off doing a repair install of Vista.

     

    2008年10月24日 12:46
  • I don't know if this will help you or if it's already been suggested but I fixed this error on a friends Vista laptop;

     

    Try searching for the update that keeps failing manually. In my case it was KB938123. Every time I tried to update I got the above error message - 800B0100. I searched for 'download KB938123' on google and downloaded it to my desktop from the microsoft web site. I then performed a normal manual install. After that the laptop downloaded updates normally.

     

    Hope this helps someone out there as the suggestions in this thread are very complicated - I can imagine most people giving up after reading them!

    2008年11月10日 12:42
  • My problem isn't simply with SP1..... Whenever I try to check for updates I get the error "Windows could not search for new updates Code 800B0100"  So I have no idea if there is a specific update that is causing it to fail or not.

     

    2008年12月5日 13:29
  • I am having the same problem installing service pack 1 on vista. I installed the tool (Windows6.0-KB947821-v4-x86) that seems to have resolved this issue for many people; however, i am still receiving the same error. Please advise.
    2008年12月21日 17:47
  • My problem with this install went away when I upgrade my ram from 512 to 2 gigs.  Right after the ram install the update loaded with no problem.
    2008年12月30日 5:27
  • Help plz someone With sp1 update package getting error messege
    2008年12月31日 17:43