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