Windows Update causes > 600 errors to show up in MMC

[nullpointerus]

My hardware:

- Intel Core 2 Duo E4400
- Gigabyte GA-P35-DS3R v1.0
- 4x1 GB PC2-5300 DDR2-667 5-5-5-15 @ 1.8v
- Radeon HD2900XT 512MB
- WD SE16 320GB SATA HDD x2 (not in RAID)
- SATA DVD Writer (not sure of brand)
- On-board HD Audio (Realtek ALC880 or something)
- On-board LAN (Realtek 8xxx)
- OCZ GameXStream 700W
- CyberPower UPS 750W (not sure of model)
- HP w2207 LCD Monitor
- Generic 17" LCD Monitor
- Belkin Natural Black PS/2
- Logitech MX518 Gaming Mouse (USB)
- Klipsch 2.1 THX Speakers


OK...so I do the following (rebooting as needed):

01. Backup all my data to another SATA drive.
02. Change all overclocked stuff back to stock.
03. Change the HPET in BIOS to 32-bit.
04. Boot from the Vista x86 Setup DVD.
05. Delete my Vista x64 partition and create a new one.
06. Install to the new partition.
07. Install Intel INF Update Utility 8.3.0.1013.
08. Install Realtek HD Audio R1.85 for Vista x86.
09. Install Catalyst 8.1 w/ CCC.
10. Install Catalyst 8.1 Theater Drivers (550 Pro)

--> I open MMC's Event Viewer, and see zero errors.

12. Open Windows Update (WU), which makes me install a new version of WU.

--> ~12 errors in Event Viewer (cannot set the "State" of various updates)

13. Open WU and install all security updates.

--> ~200 errors in Event Viewer (very similar messages)

14. Open WU and install all optional updates.

--> ~550 errors in Event Viewer (very similar messages)

15. Manually install the DX9/10 video hotfixes.

--> ~600 errors in Event Viewer (very similar messages)

:shocked:


I tried this process twice, with the *same* results...?

Is this a problem with my PC, or is the newest Windows Update on Vista x86 just *this* buggy?

All the updates reported that they succeeded, and my computer seems to start up OK.


Notes:

- I get no errors during Vista Setup.

- My BIOS is updated to the latest version (F11).

- My Intel ICH9R controller is set to AHCI mode w/ Ports 1-3 native mode enabled.

- My PSU (OCZ GameXStream 700W) is certified by ATI for my GPU (HD2900XT 512MB).

- My UPS (750W CyberPower) is rated higher than my PSU (700W), which should itself be overkill for this PC.

- I'm running a CoolerMaster CM690 case w/ Tuniq Tower 120 and plenty of 120mm fans keeping everything *very* cool.

- My rig had passed many stability tests, both at stock and while overclocked. Memtest86 > 3 hr., all three torture tests of Prime95 > 10 hr. each, etc. and was stable in games for hours at a time with no crashes.


Does anyone have *any* idea where to begin troubleshooting this problem?
:Q


