27164 23:33:40 (0) ** WMIDiag v2.2 started on 10 августа 2020 г. at 23:28.
27165 23:33:40 (0) ** 
27166 23:33:40 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
27167 23:33:40 (0) ** 
27168 23:33:40 (0) ** This script is not supported under any Microsoft standard support program or service.
27169 23:33:40 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
27170 23:33:40 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
27171 23:33:40 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
27172 23:33:40 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
27173 23:33:40 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
27174 23:33:40 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
27175 23:33:40 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
27176 23:33:40 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
27177 23:33:40 (0) ** of the possibility of such damages.
27178 23:33:40 (0) ** 
27179 23:33:40 (0) ** 
27180 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27181 23:33:40 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
27182 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27183 23:33:40 (0) ** 
27184 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27185 23:33:40 (0) ** Windows 7 - Service Pack 1 - 64-bit (7601) - User 'HP-P17-LT\YAROSLAV' on computer 'HP-P17-LT'.
27186 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27187 23:33:40 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
27188 23:33:40 (0) ** INFO: => 4 possible incorrect shutdown(s) detected on:
27189 23:33:40 (0) **          - Shutdown on 06 August 2020 02:35:25 (GMT-0).
27190 23:33:40 (0) **          - Shutdown on 07 August 2020 19:25:55 (GMT-0).
27191 23:33:40 (0) **          - Shutdown on 07 August 2020 19:45:03 (GMT-0).
27192 23:33:40 (0) **          - Shutdown on 09 August 2020 16:18:19 (GMT-0).
27193 23:33:40 (0) ** 
27194 23:33:40 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #2).
27195 23:33:40 (0) ** Drive type: ......................................................................................................... IDE (HGST HTS721010A9E630 SCSI Disk Device).
27196 23:33:40 (0) ** There are no missing WMI system files: .............................................................................. OK.
27197 23:33:40 (0) ** There are no missing WMI repository files: .......................................................................... OK.
27198 23:33:40 (0) ** WMI repository state: ............................................................................................... N/A.
27199 23:33:40 (0) ** AFTER running WMIDiag:
27200 23:33:40 (0) ** The WMI repository has a size of: ................................................................................... 14 MB.
27201 23:33:40 (0) ** - Disk free space on 'C:': .......................................................................................... 9805 MB.
27202 23:33:40 (0) **   - INDEX.BTR,                     2433024 bytes,      10.08.2020 23:30:54
27203 23:33:40 (0) **   - MAPPING1.MAP,                  42224 bytes,        10.08.2020 23:30:54
27204 23:33:40 (0) **   - MAPPING2.MAP,                  42224 bytes,        10.08.2020 23:30:54
27205 23:33:40 (0) **   - OBJECTS.DATA,                  12632064 bytes,     10.08.2020 23:30:54
27206 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27207 23:33:40 (2) !! WARNING: Windows Firewall Service: .................................................................................. STOPPED.
27208 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27209 23:33:40 (0) ** DCOM Status: ........................................................................................................ OK.
27210 23:33:40 (0) ** WMI registry setup: ................................................................................................. OK.
27211 23:33:40 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
27212 23:33:40 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
27213 23:33:40 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
27214 23:33:40 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
27215 23:33:40 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
27216 23:33:40 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
27217 23:33:40 (0) **          this can prevent the service/application to work as expected.
27218 23:33:40 (0) ** 
27219 23:33:40 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
27220 23:33:40 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
27221 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27222 23:33:40 (0) ** WMI service DCOM setup: ............................................................................................. OK.
27223 23:33:40 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 2 WARNING(S)!
27224 23:33:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPMIPRV.DLL (\CLSID\{FD209E2E-813B-41C0-8646-4C3E9C917511}\InProcServer32)
27225 23:33:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SERVERCOMPPROV.DLL (\CLSID\{9042E1B1-8FD4-4008-89FE-4040CC74575A}\InProcServer32)
27226 23:33:40 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
27227 23:33:40 (0) **    fail depending on the operation requested.
27228 23:33:40 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
27229 23:33:40 (0) ** 
27230 23:33:40 (0) ** WMI ProgID registrations: ........................................................................................... OK.
27231 23:33:40 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
27232 23:33:40 (2) !! WARNING: WMI provider CIM registrations missing for the following provider(s): ...................................... 1 WARNING(S)!
27233 23:33:40 (0) ** - ROOT/WMI, Provider_BIOSInterface (i.e. WMI Class 'HPBIOS_BIOSEvent')
27234 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27235 23:33:40 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
27236 23:33:40 (0) **    while the CIM registration is wrong or missing. This can be due to:
27237 23:33:40 (0) **    - a de-installation of the software.
27238 23:33:40 (0) **    - a deletion of some CIM registration information.
27239 23:33:40 (0) ** => You can correct the CIM configuration by:
27240 23:33:40 (0) **    - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
27241 23:33:40 (0) **    Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
27242 23:33:40 (0) **          (This list can be built on a similar and working WMI Windows installation)
27243 23:33:40 (0) **          The following command line must be used:
27244 23:33:40 (0) **          i.e. 'WMIDiag CorrelateClassAndProvider'
27245 23:33:40 (0) **    - Re-installing the software.
27246 23:33:40 (0) ** => If the software has been de-installed intentionally, then this information must be
27247 23:33:40 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider
27248 23:33:40 (0) **    registration data and its set of associated classes.
27249 23:33:40 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\WMI path __Win32Provider Where Name='Provider_BIOSInterface' DELETE'
27250 23:33:40 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\WMI Class HPBIOS_BIOSEvent DELETE'
27251 23:33:40 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
27252 23:33:40 (0) **    the namespace and ALL its content can be ENTIRELY deleted.
27253 23:33:40 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='WMI' DELETE'
27254 23:33:40 (0) ** 
27255 23:33:40 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
27256 23:33:40 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
27257 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27258 23:33:40 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
27259 23:33:40 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
27260 23:33:40 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
27261 23:33:40 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
27262 23:33:40 (0) **         selecting 'Run as Administrator'.
27263 23:33:40 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
27264 23:33:40 (0) **         in the Task Scheduler within the right security context.
27265 23:33:40 (0) ** 
27266 23:33:40 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
27267 23:33:40 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
27268 23:33:40 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
27269 23:33:40 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
27270 23:33:40 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
27271 23:33:40 (0) ** 
27272 23:33:40 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Default): .................................................. MODIFIED.
27273 23:33:40 (1) !! ERROR: Default trustee 'NT AUTHORITY\SELF' has been REMOVED!
27274 23:33:40 (0) **        - REMOVED ACE:
27275 23:33:40 (0) **          ACEType:  &h0
27276 23:33:40 (0) **                    ACCESS_ALLOWED_ACE_TYPE
27277 23:33:40 (0) **          ACEFlags: &h0
27278 23:33:40 (0) **          ACEMask:  &h7
27279 23:33:40 (0) **                    DCOM_RIGHT_EXECUTE
27280 23:33:40 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
27281 23:33:40 (0) **                    DCOM_RIGHT_ACCESS_REMOTE
27282 23:33:40 (0) ** 
27283 23:33:40 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
27284 23:33:40 (0) **    Removing default security will cause some operations to fail!
27285 23:33:40 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
27286 23:33:40 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
27287 23:33:40 (0) ** 
27288 23:33:40 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Default): .................................................. MODIFIED.
27289 23:33:40 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
27290 23:33:40 (0) **        - REMOVED ACE:
27291 23:33:40 (0) **          ACEType:  &h0
27292 23:33:40 (0) **                    ACCESS_ALLOWED_ACE_TYPE
27293 23:33:40 (0) **          ACEFlags: &h0
27294 23:33:40 (0) **          ACEMask:  &h3
27295 23:33:40 (0) **                    DCOM_RIGHT_EXECUTE
27296 23:33:40 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
27297 23:33:40 (0) ** 
27298 23:33:40 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
27299 23:33:40 (0) **    Removing default security will cause some operations to fail!
27300 23:33:40 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
27301 23:33:40 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
27302 23:33:40 (0) ** 
27303 23:33:40 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
27304 23:33:40 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
27305 23:33:40 (0) **        - REMOVED ACE:
27306 23:33:40 (0) **          ACEType:  &h0
27307 23:33:40 (0) **                    ACCESS_ALLOWED_ACE_TYPE
27308 23:33:40 (0) **          ACEFlags: &h0
27309 23:33:40 (0) **          ACEMask:  &h1F
27310 23:33:40 (0) **                    DCOM_RIGHT_EXECUTE
27311 23:33:40 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
27312 23:33:40 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
27313 23:33:40 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
27314 23:33:40 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
27315 23:33:40 (0) ** 
27316 23:33:40 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
27317 23:33:40 (0) **    Removing default security will cause some operations to fail!
27318 23:33:40 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
27319 23:33:40 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
27320 23:33:40 (0) ** 
27321 23:33:40 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
27322 23:33:40 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
27323 23:33:40 (0) **        - REMOVED ACE:
27324 23:33:40 (0) **          ACEType:  &h0
27325 23:33:40 (0) **                    ACCESS_ALLOWED_ACE_TYPE
27326 23:33:40 (0) **          ACEFlags: &h0
27327 23:33:40 (0) **          ACEMask:  &h1F
27328 23:33:40 (0) **                    DCOM_RIGHT_EXECUTE
27329 23:33:40 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
27330 23:33:40 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
27331 23:33:40 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
27332 23:33:40 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
27333 23:33:40 (0) ** 
27334 23:33:40 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
27335 23:33:40 (0) **    Removing default security will cause some operations to fail!
27336 23:33:40 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
27337 23:33:40 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
27338 23:33:40 (0) ** 
27339 23:33:40 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
27340 23:33:40 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
27341 23:33:40 (0) **        - REMOVED ACE:
27342 23:33:40 (0) **          ACEType:  &h0
27343 23:33:40 (0) **                    ACCESS_ALLOWED_ACE_TYPE
27344 23:33:40 (0) **          ACEFlags: &h0
27345 23:33:40 (0) **          ACEMask:  &h1F
27346 23:33:40 (0) **                    DCOM_RIGHT_EXECUTE
27347 23:33:40 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
27348 23:33:40 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
27349 23:33:40 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
27350 23:33:40 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
27351 23:33:40 (0) ** 
27352 23:33:40 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
27353 23:33:40 (0) **    Removing default security will cause some operations to fail!
27354 23:33:40 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
27355 23:33:40 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
27356 23:33:40 (0) ** 
27357 23:33:40 (0) ** 
27358 23:33:40 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
27359 23:33:40 (0) ** DCOM security error(s) detected: .................................................................................... 5.
27360 23:33:40 (0) ** WMI security warning(s) detected: ................................................................................... 0.
27361 23:33:40 (0) ** WMI security error(s) detected: ..................................................................................... 0.
27362 23:33:40 (0) ** 
27363 23:33:40 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
27364 23:33:40 (0) ** Overall WMI security status: ........................................................................................ OK.
27365 23:33:40 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
27366 23:33:40 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
27367 23:33:40 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
27368 23:33:40 (0) **   'select * from MSFT_SCMEventLogEvent'
27369 23:33:40 (0) ** 
27370 23:33:40 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
27371 23:33:40 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 4 NAMESPACE(S)!
27372 23:33:40 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
27373 23:33:40 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTVOLUMEENCRYPTION.
27374 23:33:40 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
27375 23:33:40 (0) ** - ROOT/SERVICEMODEL.
27376 23:33:40 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
27377 23:33:40 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
27378 23:33:40 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
27379 23:33:40 (0) **    i.e. 'WMIC.EXE /NODE:"HP-P17-LT" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
27380 23:33:40 (0) ** 
27381 23:33:40 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
27382 23:33:40 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 2 ERROR(S)!
27383 23:33:40 (0) ** - Root/directory, 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found.
27384 23:33:40 (0) ** - Root/directory/LDAP, 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found.
27385 23:33:40 (0) ** 
27386 23:33:40 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 29 ERROR(S)!
27387 23:33:40 (0) ** - Root/CIMV2, Win32_PnPSignedDriver, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27388 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27389 23:33:40 (0) ** - Root/CIMV2, Win32_PnPSignedDriverCIMDataFile, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27390 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27391 23:33:40 (0) ** - Root/CIMV2, Win32_PerfFormattedData_MSDTC_DistributedTransactionCoordinator, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27392 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27393 23:33:40 (0) ** - Root/CIMV2, Win32_PerfRawData_MSDTC_DistributedTransactionCoordinator, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27394 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27395 23:33:40 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27396 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27397 23:33:40 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27398 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27399 23:33:40 (0) ** - Root/CIMV2, Win32_PerfFormattedData_RemoteAccess_RASPort, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27400 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27401 23:33:40 (0) ** - Root/CIMV2, Win32_PerfRawData_RemoteAccess_RASPort, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27402 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27403 23:33:40 (0) ** - Root/CIMV2, Win32_PerfFormattedData_RemoteAccess_RASTotal, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27404 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27405 23:33:40 (0) ** - Root/CIMV2, Win32_PerfRawData_RemoteAccess_RASTotal, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27406 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27407 23:33:40 (0) ** - Root/WMI, BcdStore, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27408 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27409 23:33:40 (0) ** - Root/WMI, BcdElement, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27410 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27411 23:33:40 (0) ** - Root/WMI, BcdObjectElement, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27412 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27413 23:33:40 (0) ** - Root/WMI, BcdDeviceElement, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27414 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27415 23:33:40 (0) ** - Root/WMI, BcdStringElement, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27416 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27417 23:33:40 (0) ** - Root/WMI, BcdBooleanElement, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27418 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27419 23:33:40 (0) ** - Root/WMI, BcdIntegerElement, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27420 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27421 23:33:40 (0) ** - Root/WMI, BcdObjectListElement, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27422 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27423 23:33:40 (0) ** - Root/WMI, MSNT_FileBaseTrace_VolumeToLog, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27424 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27425 23:33:40 (0) ** - Root/WMI, MSNT_FileBaseTrace_Set1, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27426 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27427 23:33:40 (0) ** - Root/WMI, FileTrace, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27428 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27429 23:33:40 (0) ** - Root/WMI, FileOperation, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27430 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27431 23:33:40 (0) ** - Root/WMI, WinLogon, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27432 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27433 23:33:40 (0) ** - Root/WMI, RFSMon, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27434 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27435 23:33:40 (0) ** - Root/WMI, BcdDeviceData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27436 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27437 23:33:40 (0) ** - Root/WMI, BcdDeviceFileData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27438 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27439 23:33:40 (0) ** - Root/WMI, BcdDevicePartitionData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27440 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27441 23:33:40 (0) ** - Root/WMI, BcdDeviceUnknownData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27442 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27443 23:33:40 (0) ** - Root/WMI, BcdObject, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27444 23:33:40 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
27445 23:33:40 (0) ** 
27446 23:33:40 (0) ** WMI MOF representations: ............................................................................................ OK.
27447 23:33:40 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
27448 23:33:40 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
27449 23:33:40 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
27450 23:33:40 (1) !! ERROR: WMI GET VALUE operation errors reported: ..................................................................... 1 ERROR(S)!
27451 23:33:40 (0) ** - Root/CIMV2, Instance: Win32_Service='WSCSVC', Property: Displayname='Центр обеспечения безопасности' (Expected default='Security Center').
27452 23:33:40 (0) ** 
27453 23:33:40 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
27454 23:33:40 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
27455 23:33:40 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
27456 23:33:40 (0) ** WMI static instances retrieved: ..................................................................................... 605.
27457 23:33:40 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
27458 23:33:40 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
27459 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27460 23:33:40 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
27461 23:33:40 (0) **   DCOM: ............................................................................................................. 0.
27462 23:33:40 (0) **   WINMGMT: .......................................................................................................... 0.
27463 23:33:40 (0) **   WMIADAPTER: ....................................................................................................... 0.
27464 23:33:40 (0) ** 
27465 23:33:40 (0) ** # of additional Event Log events AFTER WMIDiag execution:
27466 23:33:40 (0) **   DCOM: ............................................................................................................. 0.
27467 23:33:40 (0) **   WINMGMT: .......................................................................................................... 0.
27468 23:33:40 (0) **   WMIADAPTER: ....................................................................................................... 0.
27469 23:33:40 (0) ** 
27470 23:33:40 (0) ** 2 error(s) 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found
27471 23:33:40 (0) ** 
27472 23:33:40 (0) ** 29 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
27473 23:33:40 (0) ** => This error is typically a WMI error. This WMI error is due to:
27474 23:33:40 (0) **    - a missing WMI class definition or object.
27475 23:33:40 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
27476 23:33:40 (0) **      You can correct the missing class definitions by:
27477 23:33:40 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
27478 23:33:40 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
27479 23:33:40 (0) **            (This list can be built on a similar and working WMI Windows installation)
27480 23:33:40 (0) **            The following command line must be used:
27481 23:33:40 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
27482 23:33:40 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
27483 23:33:40 (0) **            with WMI by starting the ADAP process.
27484 23:33:40 (0) **    - a WMI repository corruption.
27485 23:33:40 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
27486 23:33:40 (0) **      to validate the WMI repository operations.
27487 23:33:40 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
27488 23:33:40 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
27489 23:33:40 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
27490 23:33:40 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
27491 23:33:40 (0) **      the WMI repository must be reconstructed.
27492 23:33:40 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
27493 23:33:40 (0) **          otherwise some applications may fail after the reconstruction.
27494 23:33:40 (0) **          This can be achieved with the following command:
27495 23:33:40 (0) **          i.e. 'WMIDiag ShowMOFErrors'
27496 23:33:40 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
27497 23:33:40 (0) **          ALL fixes previously mentioned.
27498 23:33:40 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
27499 23:33:40 (0) ** 
27500 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27501 23:33:40 (0) ** WMI Registry key setup: ............................................................................................. OK.
27502 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27503 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27504 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27505 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27506 23:33:40 (0) ** 
27507 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27508 23:33:40 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
27509 23:33:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
27510 23:33:40 (0) ** 
27511 23:33:40 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\YAROSLAV\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN7_.CLI.SP1.64_HP-P17-LT_2020.08.10_23.28.10.LOG' for details.
27512 23:33:40 (0) ** 
27513 23:33:40 (0) ** WMIDiag v2.2 ended on 10 августа 2020 г. at 23:33 (W:301 E:51 S:1).