[SOLVED] Windows updates repeatedly install and one fails

4

4on4off

Well-known member
Joined
Jul 10, 2012
Posts
141
Hello,

I was referred to this forum by DonnaB.

I am running vista home premium 32bit with IE9.

Some time ago I noticed that these updates were repeatedly saying they installed successfully but then show up as ready to install over and over again:

security update for windows vista KB2621440
security update for windows vista KB2665364
security update for windows vista KB2676562
update for windows mail junk filter [march 2012] KB905866
update for windows vista KB2679255

They do not show up in installed updates.

The following update fails to install with the error code 9C48:

windows internet explorer 9 for windows vista

Other updates show up and install successfully and do not return as ready to install.

I have tried multiple fix it tools for resetting windwos update components, fix common issues with windows update..etc..to no avail.

I have tried uninstalling IE9 via command prompt to no avail.

I do not see any of those updates in view installed updates and the section for Microsoft Windows is missing from the list of installed updates.

I have scanned my pc with various tools from malwarebytes to combofix and it is clean.

The machine in question runs fine outside of these updates that repeat and the one that fails.

I have started other threads about this but eventually anyone attempting to help stops responding. I realize they are probably busy with other stuff.
For example:

http://social.technet.microsoft.com...p/thread/45cdeb11-d77b-4615-9685-7297fd466cd5

Any advice would be greatly appreciated.

4
 
Hi 4on4off, :wave:

Welcome to Sysnative!

I'm going to go ahead and post the links from Bleeping Computer. I feel that they include vital information that will help.

Thread started May 31st "windows updates" (moved from All forum)

Thread started June 5th "Possible infection" (helper abandoned thread)

Thread started June 19th "IE9 "

Thread started June 21st "Possible infection confrmed Win32:SMSSend-IG" (helper abandoned thread)

After further research, I found that possible infection could be FP as discussed "here"

I do not see any of those updates in view installed updates and the section for Microsoft Windows is missing from the list of installed updates.
Click to expand...

Image of Installed updates that was shared with me that show that Microsoft Windows is not there:

Capture.JPG
 
Hello, and welcome to Sysnative!

The majority, although unfortunately not all, of the repeatedly successfully installed update(s) part of your problem is caused when the Common Log File System's (CLFS) System Log File is in an inconsistent state. Fortunately, this can easily be reset, and is a very good place for us to start our investigation.

First, can you please go to:

Start > All Programs > Accessories > right click on Command Prompt > Run as Administrator (it is essential that you run as an administrator)

Right click and paste in:

fsutil resource setautoreset true %systemdrive%\

and press enter. Please confirm that the text:

"The operation completed successfully."

is displayed, and tell me if it was not.

After that, please restart your computer, and tell me if the problems persist. Sometimes this simple fix is all that is required. Other times more complicated action is required, but we should always try the simple stuff first.

The very best of luck!

Richard
 
Forgot to mention:

You will have to install the updates one final time after performing this fix, because despite them being reported as successful, actually (in most cases at least) they have not been installed at all. You need one final, clean install of them to actually get them onto your machine (which is why I always say to everyone that it is usually a very bad idea to hide repeatedly offered updates - they have usually not been installed at all, and the success message lulls you into a false sense of security).

If they get re-offered a second time after the fix, then the problems persist.

Richard
 
@usasma

Thank you.

@neimiro

I navigated to the cmd.exe in system32 right clicked and ran as admin. I just copied and pasted the command and the message "The operation completed successfully." popped up without having to hit enter.

I then restarted the machine and installed the updates. They once again stated they were successful but reappreared as ready to install and the update for IE9 gave me the failed error 9C48 once again.

4
 
4on4off said:
@neimiro

I navigated to the cmd.exe in system32 right clicked and ran as admin. I just copied and pasted the command and the message "The operation completed successfully." popped up without having to hit enter.

I then restarted the machine and installed the updates. They once again stated they were successful but reappreared as ready to install and the update for IE9 gave me the failed error 9C48 once again.

4
Click to expand...

That is a shame. Ah well. Anyway, please download and run (and store in a safe place, as we may need it again later) the System Update Readiness Tool: http://windows.microsoft.com/en-us/windows7/What-is-the-System-Update-Readiness-Tool

If you have already run this under a previous helper, there is no need to run it again at this time.

After the tool has finished executing if not already run, please copy the C:\Windows\Logs\CBS folder to your Desktop, right click on it > Send to > Compressed (zipped) folder, and upload the newly created .zip file here.

Thanks a lot,

Richard
 
niemiro,

I saved the tool to my desktop and ran it. The initialization was successful but the installation is hung up about 2/3 of the way in. It has been there for about 15 minutes. I assume this is not normal but I thought I would check before trying to cancel it.

4
 
4on4off said:
niemiro,

I saved the tool to my desktop and ran it. The initialization was successful but the installation is hung up about 2/3 of the way in. It has been there for about 15 minutes. I assume this is not normal but I thought I would check before trying to cancel it.

4
Click to expand...

Sorry, I probably should have told you about this. Yes, it sounds normal at this time. The tool will perform all of its work at the 60% mark, and will appear to hang there. It will then shoot up to 100% and finish once complete. It also takes a long time to complete. I have seen it take anywhere from 45 seconds right up to 36 hours depending on how badly damaged the system is. I would put the average at around 30mins to 45mins. You may use the computer whilst it is running.

Sorry for not mentioning this. I really should have. If you have already cancelled it, would you mind re-starting it? It is a very useful tool.

