locked
Windows Vista - Processor info shows "not available" / WMI not working

    Question

  • I have isolated a problem i'm having down to WMI (the windows management instrumentation service)

    Two issues that are immediately noticable:

    In system info, the Processor/Ram show "Not Available"

    When going into Msinfo32 (System Information) there's an error "Can’t Collect Information - Cannot access the Windows Management Instrumentation software. Windows Management

    files may be moved or missing."


    Already tried running sfc /scannow, no errors.  Tried a WMI fix for Windows XP too (found at http://blog.perfectspace.com/2004/07/21/windows-management-instrumentation-wmi-error/)



    This was working fine until i turned off UAC in vista, I believe, because I know I saw system info shortly after installing Windows Vista.



    Anyone have any ideas?

    Tuesday, September 11, 2007 1:29 AM

Answers

  • try this

     

    c:\>net localgroup administrators NetworkService /ADD

     

    I got this from Ivan Brugiolo's guide - credit goes to him

     

    had issues with network and sharing center not coming up at all "server execution failed" and had to fix that by adding administrators to localservice so i figured it was a permissions issue

     

    as soon as i typed this in cmd prompt and started wmi my stuff came right up

     

     

    Sunday, October 28, 2007 12:18 PM

All replies

  • isnt anyone from microsoft on this forum?  I don't have a single reply or even an idea of what's going on here.
    Saturday, September 15, 2007 4:35 PM
  • I have the same exact problem, it stopped showing up as soon as i hit 3.12ghz on my core 2 duo while i was overclocking, my pc runs perfectly, WMI is running but no information is actually displayed.
    Monday, October 01, 2007 3:01 AM
  • DITTO -- on all counts. 

    This appeared to happen after I started using AOL IM 5.9.  This program actually killed a bunch of other things on my system as well, but I was able to repair all of the other symptoms, except this one, after uninstalling this program.

    HELP, Microsoft!!!
    Wednesday, October 03, 2007 4:09 AM
  • Since I posted this I've done more searching and didn't really find a solution.. I did find a tool microsoft has called the WMI Diagnosis Utility, which told me a lot about what's wrong with WMI on my machine (lots of access denied errors) but wouldn't tell me how i'm supposed to fix it (it had some things I was able to fix in the report, but the underlying problem is still here)

    Anyway, here's the link to the WMI Diagnosis Utility.  You may find something interesting by running it.  I can't seem to fix my issue though, I wish people from Microsoft actually read this damn forum because this is really shaking my confidence in running Windows Vista on my new Core2 Quad 2.4ghz.


    Wednesday, October 03, 2007 4:21 AM
  • I have a question, have either of you tried to restore your system to a date prior to the software changes? I would try it but i have installed so much software since this problem started with WMI and im not sure if it will mess my programs up.

    Wednesday, October 03, 2007 6:51 AM
  • I found one possible solution that might help one of you, go to start then type wmimgmt.msc  into the search box then run the program once its found.  Click on MORE ACTIONS under ACTIONS. click it then go to properties and to restore. Let me know if this helps at it, it didnt for me but you seem to have different issues causing your WMI to fail.

    Wednesday, October 03, 2007 7:06 AM
  •  

    If that doesn't work, I found a solution(sorry bout all the posts) that worked for me:

     

    1. At the command line, type net stop winmgmt. You may get a warning that other services need to be stopped as well; type Y and continue.
    2. Open Explorer and go to the folder called %SystemRoot%\System32\WBEM\Repository.
    3. Delete that folder and everything in it.
    4. Reboot the system normally.
    5. On the next login, open a command prompt and type the following commands in this order:
    winmgmt /clearadap
    winmgmt /kill
    winmgmt /unregserver
    winmgmt /regserver
    winmgmt /resyncperf


     

    "This procedure will force the WINMGMT service to re-register itself as well, although, if WMI is damaged, re-registering can be a problem. If this approach does not work, an in-place upgrade (i.e., a reinstall) might be required. "

     

    The first 4 of the five commands wouldn't work, so i typed the last one in and BAM! Now i can see the results of my overclocking and well as see all my systems info again.

     

     

    Credit for this fix goes to: http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1160143,00.html 

    "Serdar Yegulalp, Contributor"

     

    I hope this helps.

     

    Wednesday, October 03, 2007 7:25 AM
  • I tried a system restore, but: 1) I'm not sure that it was far enough back since for some reason Vista, or at least my system, only keeps 3 restore points, so I couldn't go back that far; and 2) after I did the restore, it said that there some errors during the process, which I believe I have read to be another symptom of this same problem.

    Also, the winmgmt /clearadap, winmgmt /kill, etc. commands don't run on my system.  Are those XP commands?  I have been using winmgmt /resetrepository; is that the equivalent?

    Thanks.
    Thursday, October 04, 2007 12:10 AM
  • Thanks for the info.  I downloaded and ran the WMIDiag tool you refer to and it does report some interesting results.  However, some of the suggested fixes are easy to follow, i.e. adding the "SYSTEM" account to 'Impersonate Client after authentication' Local Policy, but the other suggestions are vague and esoteric. 

    I'm not sure of your level of expertise, but do you have any advice for me after looking at a portion of the log file which was created with this tool below:


    24346 15:26:39 (0) ** 33 error(s) 0x80070005 - (WBEM_UNKNOWN) This error code is external to WMI.
    24347 15:26:39 (0) ** => This error is not a WMI error. It is typically due to:
    24348 15:26:39 (0) **    - The DCOM security modifications.
    24349 15:26:39 (0) **      => Ensure that DCOM security configuration settings are not modified.
    24350 15:26:39 (0) **    - The user running WMIDiag has not enough privileges or rights to issue requests
    24351 15:26:39 (0) **      against software components exposing information through WMI.
    24352 15:26:39 (0) **      => Ensure that no third party applications installing additional WMI providers have
    24353 15:26:39 (0) **         specific security requirements (i.e. group membership, privileges, etc ...)
    24354 15:26:39 (0) **    - The 'Impersonate Client after authentication' Local Policy is disabled or the
    24355 15:26:39 (0) **      'SERVICE' account has been removed from that Local Policy.
    24356 15:26:39 (0) **      => You must add the 'SERVICE' account to the 'Impersonate Client after authentication'
    24357 15:26:39 (0) **         Local Policy in the 'Local Policies/User Right Assignments' MMC snap-in (GPEDIT.MSC).
    24358 15:26:39 (0) **         By default, this Local Policy includes the 'SERVICE' account.
    24359 15:26:39 (0) **
    24360 15:26:39 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
    24361 15:26:39 (0) **    with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x0005)
    24362 15:26:39 (0) **    converted in decimal (5).
    24363 15:26:39 (0) **    - NET HELPMSG 5


    THANKS!
    Thursday, October 04, 2007 12:16 AM
  •  rippedrob420 wrote:

     

    If that doesn't work, I found a solution(sorry bout all the posts) that worked for me:

     

    1. At the command line, type net stop winmgmt. You may get a warning that other services need to be stopped as well; type Y and continue.
    2. Open Explorer and go to the folder called %SystemRoot%\System32\WBEM\Repository.
    3. Delete that folder and everything in it.
    4. Reboot the system normally.
    5. On the next login, open a command prompt and type the following commands in this order:
    winmgmt /clearadap
    winmgmt /kill
    winmgmt /unregserver
    winmgmt /regserver
    winmgmt /resyncperf


     

    "This procedure will force the WINMGMT service to re-register itself as well, although, if WMI is damaged, re-registering can be a problem. If this approach does not work, an in-place upgrade (i.e., a reinstall) might be required. "

     

    The first 4 of the five commands wouldn't work, so i typed the last one in and BAM! Now i can see the results of my overclocking and well as see all my systems info again.

     

     

    Credit for this fix goes to: http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1160143,00.html 

    "Serdar Yegulalp, Contributor"

     

    I hope this helps.

     



    The first 4 items on #5 don't even work on the vista version of WMI.  The rest of these tips don't solve this problem.
    Thursday, October 04, 2007 12:18 AM
  •  735 wrote:
    Thanks for the info.  I downloaded and ran the WMIDiag tool you refer to and it does report some interesting results.  However, some of the suggested fixes are easy to follow, i.e. adding the "SYSTEM" account to 'Impersonate Client after authentication' Local Policy, but the other suggestions are vague and esoteric. 

    I'm not sure of your level of expertise, but do you have any advice for me after looking at a portion of the log file which was created with this tool below:


    24346 15:26:39 (0) ** 33 error(s) 0x80070005 - (WBEM_UNKNOWN) This error code is external to WMI.
    24347 15:26:39 (0) ** => This error is not a WMI error. It is typically due to:
    24348 15:26:39 (0) **    - The DCOM security modifications.
    24349 15:26:39 (0) **      => Ensure that DCOM security configuration settings are not modified.
    24350 15:26:39 (0) **    - The user running WMIDiag has not enough privileges or rights to issue requests
    24351 15:26:39 (0) **      against software components exposing information through WMI.
    24352 15:26:39 (0) **      => Ensure that no third party applications installing additional WMI providers have
    24353 15:26:39 (0) **         specific security requirements (i.e. group membership, privileges, etc ...)
    24354 15:26:39 (0) **    - The 'Impersonate Client after authentication' Local Policy is disabled or the
    24355 15:26:39 (0) **      'SERVICE' account has been removed from that Local Policy.
    24356 15:26:39 (0) **      => You must add the 'SERVICE' account to the 'Impersonate Client after authentication'
    24357 15:26:39 (0) **         Local Policy in the 'Local Policies/User Right Assignments' MMC snap-in (GPEDIT.MSC).
    24358 15:26:39 (0) **         By default, this Local Policy includes the 'SERVICE' account.
    24359 15:26:39 (0) **
    24360 15:26:39 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
    24361 15:26:39 (0) **    with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x0005)
    24362 15:26:39 (0) **    converted in decimal (5).
    24363 15:26:39 (0) **    - NET HELPMSG 5


    THANKS!


    I'm no expert on the tool itself, that's why I was asking for help.  My errors are very consistent to the ones you have though, lots of "access denied" errors (0x8007005) which it claims have nothing to do with WMI... yet WMI continues to be broken.

    There's gotta be something that caused this for all of us.
    Thursday, October 04, 2007 12:20 AM
  •  

    i understand that the first four dont work on vista, thats why i said "The first 4 of the five commands wouldn't work"..so i skipped them and typed the last one(winmgmt /resyncperf) in after completing steps 1-4 and my system info showed up again.
    Thursday, October 04, 2007 3:20 AM
  •  rippedrob420 wrote:

     

    i understand that the first four dont work on vista, thats why i said "The first 4 of the five commands wouldn't work"..so i skipped them and typed the last one(winmgmt /resyncperf) in after completing steps 1-4 and my system info showed up again.


    You most likely don't have the same underlying issue that we're dealing with, then.
    Thursday, October 04, 2007 3:31 AM
  •  

    Has anyone had any luck fixing this? I am having this same issue. I am seriously considering a full reinstall but I would prefer not to go to that extent.
    Saturday, October 06, 2007 4:54 PM
  •  

    I am also experiences these error can anyone from MS please help?
    Tuesday, October 16, 2007 3:17 PM
  • I have this same issue! What gives?

    Tuesday, October 23, 2007 7:06 AM
  •  rippedrob420 wrote:

     

    If that doesn't work, I found a solution(sorry bout all the posts) that worked for me:

     

    1. At the command line, type net stop winmgmt. You may get a warning that other services need to be stopped as well; type Y and continue.
    2. Open Explorer and go to the folder called %SystemRoot%\System32\WBEM\Repository.
    3. Delete that folder and everything in it.
    4. Reboot the system normally.
    5. On the next login, open a command prompt and type the following command:
    winmgmt /resyncperf


     

    "This procedure will force the WINMGMT service to re-register itself as well, although, if WMI is damaged, re-registering can be a problem. If this approach does not work, an in-place upgrade (i.e., a reinstall) might be required. "

     

    The first 4 of the five commands wouldn't work, so i typed the last one in and BAM! Now i can see the results of my overclocking and well as see all my systems info again.

     

     

    Credit for this fix goes to: http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1160143,00.html 

    "Serdar Yegulalp, Contributor"

     

    I hope this helps.

     




    this worked no problem for me, just give it a try and it will probably help.
    Tuesday, October 23, 2007 7:15 AM
  • I resolved the Processor Information "not available" by adding the NETWORK SERVICE account to the Administrators group.  Howerver, I still get the following errors from WMIDiag:

     

    33429 16:47:45 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 16 ERROR(S)!
    33430 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Cache', 0x80004002 - No such interface supported.
    33431 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33432 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Memory', 0x80004002 - No such interface supported.
    33433 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33434 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Objects', 0x80004002 - No such interface supported.
    33435 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33436 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_PagingFile', 0x80004002 - No such interface supported.
    33437 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33438 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Processor', 0x80004002 - No such interface supported.
    33439 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33440 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_System', 0x80004002 - No such interface supported.
    33441 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33442 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Process', 0x80004002 - No such interface supported.
    33443 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33444 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Thread', 0x80004002 - No such interface supported.
    33445 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33446 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMP', 0x80004002 - No such interface supported.
    33447 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33448 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMPv6', 0x80004002 - No such interface supported.
    33449 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33450 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv4', 0x80004002 - No such interface supported.
    33451 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33452 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv6', 0x80004002 - No such interface supported.
    33453 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33454 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv4', 0x80004002 - No such interface supported.
    33455 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33456 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv6', 0x80004002 - No such interface supported.
    33457 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33458 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv4', 0x80004002 - No such interface supported.
    33459 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33460 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv6', 0x80004002 - No such interface supported.
    33461 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33462 16:47:45 (0) **
    33463 16:47:45 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    33464 16:47:45 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    33465 16:47:45 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    33466 16:47:45 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    33467 16:47:45 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    33468 16:47:45 (0) ** WMI static instances retrieved: ..................................................................................... 1646.
    33469 16:47:45 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    33470 16:47:45 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    33471 16:47:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    33472 16:47:45 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    33473 16:47:45 (0) **   DCOM: ............................................................................................................. 0.
    33474 16:47:45 (0) **   WINMGMT: .......................................................................................................... 0.
    33475 16:47:45 (0) **   WMIADAPTER: ....................................................................................................... 0.
    33476 16:47:45 (0) **
    33477 16:47:45 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    33478 16:47:45 (0) **   DCOM: ............................................................................................................. 0.
    33479 16:47:45 (0) **   WINMGMT: .......................................................................................................... 0.
    33480 16:47:45 (0) **   WMIADAPTER: ....................................................................................................... 0.
    33481 16:47:45 (0) **
    33482 16:47:45 (0) ** 16 error(s) 0x80004002 - (WBEM_UNKNOWN) This error code is external to WMI.
    33483 16:47:45 (0) ** => This error is not a WMI error. It is a DCOM error due to the following reasons:
    33484 16:47:45 (0) **    - An application has changed the COM/DCOM settings of OLE32.DLL and/or OLEAUT32.DLL.
    33485 16:47:45 (0) **    - The registry settings of COM/DCOM has been damage or wrongly modified.
    33486 16:47:45 (0) ** => To correct this situation, you must re-register the original COM/DCOM DLLs with REGSVR32.EXE
    33487 16:47:45 (0) **    i.e. 'REGSVR32.EXE OLE32.DLL'
    33488 16:47:45 (0) **    i.e. 'REGSVR32.EXE OLEAUT32.DLL'

     

    The following also return errors:

    Running "REGSVR32.EXE OLE32.DLL"

    SQL Server Configuration Manager

    SQL Server Reporting Services

     

    I have several posts on the various MSDN forums on this, but no-one from Microsoft is forthcoming.

    Tuesday, October 23, 2007 7:21 AM
  • microsoft just won't care until its affecting at least a few hundred people....so if we make a few hundred user accounts and complain........
    Tuesday, October 23, 2007 7:24 AM
  • haha, i like your idea about creating a few hundred accounts; even though it maybe a small issue, it's yet really a big problem if something like that doesn't work.

     

    Thursday, October 25, 2007 7:05 PM
  • Due to the none existance support from Microsoft on this issue, I shall be removing Vista from my Laptop and returning to XP.  Once I can free up two days to perform this.

    Friday, October 26, 2007 8:13 AM
  • try this

     

    c:\>net localgroup administrators NetworkService /ADD

     

    I got this from Ivan Brugiolo's guide - credit goes to him

     

    had issues with network and sharing center not coming up at all "server execution failed" and had to fix that by adding administrators to localservice so i figured it was a permissions issue

     

    as soon as i typed this in cmd prompt and started wmi my stuff came right up

     

     

    Sunday, October 28, 2007 12:18 PM
  •  SlayerOFP wrote:

    try this

     

    c:\>net localgroup administrators NetworkService /ADD

     

    I got this from Ivan Brugiolo's guide - credit goes to him

     

    had issues with network and sharing center not coming up at all "server execution failed" and had to fix that by adding administrators to localservice so i figured it was a permissions issue

     

    as soon as i typed this in cmd prompt and started wmi my stuff came right up

     

     

     

    Wow, it took weeks.. but this finally solved my problem!

     

    Who knows why, but it works now... awesome!

    Sunday, October 28, 2007 3:52 PM
  • Step 1 click on start icon in search type "services"
    Then run this application

    Step 2 find "Windows management instrumentation"
    Right click and select stop, dont close this application at the moment

    Step 3 locate "repository folder" in C:\windows\system32\wbem\repository
    Then delete folder...........(backup if you wish but after reboot vista will recreate folder and files anyway)

    Step 4 after delete open "services" again and restart "Windows management instumentation"

    Step 5 Reboot and as if by magic all is back to normal.
    • Proposed as answer by cowboy1618 Monday, November 02, 2009 5:21 PM
    Sunday, November 04, 2007 11:39 AM
  •  PaulGardner wrote:
    Step 1 click on start icon in search type "services"
    Then run this application

    Step 2 find "Windows management instrumentation"
    Right click and select stop, dont close this application at the moment

    Step 3 locate "repository folder" in C:\windows\system32\wbem\repository
    Then delete folder...........(backup if you wish but after reboot vista will recreate folder and files anyway)

    Step 4 after delete open "services" again and restart "Windows management instumentation"

    Step 5 Reboot and as if by magic all is back to normal.


    please read the thread before posting old solutions that don't fix the problem.  the solution was already found.
    Sunday, November 04, 2007 3:39 PM
  • The solution has not been found to my post.

    Monday, November 05, 2007 8:50 AM
  • Ok i had this problem tried all the fixes listed in previous replies and still came up with nothing.. so i decided to try something and it worked! Its very simple..I went to System Restore and restored to the earliest time available..(the date i bought my machine) which intern rolled back all the updates and everything I had installed on my laptop. (that was the down side) however after the restore my processor and memory is finally showing! I hope this helps you guys. It worked for me!

    Good luck!


    Tuesday, November 06, 2007 5:08 PM
  • So far I've tried all the fixes and nothing there helped me. I finally tried resetting the ownership of the windows directory & sub folders, then resetting the security on the windows directory & sub folders making sure system and administrators had full access to everything. Gave it a reboot and my processor and memory show up now. Still having an issue where my network icon and networking panel don't show any adapters even though it's working fine.
    Wednesday, November 07, 2007 2:46 AM
  • I'm going back to XP.

    Wednesday, November 07, 2007 9:42 AM
  • Hey I had the same problems with the 'Network center problem - w/ red X in the tray'
    and the  processor and ram in the system information as Not available. It seems that
    Aol Instant Messenger AIM caused these problems for me.
    Don't go jumping the gun and blaming microsoft and vista.
     
    SERVER EXECUTION FAILED
    SOLUTION::::
          1) Right click on Computer
          2) Click Local Users and Groups
          3) Click on Groups (or double click it in right pane)
          4) Double click on Administrators
          5) Window pops up (Administrator Properties):
              A) Click [Add...]
              B) Window pops up (Select Users):
                   i) Click [Advanced...]
                   ii) Window pops up (Select Users):
                          a) Click [Find Now]
                          b) Scroll down list select LOCAL SERVICE
                          c) Click [OK]
                  iii) Click [OK] 
             C) Click [Apply]   
     
    OR
     
    cmd prompt:
    Code Block
    Net localgroup Administrators LocalService /add

     

    reboot. Smile

     
    source: multiple places...link below too.
     
    PROCESSOR UNAVAILABLE:
    RAM UNAVAILABLE:
    WMI not WORKING:
    SOLUTION:::

     

    cmd prompt:

    Code Block
    Net localgroup Administrators Service /add

     

    reboot. Smile

     

    solution found at

    http://forums.microsoft.com/technet/showpost.aspx?postid=1185469&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=13

     

    poster iskh

    • Proposed as answer by handyandy27 Monday, October 26, 2009 9:38 PM
    Friday, November 09, 2007 7:34 AM
  • This is not resolving some of the other WMI problems on my Lap Top.  WMIDaig, returns the following:

     

    33429 16:47:45 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 16 ERROR(S)!
    33430 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Cache', 0x80004002 - No such interface supported.
    33431 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33432 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Memory', 0x80004002 - No such interface supported.
    33433 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33434 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Objects', 0x80004002 - No such interface supported.
    33435 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33436 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_PagingFile', 0x80004002 - No such interface supported.
    33437 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33438 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Processor', 0x80004002 - No such interface supported.
    33439 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33440 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_System', 0x80004002 - No such interface supported.
    33441 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33442 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Process', 0x80004002 - No such interface supported.
    33443 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33444 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Thread', 0x80004002 - No such interface supported.
    33445 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33446 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMP', 0x80004002 - No such interface supported.
    33447 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33448 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMPv6', 0x80004002 - No such interface supported.
    33449 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33450 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv4', 0x80004002 - No such interface supported.
    33451 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33452 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv6', 0x80004002 - No such interface supported.
    33453 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33454 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv4', 0x80004002 - No such interface supported.
    33455 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33456 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv6', 0x80004002 - No such interface supported.
    33457 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33458 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv4', 0x80004002 - No such interface supported.
    33459 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33460 16:47:45 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv6', 0x80004002 - No such interface supported.
    33461 16:47:45 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33462 16:47:45 (0) **
    33463 16:47:45 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    33464 16:47:45 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    33465 16:47:45 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    33466 16:47:45 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    33467 16:47:45 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    33468 16:47:45 (0) ** WMI static instances retrieved: ..................................................................................... 1646.
    33469 16:47:45 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    33470 16:47:45 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    33471 16:47:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    33472 16:47:45 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    33473 16:47:45 (0) **   DCOM: ............................................................................................................. 0.
    33474 16:47:45 (0) **   WINMGMT: .......................................................................................................... 0.
    33475 16:47:45 (0) **   WMIADAPTER: ....................................................................................................... 0.
    33476 16:47:45 (0) **
    33477 16:47:45 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    33478 16:47:45 (0) **   DCOM: ............................................................................................................. 0.
    33479 16:47:45 (0) **   WINMGMT: .......................................................................................................... 0.
    33480 16:47:45 (0) **   WMIADAPTER: ....................................................................................................... 0.
    33481 16:47:45 (0) **
    33482 16:47:45 (0) ** 16 error(s) 0x80004002 - (WBEM_UNKNOWN) This error code is external to WMI.
    33483 16:47:45 (0) ** => This error is not a WMI error. It is a DCOM error due to the following reasons:
    33484 16:47:45 (0) **    - An application has changed the COM/DCOM settings of OLE32.DLL and/or OLEAUT32.DLL.
    33485 16:47:45 (0) **    - The registry settings of COM/DCOM has been damage or wrongly modified.
    33486 16:47:45 (0) ** => To correct this situation, you must re-register the original COM/DCOM DLLs with REGSVR32.EXE
    33487 16:47:45 (0) **    i.e. 'REGSVR32.EXE OLE32.DLL'
    33488 16:47:45 (0) **    i.e. 'REGSVR32.EXE OLEAUT32.DLL'

     

    When I attempt to run "REGSVR32.EXE OLE32.DLL", I get the following error:

     

    "The module "OLE32.DLL" was loaded but the call to DllRegisterServer failed with error code 0x80070005."

     

    When I open SQL Server 2005 Configuration Manager I get this error:

     

    "Cannot connect to WMI provider.  You do not have the permissions or the server is unreachable.  Note that you can only manage SQL Server 2005 servers with SQL server Configuration Manager.

    Invalid class [0x80041010]"

     

    Yes these problems only manifested after I installed AIM, but where is Microsoft's support?

    Friday, November 09, 2007 10:04 AM
  • This worked for me.  Thanks!!!
    Friday, November 09, 2007 6:18 PM
  •  

    This worked for me, it's rediculous we have to fix things that shouldnt be broken.
    Thursday, November 22, 2007 10:26 AM
  • tjmehta..... thank you SOOO much. I've tried several methods on the 'nets to fix my issue and none of them worked. yours did. now the last issue (WMI/proc/ram blank) I had with my new lappie is taken care of. man, you rock! I appreciate you taking the time to post your collection of remedy steps.


    all the best,
    nick
    Friday, January 11, 2008 12:53 AM
  • Thank you SOOOO much slayer, that helped me lots Big Smile now i have a fully working vista install again woot!!!! thnx again
    Monday, March 17, 2008 8:49 AM
  • For Vista:

     

    Run the command prompt as Administrator.

     

    net localgroup administrators NetworkService /ADD

     

    That should be it.

     

    • Proposed as answer by handyandy27 Monday, October 26, 2009 9:38 PM
    Tuesday, April 01, 2008 1:19 AM
  • Thanks guys, worked for me. Good thing, this prob was driving me into an "else if" loop.
    Wednesday, April 16, 2008 4:12 PM
  • Excellent!!!  thankyou!!!SlayerOFP
    Wednesday, June 24, 2009 1:30 AM
  • I have this exact problem and none of the fixes above are working for me. Googling shows there are several people on the net for whom non of these fixes are working

    Moreover I think this is interfering with win 7 upgrade advisory which is reporting fine on devices and programs but is reporting that it cannot check the actual system! "We had a problem checking your system for compatability with Windows 7"

    As a further symptom. I am also unable to create detales page from performance informaiton and tools. "view and print details" returns box "could not create details page."
    Device manager Shows all four cores correct CPU (q6600).

    I cannot isolate when this occured. I do recall that I certainly had processor and ram showing regularly.

    Also if I run msinfo32

    I get:
    "Can't Collect Information Cannot access the Windows Management Instrumentation software. Windows
    Management files may be moved or missing."
    Monday, January 25, 2010 10:54 PM
  • It worked!  You are an absolute genius!  Thank you!  Thank you!  Thank you!  My System Rating, Processor, and Memory (RAM) now show up.  Sticky this for every Vista user to follow, if their 'System' info doesn't show up in 'View basic information about your computer'.
    Sunday, January 31, 2010 1:47 AM
  • SlayerOFP's method worked for me! Put that command in the command prompt- went to services-> right click WMI - click Restart-> go to system and WHAM-O!! Every thing shows up.

    thanks!

    Thursday, April 29, 2010 12:12 AM
  • Okay, now I see that that the other fix worked for many people, but in some rare case, the WMI becomes severely corrupted and this is how you fix it:

    Instructions

            1

            Press the Windows key. Type "cmd" in the search box and press "Enter." This will launch the Command Prompt.
            2

            Type "net stop winmgmt" at the prompt and press "Enter." Minimize the Command Prompt.

           
            3

            Press the Windows key and click "Computer." Navigate to the following folder path:

            C:\Windows\system32\wbem directory

            Delete the wbem directory.
            4

            Go back to the Command Prompt. Type the following commands at the prompt, one at time, and press "Enter:"

            net start winmgmt

            cd /d %windir%\system32\wbem

            for %i in (*.dll) do RegSvr32 -s %i

            for %i in (*.exe) do %i /RegServer


    I hope I helped!!


    Friday, March 16, 2012 3:06 PM