Windows Vista vista Update Mismatch

Hi all,
I am using Vista Home Premium SP1 (64 bit) and I noticed a lot of warnings for servicing in event viewer. They pertain to auto updates. These are the errors from the last set of auto updates.
Warning 4/15/2009 5:48:20 PM Microsoft-Windows-Servicing 4374 None Windows Servicing identified that package KB960803(Security Update) is not applicable for this system

Warning 4/15/2009 5:48:03 PM Microsoft-Windows-Servicing 4374 None Windows Servicing identified that package KB959426(Security Update) is not applicable for this system

Warning 4/15/2009 5:46:44 PM Microsoft-Windows-Servicing 4374 None Windows Servicing identified that package KB963027(Security Update) is not applicable for this system

Warning 4/15/2009 5:46:39 PM Microsoft-Windows-Servicing 4374 None Windows Servicing identified that package KB938464(Security Update) is not applicable for this system

Warning 4/15/2009 5:46:36 PM Microsoft-Windows-Servicing 4374 None Windows Servicing identified that package KB950762(Security Update) is not applicable for this system

It appears that all the updates I have applied have this same problem. I never received any warning about the mismatch. Did not encounter any interrupted or failed updates. They all completed normally after reboot.

It doesn't make any sense because on the surface the machine doesn't exhibit any crashes or hangs.
This is a new laptop that I finally got setup to my liking, even with the nagging old hen.
Any help will be greatly appreciated. Sincerely, OleGreyGhost

 

Steve,
Thank you for the quick reply. I Will follow your suggestion to see what I can learn. As to your observation:

I understand what you mean. In my case the

At least that is what the windows update page is displaying. I will return to let you know how I made out. OleGreyGhost

 

Steve,
The results of my query on google only revealed a few pertinent entries. The one that closest resembles my problem was by Chris Lent, with the same message & event ID 4374:

This was logged as a warning. Where we differed was in the second warning (Event ID 4385). In Chris' case Windows Servicing failed to complete the process of his update. His update did not install.

In my case the update installed with the message:

Again logged as a warning, both warnings were listed four times. A check of the installed updates shows the same warnings for every update that I installed since I purchased the machine in January. It also shows that the updates were successful.

What I find interesting is the root of Chris' problem. He found the Windows Management Instrumentation & Windows Modules Installer services were disabled on his sysem. Turning them on resolved his problem. On my system both services are running.

The interesting part is in event viewer WMI is logged an an error in administrative events with the following messsage:

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 11/21/2008 7:40:24 AM (Setup date by Gateway)
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WIN-6CN4XQWXGU1
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

The above error has been logged every day since I purchased the machine in January.
Could this be the source of my problem? Sincerely, OleGreyGhost

 

Hi Steve,
The only information I could find on Microsofts' site on CIMV2 pertained to MS Server 2008. Don't know if this applies to my problem or not.

I apologize for misidentifying security update KB960803, this is to prevent an unauthenticated remote attacker.

I did some further research. I queried Event ID 4374 at microsoft thru event viewer which produced: Event ID 4374 — Package Installations or Removals Updated: September 20, 2007 Applies To: Windows Server 2008.

An excerpt explains Event ID 4376: Note: If you receive Event 4376 (Servicing has required reboot to complete the operation of setting package <PackageName>(<PackageReleaseType>) into <LocalizedPackageInstallState>(<PackageInstallState>) state), then the package may be reported as installed even though you still need a restart the computer to complete the installation.

To verify the installation check in the Registry Editor (Regedit.exe) to confirm the installation status of that package under the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.

If you were installing, check that your package is listed and that the value for the CurrentState key is one of the following: 7 (installed), 6 (installation is pending a reboot), or 4 (all of the manifests and files are present on the computer, but the files have not been projected and are not being used by the computer).

These are the packages for the unauthenticated remote attacker:

KB960803_client_0~31bf3586ad364e35~amd64~~6.0.1.0
KB960803_client_1~31bf3586ad364e35~amd64~~6.0.1.0
KB960803_client~31bf3586ad364e35~amd64~~6.0.1.0
KB960803~31bf3586ad364e35~amd64~~6.0.1.0
The CurrentState key for all four is 7 (installed). This is the same for the rest of the updates that were installed.

I notice in the package release number "amd64 ". All the update packages have this "amd64" designation. My question now is, are the packages listed above for an AMD processor? If so that would probably explain the mismatch, or my naivete about the OS. This machine is running an intel chip.

I await your reply. Sincerely, OleGreyGhost

 

Arie,
Thanks for the explanation & the link. I didn't think it would be that easy to find the answer to this problem. Don't really know where to look after this. Will try to follow this clue: "//./root/CIMV2" because of error 0x80041003. If any of the other gurus have a suggestion or solution, please feel free to contribute. Sincerely OleGreyGhost

 

Arie,
You are the man. Thank you for your continuing effort.

I think I understand what you are doing. With that command I will be deleting the contents of the Winmgmt repository, thereby removing the error.

By rebooting twice, is this going to rebuild the information in the repository, or will it be
built up over time with normal usage? I am just trying to understand how these things work.

I'll make a backup of the files first.

Will give it a try & let you know how I made out. --- Sincerely, OleGreyGhost

 

Arie,
Your fix worked like a charm. After a half dozen reboots, no more WMI error.

Checking for the files in the repository folder reveals they are rebuilt after the first reboot. Thanks again for your kind assistance. Problem resolved.

Sincerely, OleGreyGhost