Thanks a lot.

Richard
 
No problem. I did not stop it. I will report back when it completes with the log.

That gives me time to clean my nieces laptop anyway.

Thank you for your assistance.

4
 
4on4off said:
No problem. I did not stop it. I will report back when it completes with the log.

That gives me time to clean my nieces laptop anyway.

Thank you for your assistance.

4
Click to expand...

That would be great. Meet you back here when it is done :)
 
I will get back to you on this.

"Found 33931 errors"

That is quite a few, and is certainly more than I can manually fix. We will need an automated solution here.

Please give me a little time to think.
 
4on4off said:
Holy KEEEErap, that is alot. No problemo,,,,,,on standby and many thanks.
Click to expand...

Yes.....it isn't good news. One of the biggest problems here is that it affects so many different windows updates. If it was just one or two, we could consider trying to uninstall them and reinstall them.

But look below (red colouring downwards). See how many are involved? This is a tiny exert of all 34,000 errors:

Code: 
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_[COLOR=#ff0000][B]KB951072[/B][/COLOR]~31bf3856ad364e35~x86~~6.0.2.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB955302~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB952709~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB956390~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB956841~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB954211~31bf3856ad364e35~x86~~6.0.1.4 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB958644~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB957097~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB956802~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB958623~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB958215~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB955839~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB961260~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB958690~31bf3856ad364e35~x86~~6.0.1.6 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB960225~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB963027~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB959426~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB956572~31bf3856ad364e35~x86~~6.0.1.5 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB960803~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB969897~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB970238~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB968537~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB961371~31bf3856ad364e35~x86~~6.0.1.4 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB971657~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB973507~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB970653~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB967723~31bf3856ad364e35~x86~~6.0.1.7 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB968389~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB974571~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB971486~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB975467~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB969947~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB973565~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB976098~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB974318~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB970430~31bf3856ad364e35~x86~~6.0.1.6 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB971737~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB972270~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB978251~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB974145~31bf3856ad364e35~x86~~6.0.1.4 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB977165~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB979306~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB973917~31bf3856ad364e35~x86~~6.0.2.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB978601~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB978338~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB979683~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB980232~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB981793~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB979559~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB980218~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB979482~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2286198~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB978886~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2079403~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB981852~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB982799~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2160329~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB980436~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB981322~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2158563~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2296011~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB979688~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB981957~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB979687~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2207566~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2443685~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2296199~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2305420~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2436673~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2419640~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2485376~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2483185~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2393802~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2479628~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB971029~31bf3856ad364e35~x86~~6.0.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2524375~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2509553~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2412687~31bf3856ad364e35~x86~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2506223~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2506212~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-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2511455~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2507618~31bf3856ad364e35~x86~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~0.0.0.0 Package_for_KB2541763~31bf3856ad364e35~x86~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist

Also, this particular error has no specific solution. The only technique known to be effective is to delete the registry presence for every error listed. This has actually had a 100% success rate for me. The whole point about this error is that these updates are orphaned - almost nothing exists of them, except for a small registry presence - deleting this registry presence usually puts the registry back into a consistent enough state for Windows Update to fix the rest. But it is always a slightly risky proposition. To be quite honest, we are walking on thin ice here. Any fix we attempt to push this computer over the brink.

What Service Pack level are you currently on?

My proposition would be to back up all important data, and attempt a Repair Install. This should not delete any of your files, but I must warn you that on a system this unstable, any servicing operation could push it to the point of no boot. You must be prepared for that, and have everything adequately backed up: http://www.sevenforums.com/tutorials/3413-repair-install.html

If a Repair Install fails, our only option is to delete all 34,000 registry presences, and hope that that makes the computer worse rather than better. As I have said above, I have never actually heard of this going wrong, but I have never attempted this on a machine with more than 750 errors across one or two updates before. But there should be no real difference...hopefully.

Alternatively, if you want to have a bit of fun, we could attempt the fix, missing out the Repair Install entirely...!

Richard
 
I am currently on sp2.

Not really too much I need to save off of that machine, my wife made copies of the pics on there to a disc already.

I am all about the fun so I am down with the fix if you are.

That machine is being demoted to a test facility anyway I think for my own learning purposes for fighting malware and what not.

4
 
4on4off said:
I am currently on sp2.

Not really too much I need to save off of that machine, my wife made copies of the pics on there to a disc already.

I am all about the fun so I am down with the fix if you are.

That machine is being demoted to a test facility anyway I think for my own learning purposes for fighting malware and what not.

4
Click to expand...

Not a problem. I will post the fix tomorrow, if OK with you. It is getting late here.

Richard
 
You bet and thank you for your time and efforts.

I have to head out for work in the mornning around 6 am and will be back after work around 7 pm tomorrow and the next day.

Thanks again.

4
 
Good morning :)

Let's give it a shot then! If everything is safely backed up, you may proceed.

Please press and hold the Windows Key, and then press R to open the Run dialogue > type regedit > OK > File > Export > Selected Branch

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect

Please then give it a sensible, but short, file name, and save it somewhere safe. After that, please repeat for:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect



WARNING! This fix was created specifically for this user! If you are not this user, do not follow these instructions!

After that, please download and run the attached registry fix. It may take a good few seconds to process as there are 34,000 entries in it :p

Then please re-start your computer, re-run the System Update Readiness Tool, and attach a copy of C:\Windows\Logs\CBS\CheckSUR.log to your next post.

Thanks a lot, and the very best of luck.

Richard
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top