.1716 13:38:29 (0) ** WMIDiag v2.2 started on 24 września 2016 at 13:38.
.1717 13:38:29 (0) ** 
.1718 13:38:29 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1719 13:38:29 (0) ** 
.1720 13:38:29 (0) ** This script is not supported under any Microsoft standard support program or service.
.1721 13:38:29 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1722 13:38:29 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1723 13:38:29 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1724 13:38:29 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1725 13:38:29 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1726 13:38:29 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1727 13:38:29 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1728 13:38:29 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1729 13:38:29 (0) ** of the possibility of such damages.
.1730 13:38:29 (0) ** 
.1731 13:38:29 (0) ** 
.1732 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1733 13:38:29 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1734 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1735 13:38:29 (0) ** 
.1736 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1737 13:38:29 (0) ** Windows 8.1 - No Service Pack - 64-bit (9600) - User 'PIOTR-MISIASZEK\PIOTR' on computer 'PIOTR-MISIASZEK'.
.1738 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1739 13:38:29 (0) ** Environment: ........................................................................................................ OK.
.1740 13:38:29 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1741 13:38:29 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1742 13:38:29 (0) ** WMI repository state: ............................................................................................... N/A.
.1743 13:38:29 (0) ** AFTER running WMIDiag:
.1744 13:38:29 (0) ** The WMI repository has a size of: ................................................................................... 29 MB.
.1745 13:38:29 (0) ** - Disk free space on 'C:': .......................................................................................... 119212 MB.
.1746 13:38:29 (0) **   - INDEX.BTR,                     5398528 bytes,      2016-02-17 19:00:48
.1747 13:38:29 (0) **   - MAPPING1.MAP,                  81852 bytes,        2016-02-17 18:53:13
.1748 13:38:29 (0) **   - MAPPING2.MAP,                  81852 bytes,        2016-02-17 19:40:39
.1749 13:38:29 (0) **   - OBJECTS.DATA,                  24879104 bytes,     2016-02-17 19:00:47
.1750 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1751 13:38:29 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
.1752 13:38:29 (0) ** Windows Firewall Profile: ........................................................................................... PRIVATE.
.1753 13:38:29 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
.1754 13:38:29 (0) ** => This will prevent any WMI remote connectivity to this computer except
.1755 13:38:29 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
.1756 13:38:29 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
.1757 13:38:29 (0) **    - 'Windows Management Instrumentation (WMI-In)'
.1758 13:38:29 (0) **    - 'Windows Management Instrumentation (ASync-In)'
.1759 13:38:29 (0) **    Verify the reported status for each of these three inbound rules below.
.1760 13:38:29 (0) ** 
.1761 13:38:29 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
.1762 13:38:29 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
.1763 13:38:29 (0) **    - You can adjust the configuration by executing the following command:
.1764 13:38:29 (0) **    i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
.1765 13:38:29 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
.1766 13:38:29 (0) **       You can also enable each individual rule instead of activating the group rule.
.1767 13:38:29 (0) ** 
.1768 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1769 13:38:29 (0) ** DCOM Status: ........................................................................................................ OK.
.1770 13:38:29 (1) !! ERROR: WMI registry setup: .......................................................................................... DISABLED!
.1771 13:38:29 (0) ** => The WMI service automatic startup is DISABLED!
.1772 13:38:29 (0) **    - It is a best practice for manageability purposes to start
.1773 13:38:29 (0) **      the WMI service at computer startup (automactic startup).
.1774 13:38:29 (0) ** => The service startup state can be changed with the SERVICES MMC snap-in.
.1775 13:38:29 (0) **    or with the the command:
.1776 13:38:29 (0) **    i.e. 'SC.EXE CONFIG WINMGMT START= AUTO'
.1777 13:38:29 (0) **    Note: The SC.EXE command is available in the Windows Resource Kit.
.1778 13:38:29 (0) ** => You can also check the registry key setup further in this report.
.1779 13:38:29 (0) ** 
.1780 13:38:29 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1781 13:38:29 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1782 13:38:29 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
.1783 13:38:29 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1784 13:38:29 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1785 13:38:29 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1786 13:38:29 (0) **          this can prevent the service/application to work as expected.
.1787 13:38:29 (0) ** 
.1788 13:38:29 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1789 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1790 13:38:29 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1791 13:38:29 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1792 13:38:29 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1793 13:38:29 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1794 13:38:29 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1795 13:38:29 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1796 13:38:29 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1797 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1798 13:38:29 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.1799 13:38:29 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.1800 13:38:29 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
.1801 13:38:29 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.1802 13:38:29 (0) **         selecting 'Run as Administrator'.
.1803 13:38:29 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
.1804 13:38:29 (0) **         in the Task Scheduler within the right security context.
.1805 13:38:29 (0) ** 
.1806 13:38:29 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1807 13:38:29 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1808 13:38:29 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1809 13:38:29 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
.1810 13:38:29 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1811 13:38:29 (0) ** 
.1812 13:38:29 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.1813 13:38:29 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
.1814 13:38:29 (0) **        - REMOVED ACE:
.1815 13:38:29 (0) **          ACEType:  &h0
.1816 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1817 13:38:29 (0) **          ACEFlags: &h0
.1818 13:38:29 (0) **          ACEMask:  &h3
.1819 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1820 13:38:29 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
.1821 13:38:29 (0) ** 
.1822 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1823 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1824 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1825 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1826 13:38:29 (0) ** 
.1827 13:38:29 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.1828 13:38:29 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
.1829 13:38:29 (0) **        - REMOVED ACE:
.1830 13:38:29 (0) **          ACEType:  &h0
.1831 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1832 13:38:29 (0) **          ACEFlags: &h0
.1833 13:38:29 (0) **          ACEMask:  &h7
.1834 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1835 13:38:29 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
.1836 13:38:29 (0) **                    DCOM_RIGHT_ACCESS_REMOTE
.1837 13:38:29 (0) ** 
.1838 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1839 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1840 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1841 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1842 13:38:29 (0) ** 
.1843 13:38:29 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.1844 13:38:29 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
.1845 13:38:29 (0) **        - REMOVED ACE:
.1846 13:38:29 (0) **          ACEType:  &h0
.1847 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1848 13:38:29 (0) **          ACEFlags: &h0
.1849 13:38:29 (0) **          ACEMask:  &h7
.1850 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1851 13:38:29 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
.1852 13:38:29 (0) **                    DCOM_RIGHT_ACCESS_REMOTE
.1853 13:38:29 (0) ** 
.1854 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1855 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1856 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1857 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1858 13:38:29 (0) ** 
.1859 13:38:29 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1860 13:38:29 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1861 13:38:29 (0) **        - REMOVED ACE:
.1862 13:38:29 (0) **          ACEType:  &h0
.1863 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1864 13:38:29 (0) **          ACEFlags: &h0
.1865 13:38:29 (0) **          ACEMask:  &h1F
.1866 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1867 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1868 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1869 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1870 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1871 13:38:29 (0) ** 
.1872 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1873 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1874 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1875 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1876 13:38:29 (0) ** 
.1877 13:38:29 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1878 13:38:29 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.1879 13:38:29 (0) **        - REMOVED ACE:
.1880 13:38:29 (0) **          ACEType:  &h0
.1881 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1882 13:38:29 (0) **          ACEFlags: &h0
.1883 13:38:29 (0) **          ACEMask:  &h1F
.1884 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1885 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1886 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1887 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1888 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1889 13:38:29 (0) ** 
.1890 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1891 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1892 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1893 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1894 13:38:29 (0) ** 
.1895 13:38:29 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.1896 13:38:29 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.1897 13:38:29 (0) **        - REMOVED ACE:
.1898 13:38:29 (0) **          ACEType:  &h0
.1899 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1900 13:38:29 (0) **          ACEFlags: &h0
.1901 13:38:29 (0) **          ACEMask:  &h1F
.1902 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1903 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1904 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1905 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1906 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1907 13:38:29 (0) ** 
.1908 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1909 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1910 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1911 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1912 13:38:29 (0) ** 
.1913 13:38:29 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.1914 13:38:29 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1915 13:38:29 (0) **        - REMOVED ACE:
.1916 13:38:29 (0) **          ACEType:  &h0
.1917 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1918 13:38:29 (0) **          ACEFlags: &h0
.1919 13:38:29 (0) **          ACEMask:  &h1F
.1920 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1921 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1922 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1923 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1924 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1925 13:38:29 (0) ** 
.1926 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1927 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1928 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1929 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1930 13:38:29 (0) ** 
.1931 13:38:29 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.1932 13:38:29 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
.1933 13:38:29 (0) **        - REMOVED ACE:
.1934 13:38:29 (0) **          ACEType:  &h0
.1935 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1936 13:38:29 (0) **          ACEFlags: &h0
.1937 13:38:29 (0) **          ACEMask:  &h1F
.1938 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1939 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1940 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1941 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1942 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1943 13:38:29 (0) ** 
.1944 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1945 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1946 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1947 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1948 13:38:29 (0) ** 
.1949 13:38:29 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.1950 13:38:29 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
.1951 13:38:29 (0) **        - REMOVED ACE:
.1952 13:38:29 (0) **          ACEType:  &h0
.1953 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1954 13:38:29 (0) **          ACEFlags: &h0
.1955 13:38:29 (0) **          ACEMask:  &hB
.1956 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1957 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1958 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1959 13:38:29 (0) ** 
.1960 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1961 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1962 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1963 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1964 13:38:29 (0) ** 
.1965 13:38:29 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1966 13:38:29 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1967 13:38:29 (0) **        - REMOVED ACE:
.1968 13:38:29 (0) **          ACEType:  &h0
.1969 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1970 13:38:29 (0) **          ACEFlags: &h0
.1971 13:38:29 (0) **          ACEMask:  &h1F
.1972 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1973 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1974 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1975 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1976 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1977 13:38:29 (0) ** 
.1978 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1979 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1980 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1981 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1982 13:38:29 (0) ** 
.1983 13:38:29 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1984 13:38:29 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.1985 13:38:29 (0) **        - REMOVED ACE:
.1986 13:38:29 (0) **          ACEType:  &h0
.1987 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1988 13:38:29 (0) **          ACEFlags: &h0
.1989 13:38:29 (0) **          ACEMask:  &h1F
.1990 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.1991 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1992 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1993 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1994 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1995 13:38:29 (0) ** 
.1996 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1997 13:38:29 (0) **    Removing default security will cause some operations to fail!
.1998 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1999 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2000 13:38:29 (0) ** 
.2001 13:38:29 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2002 13:38:29 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.2003 13:38:29 (0) **        - REMOVED ACE:
.2004 13:38:29 (0) **          ACEType:  &h0
.2005 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2006 13:38:29 (0) **          ACEFlags: &h0
.2007 13:38:29 (0) **          ACEMask:  &h1F
.2008 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.2009 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2010 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2011 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2012 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2013 13:38:29 (0) ** 
.2014 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2015 13:38:29 (0) **    Removing default security will cause some operations to fail!
.2016 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2017 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2018 13:38:29 (0) ** 
.2019 13:38:29 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2020 13:38:29 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
.2021 13:38:29 (0) **        - REMOVED ACE:
.2022 13:38:29 (0) **          ACEType:  &h0
.2023 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2024 13:38:29 (0) **          ACEFlags: &h0
.2025 13:38:29 (0) **          ACEMask:  &h1F
.2026 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.2027 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2028 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2029 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2030 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2031 13:38:29 (0) ** 
.2032 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2033 13:38:29 (0) **    Removing default security will cause some operations to fail!
.2034 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2035 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2036 13:38:29 (0) ** 
.2037 13:38:29 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2038 13:38:29 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
.2039 13:38:29 (0) **        - REMOVED ACE:
.2040 13:38:29 (0) **          ACEType:  &h0
.2041 13:38:29 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.2042 13:38:29 (0) **          ACEFlags: &h0
.2043 13:38:29 (0) **          ACEMask:  &h1F
.2044 13:38:29 (0) **                    DCOM_RIGHT_EXECUTE
.2045 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.2046 13:38:29 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.2047 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.2048 13:38:29 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.2049 13:38:29 (0) ** 
.2050 13:38:29 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2051 13:38:29 (0) **    Removing default security will cause some operations to fail!
.2052 13:38:29 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2053 13:38:29 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2054 13:38:29 (0) ** 
.2055 13:38:29 (0) ** 
.2056 13:38:29 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
.2057 13:38:29 (0) ** DCOM security error(s) detected: .................................................................................... 14.
.2058 13:38:29 (0) ** WMI security warning(s) detected: ................................................................................... 0.
.2059 13:38:29 (0) ** WMI security error(s) detected: ..................................................................................... 0.
.2060 13:38:29 (0) ** 
.2061 13:38:29 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
.2062 13:38:29 (0) ** Overall WMI security status: ........................................................................................ OK.
.2063 13:38:29 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.2064 13:38:29 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.2065 13:38:29 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.2066 13:38:29 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.2067 13:38:29 (0) ** - Root, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2068 13:38:29 (0) ** 
.2069 13:38:29 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 17 ERROR(S)!
.2070 13:38:29 (0) ** - Root, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2071 13:38:29 (0) ** - Root, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2072 13:38:29 (0) ** - Root/subscription, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2073 13:38:29 (0) ** - Root/DEFAULT, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2074 13:38:29 (0) ** - Root/CIMV2, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2075 13:38:29 (0) ** - Root/CIMV2/Security, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2076 13:38:29 (0) ** - Root/CIMV2/Applications, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2077 13:38:29 (0) ** - Root/nap, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2078 13:38:29 (0) ** - Root/SECURITY, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2079 13:38:29 (0) ** - Root/STANDARDCIMV2, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2080 13:38:29 (0) ** - Root/WMI, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2081 13:38:29 (0) ** - Root/directory, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2082 13:38:29 (0) ** - Root/directory/LDAP, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2083 13:38:29 (0) ** - Root/SecurityCenter, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2084 13:38:29 (0) ** - Root/Microsoft, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2085 13:38:29 (0) ** - Root/Microsoft/HomeNet, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2086 13:38:29 (0) ** - Root/aspnet, 0x80070422 - Nie można uruchomić określonej usługi ponieważ jest ona wyłączona lub ponieważ nie są włączone skojarzone z nią urządzenia..
.2087 13:38:29 (0) ** 
.2088 13:38:29 (0) ** WMI GET operations: ................................................................................................. OK.
.2089 13:38:29 (0) ** WMI MOF representations: ............................................................................................ OK.
.2090 13:38:29 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.2091 13:38:29 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.2092 13:38:29 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.2093 13:38:29 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.2094 13:38:29 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.2095 13:38:29 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.2096 13:38:29 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.2097 13:38:29 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.2098 13:38:29 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.2099 13:38:29 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.2100 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2101 13:38:29 (0) ** 
.2102 13:38:29 (0) ** 18 error(s) 0x80070422 - (WBEM_UNKNOWN) This error code is external to WMI.
.2103 13:38:29 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
.2104 13:38:29 (0) **    with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x0422) 
.2105 13:38:29 (0) **    converted in decimal (1058).
.2106 13:38:29 (0) **    - NET HELPMSG 1058
.2107 13:38:29 (0) ** 
.2108 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2109 13:38:29 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
.2110 13:38:29 (1) !! ERROR: Unexpected registry key value:
.2111 13:38:29 (0) **   - Current:  HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h4
.2112 13:38:29 (0) **   - Expected: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h2
.2113 13:38:29 (0) **     From the command line, the registry configuration can be corrected with the following command:
.2114 13:38:29 (0) **     i.e. 'REG.EXE Add "HKLM\SYSTEM\CurrentControlSet\Services\winmgmt" /v "Start" /t "REG_DWORD" /d "2" /f'
.2115 13:38:29 (0) ** 
.2116 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2117 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2118 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2119 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2120 13:38:29 (0) ** 
.2121 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2122 13:38:29 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.2123 13:38:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2124 13:38:29 (0) ** 
.2125 13:38:29 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\ADMIN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN8.1_.CLI.RTM.64_PIOTR-MISIASZEK_2016.09.24_13.38.07.LOG' for details.
.2126 13:38:29 (0) ** 
.2127 13:38:29 (0) ** WMIDiag v2.2 ended on 24 września 2016 at 13:38 (W:48 E:45 S:1).