1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

System Information - "Can't Collect Information"

Discussion in 'Windows Vista' started by microsvc, Feb 9, 2008.

  1. microsvc

    microsvc Guest

    In my System Information screen, theres a message reading: "Can't Collect
    Information". cannot access the windows management Instrumentation Software.
    Windows management files may be moved or missing.

    Also as a result of this, the Control Panel/System window is missing the
    Rating, Processor and memory information. Suggestions?
     
  2. gerryf

    gerryf Guest

    This can result from the %SystemRoot%System32WbemRepository folder being
    corrupt.

    Right click My Computer, and then click Manage.

    Under “Services and Applications”, right click Services, and then find
    Windows Management Instrumentation service. Press the STOP link

    Now, Delete all of the files that are INSIDE the
    %SystemRoot%System32WbemRepository folder. (usually
    c:\windows\system32\wbemrespository (do not delete the folder

    Restart the computer. The files are recreated when the computer restarts.

    Try again

    "microsvc" <microsvc@discussions.microsoft.com> wrote in message
    news:CF92243A-54D8-4ED0-A209-E247E1114648@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > In my System Information screen, theres a message reading: "Can't Collect
    > Information". cannot access the windows management Instrumentation
    > Software.
    > Windows management files may be moved or missing.
    >
    > Also as a result of this, the Control Panel/System window is missing the
    > Rating, Processor and memory information. Suggestions? <!--colorc--><!--/colorc-->
     
  3. microsvc

    microsvc Guest

  4. microsvc

    microsvc Guest

    Gerry, I followed your steps, and deleted those files, rebooted, yet the
    problem hasnt been resolved.

    "gerryf" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > This can result from the %SystemRoot%System32WbemRepository folder being
    > corrupt.
    >
    > Right click My Computer, and then click Manage.
    >
    > Under “Services and Applications”, right click Services, and then find
    > Windows Management Instrumentation service. Press the STOP link
    >
    > Now, Delete all of the files that are INSIDE the
    > %SystemRoot%System32WbemRepository folder. (usually
    > c:windowssystem32wbemrespository (do not delete the folder
    >
    > Restart the computer. The files are recreated when the computer restarts.
    >
    > Try again
    >
    > "microsvc" <microsvc@discussions.microsoft.com> wrote in message
    > news:CF92243A-54D8-4ED0-A209-E247E1114648@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    > > In my System Information screen, theres a message reading: "Can't Collect
    > > Information". cannot access the windows management Instrumentation
    > > Software.
    > > Windows management files may be moved or missing.
    > >
    > > Also as a result of this, the Control Panel/System window is missing the
    > > Rating, Processor and memory information. Suggestions? <!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
  5. gerryf

    gerryf Guest

    Reading Mark's post above

    In addition to
    Windows Management Instrumentation

    Are
    Event Log
    Remote Procedure Call (RPC)
    also started?

    If not, start them and try again


    "microsvc" <microsvc@discussions.microsoft.com> wrote in message
    news:DD1C4991-B34A-40EB-AFBC-B4C44AD921DA@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Gerry, I followed your steps, and deleted those files, rebooted, yet the
    > problem hasnt been resolved.
    >
    > "gerryf" wrote:
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    >> This can result from the %SystemRoot%System32WbemRepository folder being
    >> corrupt.
    >>
    >> Right click My Computer, and then click Manage.
    >>
    >> Under “Services and Applications”, right click Services, and then find
    >> Windows Management Instrumentation service. Press the STOP link
    >>
    >> Now, Delete all of the files that are INSIDE the
    >> %SystemRoot%System32WbemRepository folder. (usually
    >> c:windowssystem32wbemrespository (do not delete the folder
    >>
    >> Restart the computer. The files are recreated when the computer restarts.
    >>
    >> Try again
    >>
    >> "microsvc" <microsvc@discussions.microsoft.com> wrote in message
    >> news:CF92243A-54D8-4ED0-A209-E247E1114648@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >> > In my System Information screen, theres a message reading: "Can't
    >> > Collect
    >> > Information". cannot access the windows management Instrumentation
    >> > Software.
    >> > Windows management files may be moved or missing.
    >> >
    >> > Also as a result of this, the Control Panel/System window is missing
    >> > the
    >> > Rating, Processor and memory information. Suggestions?<!--colorc--><!--/colorc-->
    >> <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
     
  6. microsvc

    microsvc Guest

    RPC is started. Is there a service called "Event Log"? If so, its not there.

    "gerryf" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Reading Mark's post above
    >
    > In addition to
    > Windows Management Instrumentation
    >
    > Are
    > Event Log
    > Remote Procedure Call (RPC)
    > also started?
    >
    > If not, start them and try again
    >
    >
    > "microsvc" <microsvc@discussions.microsoft.com> wrote in message
    > news:DD1C4991-B34A-40EB-AFBC-B4C44AD921DA@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    > > Gerry, I followed your steps, and deleted those files, rebooted, yet the
    > > problem hasnt been resolved.
    > >
    > > "gerryf" wrote:
    > ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > >> This can result from the %SystemRoot%System32WbemRepository folder being
    > >> corrupt.
    > >>
    > >> Right click My Computer, and then click Manage.
    > >>
    > >> Under “Services and Applications”, right click Services, and then find
    > >> Windows Management Instrumentation service. Press the STOP link
    > >>
    > >> Now, Delete all of the files that are INSIDE the
    > >> %SystemRoot%System32WbemRepository folder. (usually
    > >> c:windowssystem32wbemrespository (do not delete the folder
    > >>
    > >> Restart the computer. The files are recreated when the computer restarts.
    > >>
    > >> Try again
    > >>
    > >> "microsvc" <microsvc@discussions.microsoft.com> wrote in message
    > >> news:CF92243A-54D8-4ED0-A209-E247E1114648@microsoft.com...
    > >> > In my System Information screen, theres a message reading: "Can't
    > >> > Collect
    > >> > Information". cannot access the windows management Instrumentation
    > >> > Software.
    > >> > Windows management files may be moved or missing.
    > >> >
    > >> > Also as a result of this, the Control Panel/System window is missing
    > >> > the
    > >> > Rating, Processor and memory information. Suggestions?
    > >> <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
     
  7. microsvc

    microsvc Guest

    Nobody has any explanation as to why this anomoly is happening, and what I
    may do to fix it for good?

    I'd hate this to be another broken part of Vista I'll have to "Live with".

    "microsvc" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > In my System Information screen, theres a message reading: "Can't Collect
    > Information". cannot access the windows management Instrumentation Software.
    > Windows management files may be moved or missing.
    >
    > Also as a result of this, the Control Panel/System window is missing the
    > Rating, Processor and memory information. Suggestions? <!--colorc--><!--/colorc-->
     
  8. stevejum

    stevejum Guest

    Don't feel alone ... when I try to look at my system information
    (msinfo32.exe), I get the same emtpy window with the message "Can't
    Collect Information" "Cannot access the Windows Management
    Instrumentation software. Windows Management files may be moved or
    missing."

    And of course, none of the above suggestions have had any affect ... my
    WMI and RPC services are running, and I emptied the "wbemrespository"
    directory and rebooted.

    I've got 6 weeks into trying to establish a stable copy of Vista, and
    I'm on my eighth reload of the OS and my application suites. I wish it
    would stop slowly eating itself.


    --
    stevejum
     
  9. stevejum

    stevejum Guest

    More data, my event log has about 50 or more WMI events ... all right in
    a row ... half of which are hard errors (event ID 24 in red) and half of
    which are warnings (event ID 63 in yellow).

    The first entry (informational), Event ID 5617 says:

    - "Windows Management Instrumentation Service subsystems initialized
    successfully"

    And then is followed by around 50 WMI errors and warnings as noted
    below.

    The 25 or so Event ID 24's are all similar, e.g.:

    - "Event provider $Core attempted to register query "select * from
    __InstanceOperationEvent" whose target class "__InstanceOperationEvent"
    in //./root namespace does not exist. The query will be ignored."

    - "Event provider $Core attempted to register query "select * from
    __SystemEvent" whose target class "__SystemEvent" in //./root/SECURITY
    namespace does not exist. The query will be ignored."

    - "Event provider $Core attempted to register query "select * from
    __TimerEvent" whose target class "__TimerEvent" in //./root/SECURITY
    namespace does not exist. The query will be ignored."

    Those errors are followed by about 25 Event ID 63's, which are all
    similar, e.g.:

    - "A provider, ActiveScriptEventConsumer, has been registered in the
    Windows Management Instrumentation namespace root\default to use the
    LocalSystem account. This account is privileged and the provider may
    cause a security violation if it does not correctly impersonate user
    requests."

    - "A provider, CommandLineEventConsumer, has been registered in the
    Windows Management Instrumentation namespace root\default to use the
    LocalSystem account. This account is privileged and the provider may
    cause a security violation if it does not correctly impersonate user
    requests."

    SOooooo ... does anyone know who this mysterious event provider "$Core"
    is .... ?


    --
    stevejum
     
  10. GerryF.....are you still with us....???

    Here is one thing you can try to get your WMI back up and running:

    Open a command prompt...(START - RUN - type CMD in the "Open:" box)

    At the prompt...copy/paste (or type) each of these commands in THIS
    order:

    winmgmt /clearadap
    winmgmt /kill
    winmgmt /unregserver
    winmgmt /regserver
    winmgmt /resyncperf

    Hit ENTER when necessary...(the copy/paste method should enter the
    commands automatically).


    Here is what each switch does:

    The "clearadap" switch clears prior WMI /resyncperf information
    from the registry.
    The "kill" switch causes WINMGMT to stop running copies.
    The "unregserver" switch removes the registry entries.
    The "regserver" switch invokes self registration.
    The "resyncperf" switch registers the system's performance
    libraries with WMI.





    I can also help you return EventLog to your services list.


    First...ensure that the EventLog service is running by attempting to
    start EventLog, like so:

    Open another command prompt and type NET START EVENTLOG at the
    prompt.
    If EventLog is already started...you will receive a message
    stating such.

    After making sure that the service is running, proceed to the next
    step:

    Check for the following key in your registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
    \Eventlog

    If the key IS found...it may be corrupt...in which case, it must
    be replaced using the method found below.
    If the key is not found...you need to get a copy of the key from
    another computer, and IMPORT if into your registry.

    If you don't have another computer from which to copy the key...I
    can email you a copy.
    The file, in text form, is simply too lengthy to post here.
    Please respond if you would like this file emailed to you.

    GOOD LUCK.....!!!! Let us know how things work out...!!!
     
  11. Chuck

    Chuck Guest

    Hi i know this post is a month old but i was wondering if you could email me
    a copy of the key. I'm having the same problem and have been going crazy
    trying to find a fix. This is the first post that i've seen that trys
    something different. my email address is cmccall45@verizon.net
    thanks.
    Chuck

    "Jme63SCH@aol.com" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > GerryF.....are you still with us....???
    >
    > Here is one thing you can try to get your WMI back up and running:
    >
    > Open a command prompt...(START - RUN - type CMD in the "Open:" box)
    >
    > At the prompt...copy/paste (or type) each of these commands in THIS
    > order:
    >
    > winmgmt /clearadap
    > winmgmt /kill
    > winmgmt /unregserver
    > winmgmt /regserver
    > winmgmt /resyncperf
    >
    > Hit ENTER when necessary...(the copy/paste method should enter the
    > commands automatically).
    >
    >
    > Here is what each switch does:
    >
    > The "clearadap" switch clears prior WMI /resyncperf information
    > from the registry.
    > The "kill" switch causes WINMGMT to stop running copies.
    > The "unregserver" switch removes the registry entries.
    > The "regserver" switch invokes self registration.
    > The "resyncperf" switch registers the system's performance
    > libraries with WMI.
    >
    >
    >
    >
    >
    > I can also help you return EventLog to your services list.
    >
    >
    > First...ensure that the EventLog service is running by attempting to
    > start EventLog, like so:
    >
    > Open another command prompt and type NET START EVENTLOG at the
    > prompt.
    > If EventLog is already started...you will receive a message
    > stating such.
    >
    > After making sure that the service is running, proceed to the next
    > step:
    >
    > Check for the following key in your registry:
    >
    > HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
    > Eventlog
    >
    > If the key IS found...it may be corrupt...in which case, it must
    > be replaced using the method found below.
    > If the key is not found...you need to get a copy of the key from
    > another computer, and IMPORT if into your registry.
    >
    > If you don't have another computer from which to copy the key...I
    > can email you a copy.
    > The file, in text form, is simply too lengthy to post here.
    > Please respond if you would like this file emailed to you.
    >
    > GOOD LUCK.....!!!! Let us know how things work out...!!!
    >
    >
    >
    >
    >
    >
    >
    > <!--colorc--><!--/colorc-->
     
  12. bmn

    bmn Guest

    The service is listed as "WINDOWS EVENT LOG". Not "EVENT LOG".


    --
    bmn
     
  13. Hey all, here's the solution to your "Unavailable Rating" and SysInfo
    problems

    Start --> Run

    CMD

    net localgroup administrators NetworkService /ADD

    Enter

    :)All fixed [​IMG]


    --
    CharBroiled20s
     
  14. steve1980

    steve1980 Guest

    Thanks CharBroiled20s, this worked for me [​IMG]


    --
    steve1980
    ------------------------------------------------------------------------
    steve1980's Profile:
    View this thread:


     
  15. tjones1966

    tjones1966 Guest

    THANKS SO MUCH!!!!!!

    Sorry for yelling but thats how I feal after chasing this for weeks.


    --
    tjones1966
    ------------------------------------------------------------------------
    tjones1966's Profile:
    View this thread:


     
  16. LOL @ tjones1966.

    It sucks to hunt for an answer & not find it - glad I could help!

    Have a good one!


    --
    CharBroiled20s

    DO I REALLY NEED TO SAY - DON'T TYPE THE QUOTATION MARKS? [​IMG]
     
  17. cakeluvr9

    cakeluvr9 Guest

    CharBroiled!!!!! How I love you! You were the ONLY person who fixed this
    problem for me. Thanks so much for knowing what to do. Now what I want
    to know, if you can tell me, What was causing this error, and why did
    that simple dos prompt fix it? It's not enough for me just to have my
    problem fixed! I need to know -why-...


    --
    cakeluvr9
     
  18. undisclosed

    undisclosed Guest

    I'm having the same problem done all the fixes found the key but default
    says that it has no value Is that the problem ? If so could some one
    email the new key or tell me how to fix it Ta


    --
    Silver
     
  19. John Galt

    John Galt Guest

    undisclosed wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >I'm having the same problem done all the fixes found the key but default
    >says that it has no value Is that the problem ? If so could some one
    >email the new key or tell me how to fix it Ta<!--colorc--><!--/colorc-->

    WTF are you talking about? Are you replying to a really old
    post/thread?

    Either quote what you are replying to (the same problem, all the
    fixes) or start a new thread so we will know what you're talking
    about.
     

Share This Page