The script didn't run. Got an error message.
https://upload.cat/0762c7dcac4d38ce
With regards to the registry entries no enabled or disabled value.
.1316 20:50:32 (0) ** WMIDiag v2.2 started on 26 November 2018 at 20:50.
.1317 20:50:32 (0) **
.1318 20:50:32 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1319 20:50:32 (0) **
.1320 20:50:32 (0) ** This script is not supported under any Microsoft standard support program or service.
.1321 20:50:32 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1322 20:50:32 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1323 20:50:32 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1324 20:50:32 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1325 20:50:32 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1326 20:50:32 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1327 20:50:32 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1328 20:50:32 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1329 20:50:32 (0) ** of the possibility of such damages.
.1330 20:50:32 (0) **
.1331 20:50:32 (0) **
.1332 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1333 20:50:32 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1334 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1335 20:50:32 (0) **
.1336 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1337 20:50:32 (0) ** Windows 7 - Service Pack 1 - 64-bit (7601) - User 'LAPTOP\HOLWELL' on computer 'LAPTOP'.
.1338 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1339 20:50:32 (0) ** Environment: ........................................................................................................ OK.
.1340 20:50:32 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1341 20:50:32 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1342 20:50:32 (0) ** WMI repository state: ............................................................................................... N/A.
.1343 20:50:32 (0) ** AFTER running WMIDiag:
.1344 20:50:32 (0) ** The WMI repository has a size of: ................................................................................... 19 MB.
.1345 20:50:32 (0) ** - Disk free space on 'C:': .......................................................................................... 24467 MB.
.1346 20:50:32 (0) ** - INDEX.BTR, 4825088 bytes, 12/05/2018 18:05:13
.1347 20:50:32 (0) ** - MAPPING1.MAP, 48380 bytes, 12/05/2018 18:05:14
.1348 20:50:32 (0) ** - MAPPING2.MAP, 48380 bytes, 12/05/2018 06:37:42
.1349 20:50:32 (0) ** - OBJECTS.DATA, 14745600 bytes, 12/05/2018 18:05:13
.1350 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1351 20:50:32 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
.1352 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1353 20:50:32 (0) ** DCOM Status: ........................................................................................................ OK.
.1354 20:50:32 (0) ** WMI registry setup: ................................................................................................. OK.
.1355 20:50:32 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1356 20:50:32 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1357 20:50:32 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
.1358 20:50:32 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1359 20:50:32 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
.1360 20:50:32 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
.1361 20:50:32 (0) ** this can prevent the service/application to work as expected.
.1362 20:50:32 (0) **
.1363 20:50:32 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1364 20:50:32 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1365 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1366 20:50:32 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1367 20:50:32 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 4 WARNING(S)!
.1368 20:50:32 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPMIPRV.DLL (\CLSID\{FD209E2E-813B-41C0-8646-4C3E9C917511}\InProcServer32)
.1369 20:50:32 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.DLL (\CLSID\{69D76D1B-B12E-4913-8F48-671B90195A2B}\InProcServer32)
.1370 20:50:32 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.DLL (\CLSID\{AAEAE72F-0328-4763-8ECB-23422EDE2DB5}\InProcServer32)
.1371 20:50:32 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SERVERCOMPPROV.DLL (\CLSID\{9042E1B1-8FD4-4008-89FE-4040CC74575A}\InProcServer32)
.1372 20:50:32 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1373 20:50:32 (0) ** fail depending on the operation requested.
.1374 20:50:32 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1375 20:50:32 (0) **
.1376 20:50:32 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1377 20:50:32 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1378 20:50:32 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1379 20:50:32 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1380 20:50:32 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1381 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1382 20:50:32 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.1383 20:50:32 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.1384 20:50:32 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
.1385 20:50:32 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.1386 20:50:32 (0) ** selecting 'Run as Administrator'.
.1387 20:50:32 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
.1388 20:50:32 (0) ** in the Task Scheduler within the right security context.
.1389 20:50:32 (0) **
.1390 20:50:32 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1391 20:50:32 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1392 20:50:32 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1393 20:50:32 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
.1394 20:50:32 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1395 20:50:32 (0) **
.1396 20:50:32 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1397 20:50:32 (0) ** Overall WMI security status: ........................................................................................ OK.
.1398 20:50:32 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1399 20:50:32 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1400 20:50:32 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1401 20:50:32 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1402 20:50:32 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1403 20:50:32 (0) **
.1404 20:50:32 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
.1405 20:50:32 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1406 20:50:32 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1407 20:50:32 (0) ** - Root/subscription, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1408 20:50:32 (0) ** - Root/DEFAULT, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1409 20:50:32 (0) ** - Root/CIMV2, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1410 20:50:32 (0) ** - Root/CIMV2/Security, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1411 20:50:32 (0) ** - Root/CIMV2/Applications, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1412 20:50:32 (0) ** - Root/nap, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1413 20:50:32 (0) ** - Root/SECURITY, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1414 20:50:32 (0) ** - Root/WMI, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1415 20:50:32 (0) ** - Root/directory, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1416 20:50:32 (0) ** - Root/directory/LDAP, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1417 20:50:32 (0) ** - Root/SecurityCenter, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1418 20:50:32 (0) ** - Root/Microsoft, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1419 20:50:32 (0) ** - Root/Microsoft/HomeNet, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1420 20:50:32 (0) ** - Root/aspnet, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1421 20:50:32 (0) **
.1422 20:50:32 (0) ** WMI GET operations: ................................................................................................. OK.
.1423 20:50:32 (0) ** WMI MOF representations: ............................................................................................ OK.
.1424 20:50:32 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1425 20:50:32 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1426 20:50:32 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1427 20:50:32 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1428 20:50:32 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1429 20:50:32 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1430 20:50:32 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1431 20:50:32 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1432 20:50:32 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1433 20:50:32 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1434 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1435 20:50:32 (0) **
.1436 20:50:32 (0) ** 17 error(s) 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred.
.1437 20:50:32 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:
.1438 20:50:32 (0) ** - Failing WMI system components (see any missing WMI system files or DCOM registration
.1439 20:50:32 (0) ** issues previously mentioned).
.1440 20:50:32 (0) ** - Failing WMI providers (see any DCOM registration issues previously mentioned).
.1441 20:50:32 (0) ** - a WMI repository corruption.
.1442 20:50:32 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1443 20:50:32 (0) ** to validate the WMI repository operations.
.1444 20:50:32 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1445 20:50:32 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1446 20:50:32 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
.1447 20:50:32 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1448 20:50:32 (0) ** the WMI repository must be reconstructed.
.1449 20:50:32 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1450 20:50:32 (0) ** otherwise some applications may fail after the reconstruction.
.1451 20:50:32 (0) ** This can be achieved with the following command:
.1452 20:50:32 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1453 20:50:32 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1454 20:50:32 (0) ** ALL fixes previously mentioned.
.1455 20:50:32 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1456 20:50:32 (0) **
.1457 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1458 20:50:32 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1459 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1460 20:50:32 (0) ** => The Auto-Recovery key is missing! If the WMI repository is rebuilt,
.1461 20:50:32 (0) ** none of the WMI definitions will be recreated. In such a case, two options are possible:
.1462 20:50:32 (0) ** - You must restore a backup copy of the repository.
.1463 20:50:32 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1464 20:50:32 (0) ** of the WMI repository.
.1465 20:50:32 (0) ** - On Windows Vista, a fresh copy of the WMI repository can be manually reloaded from the CD.
.1466 20:50:32 (0) **
.1467 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1468 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1469 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1470 20:50:32 (0) **
.1471 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1472 20:50:32 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1473 20:50:32 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1474 20:50:32 (0) **
.1475 20:50:32 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\HOLWELL\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN7_.CLI.SP1.64_LAPTOP_2018.11.26_20.50.21.LOG' for details.
.1476 20:50:32 (0) **
.1477 20:50:32 (0) ** WMIDiag v2.2 ended on 26 November 2018 at 20:50 (W:21 E:32 S:1).
sfc /scannow
dism /online /cleanup-wim /restorehealth
Return to Installation / Updating
Users browsing this forum: No registered users and 192 guests