Now I will try *another* clean installation -- this time without installing any drivers. If Vista x86's latest Windows Update client fails with that setup, it's got to be either a hardware problem (which I doubt, but it's possible) or a bug somewhere in Vista x86 or the WU client.


(Don't post a "don't worry about it" message because I *will* worry about it. )

 

[robisbell]

sounds like a buggy update and nothing to do with your end. I'd go through if you reload Vista fresh, to manually go through the updates and skip anything hardware related.

 

[nullpointerus]

Ah, but that's the trouble...

You see, I can't get to any of the updates. As soon as I launch Windows Update in Vista x86 for the first time, it requires that I install a new version of the Windows Update client.

And this is where the errors begin...

http://img520.imageshack.us/my...image=wuerrors1lj0.jpg
http://img520.imageshack.us/my...image=wuerrors2kp6.jpg

That's just from installing the new Windows Update client...no "real" updates yet.

I had those errors *again* on a clean install with no third party software or drivers...
...all I did was log in and install the new WU client (as prompted). :Q


So...I'm completely lost here...

How can I troubleshoot a problem like this?

 

[mrblotto]

Try using only 2 sticks of RAM

 

[robisbell]

okay, I'd download The Ultimate Boot CD, and have it run memtest86+ for 6 hours on all of the ram.
you know going to a 32bit version you're wasting 2 GB of ram.
after memtest has run, posts the results.

 

[nullpointerus]

Try using only 2 sticks of RAM

Yep, tried that -- same result. Maybe the first two sticks are bad...

I also tried changing SATA cables and putting the HDD/DVD into IDE compatibility mode -- same result.

The BIOS had some auto-o/c setting on by default (kinda stupid IMO), so I shut it off and tried again -- same result.

okay, I'd download The Ultimate Boot CD, and have it run memtest86+ for 6 hours on all of the ram.
...
after memtest has run, posts the results.

I will set that up to run overnight.

you know going to a 32bit version you're wasting 2 GB of ram.

Eh...well, more like 768 MB wasted.

Y'know, I went 32-bit because of HW/SW troubles I couldn't track down in 64-bit Vista.


Now we know how great an idea *that* was.




If the problem does turn out to be a bad stick (or more) of RAM, then perhaps it will solve all the other wierd problems I've had over the past year or so with Vista.

 

[nullpointerus]

I tried swapping the first 2 GB for the second 2 GB -- same result.

It's kinda funny that two sticks would be bad in exactly the same way, but what do I know?


Oddly enough, the number of errors remains constant. It's always 52, split into two categories. When the original DIMM order, the errors were split 7/45. Then when I pulled the second two DIMMs, the same thing happened. But when I replaced the first two DIMMs with the second two DIMMs (i.e still 2 GB total in the machine), the errors split 8/44. Now that I've added the first two DIMMs back in where the second two DIMMs used to be (i.e. full 4 GB in the machine), the errors are still split 8/44.

Then again, maybe I'm just imagining this... *sigh*


I swapped the HD2900XT out for a passively-cooled X1550 -- same result.

I tried the DVD drive on the other SATA controller -- same result.


Nevertheless, I put the full 4 GB in and ran the memory test overnight:

Memtest86+ v1.70
L1 Cache: 64K 32787MB/s
L2 Cache: 2048K 13986MB/s
Memory: 4095M 3257MB/s

WallTime: 8:55:06
Cached: 4095M
RsvdMem: 84M
MemMap: e820-Std
Cache: on
ECC: off
Test: Std
Pass: 9
Errors: 0
ECC Errors:

Nothing. It would have been SO nice to find a convenient little hardware problem that could explain all the other seemingly unrelated (and sometimes unresolvable) software problems I've been having.


I'm open to suggestions. At this point, the problem could be:

- A bad Vista x86 DVD.
- My RAM is faulty, but Memtest86+ couldn't find that.
- Bad cache on the CPU, that Memtest86+ just doesn't happen to hit. (<-- possible?)
- My DVD drive cannot read the DVD properly.
- The MB has a fault that results in this error.
- The CPU has a fault that results in this error.
- Life just has a personal (and particularly nasty) grudge against me.

I ran Vista x86 for months on the same MB+CPU+RAM without these odd Windows Update errors. Some hardware component could have gone bad, I suppose, but then I would have thought that all the stability tests would have turned up something.




I do NOT want to get to the point where I'm swapping CPUs or motherboards...

 

[dclive]

Originally posted by: nullpointerus
I tried swapping the first 2 GB for the second 2 GB -- same result.

It's kinda funny that two sticks would be bad in exactly the same way, but what do I know?


Oddly enough, the number of errors remains constant. It's always 52, split into two categories. When the original DIMM order, the errors were split 7/45. Then when I pulled the second two DIMMs, the same thing happened. But when I replaced the first two DIMMs with the second two DIMMs (i.e still 2 GB total in the machine), the errors split 8/44. Now that I've added the first two DIMMs back in where the second two DIMMs used to be (i.e. full 4 GB in the machine), the errors are still split 8/44.

Then again, maybe I'm just imagining this... *sigh*


I swapped the HD2900XT out for a passively-cooled X1550 -- same result.

I tried the DVD drive on the other SATA controller -- same result.


Nevertheless, I put the full 4 GB in and ran the memory test overnight:

Memtest86+ v1.70
L1 Cache: 64K 32787MB/s
L2 Cache: 2048K 13986MB/s
Memory: 4095M 3257MB/s

WallTime: 8:55:06
Cached: 4095M
RsvdMem: 84M
MemMap: e820-Std
Cache: on
ECC: off
Test: Std
Pass: 9
Errors: 0
ECC Errors:

Nothing. It would have been SO nice to find a convenient little hardware problem that could explain all the other seemingly unrelated (and sometimes unresolvable) software problems I've been having.


I'm open to suggestions. At this point, the problem could be:

- A bad Vista x86 DVD.
- My RAM is faulty, but Memtest86+ couldn't find that.
- Bad cache on the CPU, that Memtest86+ just doesn't happen to hit. (<-- possible?)
- My DVD drive cannot read the DVD properly.
- The MB has a fault that results in this error.
- The CPU has a fault that results in this error.
- Life just has a personal (and particularly nasty) grudge against me.

I ran Vista x86 for months on the same MB+CPU+RAM without these odd Windows Update errors. Some hardware component could have gone bad, I suppose, but then I would have thought that all the stability tests would have turned up something.




I do NOT want to get to the point where I'm swapping CPUs or motherboards...

Guys, this is a Windows issue, not a hardware issue. Not being able to apply MS Updates is a Windows problem...

You're having problems installing Windows Update. Microsoft supports this for free. Call them up, tell them what's going on, and I suspect they'll have you fixed quickly.

 

[nullpointerus]

I tried using a different DVD drive -- same problem.

I tried switching my SATA HDD and DVD to a different SATA controller -- same problem.

I'm also getting a LOT of wierd errors with ATI's Catalyst Control Center -- quite a few problems that a friend is not getting on nearly identical hardware w/ a clean installation of Vista x86 *and* x64. CCC almost constantly at startup in Vista x86, and it takes a *lot* of work to get the CCC window up on the screen. Also, I'm having power-saving issues in Vista x64 where CCC takes up massive CPU and RAM by getting itself into an infinite loop -- but only when Vista is set to automatically shut the monitor off.

*Finally*, CCC changing any 3D settings in CCC in Vista x64 causes my 3D settings and video settings to get completely screwed up. I've had this problem since Catalyst 7.4...

Nevertheless, I'll give that MS support option a shot...

(I'm not sure how I could screw up the Install Now! button, but if it's *free* support... )

*groan*

First, I'll try reflashing the BIOS...then I'm *completely* out of HW-related ideas.

Second, I'll see if I get these same CCC errors with that ATI X1550. If not, then my HD2900XT might be defective (or might not be getting enough power, somehow? failing UPS maybe?). If so, then I'll have another piece of the puzzle for my current ATI support ticket.

Now I've got to put my case back in its original configuration...


(To make matters worse, I broke part of my case's front cover while swapping DVD drives.)

 

[robisbell]

I'd use The Ultimate Boot CD and use it to wipe the drives completely clean of partitions and then try reinstalling. the dvd's for vista are original and not copies, correct?

 

[dclive]

Originally posted by: nullpointerus
Nevertheless, I'll give that MS support option a shot...

If the issue you're troubleshooting is related to Windows Updates, Microsoft will support this for free.

I would do that first, long before rebuilding the machine, if you've put work into adding any additional programs to Windows since you installed it.

If you've installed nothing since installing Vista, then I'd still call MS first - since if you've installed nothing, their plain OS should certainly do Windows Updates!

 

[nullpointerus]

Yes, I'm using the original DVDs.

I found someone with the same problem:
http://forums.microsoft.com/Te...stID=2112409&SiteID=17

...which references this page:
http://www.eggheadcafe.com/sof...30636397/kb938979.aspx

However, those people have moved their user folders to different locations. I'm dealing with a clean installation where everything ought to be exactly where Vista Setup created it.

A similar problem is here:
http://forums.microsoft.com/Te...stID=1460036&SiteID=17


I ran the WMIDiag tool from Microsoft:
http://www.microsoft.com/downl...92ae97d&displaylang=en

...which spat out tons of errors like these two:

21463 15:02:31 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
21464 15:02:31 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
21465 15:02:31 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
21466 15:02:31 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
21467 15:02:31 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
21468 15:02:31 (0) **
21469 15:02:31 (0) ** WMI namespace security for 'Root': .................................................................................. MODIFIED.
21470 15:02:31 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
21471 15:02:31 (0) ** - REMOVED ACE:
21472 15:02:31 (0) ** ACEType: &h0
21473 15:02:31 (0) ** ACCESS_ALLOWED_ACE_TYPE
21474 15:02:31 (0) ** ACEFlags: &h12
21475 15:02:31 (0) ** CONTAINER_INHERIT_ACE
21476 15:02:31 (0) ** INHERITED_ACE
21477 15:02:31 (0) ** ACEMask: &h6003F
21478 15:02:31 (0) ** WBEM_ENABLE
21479 15:02:31 (0) ** WBEM_METHOD_EXECUTE
21480 15:02:31 (0) ** WBEM_FULL_WRITE_REP
21481 15:02:31 (0) ** WBEM_PARTIAL_WRITE_REP
21482 15:02:31 (0) ** WBEM_WRITE_PROVIDER
21483 15:02:31 (0) ** WBEM_REMOTE_ACCESS
21484 15:02:31 (0) ** WBEM_WRITE_DAC
21485 15:02:31 (0) ** WBEM_READ_CONTROL
21486 15:02:31 (0) **
21487 15:02:31 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
21488 15:02:31 (0) ** Removing default security will cause some operations to fail!
21489 15:02:31 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
21490 15:02:31 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
21491 15:02:31 (0) **
21492 15:02:31 (0) ** WMI namespace security for 'Root': .................................................................................. MODIFIED.
21493 15:02:31 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
21494 15:02:31 (0) ** - REMOVED ACE:
21495 15:02:31 (0) ** ACEType: &h0
21496 15:02:31 (0) ** ACCESS_ALLOWED_ACE_TYPE
21497 15:02:31 (0) ** ACEFlags: &h12
21498 15:02:31 (0) ** CONTAINER_INHERIT_ACE
21499 15:02:31 (0) ** INHERITED_ACE
21500 15:02:31 (0) ** ACEMask: &h13
21501 15:02:31 (0) ** WBEM_ENABLE
21502 15:02:31 (0) ** WBEM_METHOD_EXECUTE
21503 15:02:31 (0) ** WBEM_WRITE_PROVIDER
21504 15:02:31 (0) **
21505 15:02:31 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
21506 15:02:31 (0) ** Removing default security will cause some operations to fail!
21507 15:02:31 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
21508 15:02:31 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
21509 15:02:31 (0) **

...and plenty of other errors...

22872 15:02:31 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
22873 15:02:31 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
22874 15:02:31 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
22875 15:02:31 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
22876 15:02:31 (0) ** 'select * from MSFT_SCMEventLogEvent'
22877 15:02:31 (0) **
22878 15:02:31 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
22879 15:02:31 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 6 ERROR(S)!
22880 15:02:31 (0) ** - ROOT/MICROSOFTDFS, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22881 15:02:31 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22882 15:02:31 (0) ** - ROOT/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22883 15:02:31 (0) ** - ROOT/RSOP/USER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22884 15:02:31 (0) ** - ROOT/RSOP/COMPUTER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22885 15:02:31 (0) ** - ROOT/SERVICEMODEL, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22886 15:02:31 (0) **
22887 15:02:31 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 7 ERROR(S)!
22888 15:02:31 (0) ** - ROOT/MICROSOFTDFS, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22889 15:02:31 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22890 15:02:31 (0) ** - ROOT/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22891 15:02:31 (0) ** - ROOT/RSOP/USER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22892 15:02:31 (0) ** - ROOT/RSOP/COMPUTER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22893 15:02:31 (0) ** - ROOT/SERVICEMODEL, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22894 15:02:31 (0) ** - Root/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22895 15:02:31 (0) **
22896 15:02:31 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 18 ERROR(S)!
22897 15:02:31 (0) ** - Root, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22898 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22899 15:02:31 (0) ** - ROOT/SUBSCRIPTION, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22900 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22901 15:02:31 (0) ** - ROOT/DEFAULT, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22902 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22903 15:02:31 (0) ** - ROOT/CIMV2, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22904 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22905 15:02:31 (0) ** - ROOT/CIMV2/SECURITY, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22906 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22907 15:02:31 (0) ** - ROOT/CIMV2/APPLICATIONS, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22908 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22909 15:02:31 (0) ** - ROOT/CIMV2/APPLICATIONS/WINDOWSPARENTALCONTROLS, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22910 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22911 15:02:31 (0) ** - ROOT/CIMV2/APPLICATIONS/GAMES, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22912 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22913 15:02:31 (0) ** - ROOT/CLI, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22914 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22915 15:02:31 (0) ** - ROOT/NAP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22916 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22917 15:02:31 (0) ** - ROOT/RSOP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22918 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22919 15:02:31 (0) ** - ROOT/WMI, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22920 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22921 15:02:31 (0) ** - ROOT/DIRECTORY, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22922 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22923 15:02:31 (0) ** - ROOT/DIRECTORY/LDAP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22924 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22925 15:02:31 (0) ** - ROOT/SECURITYCENTER, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22926 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22927 15:02:31 (0) ** - ROOT/MICROSOFT, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22928 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22929 15:02:31 (0) ** - ROOT/MICROSOFT/HOMENET, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22930 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22931 15:02:31 (0) ** - ROOT/ASPNET, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22932 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22933 15:02:31 (0) **
22934 15:02:31 (0) ** WMI MOF representations: ............................................................................................ OK.
22935 15:02:31 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
22936 15:02:31 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 17 ERROR(S)!
22937 15:02:31 (0) ** - ROOT/WMI, InstancesOfAsync, 'MSMouse', 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
22938 15:02:31 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
22939 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Cache' did not return any instance while AT LEAST 1 instance is expected.
22940 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22941 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Memory' did not return any instance while AT LEAST 1 instance is expected.
22942 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22943 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Objects' did not return any instance while AT LEAST 1 instance is expected.
22944 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22945 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_PagingFile' did not return any instance while AT LEAST 1 instance is expected.
22946 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22947 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Processor' did not return any instance while AT LEAST 1 instance is expected.
22948 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22949 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_System' did not return any instance while AT LEAST 1 instance is expected.
22950 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22951 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Process' did not return any instance while AT LEAST 1 instance is expected.
22952 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22953 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Thread' did not return any instance while AT LEAST 1 instance is expected.
22954 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22955 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMP' did not return any instance while AT LEAST 1 instance is expected.
22956 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22957 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMPv6' did not return any instance while AT LEAST 1 instance is expected.
22958 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22959 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv4' did not return any instance while AT LEAST 1 instance is expected.
22960 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22961 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv6' did not return any instance while AT LEAST 1 instance is expected.
22962 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22963 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv4' did not return any instance while AT LEAST 1 instance is expected.
22964 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22965 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv6' did not return any instance while AT LEAST 1 instance is expected.
22966 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22967 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv4' did not return any instance while AT LEAST 1 instance is expected.
22968 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22969 15:02:31 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv6' did not return any instance while AT LEAST 1 instance is expected.
22970 15:02:31 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
22971 15:02:31 (0) **
22972 15:02:31 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
22973 15:02:31 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
22974 15:02:31 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
22975 15:02:31 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
22976 15:02:31 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
22977 15:02:31 (0) ** WMI static instances retrieved: ..................................................................................... 1444.
22978 15:02:31 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
22979 15:02:31 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
22980 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22981 15:02:31 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
22982 15:02:31 (0) ** DCOM: ............................................................................................................. 0.
22983 15:02:31 (0) ** WINMGMT: .......................................................................................................... 0.
22984 15:02:31 (0) ** WMIADAPTER: ....................................................................................................... 0.
22985 15:02:31 (0) **
22986 15:02:31 (0) ** # of additional Event Log events AFTER WMIDiag execution:
22987 15:02:31 (0) ** DCOM: ............................................................................................................. 0.
22988 15:02:31 (0) ** WINMGMT: .......................................................................................................... 0.
22989 15:02:31 (0) ** WMIADAPTER: ....................................................................................................... 0.
22990 15:02:31 (0) **
22991 15:02:31 (0) ** 32 error(s) 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action
22992 15:02:31 (0) ** => This error is typically due to insufficient or restricted permissions in the examined system.
22993 15:02:31 (0) ** => ENSURE you are a Full Administrator of the examined system, if the WMI provider or the
22994 15:02:31 (0) ** WMI system security do not enforce any restrictions.
22995 15:02:31 (0) **
22996 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22997 15:02:31 (0) ** WMI Registry key setup: ............................................................................................. OK.
22998 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22999 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23000 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23001 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23002 15:02:31 (0) **
23003 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23004 15:02:31 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
23005 15:02:31 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23006 15:02:31 (0) **
23007 15:02:31 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\MICHAEL\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0_VISTA.CLI.RTM.32_MICHAEL-PC_2008.01.26_14.55.01.LOG' for details.
23008 15:02:31 (0) **
23009 15:02:31 (0) ** WMIDiag v2.0 ended on Saturday, January 26, 2008 at 15:02 (W:126 E:126 S:1).

No wonder nothing updates properly!

(This is *immediately* after a clean installation of Vista x86.)


I'll try the disk repartitioning now...everything is backed up anyway.

 

[robisbell]

I'd seriously run a full diagnsotic on the HDD's, somethings telling me that there's a hardware issue.

 

[nullpointerus]

Originally posted by: robisbell
I'd seriously run a full diagnsotic on the HDD's, somethings telling me that there's a hardware issue.

After the repartitioning, WMIDiag reports success!

However, the problem remains: I get ~50 errors after updating the WU client.

WMIDiag still reports that WMI is working OK after that.


So...we were dealing with multiple problems before...


Now there's a new error, dated shortly after initial setup:

Event 1533, User Profile Service

Windows cannot delete the profile directory C:\Users\Administrator. This error may be caused by files in this directory being used by another program.

:shocked:


I think you're right... I will schedule a surface scan on the HDD for tonight.

These HDDs are brand new --> October 2007

What stumps me is that I've tried installing to partitions that are on different areas of the disk. Why would all these clean installations fail the same way if the disk has a physical defect? Maybe there's bad cache RAM on the disk PCB, or some other similar fault.

I will also try a different HDD.


BTW, is there some kind of utility to check the setup DVD? I know that some Linux distributions have a media check program that's spotted errors for me in the past. Maybe there some hairline scratch or something else I can't see that's confusing Vista Setup.

 

[robisbell]

not sure about the vista dvd's, but you are aware about then they had a lot of defective and infected HDD's sold new on the market?

 

[nullpointerus]

Originally posted by: robisbell
not sure about the vista dvd's, but you are aware about then they had a lot of defective and infected HDD's sold new on the market?

Defective? Yes, I heard about that since the IBM days...

But infected...?! :shocked:

What kind of virus is it?

- Could it spread to other HDDs?
- Could it infect the BIOS?
- Could it cause these errors?
- How could I find/eliminate it?


OK...so...no matter what I try, I get the same errors...

What has remained constant throughout this testing?

- Vista x86 DVD
- CPU
- MB
- WLAN
- DSL
- PSU
- UPS



Now I have no idea what to try next.


These errors *really* bug me!

I need to find the cause, not just put the x86 DVD away and forget about it.


I suppose the thing to do is contact WU support on Monday...


BTW, I tried reflashing the BIOS -- same result. I can't shake these damned errors!

 

[dclive]

Contact WU support. So far this is a software issue, and I have seen nothing to suggest otherwise. Have you seen disk-related errors in the event log, for example?

 

[robisbell]

http://www.google.com/search?i...s=1&q=new+hdd+infected

 

[cubby1223]

Originally posted by: robisbell
http://www.google.com/search?i...s=1&q=new+hdd+infected

One thing in common are those are all *external* drives.

You do not install operating systems on external drives.

Internal drives come unformatted. No infections.

And by "a lot" I'm sure you really meant "extremely few".

 

[cubby1223]

In Windows XP when there's Windows Update errors (which is very common and can happen immediately following a clean install or a repair install) I have a batch file that does this, and has corrected all problems I've come across so far:

regsvr32.exe regwizc.dll
regsvr32.exe Mssip32.dll
regsvr32.exe Wintrust.dll
regsvr32.exe Softpub.dll
regsvr32.exe Initpki.dll
regsvr32.exe Dssenh.dll
regsvr32.exe Rsaenh.dll
regsvr32.exe Gpkcsp.dll
regsvr32.exe Slbcsp.dll
regsvr32.exe Cryptdlg.dll
regsvr32.exe licdll.dll
regsvr32.exe Sccbase.dll
regsvr32.exe Msxml.dll
regsvr32.exe Msxml2.dll
regsvr32.exe Msxml3.dll
regsvr32.exe c:\windows\system32\wuweb.dll
regsvr32.exe c:\windows\system32\wups2.dll
regsvr32.exe c:\windows\system32\wups.dll
regsvr32.exe c:\windows\system32\wucltui.dll
regsvr32.exe c:\windows\system32\wuaueng1.dll
regsvr32.exe c:\windows\system32\wuaueng.dll
regsvr32.exe c:\windows\system32\wuapi.dll

Can the same process be done in Vista? Sorry I don't have much experience with Vista yet.

 

[soccerballtux]

This means you need to turn your harddrive upside down. The data is starting to fall off the top platters onto the bottom platters, which is ok, but the data on the bottom platters is falling off to the bottom of the drive (and thus not being read). If you turn it upside down it'll be fine, just be careful when you do or all the data will get too jumbled up and it'll be useless.

Let us know if this works.

 

[nullpointerus]

Originally posted by: dclive
Contact WU support. So far this is a software issue, and I have seen nothing to suggest otherwise. Have you seen disk-related errors in the event log, for example?

1. This is a clean installation.
2. Windows Update does NOT work.
3. No one else seems to have this problem (under these circumstances).

It's possible that Microsoft has broken WU this fundamentally, but what about apoppin, who did a clean installation on similar hardware and experienced no such errors. He had the same base OS install package (i.e. home premium x86), and I asked him to check his event log re: windows updates. Not a single error for hime. Yet, on my PC, everytime WU does anything there's an error about a state transition. Just downloading updates (without automatically installing them) leaves several hundred errors in the event log.

What about these other errors:

Event 1533, User Profile Service

Windows cannot delete the profile directory C:\Users\Administrator. This error may be caused by files in this directory being used by another program.

Event 10, VDS Dynamic Provider 2.0

The provider failed while storing notifications from the driver. The Virtual Disk Service should be restarted. hr=80042505

...which never appear twice...?!

The following errors are now appearing consistently:

Event 1005, Perflib

Unable to locate the open procedure "OpenIPSecPerformanceData" in DLL "C:\Windows\System32\ipsecsvc.dll" for the "PolicyAgent" service. Performance data for this service will not be available.

Event 1008, Perflib

The Open Procedure for this service "PNRPsvc" in DLL "C:\Windows\system32\pnrpperf.dll" failed. Performance data for this service will not be available.

Event 1008, Perflib

The Open Procedure for this service "DFSR" in DLL "C:\Windows\System32\DfsrPerf.dll" failed. Performance data for this service will not be available.

Event 1017, Perflib

Disabled performance counter data collection from the "PolicyAgent" service because the performance counter library for that service has generated one or more errors. The errors that forced this action have been written to the application event log. Correct the errors before enabling performance counters for this service.

Event 2004, usbperf (<-- 3 times)

Usbperf data collection failed. Collect function called with unsupported Query Type.

Important functions not being found...in DLL files...
To me, it's looking more and more like the OS is not being copied/configured correctly. I'll run a sfc scan in a little while to be sure. On a clean installation, every file ought to check out OK with this program, right? I'll also need to see the Windows Setup logs.

What about the broken WMI caused by invalid partitions, that we tracked down and fixed? Where they Windows Update problems? Why did my partition setup become corrupted in the first place? I experienced none of *these* errors throughout all the clean installations I performed in Vista x64.

Tell me, do any of *you* get these errors?

I can try to "fix" the clean installation by reregistering those DLLs, but then...why were they not registered in the first place? Why would that happen on my PC and no one else's? And how would I know that there aren't now other related problems with the same underlying cause? The whole point of the clean installations was to *eliminate* hardware as a factor in this problem *and* the other problems I've been having.

- The RAM tests eliminated RAM as a factor.
- The HDD tests (different drive and surface scan) eliminated HDD as a factor.
- The DVD tests (different drives) eliminated DVD drives as a factor.
- The BIOS tests (flash and default settings) eliminated BIOS settings as a factor.
- The SATA tests (different cables, controller, etc.) eliminated SATA as a factor.
- The power tests (low-power vid. card, unplugging nonessentials) eliminated power as a factor.

In Vista x64 (and possibly x86 -- haven't gotten that far yet), I cannot get a stable, working installation of Catalyst Control Center. Leave it alone w/ its factory defaults, and the CCC does OK, but change any settings, and the program goes nuts. It loses my video settings, multi-monitor setup, 3D settings. They all get set to random values. This has been the case from Catalyst 7.4 to 8.1. As a result, I tended to leave CCC alone. But no one else seems to have this problem...on clean installations. Why won't it work on my PC?

In Vista x64 (and possibly x86 -- haven't gotten that far yet), CCC.exe will use massive CPU time and gobs of RAM whenever my monitor goes into power-saving move. This may also persist when the monitor has left power-saving mode, so I'm left with everything on the PC being jerky as heck unless I end-process CCC.exe or reboot the PC.

The above two problems with CCC happen with a clean installation of Vista x64...but not on a clean installation of Vista x64 made on an almost identical HW configuration with a copy of the setup DVD. What does that tell you?

In Vista x86, ATI's (?) MMLoader.exe crashed every boot (twice, because it tries to reload after failing the first time). Yes, on a clean installation. But, in the process of troubleshooting this issue, I've learned that this only happens on my HD2900XT with a multi-monitor setup. Now, is this due to a driver bug, or is it due to an OS file/setting being incorrectly configured during Vista Setup?

So...were these Vista installations really "clean" or did they fail at some point? Or am I still stuck with a bunch of *seemingly* unrelated problems that have no known solutions. Working through the issues individually with ATI support just means they'll end up suspecting my HW and OS installation one-by-one *anyway*. Generally, whatever tech. support cannot reproduce gets chalked up to HW or user error...

How can I continue the support tickets with ATI about my HD2900XT and CCC issues if I can't be sure the OS has installed properly? or if I have no confidence in my other HW?

Windows Update support may be able to fix the WU errors (which I doubt, but I'll try anyway), but they cannot answer any of the other questions in this thread.

 

[nullpointerus]

SFC reports no integrity violations.

(I assume that SFC checks the file checksums, or something like that?)

UPDATE:

I tried doing a manual hotfix installation -- no errors!

However, doing an automatic update after that resulted in more of the usual errors. And there was one that I found puzzling:

Event 8194, VSS

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or reuestor process.

Security settings...isn't that what the other ipsec-whatever errors are talking about?

Windows Update appears to be incapable of downloading files...now the question is why...?




I'll contact WU support on Monday. In the meantime, I have one more idea to try...

 

[nullpointerus]

Vista x64 now has the same problem... >600 errors...



:|


Well, we know it's definitely not the media...
...both DVDs aren't likely to be wrecked in the same way...
...ditto for the DVD drives, HDDs, SATA controllers, and so on...

WMIDiag reports that WMI is working correctly.

That leaves software problems (which apparently *no one* else has with the *same* default settings...?!) and serious hardware problems with the CPU and MB. Personally, I think that my CPU and MB are the only things I've got that the people without this problem do not have. We've cleared nearly every other piece of hardware in my rig.

In *theory*, Microsoft could have released a version of the Windows Update client that does work for existing systems having some pre-existing updates but that does *not* work for systems having no updates. However, apoppin did the x86 and x64 installs (after me!) without encountering this issue at all. I asked him specifically to look in Event Viewer, and he confirmed that there were no errors logged on his machine.

This problem didn't even happen on my rig just a day or so before this thread (although I have been wrestling with those ATI/CCC issues for quite a while).

Since manual updates appear to work fine, I'll try manually applying the ~40 or so updates that would presumably have worked fine with the old client (or back when my rig was working, if this is a hardware problem), and then I'll try auto-updating the WU client itself.

:Q


(Not that it'll work... )

At least I'll have a bunch of info. to give my WU support rep. :thumbsup:

 

[robisbell]

this is sounding like a memory issue now, or hdd not tracking properly when they write data.