.1710 12:24:07 (0) ** WMIDiag v2.2 started on 7 maja 2016 at 12:23.
.1711 12:24:07 (0) ** 
.1712 12:24:07 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1713 12:24:07 (0) ** 
.1714 12:24:07 (0) ** This script is not supported under any Microsoft standard support program or service.
.1715 12:24:07 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1716 12:24:07 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1717 12:24:07 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1718 12:24:07 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1719 12:24:07 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1720 12:24:07 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1721 12:24:07 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1722 12:24:07 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1723 12:24:07 (0) ** of the possibility of such damages.
.1724 12:24:07 (0) ** 
.1725 12:24:07 (0) ** 
.1726 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1727 12:24:07 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1728 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1729 12:24:07 (0) ** 
.1730 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1731 12:24:07 (0) ** Windows 7 - Service Pack 1 - 64-bit (7601) - User 'ASUS-KOMPUTER\ASUS' on computer 'ASUS-KOMPUTER'.
.1732 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1733 12:24:07 (0) ** Environment: ........................................................................................................ OK.
.1734 12:24:07 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1735 12:24:07 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1736 12:24:07 (0) ** WMI repository state: ............................................................................................... N/A.
.1737 12:24:07 (0) ** AFTER running WMIDiag:
.1738 12:24:07 (0) ** The WMI repository has a size of: ................................................................................... 21 MB.
.1739 12:24:07 (0) ** - Disk free space on 'C:': .......................................................................................... 251917 MB.
.1740 12:24:07 (0) **   - INDEX.BTR,                     4521984 bytes,      2016-04-09 18:57:48
.1741 12:24:07 (0) **   - MAPPING1.MAP,                  58328 bytes,        2016-04-09 18:40:30
.1742 12:24:07 (0) **   - MAPPING2.MAP,                  58328 bytes,        2016-04-09 18:57:48
.1743 12:24:07 (0) **   - OBJECTS.DATA,                  17227776 bytes,     2016-04-09 18:57:48
.1744 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1745 12:24:07 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
.1746 12:24:07 (0) ** Windows Firewall Profile: ........................................................................................... PRIVATE.
.1747 12:24:07 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
.1748 12:24:07 (0) ** => This will prevent any WMI remote connectivity to this computer except
.1749 12:24:07 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
.1750 12:24:07 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
.1751 12:24:07 (0) **    - 'Windows Management Instrumentation (WMI-In)'
.1752 12:24:07 (0) **    - 'Windows Management Instrumentation (ASync-In)'
.1753 12:24:07 (0) **    Verify the reported status for each of these three inbound rules below.
.1754 12:24:07 (0) ** 
.1755 12:24:07 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
.1756 12:24:07 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
.1757 12:24:07 (0) **    - You can adjust the configuration by executing the following command:
.1758 12:24:07 (0) **    i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
.1759 12:24:07 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
.1760 12:24:07 (0) **       You can also enable each individual rule instead of activating the group rule.
.1761 12:24:07 (0) ** 
.1762 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1763 12:24:07 (0) ** DCOM Status: ........................................................................................................ OK.
.1764 12:24:07 (2) !! WARNING: WMI registry setup: ........................................................................................ INVALID HOSTING SETUP!
.1765 12:24:07 (0) ** => The WMI service must be configured to run as a STANDALONE service host or
.1766 12:24:07 (0) **    as a SHARED service host but the (SvcHost) configuration contains invalid information.
.1767 12:24:07 (0) ** => You can fix this issue by running ONE of the following commands:
.1768 12:24:07 (0) **    - Shared service host (recommended):
.1769 12:24:07 (0) **      i.e. 'WINMGMT.EXE /SharedHost'
.1770 12:24:07 (0) **    - Standalone service host:
.1771 12:24:07 (0) **      i.e. 'WINMGMT.EXE /StandaloneHost'
.1772 12:24:07 (0) ** => Reboot the system.
.1773 12:24:07 (0) ** 
.1774 12:24:07 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1775 12:24:07 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1776 12:24:07 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
.1777 12:24:07 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1778 12:24:07 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1779 12:24:07 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1780 12:24:07 (0) **          this can prevent the service/application to work as expected.
.1781 12:24:07 (0) ** 
.1782 12:24:07 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1783 12:24:07 (0) ** WINMGMT service: .................................................................................................... Failed to start.
.1784 12:24:07 (0) ** => The WINMGMT service can't be started. This could be due to the following reasons:
.1785 12:24:07 (0) **    - The service is DISABLED. You can re-enable the service with the command:
.1786 12:24:07 (0) **      i.e. 'SC.EXE CONFIG WINMGMT START= AUTO'
.1787 12:24:07 (0) **    Note: The SC.EXE command is available in the Windows Resource Kit.
.1788 12:24:07 (0) **    - The WINMGMT service depends on RPCSS service which is DISABLED or unable to start.
.1789 12:24:07 (0) **    - If the service is ENABLED but can't start, then the service registry may contains bad data.
.1790 12:24:07 (0) **    Note: Registry setup errors should be reported. Follow the steps related to registry issues.
.1791 12:24:07 (0) ** => After verifying the registry, if the WMI service does not start yet, you can try to
.1792 12:24:07 (0) **    to run the service as a STANDALONE service host or as a SHARED service host (SvcHost)
.1793 12:24:07 (0) **    You can achieve this by running ONE of the following commands:
.1794 12:24:07 (0) **    - to configure the service to run as a SHARED service host (recommended):
.1795 12:24:07 (0) **      i.e. 'WINMGMT.EXE /SharedHost'
.1796 12:24:07 (0) **    - if you have issue to get it running as a SHARED service host, the WMI service
.1797 12:24:07 (0) **      can be configured to run as a STANDALONE service host:
.1798 12:24:07 (0) **      i.e. 'WINMGMT.EXE /StandaloneHost'
.1799 12:24:07 (0) ** => If the registry is correct and the WMI service does not start yet, the WMI repository could be inconsistent.
.1800 12:24:07 (0) **    - Validating the repository consistency. In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1801 12:24:07 (0) **      to validate the WMI repository operations.
.1802 12:24:07 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1803 12:24:07 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1804 12:24:07 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
.1805 12:24:07 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1806 12:24:07 (0) **      the WMI repository must be reconstructed/recovered.
.1807 12:24:07 (0) **    - The repository can be recovered from a previous backup.
.1808 12:24:07 (0) **    Note: The System State backup or the System Restore snapshot contain a backup of
.1809 12:24:07 (0) **          of the WMI repository.
.1810 12:24:07 (0) ** => If no backup is available, you must rebuild the repository.
.1811 12:24:07 (0) **    - Re-run WMIDiag with the ShowMOFErrors, this will show any MOF file issues.
.1812 12:24:07 (0) **      i.e. 'WMIDiag ShowMOFErrors'
.1813 12:24:07 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1814 12:24:07 (0) **          otherwise some applications may fail after the reconstruction.
.1815 12:24:07 (0) **          This can be achieved with the following command:
.1816 12:24:07 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1817 12:24:07 (0) **    Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1818 12:24:07 (0) **          registry key will be excluded from the WMI repository reconstruction.
.1819 12:24:07 (0) **          This may imply the lost of WMI registration information.
.1820 12:24:07 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1821 12:24:07 (0) **          ALL fixes previously mentioned.
.1822 12:24:07 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1823 12:24:07 (0) **    - To rebuild the WMI repository, you must:
.1824 12:24:07 (0) **    - Reset the WMI repository
.1825 12:24:07 (0) **      (The WMI repository rebuilt is based on auto-recovery)
.1826 12:24:07 (0) **      i.e. 'WINMGMT /ResetRepository'
.1827 12:24:07 (0) **    OR
.1828 12:24:07 (0) **    - Salvage the WMI repository if you want to attempt the retrieval of good data from the
.1829 12:24:07 (0) **      inconsistent repository
.1830 12:24:07 (0) **      (The repository rebuilt is based on auto-recovery + salvage)
.1831 12:24:07 (0) **      i.e. 'WINMGMT /SalvageRepository'
.1832 12:24:07 (0) ** 
.1833 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1834 12:24:07 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1835 12:24:07 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 2 WARNING(S)!
.1836 12:24:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPMIPRV.DLL (\CLSID\{FD209E2E-813B-41C0-8646-4C3E9C917511}\InProcServer32)
.1837 12:24:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SERVERCOMPPROV.DLL (\CLSID\{9042E1B1-8FD4-4008-89FE-4040CC74575A}\InProcServer32)
.1838 12:24:07 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1839 12:24:07 (0) **    fail depending on the operation requested.
.1840 12:24:07 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1841 12:24:07 (0) ** 
.1842 12:24:07 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1843 12:24:07 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1844 12:24:07 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1845 12:24:07 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1846 12:24:07 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1847 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1848 12:24:07 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
.1849 12:24:07 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1850 12:24:07 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1851 12:24:07 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1852 12:24:07 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
.1853 12:24:07 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1854 12:24:07 (0) ** 
.1855 12:24:07 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.1856 12:24:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
.1857 12:24:07 (0) **        - REMOVED ACE:
.1858 12:24:07 (0) **          ACEType:  &h0
.1859 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1860 12:24:07 (0) **          ACEFlags: &h0
.1861 12:24:07 (0) **          ACEMask:  &h3
.1862 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1863 12:24:07 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
.1864 12:24:07 (0) ** 
.1865 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1866 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1867 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1868 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1869 12:24:07 (0) ** 
.1870 12:24:07 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.1871 12:24:07 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
.1872 12:24:07 (0) **        - REMOVED ACE:
.1873 12:24:07 (0) **          ACEType:  &h0
.1874 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1875 12:24:07 (0) **          ACEFlags: &h0
.1876 12:24:07 (0) **          ACEMask:  &h7
.1877 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1878 12:24:07 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
.1879 12:24:07 (0) **                    DCOM_RIGHT_ACCESS_REMOTE
.1880 12:24:07 (0) ** 
.1881 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1882 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1883 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1884 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1885 12:24:07 (0) ** 
.1886 12:24:07 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.1887 12:24:07 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
.1888 12:24:07 (0) **        - REMOVED ACE:
.1889 12:24:07 (0) **          ACEType:  &h0
.1890 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1891 12:24:07 (0) **          ACEFlags: &h0
.1892 12:24:07 (0) **          ACEMask:  &h7
.1893 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1894 12:24:07 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
.1895 12:24:07 (0) **                    DCOM_RIGHT_ACCESS_REMOTE
.1896 12:24:07 (0) ** 
.1897 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1898 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1899 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1900 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1901 12:24:07 (0) ** 
.1902 12:24:07 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1903 12:24:07 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1904 12:24:07 (0) **        - REMOVED ACE:
.1905 12:24:07 (0) **          ACEType:  &h0
.1906 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1907 12:24:07 (0) **          ACEFlags: &h0
.1908 12:24:07 (0) **          ACEMask:  &h1F
.1909 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1910 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1911 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1912 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1913 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1914 12:24:07 (0) ** 
.1915 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1916 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1917 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1918 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1919 12:24:07 (0) ** 
.1920 12:24:07 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1921 12:24:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.1922 12:24:07 (0) **        - REMOVED ACE:
.1923 12:24:07 (0) **          ACEType:  &h0
.1924 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1925 12:24:07 (0) **          ACEFlags: &h0
.1926 12:24:07 (0) **          ACEMask:  &h1F
.1927 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1928 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1929 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1930 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1931 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1932 12:24:07 (0) ** 
.1933 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1934 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1935 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1936 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1937 12:24:07 (0) ** 
.1938 12:24:07 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1939 12:24:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.1940 12:24:07 (0) **        - REMOVED ACE:
.1941 12:24:07 (0) **          ACEType:  &h0
.1942 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1943 12:24:07 (0) **          ACEFlags: &h0
.1944 12:24:07 (0) **          ACEMask:  &h1F
.1945 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1946 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1947 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1948 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1949 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1950 12:24:07 (0) ** 
.1951 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1952 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1953 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1954 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1955 12:24:07 (0) ** 
.1956 12:24:07 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.1957 12:24:07 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1958 12:24:07 (0) **        - REMOVED ACE:
.1959 12:24:07 (0) **          ACEType:  &h0
.1960 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1961 12:24:07 (0) **          ACEFlags: &h0
.1962 12:24:07 (0) **          ACEMask:  &h1F
.1963 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1964 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1965 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1966 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1967 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1968 12:24:07 (0) ** 
.1969 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1970 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1971 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1972 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1973 12:24:07 (0) ** 
.1974 12:24:07 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.1975 12:24:07 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
.1976 12:24:07 (0) **        - REMOVED ACE:
.1977 12:24:07 (0) **          ACEType:  &h0
.1978 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1979 12:24:07 (0) **          ACEFlags: &h0
.1980 12:24:07 (0) **          ACEMask:  &h1F
.1981 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.1982 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1983 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1984 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1985 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1986 12:24:07 (0) ** 
.1987 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1988 12:24:07 (0) **    Removing default security will cause some operations to fail!
.1989 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1990 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1991 12:24:07 (0) ** 
.1992 12:24:07 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.1993 12:24:07 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
.1994 12:24:07 (0) **        - REMOVED ACE:
.1995 12:24:07 (0) **          ACEType:  &h0
.1996 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1997 12:24:07 (0) **          ACEFlags: &h0
.1998 12:24:07 (0) **          ACEMask:  &hB
.1999 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.2000 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2001 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2002 12:24:07 (0) ** 
.2003 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2004 12:24:07 (0) **    Removing default security will cause some operations to fail!
.2005 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2006 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2007 12:24:07 (0) ** 
.2008 12:24:07 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2009 12:24:07 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.2010 12:24:07 (0) **        - REMOVED ACE:
.2011 12:24:07 (0) **          ACEType:  &h0
.2012 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2013 12:24:07 (0) **          ACEFlags: &h0
.2014 12:24:07 (0) **          ACEMask:  &h1F
.2015 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.2016 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2017 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2018 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2019 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2020 12:24:07 (0) ** 
.2021 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2022 12:24:07 (0) **    Removing default security will cause some operations to fail!
.2023 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2024 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2025 12:24:07 (0) ** 
.2026 12:24:07 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2027 12:24:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.2028 12:24:07 (0) **        - REMOVED ACE:
.2029 12:24:07 (0) **          ACEType:  &h0
.2030 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2031 12:24:07 (0) **          ACEFlags: &h0
.2032 12:24:07 (0) **          ACEMask:  &h1F
.2033 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.2034 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2035 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2036 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2037 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2038 12:24:07 (0) ** 
.2039 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2040 12:24:07 (0) **    Removing default security will cause some operations to fail!
.2041 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2042 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2043 12:24:07 (0) ** 
.2044 12:24:07 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2045 12:24:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.2046 12:24:07 (0) **        - REMOVED ACE:
.2047 12:24:07 (0) **          ACEType:  &h0
.2048 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2049 12:24:07 (0) **          ACEFlags: &h0
.2050 12:24:07 (0) **          ACEMask:  &h1F
.2051 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.2052 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2053 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2054 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2055 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2056 12:24:07 (0) ** 
.2057 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2058 12:24:07 (0) **    Removing default security will cause some operations to fail!
.2059 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2060 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2061 12:24:07 (0) ** 
.2062 12:24:07 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2063 12:24:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
.2064 12:24:07 (0) **        - REMOVED ACE:
.2065 12:24:07 (0) **          ACEType:  &h0
.2066 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2067 12:24:07 (0) **          ACEFlags: &h0
.2068 12:24:07 (0) **          ACEMask:  &h1F
.2069 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.2070 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2071 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2072 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2073 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2074 12:24:07 (0) ** 
.2075 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2076 12:24:07 (0) **    Removing default security will cause some operations to fail!
.2077 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2078 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2079 12:24:07 (0) ** 
.2080 12:24:07 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2081 12:24:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
.2082 12:24:07 (0) **        - REMOVED ACE:
.2083 12:24:07 (0) **          ACEType:  &h0
.2084 12:24:07 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2085 12:24:07 (0) **          ACEFlags: &h0
.2086 12:24:07 (0) **          ACEMask:  &h1F
.2087 12:24:07 (0) **                    DCOM_RIGHT_EXECUTE
.2088 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2089 12:24:07 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2090 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2091 12:24:07 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2092 12:24:07 (0) ** 
.2093 12:24:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2094 12:24:07 (0) **    Removing default security will cause some operations to fail!
.2095 12:24:07 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2096 12:24:07 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2097 12:24:07 (0) ** 
.2098 12:24:07 (0) ** 
.2099 12:24:07 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
.2100 12:24:07 (0) ** DCOM security error(s) detected: .................................................................................... 14.
.2101 12:24:07 (0) ** WMI security warning(s) detected: ................................................................................... 0.
.2102 12:24:07 (0) ** WMI security error(s) detected: ..................................................................................... 0.
.2103 12:24:07 (0) ** 
.2104 12:24:07 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
.2105 12:24:07 (0) ** Overall WMI security status: ........................................................................................ OK.
.2106 12:24:07 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.2107 12:24:07 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.2108 12:24:07 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.2109 12:24:07 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.2110 12:24:07 (0) ** - Root, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2111 12:24:07 (0) ** 
.2112 12:24:07 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
.2113 12:24:07 (0) ** - Root, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2114 12:24:07 (0) ** - Root, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2115 12:24:07 (0) ** - Root/subscription, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2116 12:24:07 (0) ** - Root/DEFAULT, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2117 12:24:07 (0) ** - Root/CIMV2, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2118 12:24:07 (0) ** - Root/CIMV2/Security, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2119 12:24:07 (0) ** - Root/CIMV2/Applications, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2120 12:24:07 (0) ** - Root/nap, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2121 12:24:07 (0) ** - Root/SECURITY, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2122 12:24:07 (0) ** - Root/WMI, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2123 12:24:07 (0) ** - Root/directory, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2124 12:24:07 (0) ** - Root/directory/LDAP, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2125 12:24:07 (0) ** - Root/SecurityCenter, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2126 12:24:07 (0) ** - Root/Microsoft, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2127 12:24:07 (0) ** - Root/Microsoft/HomeNet, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2128 12:24:07 (0) ** - Root/aspnet, 0x8007043B - Program wykonywalny w którym ta usługa (zgodnie z jej konfiguracją) ma być uruchomiona nie implementuje usługi..
.2129 12:24:07 (0) ** 
.2130 12:24:07 (0) ** WMI GET operations: ................................................................................................. OK.
.2131 12:24:07 (0) ** WMI MOF representations: ............................................................................................ OK.
.2132 12:24:07 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.2133 12:24:07 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.2134 12:24:07 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.2135 12:24:07 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.2136 12:24:07 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.2137 12:24:07 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.2138 12:24:07 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.2139 12:24:07 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.2140 12:24:07 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.2141 12:24:07 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.2142 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2143 12:24:07 (0) ** 
.2144 12:24:07 (0) ** 17 error(s) 0x8007043B - (WBEM_UNKNOWN) This error code is external to WMI.
.2145 12:24:07 (0) ** => This error is not a WMI error. It is typically due to one of the following WMI service
.2146 12:24:07 (0) **    configuration issue:
.2147 12:24:07 (0) **    - The WMI service was configured to run as a standalone service host and has being updated to
.2148 12:24:07 (0) **      to run as a shared service host but the configuration is incomplete or not refreshed.
.2149 12:24:07 (0) **    - The Windows Service Host (SvcHost) contains invalid information.
.2150 12:24:07 (0) ** => You can fix this issue by running the following command (case sensitive):
.2151 12:24:07 (0) **    'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToShared'
.2152 12:24:07 (0) ** => Reboot the system.
.2153 12:24:07 (0) ** 
.2154 12:24:07 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
.2155 12:24:07 (0) **    with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x043B) 
.2156 12:24:07 (0) **    converted in decimal (1083).
.2157 12:24:07 (0) **    - NET HELPMSG 1083
.2158 12:24:07 (0) ** 
.2159 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2160 12:24:07 (0) ** WMI Registry key setup: ............................................................................................. OK.
.2161 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2162 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2163 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2164 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2165 12:24:07 (0) ** 
.2166 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2167 12:24:07 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.2168 12:24:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2169 12:24:07 (0) ** 
.2170 12:24:07 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\ASUS\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN7_.CLI.SP1.64_ASUS-KOMPUTER_2016.05.07_12.23.54.LOG' for details.
.2171 12:24:07 (0) ** 
.2172 12:24:07 (0) ** WMIDiag v2.2 ended on 7 maja 2016 at 12:24 (W:49 E:43 S:1).