none
WMI error - invalid value for registry

    Question

  • i have try to rebuild the WBEM repository as per command below, but it still give me same error "invalid value for registry"

    i have no idea how to solve this issue, please advise

    1.net stop winmgmt

    2.ren %windir%\System32\Wbem\Repository Repository_backup

    3.net start winmgmt

    4.Open Command Prompt (cmd ) with elevated credentials (administrator)

    5.Run winmgmt /salvagerepository to attempt to rebuild the repository

    6.Register WMI components

              cd /d %windir%\system32\wbem

              for /f %s in ('dir /b *.dll') do regsvr32 /s %s

              for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

              wmiprvse /regserver

              regsvr32 wmisvc.dll

    7.Restart Server

     

    Validation:

    After that, please test WMI connection with wbemtest as follows.

    1.Run %SystemRoot%\System32\Wbem\WbemTest.exe

    2.Click Connect

    3.Click Connect

    4. Restart

    ======================================================================================

    .1667 15:34:51 (0) ** WMIDiag v2.1 started on Saturday, January 12, 2013 at 15:34.

    .1668 15:34:51 (0) ** 
    .1669 15:34:51 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    .1670 15:34:51 (0) ** 
    .1671 15:34:51 (0) ** This script is not supported under any Microsoft standard support program or service.
    .1672 15:34:51 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    .1673 15:34:51 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    .1674 15:34:51 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    .1675 15:34:51 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    .1676 15:34:51 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    .1677 15:34:51 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    .1678 15:34:51 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    .1679 15:34:51 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    .1680 15:34:51 (0) ** of the possibility of such damages.
    .1681 15:34:51 (0) ** 
    .1682 15:34:51 (0) ** 
    .1683 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1684 15:34:51 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    .1685 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1686 15:34:51 (0) ** 
    .1687 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1688 15:34:51 (0) ** Windows Server 2008 - Service pack 2 - 64-bit (6002) - User 'EAPAC\XOOTZECADM' on computer 'ESESSMW0132'.
    .1689 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1690 15:34:51 (0) ** Environment: ........................................................................................................ OK.
    .1691 15:34:51 (0) ** There are no missing WMI system files: .............................................................................. OK.
    .1692 15:34:51 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    .1693 15:34:51 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    .1694 15:34:51 (0) ** AFTER running WMIDiag:
    .1695 15:34:51 (0) ** The WMI repository has a size of: ................................................................................... 22 MB.
    .1696 15:34:51 (0) ** - Disk free space on 'C:': .......................................................................................... 14748 MB.
    .1697 15:34:51 (0) **   - INDEX.BTR,                     2187264 bytes,      1/12/2013 3:04:17 PM
    .1698 15:34:51 (0) **   - MAPPING1.MAP,                  66108 bytes,        1/12/2013 3:04:17 PM
    .1699 15:34:51 (0) **   - MAPPING2.MAP,                  66108 bytes,        1/12/2013 2:36:33 PM
    .1700 15:34:51 (0) **   - OBJECTS.DATA,                  21250048 bytes,     1/12/2013 3:04:17 PM
    .1701 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1702 15:34:51 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    .1703 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1704 15:34:51 (0) ** DCOM Status: ........................................................................................................ OK.
    .1705 15:34:51 (0) ** WMI registry setup: ................................................................................................. OK.
    .1706 15:34:51 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    .1707 15:34:51 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    .1708 15:34:51 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    .1709 15:34:51 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    .1710 15:34:51 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    .1711 15:34:51 (0) **          this can prevent the service/application to work as expected.
    .1712 15:34:51 (0) ** 
    .1713 15:34:51 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    .1714 15:34:51 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    .1715 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1716 15:34:51 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    .1717 15:34:51 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    .1718 15:34:51 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    .1719 15:34:51 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    .1720 15:34:51 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    .1721 15:34:51 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    .1722 15:34:51 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    .1723 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1724 15:34:51 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
    .1725 15:34:51 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    .1726 15:34:51 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    .1727 15:34:51 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    .1728 15:34:51 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    .1729 15:34:51 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    .1730 15:34:51 (0) ** 
    .1731 15:34:51 (0) ** Overall DCOM security status: ....................................................................................... OK.
    .1732 15:34:51 (0) ** Overall WMI security status: ........................................................................................ OK.
    .1733 15:34:51 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    .1734 15:34:51 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
    .1735 15:34:51 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    .1736 15:34:51 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
    .1737 15:34:51 (0) ** - Root, 0x80040153 - Invalid value for registry.
    .1738 15:34:51 (0) ** 
    .1739 15:34:51 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 19 ERROR(S)!
    .1740 15:34:51 (0) ** - Root, 0x80040153 - Invalid value for registry.
    .1741 15:34:51 (0) ** - Root, 0x80040153 - Invalid value for registry.
    .1742 15:34:51 (0) ** - Root/subscription, 0x80040153 - Invalid value for registry.
    .1743 15:34:51 (0) ** - Root/DEFAULT, 0x80040153 - Invalid value for registry.
    .1744 15:34:51 (0) ** - Root/CIMV2, 0x80040153 - Invalid value for registry.
    .1745 15:34:51 (0) ** - Root/CIMV2/Security, 0x80040153 - Invalid value for registry.
    .1746 15:34:51 (0) ** - Root/CIMV2/TerminalServices, 0x80040153 - Invalid value for registry.
    .1747 15:34:51 (0) ** - Root/nap, 0x80040153 - Invalid value for registry.
    .1748 15:34:51 (0) ** - Root/SECURITY, 0x80040153 - Invalid value for registry.
    .1749 15:34:51 (0) ** - Root/RSOP, 0x80040153 - Invalid value for registry.
    .1750 15:34:51 (0) ** - Root/RSOP/User, 0x80040153 - Invalid value for registry.
    .1751 15:34:51 (0) ** - Root/RSOP/Computer, 0x80040153 - Invalid value for registry.
    .1752 15:34:51 (0) ** - Root/WMI, 0x80040153 - Invalid value for registry.
    .1753 15:34:51 (0) ** - Root/directory, 0x80040153 - Invalid value for registry.
    .1754 15:34:51 (0) ** - Root/directory/LDAP, 0x80040153 - Invalid value for registry.
    .1755 15:34:51 (0) ** - Root/Policy, 0x80040153 - Invalid value for registry.
    .1756 15:34:51 (0) ** - Root/Microsoft, 0x80040153 - Invalid value for registry.
    .1757 15:34:51 (0) ** - Root/Microsoft/HomeNet, 0x80040153 - Invalid value for registry.
    .1758 15:34:51 (0) ** - Root/aspnet, 0x80040153 - Invalid value for registry.
    .1759 15:34:51 (0) ** 
    .1760 15:34:51 (0) ** WMI GET operations: ................................................................................................. OK.
    .1761 15:34:51 (0) ** WMI MOF representations: ............................................................................................ OK.
    .1762 15:34:51 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    .1763 15:34:51 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    .1764 15:34:51 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    .1765 15:34:51 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    .1766 15:34:51 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    .1767 15:34:51 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    .1768 15:34:51 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    .1769 15:34:51 (0) ** WMI static instances retrieved: ..................................................................................... 0.
    .1770 15:34:51 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    .1771 15:34:51 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
    .1772 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1773 15:34:51 (0) ** 
    .1774 15:34:51 (0) ** 20 error(s) 0x80040153 - (WBEM_UNKNOWN) This error code is external to WMI.
    .1775 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1776 15:34:51 (0) ** WMI Registry key setup: ............................................................................................. OK.
    .1777 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1778 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1779 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1780 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1781 15:34:51 (0) ** 
    .1782 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1783 15:34:51 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    .1784 15:34:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    .1785 15:34:51 (0) ** 
    .1786 15:34:51 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\XOOTZECADM\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2008_.SRV.SP2.64_ESESSMW0132_2013.01.12_15.33.54.LOG' for details.
    .1787 15:34:51 (0) ** 
    .1788 15:34:51 (0) ** WMIDiag v2.1 ended on Saturday, January 12, 2013 at 15:34 (W:27 E:24 S:1).

    Saturday, January 12, 2013 2:39 PM

