[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2128
  • Last Modified:

How do I fix WMI on windows xp sp3

We are having issues with our machines receiving their Windows Updates. In September we deployed Windows XP SP3 on about 80% of our machines. Since then WMI has been failing on those machines running SP3 causing both BITS and WUAUServ to fail as well. Our machines are old. They are Gateway E6000's and were purchased I believe in 2003. Microsoft sent us a fix which works but, once the systems are rebooted they fail again. The fix from Microsoft was the following script  
Net Stop WinMgmt /y
Net Start WinMgmt

Currently we have been using LANDesk to run a scheduled task which applies this script but this is an imperfect solution at best.

How can we permanently remedy this problem?

  • 4
1 Solution
onealgAuthor Commented:
I am not sure if this is revelent because from what I read in the article it was for SP2 and we are only having the problem with SP3. But I am going to try the fix.
onealgAuthor Commented:
I have tried the fix suggested in http://windowsxp.mvps.org/repairwmi.htm but it seems it does not help. To further explain our situation. The main problem we are seeing is that our group policies are not being properly applied. When the cmd gpresult is run on our machines using SP3 it returns with the following "ERRORL Logon failure: unknown name or bad password". We believe this to be related to WMI. When we run the script I posted in the first post gpresult then works properly however after a reboot or two the machine fails again. Any further thoughts?
onealgAuthor Commented:
As long as the command sc sdshow winmgmt returns the results
gpresult executes the problem seems to be that the machines running SP3 revert to
I am not sure when this occurs but it appears to be what is mucking up everything else
onealgAuthor Commented:
This did validate how to fix WMI and clear any corruption.  Our problem actually is deeper since it was broken even on SP2.  The way we put the question was accurately answered.

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now