Hello Jessie, and welcome to Sysnative!
This is going to be a multi-step fix.
For these errors:
Code:
(w) CBS Catalog Expired 0x800B0101 servicing\Packages\Package_for_KB2705219~31bf3856ad364e35~x86~~6.0.1.0.cat
(w) CBS Catalog Expired 0x800B0101 servicing\Packages\Package_for_KB2731847_server~31bf3856ad364e35~x86~~6.0.1.0.cat
This is caused by a fault in the update at Microsoft's end (basically, they allowed the signature to expire). They have since re-released the update with a new set of catalogs with an expiry date suitably far into the future, but getting this update installed can be slightly problematic.
First port of call is to attempt to simply install the new updates (you're not really just installing the same update again, but the re-release)
Download Security Update for Windows Server 2008 (KB2705219) from Official Microsoft Download Center
Download Security Update for Windows Server 2008 (KB2731847) from Official Microsoft Download Center
If they won't install, you're going to have to pull some tricks on the computer's clock though.
See here for details:
Windows Update error 800b0101 - Microsoft Windows Help
Start from step 6, using the two .cat files I've listed above. Basically note down the expiry date of each, then set your computer's clock to before the oldest one expired. Uninstall both updates, then reset your clock to the correct date and reinstall the updates from the links I've provided.
For these errors:
Code:
Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB970710_server_0~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_3_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_7_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WirelessNetworking-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB970710_server_0~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WirelessNetworking-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_4_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WirelessNetworking-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_8_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Package_16_for_KB948465~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB970710_server_1~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Package_16_for_KB948465~31bf3856ad364e35~x86~~0.0.0.0 Package_8_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Package_206_for_KB948465~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB970710_server_1~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Package_206_for_KB948465~31bf3856ad364e35~x86~~0.0.0.0 Package_8_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-l..securityhelperclass_31bf3856ad364e35_0.0.0.0_none_a9f2daa4c1057ea9 Package_3_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-l..securityhelperclass_31bf3856ad364e35_0.0.0.0_none_a9f2daa4c1057ea9 Package_3_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-l..securityhelperclass_31bf3856ad364e35_0.0.0.0_none_a9f2daa4c1057ea9 Package_7_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-l..securityhelperclass_31bf3856ad364e35_0.0.0.0_none_a9f2daa4c1057ea9 Package_7_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-wlansvc_31bf3856ad364e35_0.0.0.0_none_c01e38004d105d6e Package_4_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-wlansvc_31bf3856ad364e35_0.0.0.0_none_c01e38004d105d6e Package_4_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-wlansvc_31bf3856ad364e35_0.0.0.0_none_c01e38004d105d6e Package_8_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-wlansvc_31bf3856ad364e35_0.0.0.0_none_c01e38004d105d6e Package_8_for_KB970710~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
Please download SFCFix.exe from here:
https://www.sysnative.com/forums/downloads/sfcfix/
Run the tool (takes about 15 minutes) and copy and paste the logfile it creates. It should fix those errors automatically provided it doesn't detect any strange conditions it doesn't understand on your computer.
For these errors:
Code:
Checking Packages
(f) CBS Registry Error 0x80070002 Package_for_KB970710_server~31bf3856ad364e35~x86~~6.0.1.1 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_for_KB970710_server~31bf3856ad364e35~x86~~6.0.1.1 failed to get Visibility
We're going to use SFCFix again, but this time it needs some direction. However, this time, we import it and see if it works. If it does, great, if not, I reassess and edit it slightly to make it work. Sometimes it takes a couple of attempts to perfect, sometimes I get it first time. We'll just have to wait and see.
SFCFix Script
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.
- Download SFCFix.exe and save this to your Desktop.
- Download the file below, SFCFixScript.txt, and save this to your Desktop.
- Save any open documents and close all open windows.
- On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
- Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
- SFCFix will now process the script.
- Upon completion, a file should be created on your Desktop: SFCFix.txt.
- Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please.
And these errors don't need to be fixed:
Code:
Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18592.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18592&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.
The SURT's already taken care of that. It's just an issue with how the SURT detects a certain condition on your system. Basically, the SURT predates a certain type of component Microsoft have now released. It doesn't recognise it so it thinks it is a corruption. In reality, it's not, and there's no action that we need to take.
Finally, after all these steps, re-run the System Update Readiness Tool, post a new CheckSUR.log, and I'll see what further action needs to be take (maybe some of the fixes don't go through properly, or maybe your current errors mask some other ones which will only show up once we've fixed the current set. Your PC has quite a variety of corruption types, and it may take a couple of posts to get it all back into working order).
Richard
