locked
WMIDIAG report errors RRS feed

  • Question

  • Hello,

      I am trying to get MSINFO32 to run under VISTA Home premium.  When I start MSINFO32 i get the following:

     

    "Can't Collect Information" - Cannot access the Windows Management Insturmentation Software.  Windows Management files may be moved or missing.
     
     
    I ran the WMIdiag utility and it listed two errors.  I have no idea what these are or how to fix them.  Can someone help?
     
    Here is the diag report:
     
    v.1911 20:20:59 (0) ** WMIDiag v2.0 started on Saturday, March 22, 2008 at 20:20.
    .1912 20:20:59 (0) **
    .1913 20:20:59 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
    .1914 20:20:59 (0) **
    .1915 20:20:59 (0) ** This script is not supported under any Microsoft standard support program or service.
    .1916 20:20:59 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    .1917 20:20:59 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    .1918 20:20:59 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    .1919 20:20:59 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    .1920 20:20:59 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    .1921 20:20:59 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    .1922 20:20:59 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    .1923 20:20:59 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    .1924 20:20:59 (0) ** of the possibility of such damages.
    .1925 20:20:59 (0) **
    .1926 20:20:59 (0) **
    .1927 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1928 20:20:59 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    .1929 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1930 20:20:59 (0) **
    .1931 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1932 20:20:59 (0) ** Windows Vista - No service pack - 32-bit (6000) - User 'XPS710\GLENN' on computer 'XPS710'.
    .1933 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1934 20:20:59 (0) ** Environment: ........................................................................................................ OK..
    .1935 20:20:59 (0) ** There are no missing WMI system files: .............................................................................. OK.
    .1936 20:20:59 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    .1937 20:20:59 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    .1938 20:20:59 (0) ** BEFORE running WMIDiag:
    .1939 20:20:59 (0) ** The WMI repository has a size of: ................................................................................... 25 MB.
    .1940 20:20:59 (0) ** - Disk free space on 'C:': .......................................................................................... 143317 MB.
    .1941 20:20:59 (0) **   - INDEX.BTR,                     3186688 bytes,      10/7/2007 19:28:52
    .1942 20:20:59 (0) **   - MAPPING1.MAP,                  73632 bytes,        10/7/2007 19:22:45
    .1943 20:20:59 (0) **   - MAPPING2.MAP,                  73632 bytes,        10/7/2007 19:26:52
    .1944 20:20:59 (0) **   - OBJECTS.DATA,                  22544384 bytes,     10/7/2007 19:28:52
    .1945 20:20:59 (0) ** AFTER running WMIDiag:
    .1946 20:20:59 (0) ** The WMI repository has a size of: ................................................................................... 25 MB.
    .1947 20:20:59 (0) ** - Disk free space on 'C:': .......................................................................................... 143317 MB.
    .1948 20:20:59 (0) **   - INDEX.BTR,                     3186688 bytes,      10/7/2007 19:28:52
    .1949 20:20:59 (0) **   - MAPPING1.MAP,                  73632 bytes,        10/7/2007 19:22:45
    .1950 20:20:59 (0) **   - MAPPING2.MAP,                  73632 bytes,        10/7/2007 19:26:52
    .1951 20:20:59 (0) **   - OBJECTS.DATA,                  22544384 bytes,     10/7/2007 19:28:52
    .1952 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1953 20:20:59 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    .1954 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1955 20:20:59 (0) ** DCOM Status: ........................................................................................................ OK.
    .1956 20:20:59 (0) ** WMI registry setup: ................................................................................................. OK.
    .1957 20:20:59 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
    .1958 20:20:59 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
    .1959 20:20:59 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
    .1960 20:20:59 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    .1961 20:20:59 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    .1962 20:20:59 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    .1963 20:20:59 (0) **          this can prevent the service/application to work as expected.
    .1964 20:20:59 (0) **
    .1965 20:20:59 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    .1966 20:20:59 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    .1967 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1968 20:20:59 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    .1969 20:20:59 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    .1970 20:20:59 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    .1971 20:20:59 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    .1972 20:20:59 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    .1973 20:20:59 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    .1974 20:20:59 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    .1975 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1976 20:20:59 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
    .1977 20:20:59 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    .1978 20:20:59 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    .1979 20:20:59 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    .1980 20:20:59 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    .1981 20:20:59 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    .1982 20:20:59 (0) **
    .1983 20:20:59 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    .1984 20:20:59 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE' DOES NOT match corresponding expected trustee rights (Actual->Default)
    .1985 20:20:59 (0) **        - ACTUAL ACE:
    .1986 20:20:59 (0) **          ACEType:  &h0
    .1987 20:20:59 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    .1988 20:20:59 (0) **          ACEFlags: &h0
    .1989 20:20:59 (0) **          ACEMask:  &hB
    .1990 20:20:59 (0) **                    DCOM_RIGHT_EXECUTE
    .1991 20:20:59 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    .1992 20:20:59 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    .1993 20:20:59 (0) **        - EXPECTED ACE:
    .1994 20:20:59 (0) **          ACEType:  &h0
    .1995 20:20:59 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    .1996 20:20:59 (0) **          ACEFlags: &h0
    .1997 20:20:59 (0) **          ACEMask:  &h1F
    .1998 20:20:59 (0) **                    DCOM_RIGHT_EXECUTE
    .1999 20:20:59 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    .2000 20:20:59 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
    .2001 20:20:59 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    .2002 20:20:59 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
    .2003 20:20:59 (0) **
    .2004 20:20:59 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
    .2005 20:20:59 (0) **    This will cause some operations to fail!
    .2006 20:20:59 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    .2007 20:20:59 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    .2008 20:20:59 (0) **
    .2009 20:20:59 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    .2010 20:20:59 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
    .2011 20:20:59 (0) **        - ACTUAL ACE:
    .2012 20:20:59 (0) **          ACEType:  &h0
    .2013 20:20:59 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    .2014 20:20:59 (0) **          ACEFlags: &h0
    .2015 20:20:59 (0) **          ACEMask:  &hB
    .2016 20:20:59 (0) **                    DCOM_RIGHT_EXECUTE
    .2017 20:20:59 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    .2018 20:20:59 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    .2019 20:20:59 (0) **        - EXPECTED ACE:
    .2020 20:20:59 (0) **          ACEType:  &h0
    .2021 20:20:59 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    .2022 20:20:59 (0) **          ACEFlags: &h0
    .2023 20:20:59 (0) **          ACEMask:  &h1F
    .2024 20:20:59 (0) **                    DCOM_RIGHT_EXECUTE
    .2025 20:20:59 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    .2026 20:20:59 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
    .2027 20:20:59 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    .2028 20:20:59 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
    .2029 20:20:59 (0) **
    .2030 20:20:59 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
    .2031 20:20:59 (0) **    This will cause some operations to fail!
    .2032 20:20:59 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    .2033 20:20:59 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    .2034 20:20:59 (0) **
    .2035 20:20:59 (0) **
    .2036 20:20:59 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
    .2037 20:20:59 (0) ** DCOM security error(s) detected: .................................................................................... 2.
    .2038 20:20:59 (0) ** WMI security warning(s) detected: ................................................................................... 0.
    .2039 20:20:59 (0) ** WMI security error(s) detected: ..................................................................................... 0.
    .2040 20:20:59 (0) **
    .2041 20:20:59 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
    .2042 20:20:59 (0) ** Overall WMI security status: ........................................................................................ OK.
    .2043 20:20:59 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    .2044 20:20:59 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
    .2045 20:20:59 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    .2046 20:20:59 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
    .2047 20:20:59 (0) ** - Root, 0x80041021 - (WBEM_E_INVALID_SYNTAX) Query is syntactically invalid.
    .2048 20:20:59 (0) **
    .2049 20:20:59 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
    .2050 20:20:59 (0) ** - Root, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2051 20:20:59 (0) ** - Root, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2052 20:20:59 (0) ** - Root/subscription, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2053 20:20:59 (0) ** - Root/DEFAULT, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2054 20:20:59 (0) ** - Root/CIMV2, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2055 20:20:59 (0) ** - Root/CIMV2/Security, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2056 20:20:59 (0) ** - Root/CIMV2/Applications, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2057 20:20:59 (0) ** - Root/nap, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2058 20:20:59 (0) ** - Root/SECURITY, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2059 20:20:59 (0) ** - Root/WMI, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2060 20:20:59 (0) ** - Root/directory, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2061 20:20:59 (0) ** - Root/directory/LDAP, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2062 20:20:59 (0) ** - Root/SecurityCenter, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2063 20:20:59 (0) ** - Root/Microsoft, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2064 20:20:59 (0) ** - Root/Microsoft/HomeNet, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2065 20:20:59 (0) ** - Root/aspnet, 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct.
    .2066 20:20:59 (0) **
    .2067 20:20:59 (0) ** WMI GET operations: ................................................................................................. OK.
    .2068 20:20:59 (0) ** WMI MOF representations: ............................................................................................ OK.
    .2069 20:20:59 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    .2070 20:20:59 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    .2071 20:20:59 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    .2072 20:20:59 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    .2073 20:20:59 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    .2074 20:20:59 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    .2075 20:20:59 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    .2076 20:20:59 (0) ** WMI static instances retrieved: ..................................................................................... 0.
    .2077 20:20:59 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    .2078 20:20:59 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
    .2079 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2080 20:20:59 (0) **
    .2081 20:20:59 (0) ** 1 error(s) 0x80041021 - (WBEM_E_INVALID_SYNTAX) Query is syntactically invalid
    .2082 20:20:59 (0) **
    .2083 20:20:59 (0) ** 16 error(s) 0x80041008 - (WBEM_E_INVALID_PARAMETER) One of the parameters to the call is not correct
    .2084 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2085 20:20:59 (0) ** WMI Registry key setup: ............................................................................................. OK.
    .2086 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2087 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2088 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2089 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2090 20:20:59 (0) **
    .2091 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2092 20:20:59 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    .2093 20:20:59 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .2094 20:20:59 (0) **
    .2095 20:20:59 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\GLENN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0_VISTA.CLI.RTM.32_XPS710_2008.03.22_20.20.04.LOG' for details.
    .2096 20:20:59 (0) **
    .2097 20:20:59 (0) ** WMIDiag v2.0 ended on Saturday, March 22, 2008 at 20:20 (W:45 E:27 S:1).
    Sunday, March 23, 2008 2:03 AM

