No Wndows Update - Error 800F0900

[abro89]

hi :

I have received some updates for my W7E activated OS. However W7E SP1 will not update. Error 800F0900 is displayed and shows CBS_E_XML_PARSER_FAILURE in CBS.log. CBS.log log is attached as CBS.zip.

Many thx and appreciate your help from the very experienced and highly skilled team at Sysnative.

 

[Tekno Venus]

Hello and welcome to Sysnative Forums!

It seems SURT has done most of the hard work for us here:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-03-04 16:46

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~amd64~en-US~7.6.7600.256.mum        Line 1: 

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\ce046619db541ada11ba91854bf6143bb6009a35fc32541ffc5e582fb6f55f18.cat    39487a04ea9..3831068bf5f_31bf3856ad364e35_6.1.7601.17753_5a9b4c10a8504612    
(fix)    CSI Catalog Corrupt    CSI File Replaced    Deleted CatalogThumbprint
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.17753_none_91875a33222d5bc5.manifest    x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.17753_none_91875a33222d5bc5    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.17753_none_91875a33222d5bc5.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.17753_none_eda5f5b6da8accfb.manifest    amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.17753_none_eda5f5b6da8accfb    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.17753_none_eda5f5b6da8accfb.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab
(f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\b8757872c70022b39f9c374b7b65400a30ec2a3499db43e01f5c8b723e1d2841.cat    80c2572ed03..ed4350528dd_31bf3856ad364e35_6.1.7600.16940_a23df7070efdab35    
(fix)    CSI Catalog Corrupt    CSI File Replaced    Deleted CatalogThumbprint
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.16940_none_8fa8cc3b250187e3.manifest    x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.16940_none_8fa8cc3b250187e3    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.16940_none_8fa8cc3b250187e3.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.16940_none_ebc767bedd5ef919.manifest    amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.16940_none_ebc767bedd5ef919    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.16940_none_ebc767bedd5ef919.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab
(f)    CSI Catalog Thumbprint Invalid    0x00000000    b8757872c70022b39f9c374b7b65400a30ec2a3499db43e01f5c8b723e1d2841    816b5b38767..42cb52a86d2_31bf3856ad364e35_6.1.7600.21118_99347f43136c1d2a    
(fix)    CSI Catalog Thumbprint Invalid    CSI Catalog Thumbprint Deleted    b8757872c70022b39f9c374b7b65400a30ec2a3499db43e01f5c8b723e1d2841
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.21118_none_905ab33c3dffd1d4.manifest    x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.21118_none_905ab33c3dffd1d4    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.21118_none_905ab33c3dffd1d4.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.21118_none_ec794ebff65d430a.manifest    amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.21118_none_ec794ebff65d430a    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.21118_none_ec794ebff65d430a.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab
(f)    CSI Catalog Corrupt    0x800B0003    winsxs\Catalogs\24bae3a44ccf6734825e2bfb14c359db486cd3d38bcccf2508574f09375c4b6f.cat    e1fba764494..ca72f1c2fb5_31bf3856ad364e35_6.1.7601.17514_7751a6261304e8fb    
(fix)    CSI Catalog Corrupt    CSI File Replaced    File: 24bae3a44ccf6734825e2bfb14c359db486cd3d38bcccf2508574f09375c4b6f.cat From: C:\Windows\servicing\Packages\Package_1_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514.cat
(f)    CSI Catalog Thumbprint Invalid    0x00000000    ce046619db541ada11ba91854bf6143bb6009a35fc32541ffc5e582fb6f55f18    e5e9d46f0da..6eccfc248c5_31bf3856ad364e35_6.1.7601.21888_0b88e6b6a11443d2    
(fix)    CSI Catalog Thumbprint Invalid    CSI Catalog Thumbprint Deleted    ce046619db541ada11ba91854bf6143bb6009a35fc32541ffc5e582fb6f55f18
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.21888_none_91f588ac3b5ece15.manifest    x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.21888_none_91f588ac3b5ece15    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.21888_none_91f588ac3b5ece15.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.21888_none_ee14242ff3bc3f4b.manifest    amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.21888_none_ee14242ff3bc3f4b    
(fix)    CSI Manifest All Zeros    CSI File Replaced    File: amd64_microsoft-windows-timedate_31bf3856ad364e35_6.1.7601.21888_none_ee14242ff3bc3f4b.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-2jan13.cab

Which just leaves us with this one error:

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~amd64~en-US~7.6.7600.256.mum        Line 1:

That's a nice simple fix you'll be glad to here. :)

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the file, Packs.zip from my Dropbox -->here<--and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
   
   ​
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
   
   ​
