启动MWI服务时，提示“错误2：系统找不到指定文件”，怎么办？

如图。

后来我下载了WMIDIAG，生成了一份检查报告，如下：

.1565 19:09:34 (0) ** WMIDiag v2.2 started on 2017年4月30日 at 17:27.
.1566 19:09:34 (0) **
.1567 19:09:34 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1568 19:09:34 (0) **
.1569 19:09:34 (0) ** This script is not supported under any Microsoft standard support program or service.
.1570 19:09:34 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1571 19:09:34 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1572 19:09:34 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1573 19:09:34 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1574 19:09:34 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1575 19:09:34 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1576 19:09:34 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1577 19:09:34 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1578 19:09:34 (0) ** of the possibility of such damages.
.1579 19:09:34 (0) **
.1580 19:09:34 (0) **
.1581 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1582 19:09:34 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1583 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1584 19:09:34 (0) **
.1585 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1586 19:09:34 (0) ** Windows 7 - Service Pack 1 - 64-bit (7601) - User 'ABC-VAIO\ABC' on computer 'ABC-VAIO'.
.1587 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1588 19:09:34 (0) ** Environment: ........................................................................................................ OK.
.1589 19:09:34 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1590 19:09:34 (1) !! ERROR: The following WMI repository file(s) is/are missing: ......................................................... 4 ERROR(S)!
.1591 19:09:34 (0) ** - INDEX.BTR
.1592 19:09:34 (0) ** - MAPPING1.MAP
.1593 19:09:34 (0) ** - MAPPING2.MAP
.1594 19:09:34 (0) ** - OBJECTS.DATA
.1595 19:09:34 (0) ** => To fix this issue:
.1596 19:09:34 (0) ** - ENSURE you have all access rights to the WMI repository folder.
.1597 19:09:34 (0) ** - ENSURE you run WMIDiag as an Administrator.
.1598 19:09:34 (0) ** => If the issue is not due to a lack of privileges, and folder/files are really missing, while
.1599 19:09:34 (0) ** the WMI service successfully started, then WMI will rebuild the repository based on the
.1600 19:09:34 (0) ** auto-recovery mechanism. In such a case, WMI repository files shoud be available after the execution
.1601 19:09:34 (0) ** of WMIDiag. Check WMIDiag LOG.
.1602 19:09:34 (0) ** => If the issue is NOT due to a lack of privileges, and folder/files are really missing, while
.1603 19:09:34 (0) ** the WMI service does not start, then additional errors should be displayed (i.e. registry, DCOM, service hosts).
.1604 19:09:34 (0) ** You must fix those issues first!
.1605 19:09:34 (0) ** => After fixing issues, if the files are still missing and if you do not want WMI to rebuild
.1606 19:09:34 (0) ** the WMI repository, then you must restore the WMI repository from a previous backup.
.1607 19:09:34 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1608 19:09:34 (0) ** of the WMI repository.
.1609 19:09:34 (0) ** => If no backup is available, you must rebuild the repository.
.1610 19:09:34 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1611 19:09:34 (0) ** otherwise some applications may fail after the reconstruction.
.1612 19:09:34 (0) ** This can be achieved with the following command:
.1613 19:09:34 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1614 19:09:34 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1615 19:09:34 (0) ** registry key will be excluded from the WMI repository reconstruction.
.1616 19:09:34 (0) ** This may imply the lost of WMI registration information.
.1617 19:09:34 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1618 19:09:34 (0) ** ALL fixes previously mentioned.
.1619 19:09:34 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1620 19:09:34 (0) ** => To rebuild the WMI repository, you must:
.1621 19:09:34 (0) ** - Reset the WMI repository
.1622 19:09:34 (0) ** (The WMI repository rebuilt is based on auto-recovery)
.1623 19:09:34 (0) ** i.e. 'WINMGMT /ResetRepository'
.1624 19:09:34 (0) ** OR
.1625 19:09:34 (0) ** - Salvage the WMI repository if you want to attempt the retrieval of good data from the
.1626 19:09:34 (0) ** inconsistent repository
.1627 19:09:34 (0) ** (The repository rebuilt is based on auto-recovery + salvage)
.1628 19:09:34 (0) ** i.e. 'WINMGMT /SalvageRepository'
.1629 19:09:34 (0) **
.1630 19:09:34 (0) ** WMI repository state: ............................................................................................... N/A.
.1631 19:09:34 (0) ** AFTER running WMIDiag:
.1632 19:09:34 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
.1633 19:09:34 (0) ** - Disk free space on 'C:': .......................................................................................... 830952 MB.
.1634 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1635 19:09:34 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
.1636 19:09:34 (0) ** Windows Firewall Profile: ........................................................................................... PUBLIC.
.1637 19:09:34 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
.1638 19:09:34 (0) ** => This will prevent any WMI remote connectivity to this computer except
.1639 19:09:34 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
.1640 19:09:34 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
.1641 19:09:34 (0) ** - 'Windows Management Instrumentation (WMI-In)'
.1642 19:09:34 (0) ** - 'Windows Management Instrumentation (ASync-In)'
.1643 19:09:34 (0) ** Verify the reported status for each of these three inbound rules below.
.1644 19:09:34 (0) **
.1645 19:09:34 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
.1646 19:09:34 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
.1647 19:09:34 (0) ** - You can adjust the configuration by executing the following command:
.1648 19:09:34 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
.1649 19:09:34 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
.1650 19:09:34 (0) ** You can also enable each individual rule instead of activating the group rule.
.1651 19:09:34 (0) **
.1652 19:09:34 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. DISABLED.
.1653 19:09:34 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
.1654 19:09:34 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1655 19:09:34 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
.1656 19:09:34 (0) **
.1657 19:09:34 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... DISABLED.
.1658 19:09:34 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine.
.1659 19:09:34 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1660 19:09:34 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES'
.1661 19:09:34 (0) **
.1662 19:09:34 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ DISABLED.
.1663 19:09:34 (0) ** => This will prevent any WMI inbound connectivity to this machine.
.1664 19:09:34 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
.1665 19:09:34 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1666 19:09:34 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
.1667 19:09:34 (0) **
.1668 19:09:34 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... DISABLED.
.1669 19:09:34 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
.1670 19:09:34 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
.1671 19:09:34 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1672 19:09:34 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
.1673 19:09:34 (0) **
.1674 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1675 19:09:34 (0) ** DCOM Status: ........................................................................................................ OK.
.1676 19:09:34 (2) !! WARNING: WMI registry setup: ........................................................................................ SERVICE SETUP ISSUES!
.1677 19:09:34 (0) ** => If the WMI service is RUNNING and if registry settings are not correct,
.1678 19:09:34 (0) ** you should check which registry key is subject to modifications (below in this report).
.1679 19:09:34 (0) ** You can eventually repair the registry:
.1680 19:09:34 (0) ** - manually with REGEDIT.EXE.
.1681 19:09:34 (0) ** - by importing the missing registry keys from a working system (same Windows version, same SP level).
.1682 19:09:34 (0) ** - You can also repair the WMI Service registry setup by re-creating the WMI service
.1683 19:09:34 (0) ** setup with the following command:
.1684 19:09:34 (0) ** i.e. 'SC.EXE CREATE WINMGMT BINPATH= C:\WINDOWS\SYSTEM32\WBEM\WINMGMT.EXE START= AUTO'
.1685 19:09:34 (0) ** Note: The SC.EXE command is available in the Windows Resource Kit.
.1686 19:09:34 (0) ** If the command fails because the WMI service name already exists,
.1687 19:09:34 (0) ** you can delete the existing definition with the following command:
.1688 19:09:34 (0) ** i.e. 'SC.EXE DELETE WINMGMT'
.1689 19:09:34 (0) ** If the SC.EXE command does not work, you can delete with REGEDIT.EXE the registry hive at:
.1690 19:09:34 (0) ** 'HKLM\SYSTEM\CurrentControlSet\Services\Winmgmt'
.1691 19:09:34 (0) ** and re-execute the 'SC.EXE CREATE' command above.
.1692 19:09:34 (0) ** Note: It could be required to reboot the system to refresh the Service Control Manager configuration.
.1693 19:09:34 (0) ** - Once the WMI service is re-created:
.1694 19:09:34 (0) ** - Make sure there is no other registry keys missing or wrongly configured.
.1695 19:09:34 (0) ** You can manually add the missing keys with REGEDIT.
.1696 19:09:34 (0) ** - After re-creating the registry, and fixing ALL missing entries, you must configure
.1697 19:09:34 (0) ** the WMI service to run as a STANDALONE service host or as a SHARED service host (SvcHost)
.1698 19:09:34 (0) ** You can achieve this by running the following commands:
.1699 19:09:34 (0) ** - to configure the service to run as a SHARED service host (recommended):
.1700 19:09:34 (0) ** i.e. 'WINMGMT.EXE /SharedHost'
.1701 19:09:34 (0) ** - if you have issue to get the WMI service running as a SHARED service host, it
.1702 19:09:34 (0) ** can be configured to run as a STANDALONEservice host:
.1703 19:09:34 (0) ** i.e. 'WINMGMT.EXE /StandaloneHost'
.1704 19:09:34 (0) ** => Reboot the system.
.1705 19:09:34 (0) **
.1706 19:09:34 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1707 19:09:34 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1708 19:09:34 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
.1709 19:09:34 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1710 19:09:34 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
.1711 19:09:34 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
.1712 19:09:34 (0) ** this can prevent the service/application to work as expected.
.1713 19:09:34 (0) **
.1714 19:09:34 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1715 19:09:34 (0) ** WINMGMT service: .................................................................................................... Failed to start.
.1716 19:09:34 (0) ** => The WINMGMT service can't be started. This could be due to the following reasons:
.1717 19:09:34 (0) ** - The service is DISABLED. You can re-enable the service with the command:
.1718 19:09:34 (0) ** i.e. 'SC.EXE CONFIG WINMGMT START= AUTO'
.1719 19:09:34 (0) ** Note: The SC.EXE command is available in the Windows Resource Kit.
.1720 19:09:34 (0) ** - The WINMGMT service depends on RPCSS service which is DISABLED or unable to start.
.1721 19:09:34 (0) ** - If the service is ENABLED but can't start, then the service registry may contains bad data.
.1722 19:09:34 (0) ** Note: Registry setup errors should be reported. Follow the steps related to registry issues.
.1723 19:09:34 (0) ** => After verifying the registry, if the WMI service does not start yet, you can try to
.1724 19:09:34 (0) ** to run the service as a STANDALONE service host or as a SHARED service host (SvcHost)
.1725 19:09:34 (0) ** You can achieve this by running ONE of the following commands:
.1726 19:09:34 (0) ** - to configure the service to run as a SHARED service host (recommended):
.1727 19:09:34 (0) ** i.e. 'WINMGMT.EXE /SharedHost'
.1728 19:09:34 (0) ** - if you have issue to get it running as a SHARED service host, the WMI service
.1729 19:09:34 (0) ** can be configured to run as a STANDALONE service host:
.1730 19:09:34 (0) ** i.e. 'WINMGMT.EXE /StandaloneHost'
.1731 19:09:34 (0) ** => If the registry is correct and the WMI service does not start yet, the WMI repository could be inconsistent.
.1732 19:09:34 (0) ** - Validating the repository consistency. In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1733 19:09:34 (0) ** to validate the WMI repository operations.
.1734 19:09:34 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1735 19:09:34 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1736 19:09:34 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
.1737 19:09:34 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1738 19:09:34 (0) ** the WMI repository must be reconstructed/recovered.
.1739 19:09:34 (0) ** - The repository can be recovered from a previous backup.
.1740 19:09:34 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1741 19:09:34 (0) ** of the WMI repository.
.1742 19:09:34 (0) ** => If no backup is available, you must rebuild the repository.
.1743 19:09:34 (0) ** - Re-run WMIDiag with the ShowMOFErrors, this will show any MOF file issues.
.1744 19:09:34 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1745 19:09:34 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1746 19:09:34 (0) ** otherwise some applications may fail after the reconstruction.
.1747 19:09:34 (0) ** This can be achieved with the following command:
.1748 19:09:34 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1749 19:09:34 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1750 19:09:34 (0) ** registry key will be excluded from the WMI repository reconstruction.
.1751 19:09:34 (0) ** This may imply the lost of WMI registration information.
.1752 19:09:34 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1753 19:09:34 (0) ** ALL fixes previously mentioned.
.1754 19:09:34 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1755 19:09:34 (0) ** - To rebuild the WMI repository, you must:
.1756 19:09:34 (0) ** - Reset the WMI repository
.1757 19:09:34 (0) ** (The WMI repository rebuilt is based on auto-recovery)
.1758 19:09:34 (0) ** i.e. 'WINMGMT /ResetRepository'
.1759 19:09:34 (0) ** OR
.1760 19:09:34 (0) ** - Salvage the WMI repository if you want to attempt the retrieval of good data from the
.1761 19:09:34 (0) ** inconsistent repository
.1762 19:09:34 (0) ** (The repository rebuilt is based on auto-recovery + salvage)
.1763 19:09:34 (0) ** i.e. 'WINMGMT /SalvageRepository'
.1764 19:09:34 (0) **
.1765 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1766 19:09:34 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1767 19:09:34 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 4 WARNING(S)!
.1768 19:09:34 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPMIPRV.DLL (\CLSID\{FD209E2E-813B-41C0-8646-4C3E9C917511}\InProcServer32)
.1769 19:09:34 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.DLL (\CLSID\{69D76D1B-B12E-4913-8F48-671B90195A2B}\InProcServer32)
.1770 19:09:34 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.DLL (\CLSID\{AAEAE72F-0328-4763-8ECB-23422EDE2DB5}\InProcServer32)
.1771 19:09:34 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SERVERCOMPPROV.DLL (\CLSID\{9042E1B1-8FD4-4008-89FE-4040CC74575A}\InProcServer32)
.1772 19:09:34 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1773 19:09:34 (0) ** fail depending on the operation requested.
.1774 19:09:34 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1775 19:09:34 (0) **
.1776 19:09:34 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1777 19:09:34 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1778 19:09:34 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1779 19:09:34 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1780 19:09:34 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1781 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1782 19:09:34 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.1783 19:09:34 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.1784 19:09:34 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
.1785 19:09:34 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.1786 19:09:34 (0) ** selecting 'Run as Administrator'.
.1787 19:09:34 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
.1788 19:09:34 (0) ** in the Task Scheduler within the right security context.
.1789 19:09:34 (0) **
.1790 19:09:34 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1791 19:09:34 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1792 19:09:34 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1793 19:09:34 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
.1794 19:09:34 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1795 19:09:34 (0) **
.1796 19:09:34 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1797 19:09:34 (0) ** Overall WMI security status: ........................................................................................ OK.
.1798 19:09:34 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1799 19:09:34 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1800 19:09:34 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1801 19:09:34 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1802 19:09:34 (0) ** - Root, 0x1AD - ActiveX.
.1803 19:09:34 (0) **
.1804 19:09:34 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
.1805 19:09:34 (0) ** - Root, 0x80080005 - .
.1806 19:09:34 (0) ** - Root, 0x80080005 - .
.1807 19:09:34 (0) ** - Root/subscription, 0x80080005 - .
.1808 19:09:34 (0) ** - Root/DEFAULT, 0x80080005 - .
.1809 19:09:34 (0) ** - Root/CIMV2, 0x80080005 - .
.1810 19:09:34 (0) ** - Root/CIMV2/Security, 0x80080005 - .
.1811 19:09:34 (0) ** - Root/CIMV2/Applications, 0x80080005 - .
.1812 19:09:34 (0) ** - Root/nap, 0x80080005 - .
.1813 19:09:34 (0) ** - Root/SECURITY, 0x80080005 - .
.1814 19:09:34 (0) ** - Root/WMI, 0x80080005 - .
.1815 19:09:34 (0) ** - Root/directory, 0x80080005 - .
.1816 19:09:34 (0) ** - Root/directory/LDAP, 0x80080005 - .
.1817 19:09:34 (0) ** - Root/SecurityCenter, 0x80080005 - .
.1818 19:09:34 (0) ** - Root/Microsoft, 0x80080005 - .
.1819 19:09:34 (0) ** - Root/Microsoft/HomeNet, 0x80080005 - .
.1820 19:09:34 (0) ** - Root/aspnet, 0x80080005 - .
.1821 19:09:34 (0) **
.1822 19:09:34 (0) ** WMI GET operations: ................................................................................................. OK.
.1823 19:09:34 (0) ** WMI MOF representations: ............................................................................................ OK.
.1824 19:09:34 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1825 19:09:34 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1826 19:09:34 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1827 19:09:34 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1828 19:09:34 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1829 19:09:34 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1830 19:09:34 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1831 19:09:34 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1832 19:09:34 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1833 19:09:34 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1834 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1835 19:09:34 (0) **
.1836 19:09:34 (0) ** 1 error(s) 0x1AD - (WBEM_UNKNOWN) This error code is external to WMI.
.1837 19:09:34 (0) **
.1838 19:09:34 (0) ** 16 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
.1839 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1840 19:09:34 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 3 KEY(S)!
.1841 19:09:34 (1) !! ERROR: Missing registry key value:
.1842 19:09:34 (0) ** - HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Parameters\ServiceDll (REG_EXPAND_SZ) -> %SystemRoot%\system32\wbem\WMIsvc.dll
.1843 19:09:34 (0) ** From the command line, the registry configuration can be corrected with the following command:
.1844 19:09:34 (1) !! ERROR: Missing registry key value:
.1845 19:09:34 (0) ** - HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Parameters\ServiceDllUnloadOnStop (REG_DWORD) -> 1
.1846 19:09:34 (0) ** From the command line, the registry configuration can be corrected with the following command:
.1847 19:09:34 (0) ** i.e. 'REG.EXE Add "HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Parameters" /v "ServiceDllUnloadOnStop" /t "REG_DWORD" /d "1" /f'
.1848 19:09:34 (1) !! ERROR: Missing registry key value:
.1849 19:09:34 (0) ** - HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Parameters\ServiceMain (REG_SZ) -> ServiceMain
.1850 19:09:34 (0) ** From the command line, the registry configuration can be corrected with the following command:
.1851 19:09:34 (0) **
.1852 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1853 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1854 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1855 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1856 19:09:34 (0) **
.1857 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1858 19:09:34 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1859 19:09:34 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1860 19:09:34 (0) **
.1861 19:09:34 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\ABC\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN7_.CLI.SP1.64_ABC-VAIO_2017.04.30_17.27.14.LOG' for details.
.1862 19:09:34 (0) **
.1863 19:09:34 (0) ** WMIDiag v2.2 ended on 2017年4月30日 at 19:09 (W:22 E:48 S:1)

不太明白什么意思，可以帮我看一下吗，谢谢！

您好，

由于长时间未得到您的回复，该问题我们会暂时作为归档处理，如果您仍有问题，欢迎随时跟帖回复。如果有其他问题需要提交，也欢迎您再次提问。

感谢使用微软产品。

最后更新：2017-05-12 10:57:09

启动MWI服务时，提示“错误2：系统找不到指定文件”，怎么办？

上一篇：问题如下：联想笔记本Y50，更换主板后随机出现断电重启问题(另外温度较高，降频等等)

下一篇：看视频一段时间后会自动断网是怎么回事

相关内容

热门内容

最新内容

启动MWI服务时，提示“错误2：系统找不到指定文件”，怎么办？

上一篇： 问题如下：联想笔记本Y50，更换主板后随机出现断电重启问题(另外温度较高，降频等等)

下一篇： 看视频一段时间后会自动断网是怎么回事

相关内容

热门内容

最新内容

上一篇：问题如下：联想笔记本Y50，更换主板后随机出现断电重启问题(另外温度较高，降频等等)

下一篇：看视频一段时间后会自动断网是怎么回事