Also came across a few errors when running WMIDIAG but I have no idea how to
fix them.
..1605 15:52:34 (0) ** WMIDiag v2.0 started on Tuesday, August 25, 2009 at
15:52.
..1606 15:52:34 (0) **
..1607 15:52:34 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
..1608 15:52:34 (0) **
..1609 15:52:34 (0) ** This script is not supported under any Microsoft
standard support program or service.
..1610 15:52:34 (0) ** The script is provided AS IS without warranty of any
kind. Microsoft further disclaims all
..1611 15:52:34 (0) ** implied warranties including, without limitation, any
implied warranties of merchantability
..1612 15:52:34 (0) ** or of fitness for a particular purpose. The entire
risk arising out of the use or performance
..1613 15:52:34 (0) ** of the scripts and documentation remains with you. In
no event shall Microsoft, its authors,
..1614 15:52:34 (0) ** or anyone else involved in the creation, production,
or delivery of the script be liable for
..1615 15:52:34 (0) ** any damages whatsoever (including, without limitation,
damages for loss of business profits,
..1616 15:52:34 (0) ** business interruption, loss of business information,
or other pecuniary loss) arising out of
..1617 15:52:34 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
..1618 15:52:34 (0) ** of the possibility of such damages.
..1619 15:52:34 (0) **
..1620 15:52:34 (0) **
..1621 15:52:34 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1622 15:52:34 (0) ** -----------------------------------------------------
WMI REPORT: BEGIN ----------------------------------------------------------
..1623 15:52:34 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1624 15:52:34 (0) **
..1625 15:52:34 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1626 15:52:34 (0) ** Windows XP - No service pack - 32-bit (2600) - User
'C3P0\RW' on computer 'C3P0'.
..1627 15:52:34 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1628 15:52:35 (0) ** Environment:
......................................................................................................... OK..
..1629 15:52:35 (0) ** INFO: The following UNEXPECTED binary files are/is
found in the WBEM folder: ........................................ 1 FILE(S)!
..1630 15:52:35 (0) ** - EVTGPROV.DLL, 40960 bytes,
3/29/2004 6:48:36 PM
..1631 15:52:35 (0) ** => This list is provided for information. Unexpected
binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
..1632 15:52:35 (0) ** do not necessarily represent an error. For
instance, the file(s) listed can be added by
..1633 15:52:35 (0) ** any applications implementing WMI providers.
..1634 15:52:35 (0) ** => NO ACTION is required.
..1635 15:52:35 (0) **
..1636 15:52:35 (0) ** There are no missing WMI system files:
............................................................................... OK.
..1637 15:52:35 (1) !! ERROR: The WMI repository folder is missing or you do
not have access to it at: .....................................
C:\WINDOWS\SYSTEM32\WBEM\Repository\FS.
..1638 15:52:35 (1) !! ERROR: The following WMI repository file(s) is/are
missing: ......................................................... 4 ERROR(S)!
..1639 15:52:35 (0) ** - INDEX.BTR
..1640 15:52:35 (0) ** - INDEX.MAP
..1641 15:52:35 (0) ** - OBJECTS.DATA
..1642 15:52:35 (0) ** - OBJECTS.MAP
..1643 15:52:35 (0) ** => To fix this issue:
..1644 15:52:35 (0) ** - ENSURE you have all access rights to the WMI
repository folder.
..1645 15:52:35 (0) ** - ENSURE you run WMIDiag as an Administrator.
..1646 15:52:35 (0) ** => If the issue is not due to a lack of privileges,
and folder/files are really missing, while
..1647 15:52:35 (0) ** the WMI service successfully started, then WMI will
rebuild the repository based on the
..1648 15:52:35 (0) ** auto-recovery mechanism. In such a case, WMI
repository files shoud be available after the execution
..1649 15:52:35 (0) ** of WMIDiag. Check WMIDiag LOG.
..1650 15:52:35 (0) ** => If the issue is NOT due to a lack of privileges,
and folder/files are really missing, while
..1651 15:52:35 (0) ** the WMI service does not start, then additional
errors should be displayed (i.e. registry, DCOM, service hosts).
..1652 15:52:35 (0) ** You must fix those issues first!
..1653 15:52:35 (0) ** => After fixing issues, if the files are still missing
and if you do not want WMI to rebuild
..1654 15:52:35 (0) ** the WMI repository, then you must restore the WMI
repository from a previous backup.
..1655 15:52:35 (0) ** Note: The System State backup or the System Restore
snapshot contain a backup of
..1656 15:52:35 (0) ** of the WMI repository.
..1657 15:52:35 (0) ** => If no backup is available, you must rebuild the
repository.
..1658 15:52:35 (0) ** Note: The WMI repository reconstruction requires to
locate all MOF files needed to rebuild the repository,
..1659 15:52:35 (0) ** otherwise some applications may fail after
the reconstruction.
..1660 15:52:35 (0) ** This can be achieved with the following
command:
..1661 15:52:35 (0) ** i.e. 'WMIDiag ShowMOFErrors'
..1662 15:52:35 (0) ** Note: Any missing MOF files, or existing MOF files
not listed in the Auto-recovery
..1663 15:52:35 (0) ** registry key will be excluded from the WMI
repository reconstruction.
..1664 15:52:35 (0) ** This may imply the lost of WMI registration
information.
..1665 15:52:35 (0) ** Note: The repository reconstruction must be a LAST
RESORT solution and ONLY after executing
..1666 15:52:35 (0) ** ALL fixes previously mentioned.
..1667 15:52:35 (2) !! WARNING: Static information stored by external
applications in the repository will be LOST! (i.e. SMS Inventory)
..1668 15:52:35 (0) ** => To rebuild the WMI repository, you must:
..1669 15:52:35 (0) ** - Stop the WMI Service.
..1670 15:52:35 (0) ** i.e. 'NET.EXE STOP WINMGMT'
..1671 15:52:35 (0) ** - Move the existing WMI repository files to another
location.
..1672 15:52:35 (0) ** i.e. MOVE
C:\WINDOWS\SYSTEM32\WBEM\Repository\FS\*.* %TEMP%
..1673 15:52:35 (0) ** - Start the WMI Service.
..1674 15:52:35 (0) ** i.e. 'NET.EXE START WINMGMT'
..1675 15:52:35 (0) ** WMI will rebuild the WMI repository based the
auto-recovery mechanism.
..1676 15:52:35 (0) **
..1677 15:52:35 (0) ** WMI repository state:
................................................................................................ N/A.
..1678 15:52:35 (0) ** BEFORE running WMIDiag:
..1679 15:52:35 (0) ** - Disk free space on 'C:':
........................................................................................... 90165 MB.
..1680 15:52:35 (0) ** AFTER running WMIDiag:
..1681 15:52:35 (0) ** - Disk free space on 'C:':
........................................................................................... 90165 MB.
..1682 15:52:35 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1683 15:52:35 (0) ** Windows Firewall:
.................................................................................................... NOT INSTALLED.
..1684 15:52:35 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1685 15:52:35 (0) ** DCOM Status:
......................................................................................................... OK.
..1686 15:52:35 (0) ** WMI registry setup:
.................................................................................................. OK.
..1687 15:52:35 (0) ** INFO: WMI service has dependents:
.................................................................................... 1 SERVICE(S)!
..1688 15:52:35 (0) ** - IPv6 Helper Service (6TO4, StartMode='Automatic')
..1689 15:52:35 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
..1690 15:52:35 (0) ** Note: If the service is marked with (*), it means
that the service/application uses WMI but
..1691 15:52:35 (0) ** there is no hard dependency on WMI. However,
if the WMI service is stopped,
..1692 15:52:35 (0) ** this can prevent the service/application to
work as expected.
..1693 15:52:35 (0) **
..1694 15:52:35 (0) ** RPCSS service:
....................................................................................................... OK (Already started).
..1695 15:52:35 (0) ** WINMGMT service:
..................................................................................................... Failed to start.
..1696 15:52:35 (0) ** => The WINMGMT service can't be started. This could be
due to the following reasons:
..1697 15:52:35 (0) ** - The service is DISABLED. You can re-enable the
service with the command:
..1698 15:52:35 (0) ** i.e. 'SC.EXE CONFIG WINMGMT START= AUTO'
..1699 15:52:35 (0) ** Note: The SC.EXE command is available in the
Windows Resource Kit.
..1700 15:52:35 (0) ** - The WINMGMT service depends on RPCSS service
which is DISABLED or unable to start.
..1701 15:52:35 (0) ** - If the service is ENABLED but can't start, then
the service registry may contains bad data.
..1702 15:52:35 (0) ** Note: Registry setup errors should be reported.
Follow the steps related to registry issues.
..1703 15:52:35 (0) ** => After verifying the registry, if the WMI service
does not start yet, you can try to
..1704 15:52:35 (0) ** to run the service as a STANDALONE service host or
as a SHARED service host (SvcHost)
..1705 15:52:35 (0) ** You can achieve this by running ONE of the
following commands (case sensitive):
..1706 15:52:35 (0) ** - to configure the service to run as a SHARED
service host (recommended):
..1707 15:52:35 (0) ** i.e. 'RUNDLL32.EXE
C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToShared'
..1708 15:52:35 (0) ** - if you have issue to get it running as a SHARED
service host, the WMI service
..1709 15:52:35 (0) ** can be configured to run as a STANDALONE service
host:
..1710 15:52:35 (0) ** i.e. 'RUNDLL32.EXE
C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToAlone'
..1711 15:52:35 (0) ** => If the registry is correct and the WMI service does
not start yet, the WMI repository could be inconsistent.
..1712 15:52:35 (0) ** - Validating the repository consistency. In such a
case, you must rerun WMIDiag with 'WriteInRepository' parameter
..1713 15:52:35 (0) ** to validate the WMI repository operations.
..1714 15:52:35 (0) ** Note: ENSURE you are an administrator with FULL
access to WMI EVERY namespaces of the computer before
..1715 15:52:35 (0) ** executing the WriteInRepository command. To
write temporary data from the Root namespace, use:
..1716 15:52:35 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
..1717 15:52:35 (0) ** - If the WriteInRepository command fails, while
being an Administrator with ALL accesses to ALL namespaces
..1718 15:52:35 (0) ** the WMI repository must be reconstructed/recovered.
..1719 15:52:35 (0) ** - The repository can be recovered from a previous
backup.
..1720 15:52:35 (0) ** Note: The System State backup or the System Restore
snapshot contain a backup of
..1721 15:52:35 (0) ** of the WMI repository.
..1722 15:52:35 (0) ** => If no backup is available, you must rebuild the
repository.
..1723 15:52:35 (0) ** - Re-run WMIDiag with the ShowMOFErrors, this will
show any MOF file issues.
..1724 15:52:35 (0) ** i.e. 'WMIDiag ShowMOFErrors'
..1725 15:52:35 (0) ** Note: The WMI repository reconstruction requires to
locate all MOF files needed to rebuild the repository,
..1726 15:52:35 (0) ** otherwise some applications may fail after
the reconstruction.
..1727 15:52:35 (0) ** This can be achieved with the following
command:
..1728 15:52:35 (0) ** i.e. 'WMIDiag ShowMOFErrors'
..1729 15:52:35 (0) ** Note: Any missing MOF files, or existing MOF files
not listed in the Auto-recovery
..1730 15:52:35 (0) ** registry key will be excluded from the WMI
repository reconstruction.
..1731 15:52:35 (0) ** This may imply the lost of WMI registration
information.
..1732 15:52:35 (0) ** Note: The repository reconstruction must be a LAST
RESORT solution and ONLY after executing
..1733 15:52:35 (0) ** ALL fixes previously mentioned.
..1734 15:52:35 (2) !! WARNING: Static information stored by external
applications in the repository will be LOST! (i.e. SMS Inventory)
..1735 15:52:35 (0) ** - To rebuild the WMI repository, you must:
..1736 15:52:35 (0) ** - Stop the WMI Service.
..1737 15:52:35 (0) ** i.e. 'NET.EXE STOP WINMGMT'
..1738 15:52:35 (0) ** - Move the existing WMI repository files to another
location.
..1739 15:52:35 (0) ** i.e. MOVE
C:\WINDOWS\SYSTEM32\WBEM\Repository\FS\*.* %TEMP%
..1740 15:52:35 (0) ** - Start the WMI Service.
..1741 15:52:35 (0) ** i.e. 'NET.EXE START WINMGMT'
..1742 15:52:35 (0) ** WMI will rebuild the WMI repository based the
auto-recovery mechanism.
..1743 15:52:35 (0) **
..1744 15:52:35 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1745 15:52:35 (0) ** WMI service DCOM setup:
.............................................................................................. OK.
..1746 15:52:35 (0) ** WMI components DCOM registrations:
................................................................................... OK.
..1747 15:52:35 (0) ** WMI ProgID registrations:
............................................................................................ OK.
..1748 15:52:35 (0) ** WMI provider DCOM registrations:
..................................................................................... OK.
..1749 15:52:35 (0) ** WMI provider CIM registrations:
...................................................................................... OK.
..1750 15:52:35 (0) ** WMI provider CLSIDs:
................................................................................................. OK.
..1751 15:52:35 (0) ** WMI providers EXE/DLL availability:
.................................................................................. OK.
..1752 15:52:35 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1753 15:52:35 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment'
(Launch & Activation Permissions): ........................... MODIFIED.
..1754 15:52:35 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has
been REMOVED!
..1755 15:52:35 (0) ** - REMOVED ACE:
..1756 15:52:35 (0) ** ACEType: &h0
..1757 15:52:35 (0) ** ACCESS_ALLOWED_ACE_TYPE
..1758 15:52:35 (0) ** ACEFlags: &h0
..1759 15:52:35 (0) ** ACEMask: &h1
..1760 15:52:35 (0) ** DCOM_RIGHT_EXECUTE
..1761 15:52:35 (0) **
..1762 15:52:35 (0) ** => The REMOVED ACE was part of the DEFAULT setup for
the trustee.
..1763 15:52:35 (0) ** Removing default security will cause some
operations to fail!
..1764 15:52:35 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
..1765 15:52:35 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
..1766 15:52:35 (0) **
..1767 15:52:35 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment'
(Launch & Activation Permissions): ........................... MODIFIED.
..1768 15:52:35 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has
been REMOVED!
..1769 15:52:35 (0) ** - REMOVED ACE:
..1770 15:52:35 (0) ** ACEType: &h0
..1771 15:52:35 (0) ** ACCESS_ALLOWED_ACE_TYPE
..1772 15:52:35 (0) ** ACEFlags: &h0
..1773 15:52:35 (0) ** ACEMask: &h1
..1774 15:52:35 (0) ** DCOM_RIGHT_EXECUTE
..1775 15:52:35 (0) **
..1776 15:52:35 (0) ** => The REMOVED ACE was part of the DEFAULT setup for
the trustee.
..1777 15:52:35 (0) ** Removing default security will cause some
operations to fail!
..1778 15:52:35 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
..1779 15:52:35 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
..1780 15:52:35 (0) **
..1781 15:52:35 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment'
(Launch & Activation Permissions): ........................... MODIFIED.
..1782 15:52:35 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been
REMOVED!
..1783 15:52:35 (0) ** - REMOVED ACE:
..1784 15:52:35 (0) ** ACEType: &h0
..1785 15:52:35 (0) ** ACCESS_ALLOWED_ACE_TYPE
..1786 15:52:35 (0) ** ACEFlags: &h0
..1787 15:52:35 (0) ** ACEMask: &h1
..1788 15:52:35 (0) ** DCOM_RIGHT_EXECUTE
..1789 15:52:35 (0) **
..1790 15:52:35 (0) ** => The REMOVED ACE was part of the DEFAULT setup for
the trustee.
..1791 15:52:35 (0) ** Removing default security will cause some
operations to fail!
..1792 15:52:35 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
..1793 15:52:35 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
..1794 15:52:35 (0) **
..1795 15:52:35 (0) **
..1796 15:52:35 (0) ** DCOM security warning(s) detected:
................................................................................... 0.
..1797 15:52:35 (0) ** DCOM security error(s) detected:
..................................................................................... 3.
..1798 15:52:35 (0) ** WMI security warning(s) detected:
.................................................................................... 0.
..1799 15:52:35 (0) ** WMI security error(s) detected:
...................................................................................... 0.
..1800 15:52:35 (0) **
..1801 15:52:35 (1) !! ERROR: Overall DCOM security status:
................................................................................. ERROR!
..1802 15:52:35 (0) ** Overall WMI security status:
......................................................................................... OK.
..1803 15:52:35 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------------------------------------
..1804 15:52:35 (0) ** WMI permanent SUBSCRIPTION(S):
....................................................................................... NONE.
..1805 15:52:35 (0) ** WMI TIMER instruction(s):
............................................................................................ NONE.
..1806 15:52:35 (1) !! ERROR: WMI ADAP status:
.............................................................................................. NOT AVAILABLE.
..1807 15:52:35 (0) ** You can start the WMI AutoDiscovery/AutoPurge
(ADAP) process to resynchronize
..1808 15:52:35 (0) ** the performance counters with the WMI performance
classes with the following commands:
..1809 15:52:35 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'
..1810 15:52:35 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF'
..1811 15:52:35 (0) ** The ADAP process logs informative events in the
Windows NT event log.
..1812 15:52:35 (0) ** More information can be found on MSDN at:
..1813 15:52:35 (0) **
http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp
..1814 15:52:35 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the
following namespaces: .......................................... 1 ERROR(S)!
..1815 15:52:35 (0) ** - Root, 0x1AD - ActiveX component can't create object.
..1816 15:52:35 (0) **
..1817 15:52:35 (1) !! ERROR: WMI CONNECTION errors occured for the following
namespaces: .................................................. 5 ERROR(S)!
..1818 15:52:35 (0) ** - Root, 0x80040154 - Class not registered.
..1819 15:52:35 (0) ** - Root, 0x80040154 - Class not registered.
..1820 15:52:35 (0) ** - Root/Default, 0x80040154 - Class not registered.
..1821 15:52:35 (0) ** - Root/CIMv2, 0x80040154 - Class not registered.
..1822 15:52:35 (0) ** - Root/WMI, 0x80040154 - Class not registered.
..1823 15:52:35 (0) **
..1824 15:52:35 (0) ** WMI GET operations:
.................................................................................................. OK.
..1825 15:52:35 (0) ** WMI MOF representations:
............................................................................................. OK.
..1826 15:52:35 (0) ** WMI QUALIFIER access operations:
..................................................................................... OK.
..1827 15:52:35 (0) ** WMI ENUMERATION operations:
.......................................................................................... OK.
..1828 15:52:35 (0) ** WMI EXECQUERY operations:
............................................................................................ OK.
..1829 15:52:35 (0) ** WMI GET VALUE operations:
............................................................................................ OK.
..1830 15:52:35 (0) ** WMI WRITE operations:
................................................................................................ NOT TESTED.
..1831 15:52:35 (0) ** WMI PUT operations:
.................................................................................................. NOT TESTED.
..1832 15:52:35 (0) ** WMI DELETE operations:
............................................................................................... NOT TESTED.
..1833 15:52:35 (0) ** WMI static instances retrieved:
...................................................................................... 0.
..1834 15:52:35 (0) ** WMI dynamic instances retrieved:
..................................................................................... 0.
..1835 15:52:35 (0) ** WMI instance request cancellations (to limit
performance impact): ................................................... 0.
..1836 15:52:35 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1837 15:52:35 (0) **
..1838 15:52:35 (0) ** 1 error(s) 0x1AD - (WBEM_UNKNOWN) This error code is
external to WMI.
..1839 15:52:35 (0) **
..1840 15:52:35 (0) ** 5 error(s) 0x80040154 - (WBEM_UNKNOWN) This error code
is external to WMI.
..1841 15:52:35 (0) ** => This error is not a WMI error. This error is a DCOM
component registration error.
..1842 15:52:35 (0) ** The registry information for DCOM to initialize a
DCOM object is missing or wrongly configured.
..1843 15:52:35 (0) ** - An application has changed the COM/DCOM settings
of OLE32.DLL and/or OLEAUT32.DLL.
..1844 15:52:35 (0) ** - The registry settings of COM/DCOM has been damage
or wrongly modified.
..1845 15:52:35 (0) ** - The registry security settings of COM/DCOM has
been damage or wrongly modified.
..1846 15:52:35 (0) ** => To correct this situation, you must re-register the
original COM/DCOM DLLs with REGSVR32.EXE
..1847 15:52:35 (0) ** i.e. 'REGSVR32.EXE OLE32.DLL'
..1848 15:52:35 (0) ** i.e. 'REGSVR32.EXE OLEAUT32.DLL'
..1849 15:52:35 (0) ** => Verify WMIDiag report if ERRORS or WARNINGS are
reported about the DCOM security for
..1850 15:52:35 (0) ** the following DCOM objects:
..1851 15:52:35 (0) ** - 'My Computer'
..1852 15:52:35 (0) ** - 'Windows Management Instrumentation'
..1853 15:52:35 (0) ** - 'Microsoft WMI Provider Subsystem Host'
..1854 15:52:35 (0) ** - 'Microsoft WBEM UnSecured Apartment'
..1855 15:52:35 (0) ** => You must also verify with 'REGEDIT.EXE', if the
'Users' builtin group is granted read access for
..1856 15:52:35 (0) ** the following registry hives:
..1857 15:52:35 (0) ** - HKCR\APPID
..1858 15:52:35 (0) ** - HKCR\CLSID
..1859 15:52:35 (0) ** - HKCR\APPID\{1BE1F766-5536-11D1-B726-00C04FB926AF}
(WinMgmt EventSystem APPID keys)
..1860 15:52:35 (0) ** - HKCR\CLSID\{1BE1F766-5536-11D1-B726-00C04FB926AF}
(WinMgmt EventSystem CLSID keys)
..1861 15:52:35 (0) ** - HKCR\APPID\{8BC3F05E-D86B-11D0-A075-00C04FB68820}
(WinMgmt APPID keys)
..1862 15:52:35 (0) ** - HKCR\CLSID\{8BC3F05E-D86B-11D0-A075-00C04FB68820}
(WinMgmt CLSID keys)
..1863 15:52:35 (0) **
..1864 15:52:35 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1865 15:52:35 (0) ** WMI Registry key setup:
.............................................................................................. OK.
..1866 15:52:35 (0) **
----------------------------------------------------------------------------------------------------------------------------------
..1867 15:52:35 (0) ** No MOF file referenced in the Auto-Recovery list is
missing: ........................................................ OK.
..1868 15:52:35 (1) !! ERROR: MOF file(s) present in the WBEM folder not
referenced in the Auto-Recovery list: ............................. 16
ERROR(S)!
..1869 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FCONPROV.MFL (*)
..1870 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FCONPROV.MOF (*)
..1871 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (*)
..1872 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (*)
..1873 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL (*)
..1874 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF (*)
..1875 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL (*)
..1876 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF (*)
..1877 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TMPLPROV.MFL (*)
..1878 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TMPLPROV.MOF (*)
..1879 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TRNSPROV.MFL (*)
..1880 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TRNSPROV.MOF (*)
..1881 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UPDPROV.MFL (*)
..1882 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UPDPROV.MOF (*)
..1883 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL (*)
..1884 15:52:35 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF (*)
..1885 15:52:35 (0) ** => After fixing all other issues previously mentioned,
if the WMI repository is rebuilt,
..1886 15:52:35 (0) ** the listed MOF file(s) will not be recompiled, and
therefore the definition they contain
..1887 15:52:35 (0) ** will not be available in the WMI repository.
..1888 15:52:35 (0) ** => You must manually recompile the MOF file(s) with
the 'MOFCOMP.EXE <FileName.MOF>' command.
..1889 15:52:35 (0) ** => If you want the MOF file(s) to be part of the
Auto-Recovery list, make sure the
..1890 15:52:35 (0) ** statement '#PRAGMA AUTORECOVER' is included.
..1891 15:52:35 (0) ** Note: MOF file(s) marked with (*) are NEVER
included AT SETUP in the auto-recovery process.
..1892 15:52:35 (0) ** MOF file(s) containing UNINSTALL statements
(i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery
process.
..1893 15:52:35 (0) ** Refer to the list of MOF files below NOT
containing the '#PRAGMA AUTORECOVER' statement' for more information.
..1894 15:52:35 (0) **
..1895 15:52:35 (0) **