All replies

  • Hi Tze,


    Based on my research, it seems that the issue is related to DCOM permissions. If so, would you please try the steps in this KB article and see how it works.


    http://support.microsoft.com/kb/934701


    If issue persists, we may consider to re-install our system.


    More information:

    WMI Error Constants (Windows)

    A New Utility for Diagnosing and Repairing Problems with the WMI Service


    Hope this helps. 


    Jeremy Wu
    TechNet Community Support

    Monday, January 14, 2013 9:53 AM
    Moderator
  • By default is same as per this link http://support.microsoft.com/kb/934701

    Instead of rebuild the server, do we have other solution for that?

    Wednesday, January 16, 2013 8:59 AM
  • Hi ,

    Try the following steps to see if this work.

    Run the following command line as elevated permission to reregister WMI Modules:

     

    sc config winmgmt start= disabled

    net stop winmgmt

    cd %windir%\system32\wbem

    for /f %s in ('dir /b *.dll') do regsvr32 /s %s

    regsvr32 %windir%\system32\tscfgwmi.dll

    wmiprvse /regserver

    net start winmgmt

    for /f %s in ('dir /b *.mof *.mfl')
    do mofcomp %s

     

    Run the following command line to rebuild WMI Repository:

     

    sc config winmgmt start= disabled

    net stop winmgmt

    cd %windir%\system32\wbem

    rename repository repository.old

    sc config winmgmt start= auto

    for /f %s in ('dir /b *.mof *.mfl')
    do mofcomp %s

    If this doesn't work, please backup the following registry key and then import it from a working pc (same OS version).

    HKLM\Software/Microsoft/OLE

    Thanks.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, January 17, 2013 12:38 PM
  • Hi Aaron,

    The last two command i get the result as per below, please advise.

    C:\Windows\System32\wbem>for /f %s in ('dir /b *.mof *.mfl')
    The syntax of the command is incorrect.

    C:\Windows\System32\wbem>do mofcomp %s
    'do' is not recognized as an internal or external command,
    operable program or batch file.

    Tuesday, January 29, 2013 11:15 AM