Answers

  • Hi Glenn,

     

    I have checked the files and noticed that the WMI namespace was corrupted. Please re-register WMI DLL files and re-compile WMI mof files to check if the issue can be resolved. Here are the detailed steps:

     

    1. Disable and stop the Windows Management Instrumentation service.

    2. Right-click Command Prompt and select Run as Administrator.

    3. In the Command Prompt, type cd %windir%\system32\wbem and press Enter.

    4. Type for /f %s in ('dir /b *.dll') do regsvr32 /s %s and press Enter to re-register WMI DLL files.

    5. After completed, type for /f %s in ('dir /b *.mof') do mofcomp %s and press Enter to re-compile WMI mof files.

    6. After that, type the command wmiprvse /regserver and press Enter.

    7. Start the Windows Management Instrumentation service and change the Startup Type back to Automatic.

     

    If the issue persists, you will have to perform an In-place Upgrade in Windows Vista to resolve the issue. Generally, In-place Upgrade will only replace the system file, but not affect your personal data. However, I highly recommend that you perform a full backup before performing In-place Upgrade. In addition, you need to reinstall Windows updates and device driver after performing In-place upgrade.

     

    Here are the detailed steps:

     

    1. Please temporarily uninstall the antivirus software on the system.

    2. Insert the Windows Vista DVD into the computer's DVD drive.

    3. Use one of the following procedures, as appropriate:

     

    • If Windows automatically detects the DVD, the Install now screen appears. Click Install now.

    • If Windows does not automatically detect the DVD, follow these steps:

     

    a. Click Start, click Run, type Drive:\setup.exe, and then click OK.

     

    Note Drive is the drive letter of the computer's DVD drive.

    b. Click Install now.

     

    4. When you reach the Which type of installation to you want? screen, click Upgrade to upgrade the current operating system to Windows Vista.

     

    Note: We may need to reactivate the system after the upgrade.

     

    Tuesday, April 8, 2008 2:14 AM
    Moderator

