.1531 22:26:42 (0) ** WMIDiag v2.1 started on 2013-05-08 at 22:15.
.1532 22:26:42 (0) ** 
.1533 22:26:42 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1534 22:26:42 (0) ** 
.1535 22:26:42 (0) ** This script is not supported under any Microsoft standard support program or service.
.1536 22:26:42 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1537 22:26:42 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1538 22:26:42 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1539 22:26:42 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1540 22:26:42 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1541 22:26:42 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1542 22:26:42 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1543 22:26:42 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1544 22:26:42 (0) ** of the possibility of such damages.
.1545 22:26:42 (0) ** 
.1546 22:26:42 (0) ** 
.1547 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1548 22:26:42 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1549 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1550 22:26:42 (0) ** 
.1551 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1552 22:26:42 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'MICHALSK-24F056\MARCIN' on computer 'MICHALSK-24F056'.
.1553 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1554 22:26:42 (0) ** Environment: ........................................................................................................ OK.
.1555 22:26:42 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1556 22:26:42 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1557 22:26:42 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
.1558 22:26:42 (0) ** AFTER running WMIDiag:
.1559 22:26:42 (0) ** The WMI repository has a size of: ................................................................................... 25 MB.
.1560 22:26:42 (0) ** - Disk free space on 'C:': .......................................................................................... 1114 MB.
.1561 22:26:42 (0) **   - INDEX.BTR,                     1654784 bytes,      2013-05-03 21:12:42
.1562 22:26:42 (0) **   - INDEX.MAP,                     848 bytes,          2013-05-04 03:21:26
.1563 22:26:42 (0) **   - OBJECTS.DATA,                  24387584 bytes,     2013-05-03 21:12:42
.1564 22:26:42 (0) **   - OBJECTS.MAP,                   11996 bytes,        2013-05-04 03:21:26
.1565 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1566 22:26:42 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.1567 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1568 22:26:42 (0) ** DCOM Status: ........................................................................................................ OK.
.1569 22:26:42 (2) !! WARNING: WMI registry setup: ........................................................................................ SERVICE SETUP ISSUES!
.1570 22:26:42 (0) ** => If the WMI service is RUNNING and if registry settings are not correct,
.1571 22:26:42 (0) **    you should check which registry key is subject to modifications (below in this report).
.1572 22:26:42 (0) **    You can eventually repair the registry:
.1573 22:26:42 (0) **    - manually with REGEDIT.EXE.
.1574 22:26:42 (0) **    - by importing the missing registry keys from a working system (same Windows version, same SP level).
.1575 22:26:42 (0) **    - You can also repair the WMI Service registry setup by re-creating the WMI service
.1576 22:26:42 (0) **      setup with the following command:
.1577 22:26:42 (0) **      i.e. 'SC.EXE CREATE WINMGMT BINPATH= C:\WINDOWS\SYSTEM32\WBEM\WINMGMT.EXE START= AUTO'
.1578 22:26:42 (0) **    Note: The SC.EXE command is available in the Windows Resource Kit.
.1579 22:26:42 (0) **      If the command fails because the WMI service name already exists,
.1580 22:26:42 (0) **      you can delete the existing definition with the following command:
.1581 22:26:42 (0) **      i.e. 'SC.EXE DELETE WINMGMT'
.1582 22:26:42 (0) **      If the SC.EXE command does not work, you can delete with REGEDIT.EXE the registry hive at:
.1583 22:26:42 (0) **      'HKLM\SYSTEM\CurrentControlSet\Services\Winmgmt'
.1584 22:26:42 (0) **      and re-execute the 'SC.EXE CREATE' command above.
.1585 22:26:42 (0) **    Note: It could be required to reboot the system to refresh the Service Control Manager configuration.
.1586 22:26:42 (0) **      - Once the WMI service is re-created:
.1587 22:26:42 (0) **      - Make sure there is no other registry keys missing or wrongly configured.
.1588 22:26:42 (0) **        You can manually add the missing keys with REGEDIT.
.1589 22:26:42 (0) **      - After re-creating the registry, and fixing ALL missing entries, you must configure
.1590 22:26:42 (0) **        the WMI service to run as a STANDALONE service host or as a SHARED service host (SvcHost)
.1591 22:26:42 (0) **        You can achieve this by running ONE of the following commands (case sensitive):
.1592 22:26:42 (0) **        - to configure the service to run as a SHARED service host (recommended):
.1593 22:26:42 (0) **          i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToShared'
.1594 22:26:42 (0) **        - if you have issue to get the WMI service running as a SHARED service host, it
.1595 22:26:42 (0) **          can be configured to run as a STANDALONE service host:
.1596 22:26:42 (0) **          i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToAlone'
.1597 22:26:42 (0) ** => Reboot the system.
.1598 22:26:42 (0) ** 
.1599 22:26:42 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.1600 22:26:42 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1601 22:26:42 (0) ** WINMGMT service: .................................................................................................... Failed to start.
.1602 22:26:42 (0) ** => The WINMGMT service can't be started. This could be due to the following reasons:
.1603 22:26:42 (0) **    - The service is DISABLED. You can re-enable the service with the command:
.1604 22:26:42 (0) **      i.e. 'SC.EXE CONFIG WINMGMT START= AUTO'
.1605 22:26:42 (0) **    Note: The SC.EXE command is available in the Windows Resource Kit.
.1606 22:26:42 (0) **    - The WINMGMT service depends on RPCSS service which is DISABLED or unable to start.
.1607 22:26:42 (0) **    - If the service is ENABLED but can't start, then the service registry may contains bad data.
.1608 22:26:42 (0) **    Note: Registry setup errors should be reported. Follow the steps related to registry issues.
.1609 22:26:42 (0) ** => After verifying the registry, if the WMI service does not start yet, you can try to
.1610 22:26:42 (0) **    to run the service as a STANDALONE service host or as a SHARED service host (SvcHost)
.1611 22:26:42 (0) **    You can achieve this by running ONE of the following commands (case sensitive):
.1612 22:26:42 (0) **    - to configure the service to run as a SHARED service host (recommended):
.1613 22:26:42 (0) **      i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToShared'
.1614 22:26:42 (0) **    - if you have issue to get it running as a SHARED service host, the WMI service
.1615 22:26:42 (0) **      can be configured to run as a STANDALONE service host:
.1616 22:26:42 (0) **      i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToAlone'
.1617 22:26:42 (0) ** => If the registry is correct and the WMI service does not start yet, the WMI repository could be inconsistent.
.1618 22:26:42 (0) **    - Validating the repository consistency. In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1619 22:26:42 (0) **      to validate the WMI repository operations.
.1620 22:26:42 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1621 22:26:42 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1622 22:26:42 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
.1623 22:26:42 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1624 22:26:42 (0) **      the WMI repository must be reconstructed/recovered.
.1625 22:26:42 (0) **    - The repository can be recovered from a previous backup.
.1626 22:26:42 (0) **    Note: The System State backup or the System Restore snapshot contain a backup of
.1627 22:26:42 (0) **          of the WMI repository.
.1628 22:26:42 (0) ** => If no backup is available, you must rebuild the repository.
.1629 22:26:42 (0) **    - Re-run WMIDiag with the ShowMOFErrors, this will show any MOF file issues.
.1630 22:26:42 (0) **      i.e. 'WMIDiag ShowMOFErrors'
.1631 22:26:42 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1632 22:26:42 (0) **          otherwise some applications may fail after the reconstruction.
.1633 22:26:42 (0) **          This can be achieved with the following command:
.1634 22:26:42 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1635 22:26:42 (0) **    Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1636 22:26:42 (0) **          registry key will be excluded from the WMI repository reconstruction.
.1637 22:26:42 (0) **          This may imply the lost of WMI registration information.
.1638 22:26:42 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1639 22:26:42 (0) **          ALL fixes previously mentioned.
.1640 22:26:42 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1641 22:26:42 (0) **    - To rebuild the WMI repository, you must:
.1642 22:26:42 (0) **    - Stop the WMI Service.
.1643 22:26:42 (0) **      i.e. 'NET.EXE STOP WINMGMT'
.1644 22:26:42 (0) **    - Move the existing WMI repository files to another location.
.1645 22:26:42 (0) **      i.e. MOVE C:\WINDOWS\SYSTEM32\WBEM\Repository\FS\*.* %TEMP%
.1646 22:26:42 (0) **    - Start the WMI Service.
.1647 22:26:42 (0) **      i.e. 'NET.EXE START WINMGMT'
.1648 22:26:42 (0) **    WMI will rebuild the WMI repository based the auto-recovery mechanism.
.1649 22:26:42 (0) ** 
.1650 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1651 22:26:42 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1652 22:26:42 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
.1653 22:26:42 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
.1654 22:26:42 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
.1655 22:26:42 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
.1656 22:26:42 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
.1657 22:26:42 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
.1658 22:26:42 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
.1659 22:26:42 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1660 22:26:42 (0) **    fail depending on the operation requested.
.1661 22:26:42 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1662 22:26:42 (0) ** 
.1663 22:26:42 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1664 22:26:42 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1665 22:26:42 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1666 22:26:42 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1667 22:26:42 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1668 22:26:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1669 22:26:43 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1670 22:26:43 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1671 22:26:43 (0) **        - REMOVED ACE:
.1672 22:26:43 (0) **          ACEType:  &h0
.1673 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1674 22:26:43 (0) **          ACEFlags: &h0
.1675 22:26:43 (0) **          ACEMask:  &h1
.1676 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1677 22:26:43 (0) ** 
.1678 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1679 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1680 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1681 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1682 22:26:43 (0) ** 
.1683 22:26:43 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1684 22:26:43 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.1685 22:26:43 (0) **        - REMOVED ACE:
.1686 22:26:43 (0) **          ACEType:  &h0
.1687 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1688 22:26:43 (0) **          ACEFlags: &h0
.1689 22:26:43 (0) **          ACEMask:  &h1
.1690 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1691 22:26:43 (0) ** 
.1692 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1693 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1694 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1695 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1696 22:26:43 (0) ** 
.1697 22:26:43 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1698 22:26:43 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.1699 22:26:43 (0) **        - REMOVED ACE:
.1700 22:26:43 (0) **          ACEType:  &h0
.1701 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1702 22:26:43 (0) **          ACEFlags: &h0
.1703 22:26:43 (0) **          ACEMask:  &h1
.1704 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1705 22:26:43 (0) ** 
.1706 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1707 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1708 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1709 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1710 22:26:43 (0) ** 
.1711 22:26:43 (0) ** DCOM security for 'Windows Management Instrumentation' (Launch & Activation Permissions): ........................... MODIFIED.
.1712 22:26:43 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
.1713 22:26:43 (0) **        - REMOVED ACE:
.1714 22:26:43 (0) **          ACEType:  &h0
.1715 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1716 22:26:43 (0) **          ACEFlags: &h0
.1717 22:26:43 (0) **          ACEMask:  &h1
.1718 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1719 22:26:43 (0) ** 
.1720 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1721 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1722 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1723 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1724 22:26:43 (0) ** 
.1725 22:26:43 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1726 22:26:43 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1727 22:26:43 (0) **        - REMOVED ACE:
.1728 22:26:43 (0) **          ACEType:  &h0
.1729 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1730 22:26:43 (0) **          ACEFlags: &h0
.1731 22:26:43 (0) **          ACEMask:  &h1
.1732 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1733 22:26:43 (0) ** 
.1734 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1735 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1736 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1737 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1738 22:26:43 (0) ** 
.1739 22:26:43 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1740 22:26:43 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.1741 22:26:43 (0) **        - REMOVED ACE:
.1742 22:26:43 (0) **          ACEType:  &h0
.1743 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1744 22:26:43 (0) **          ACEFlags: &h0
.1745 22:26:43 (0) **          ACEMask:  &h1
.1746 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1747 22:26:43 (0) ** 
.1748 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1749 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1750 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1751 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1752 22:26:43 (0) ** 
.1753 22:26:43 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1754 22:26:43 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.1755 22:26:43 (0) **        - REMOVED ACE:
.1756 22:26:43 (0) **          ACEType:  &h0
.1757 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1758 22:26:43 (0) **          ACEFlags: &h0
.1759 22:26:43 (0) **          ACEMask:  &h1
.1760 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1761 22:26:43 (0) ** 
.1762 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1763 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1764 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1765 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1766 22:26:43 (0) ** 
.1767 22:26:43 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1768 22:26:43 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
.1769 22:26:43 (0) **        - REMOVED ACE:
.1770 22:26:43 (0) **          ACEType:  &h0
.1771 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1772 22:26:43 (0) **          ACEFlags: &h0
.1773 22:26:43 (0) **          ACEMask:  &h1
.1774 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1775 22:26:43 (0) ** 
.1776 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1777 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1778 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1779 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1780 22:26:43 (0) ** 
.1781 22:26:43 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1782 22:26:43 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
.1783 22:26:43 (0) **        - REMOVED ACE:
.1784 22:26:43 (0) **          ACEType:  &h0
.1785 22:26:43 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1786 22:26:43 (0) **          ACEFlags: &h0
.1787 22:26:43 (0) **          ACEMask:  &h1
.1788 22:26:43 (0) **                    DCOM_RIGHT_EXECUTE
.1789 22:26:43 (0) ** 
.1790 22:26:43 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1791 22:26:43 (0) **    Removing default security will cause some operations to fail!
.1792 22:26:43 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1793 22:26:43 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1794 22:26:43 (0) ** 
.1795 22:26:43 (0) ** 
.1796 22:26:43 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
.1797 22:26:43 (0) ** DCOM security error(s) detected: .................................................................................... 9.
.1798 22:26:43 (0) ** WMI security warning(s) detected: ................................................................................... 0.
.1799 22:26:43 (0) ** WMI security error(s) detected: ..................................................................................... 0.
.1800 22:26:43 (0) ** 
.1801 22:26:43 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
.1802 22:26:43 (0) ** Overall WMI security status: ........................................................................................ OK.
.1803 22:26:43 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1804 22:26:43 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1805 22:26:43 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1806 22:26:43 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1807 22:26:43 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1808 22:26:43 (0) **    the performance counters with the WMI performance classes with the following commands:
.1809 22:26:43 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1810 22:26:43 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1811 22:26:43 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1812 22:26:43 (0) **    More information can be found on MSDN at:
.1813 22:26:43 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1814 22:26:43 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1815 22:26:43 (0) ** - Root, 0x1AD - Składnik ActiveX nie może utworzyć obiektu..
.1816 22:26:43 (0) ** 
.1817 22:26:43 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1818 22:26:43 (0) ** - Root, 0x80080005 - Wykonanie serwera nie powiodło się..
.1819 22:26:43 (0) ** - Root, 0x80080005 - Wykonanie serwera nie powiodło się..
.1820 22:26:43 (0) ** - Root/Default, 0x80080005 - Wykonanie serwera nie powiodło się..
.1821 22:26:43 (0) ** - Root/CIMv2, 0x80080005 - Wykonanie serwera nie powiodło się..
.1822 22:26:43 (0) ** - Root/WMI, 0x80080005 - Wykonanie serwera nie powiodło się..
.1823 22:26:43 (0) ** 
.1824 22:26:43 (0) ** WMI GET operations: ................................................................................................. OK.
.1825 22:26:43 (0) ** WMI MOF representations: ............................................................................................ OK.
.1826 22:26:43 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1827 22:26:43 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1828 22:26:43 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1829 22:26:43 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1830 22:26:43 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1831 22:26:43 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1832 22:26:43 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1833 22:26:43 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1834 22:26:43 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1835 22:26:43 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1836 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1837 22:26:43 (0) ** 
.1838 22:26:43 (0) ** 1 error(s) 0x1AD - (WBEM_UNKNOWN) This error code is external to WMI.
.1839 22:26:43 (0) ** 
.1840 22:26:43 (0) ** 5 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
.1841 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1842 22:26:43 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
.1843 22:26:43 (1) !! ERROR: Unexpected registry key value:
.1844 22:26:43 (0) **   - Current:  HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h3
.1845 22:26:43 (0) **   - Expected: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h2
.1846 22:26:43 (0) **     From the command line, the registry configuration can be corrected with the following command:
.1847 22:26:43 (0) **     i.e. 'REG.EXE Add "HKLM\SYSTEM\CurrentControlSet\Services\winmgmt" /v "Start" /t "REG_DWORD" /d "2" /f'
.1848 22:26:43 (0) ** 
.1849 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1850 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1851 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1852 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1853 22:26:43 (0) ** 
.1854 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1855 22:26:43 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1856 22:26:43 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1857 22:26:43 (0) ** 
.1858 22:26:43 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\MARCIN\USTAWIENIA LOKALNE\TEMP\WMIDIAG-V2.1_XP___.CLI.RTM.32_MICHALSK-24F056_2013.05.08_22.15.17.LOG' for details.
.1859 22:26:43 (0) ** 
.1860 22:26:43 (0) ** WMIDiag v2.1 ended on 2013-05-08 at 22:26 (W:38 E:45 S:1).