7. Run the System Update Readiness Tool (SURT) again
8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.persist.log​

Kind regards,
Stephen

 

[abro89]

SUR after fix (log_after_fix.zip)

stephen/will:

many thx again for the fix. My W7E is now downloading all WIN updates. I have enclosed my SUR log from c:\windows\logs\cbs\checksur.persist.log as requested. Pls see log_after_fix.zip

Also I have a donation of $20.00 via PayPal to keep your web page and services going. You guys are the best.

I also have inherited another TOSHIBA w/ W7E. I have a 90-day license and activated by MS. May I send you the CBS log again???

Also I have many questions concerning the KMS for W7E. Is the forum the best palce to start? Some of my questions are easy like:

(a) once W7E is activated, can the HD be moved to a 2nd laptop?

(b) ther eis a WINDOWS Loader by Daz that will apparently activate ALL versions of W7 and W8. Any experience w/ this as my 90 day trial will run out and I would like o activate the OS for personal use;

(c) once W7E is activated by MS, is the OS activated forever?

Thx again,

alan brosz
Brattleboro, VT 05301

 

[Tekno Venus]

Hi Alan,

I've moved your post into one thread to make it more organised for me. :)

Your log is perfect, all problems are gone:

Summary:
Seconds executed: 1060
 Found 1 errors
 Fixed 1 errors
  CBS MUM Corrupt Total count: 1
  Fixed: CBS MUM Corrupt.  Total count: 1
  Fixed: CBS Paired File.  Total count: 1

Thank you very much for your donation! It's greatly appreciated!

I also have inherited another TOSHIBA w/ W7E. I have a 90-day license and activated by MS. May I send you the CBS log again???

I will certainly help you if you have another computer with problems. Just start a new thread so we can keep the machines and logs seperate

Also I have many questions concerning the KMS for W7E. Is the forum the best palce to start? Some of my questions are easy like:

(a) once W7E is activated, can the HD be moved to a 2nd laptop?

(b) ther eis a WINDOWS Loader by Daz that will apparently activate ALL versions of W7 and W8. Any experience w/ this as my 90 day trial will run out and I would like o activate the OS for personal use;

(c) once W7E is activated by MS, is the OS activated forever?

I'm not the best person to ask here, I will message an expert in a minute to give you some better answers.

By KMS, do you mean Key Management Service (KMS), for the Microsoft Volume Licensing Program?

As far as I'm aware, you can move the HDD to another laptop, but the hardware changes (different motherboard, cpu etc) would either make it impossible, or will cause Windows to ask to be activated again.

Regarding the loader, we do not support piracy here. If you use a loader, or crack the OS install so you can activate it without buying a licence, we can't help with the system. You will need to buy a licence for your system.

And yes, the licence lasts forever.

However, I will get an expert on licensing to see if he can give you a better answer.

Regards,
Stephen

 

[NoelDP]

90-day licenses are ONLY issued as trials, and require a reformat and reinstall (using appropriate media) before a perpetual license can be installed.


KMS licensing is a bit of a minefield - there are a lot of hoops which have to be jumped over.
1) You have to purchase the KMS server license, set it up and activate it.
2) you have to have AT LEAST 25 clients ( or *I think* 5 servers) using Client Keys and connecting successfully, before the server will start issuing licenses.
3) Clients (at least) must have valid SLIC tables for a qualifying OS - or no SLIC table at all. If the SLIC table is damaged, then that machine must use an MAK Key.

All KMS clients reactivate every few days against the server - if reactivation doesn't happen within 180 days, then the system will throw a wobbly, and show as non-genuine. This means that it's often not a good idea to have off-site machines using KMS activation.

The use of a Loader (AKA Activation Exploit) AUTOMATICALLY renders any system on which it is installed 'counterfeit' - even if otherwise the system would be considered genuine - since it breaks the Licensing Agreement to which you agreed when first installing Windows, by attempting to circumvent activation and validation requirements.

KMS activation will react in much the same way as ordinary activation to a change in hardware, and demand full re-activation in the event of a major hardware change. I *know* that simply changing the MAC address of a NIC adapter is sufficient to require this - although a lot of other changes don't. Since changing the motherboard almost always means a change in MAC address, (it also changes other details, which could also force a reactivation request), there is no way to change motherboard without triggering reactivation - and changing the KMS counts one way or the other.

If you want serious detail on KMS and what you can and can't do with it, then you should ask in the MS ITPro forums here....
Technet forums - Windows 7 Installation, Setup, and Deployment
If you are an MS Partner, or TechNet/MSDN subscriber, then you will get an 'official response, as well as any 'practical' response from other users.