All replies

  • Help!! Anyone??!!??!!

     

    Tuesday, March 25, 2008 4:02 AM
  • Hi Ghamil,

     

    Please perform the following steps to troubleshoot the issue:

     

    1.    Log onto Windows Vista with an administrator account, click Start, type services.msc in the Start Search box and press Enter.

    2.    In the right pane of the Service console, locate and right-click Windows Management Instrumentation, and then select Stop to stop the service.

    3.    Start Windows Explorer, and then locate the %SystemRoot%\System32\Wbem\Repository folder.

    4.    Backup and delete all the files in the %SystemRoot%\System32\Wbem\Repository folder.

    5.    Restart the computer.

     

    The files that were deleted will be re-created when the computer restarts.

     

    Note: The Windows Management Instrumentation service starts automatically when you restart the computer.

     

    After that, open System Information and check the result.

     

    Hope it helps.

     

    Tuesday, March 25, 2008 9:22 AM
    Moderator
  • Hello and thanks for this information.  I performed these steps (I renamed the Repository folder) and re-booted.  The Repository folder was never re-created.  I have since renamed the original folder back.  Any ideas why it would not recreate the repository folder?

     

    Thanks

    Glenn

     

    Tuesday, March 25, 2008 11:16 PM
  • Hi Glenn,

     

    Based on my test, the Repository folder can be re-created automatically. I would like to confirm if the Windows Management Instrumentation service starts automatically after the reboot.

     

    Thursday, March 27, 2008 9:19 AM
    Moderator
  • Hello,

      Yes, the WMI service did start automatically after reboot.

     

    Glenn

     

    Thursday, March 27, 2008 10:22 PM
  • Hi Glenn,
     
    Please move the files in the folder rather than renaming the folder to check the result.

     

    Friday, March 28, 2008 9:24 AM
    Moderator
  • I "moved" the file to another folder leaving the "Repository" folder empty.  Re-booted and the directory is still empty.

     

    Saturday, March 29, 2008 6:29 AM
  • If I enter this command:   winmgmt /salvagerepository  I get the following error:

     

    C:\Users\Glenn>winmgmt /salvagerepository
    WMI repository verification failed
    Error code:  0x8004100A

    C:\Users\Glenn>

     

    I have no Idea how to fix this.

     

    Sunday, March 30, 2008 5:20 AM
  • Hi Glenn,

     

    From the WMIDIAG report, I noticed that Default DCOM security for 'My Computer' was modified. Please re-grant the Remote Launch and Remote Activation allow permission to  INTERACTIVE and SYSTEM.

     

    Meanwhile, I’ve listed the default security as below. Please check it:

     

    Default COM Security: (In Component Services window, expand Component Services>Computers, and right-click My Computer.)

    1.    Under Default Launch Permissions, make sure that at least INTERACTIVE, SYSTEM, and Administrators are set to Allow Launch.

    2.    Make sure that the Default Access Permissions lists only the following accounts:

    SELF, SYSTEM, Administrator.

     

    Default WMI DCOM Settings: (In Component Services window, expand Component Services>Computers>My Computer>DCOM Config, and right-click Windows Management and Instrumentation.)

    1.    Authentication Level                    Default

    2.    Launch Permissions                      Everyone

    3.    Access Permissions                      Default

     

    After that, please restart the system and check the result.

     

    If the issue persists, please run WMIDiag again, zip all the output files (including the report and log) and upload it to the following space:

     

    https://sftasia.one.microsoft.com/choosetransfer.aspx?key=41ee4a23-c2bb-45f4-aa31-6c1ec35c5c20

    Password: 5)Sf)H_#SgtR#uA

     

    Hope it helps.

     

    Wednesday, April 2, 2008 9:32 AM
    Moderator
  • Hello, and thanks for your help...Here is what I have found out:

     

    I did the re-grant for "Remote launch" and "Remote activation" to INTERACTIVE and SYSTEM.

     

    For the DCOM security:

     

    In component services window I did a right click on "My computer" and then went to the "COM Security" tab.

    Under "Launch and Activation Permissions" i clicked on "Edit Default". In the default group I show the following names:

     

    SYSTEM

    Administrators (XPS710\Administrators)

    INTERACTIVE

     

    All three have the "Allow" option checked for Local/Remote Launch/Activate

     

    In the "Access Permissions" area I clicked on "edit default" and I show the following group/users:

     

    SELF

    SYSTEM

    Glenn (XPS710\Glenn)

    Administrators (XPS710\Administrators)

     

    There was not an entry for "Adminstrator"

     

    SELF, Glenn and Administrators all have "Allow" checked for Local Access and Remote Access

    SYSTEM only had "Allow" checked for Local Access.  Nothing was checked for Remote Access.

     

     

    For the Default WMI DCOM settings:

    When I expanded DCOM config I got several warnings about CLSID's not being recorded under \\HKEY_CLASSES_ROOT\Appid.  It wanted a Yes/No reply to record them....I replied "No"  was this correct?

     

    After right clicking on Windows Management Insturmentation here are the values on the "General" tab"

     

    Application Name:  Windows Management Insturmentation

    Application ID: {8BC3F05E-D86B-11D0-A075-00C04FB68820}

    Application type: Local Service

    Authentication Level: Connect

    Service Name: winmgmt

     

    On the "Security" tab here are the values:

     

    Launch and Activation Permissions

    Customize

      Group or user name:

    EVERYONE

      "Allow" is checked for all permissions (Local/Remote Launch/Activation)

     

     

    Under "Access Permissions"

    Use Default

     

     

    Under "Configuration Permissions"

    Customize

      Group or user names:

    CREATOR OWNER     - has "allow" for special permissions.  other are not checked.

    SYSTEM                    - has "allow" for Full Control, Read and Special Permissions.

    Administrators (XPS710\Administrators)  - has "allow" for Full Control, Read and Special Permissions.

    Users (XPS710\Users)  - Has "allow" for Read and Special Permissions.  Nothing is checked for Full Control.

     

    I will upload the diag report and log as you requested. 

     

    Thanks

    Glenn

     

     

     

     

     

     

     

     

    Wednesday, April 2, 2008 11:26 PM
  •  

    The WMIDiag files have been uploaded under the file name of:  WMIfiles.zip

     

    Thanks

    Glenn

    Wednesday, April 2, 2008 11:30 PM
  • Hello Joson Zhou ... Just wondering if you have had a chance to look over the logs I uploaded?

     

    Glenn

    Sunday, April 6, 2008 7:25 PM
  • Hi Glenn,

     

    I have checked the files and noticed that the WMI namespace was corrupted. Please re-register WMI DLL files and re-compile WMI mof files to check if the issue can be resolved. Here are the detailed steps:

     

    1. Disable and stop the Windows Management Instrumentation service.

    2. Right-click Command Prompt and select Run as Administrator.

    3. In the Command Prompt, type cd %windir%\system32\wbem and press Enter.

    4. Type for /f %s in ('dir /b *.dll') do regsvr32 /s %s and press Enter to re-register WMI DLL files.

    5. After completed, type for /f %s in ('dir /b *.mof') do mofcomp %s and press Enter to re-compile WMI mof files.

    6. After that, type the command wmiprvse /regserver and press Enter.

    7. Start the Windows Management Instrumentation service and change the Startup Type back to Automatic.

     

    If the issue persists, you will have to perform an In-place Upgrade in Windows Vista to resolve the issue. Generally, In-place Upgrade will only replace the system file, but not affect your personal data. However, I highly recommend that you perform a full backup before performing In-place Upgrade. In addition, you need to reinstall Windows updates and device driver after performing In-place upgrade.

     

    Here are the detailed steps:

     

    1. Please temporarily uninstall the antivirus software on the system.

    2. Insert the Windows Vista DVD into the computer's DVD drive.

    3. Use one of the following procedures, as appropriate:

     

    • If Windows automatically detects the DVD, the Install now screen appears. Click Install now.

    • If Windows does not automatically detect the DVD, follow these steps:

     

    a. Click Start, click Run, type Drive:\setup.exe, and then click OK.

     

    Note Drive is the drive letter of the computer's DVD drive.

    b. Click Install now.

     

    4. When you reach the Which type of installation to you want? screen, click Upgrade to upgrade the current operating system to Windows Vista.

     

    Note: We may need to reactivate the system after the upgrade.

     

    Tuesday, April 8, 2008 2:14 AM
    Moderator
  • Hello Joson!!  I think I have some really good news.  I followed your instructions above and the MSINFO32 command is now working!!!  Thank you VERY MUCH!!

     

    I ran the WMIDiag command again and it is still reporting some errors and warnings.  I have uploaded the logs from the report using the upload link/password you provided earlier.  The file name is NewWMIfiles.zip

     

    Can you look at these logs and tell if there are still some things that need to be fixed?  It said in the report that some of the errors could possibly be fixed by running the WINMGMT.EXE /SYNCPERF command.  I thought I would get your advice before doing anything else.

     

     

    Thanks!

    Glenn

     

    Tuesday, April 8, 2008 11:53 PM
  • Hi Glenn,

     

    Glad to hear that.

     

    Regarding the new error, please perform the following steps for troubleshooting:

     

    1. Stop the Windows Management Instrumentation service.

    2. Open Command Prompt with elevated privilege, type wmimgmt /resyncperf and press Enter.

    3. After that, type wmiadap.exe /f and press Enter.

    4. Start the service and check the result.

     

    If the issue persists, please confirm if the file WMIPERFINST.MOF exists in the folder C:\WINDOWS\SYSTEM32\WBEM.

     

    Hope it helps.

     

     

     

    Thursday, April 10, 2008 9:29 AM
    Moderator
  • Hello Joson,

      I performed the commands as you said and then ran another WMIDiag.  There are still errors showing up in the report.  I also confirmed that file WMIPERFINST.MOF is in the WBEM directory.

     

    I have uploaded the WMIDiag logs under the filename of: April10WMIDiag.zip

     

    Any further help you can provide is appreciated!!!

     

     

    Glenn

     

    Friday, April 11, 2008 1:39 AM
  • Hello Joson,

      Just wondering if you had a chance to look at the last set of log files I uploaded?  Smile

     

    Glenn

     

    Thursday, April 17, 2008 4:27 AM
  • Joson, I am having the same problem with 0x8004100a error, I am unfamiliar with the windows management instrumentation service, so if you could give a little more detail about the process to re-register WMI DLL files, I would appreciate it.

     

    I have tried 14 times to install sp1 with various fixes that have been suggested on this board and from Microsoft techs, so far nothing has worked.

     

    Gene

     

    Thursday, July 3, 2008 8:58 PM
  • Forget about the numerous suggestions spread all over the web. Mostly garbish.

    IMHO, there is no 'easy way' that works like magic.

    SP1 doesn't install because the OS has issues that must be solved one at a time, the hard way. But it worked for me.

    I had a problem like that and followed the method:
    1) run WMIDiag.vbs. I suggest to print the report, easier to work. (Mine had 35 pages!)
    2) correct all issues one by one
    3) run WMDiag.vbs again. Check the report (This time, my report has been reduced to barely over one page)
    4) When the report says that WMI is working well, install SP1.

    Thanks to all that helped.

    J
    Friday, August 29, 2008 6:51 PM
  • After many hours of searching for a solution to the same problem Glenn had, this fixed it. Thank you Ghamil!
    Monday, December 15, 2008 4:42 AM
  • Can you please please please help me? Im having a lot of WBEM problems and I don't know what to do:(  @Joson Zhou
    • Edited by Karen_10 Wednesday, July 4, 2012 2:44 AM
    Wednesday, July 4, 2012 2:39 AM