واحد مجنون
زيزوومي جديد
- إنضم
- 11 أكتوبر 2016
- المشاركات
- 5
- مستوى التفاعل
- 5
- النقاط
- 0
غير متصل
بسم الله الرحمن الرحيم ..
سلام عليكم ورحمة الله وبركاته ,
لآهنتم مشكلتي موضوعها عن Windows Management Instrumentation (WMI)
بعد تحميلي لبرنامج Ccleaner ونظفت الجهاز , صار عندي عطل في هذي الخدمة
مدري ايش المشكلة بالظبط , المهم عندي تقرير قدرت اجيبه من الـ cmd عن الخدمة
وجاني خطأ و ظهرلي التقرير التالي:-
.1453 05:06:00 (0) ** WMIDiag v2.2 started on Monday, December 25, 2017 at 05:05.
.1454 05:06:00 (0) **
.1455 05:06:00 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1456 05:06:00 (0) **
.1457 05:06:00 (0) ** This script is not supported under any Microsoft standard support program or service.
.1458 05:06:00 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1459 05:06:00 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1460 05:06:00 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1461 05:06:00 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1462 05:06:00 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1463 05:06:00 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1464 05:06:00 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1465 05:06:00 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1466 05:06:00 (0) ** of the possibility of such damages.
.1467 05:06:00 (0) **
.1468 05:06:00 (0) **
.1469 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1470 05:06:00 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1471 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1472 05:06:00 (0) **
.1473 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1474 05:06:00 (0) ** Windows 7 - Service Pack 1 - 64-bit (7601) - User 'M7MD-PC\M7MD' on computer 'M7MD-PC'.
.1475 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1476 05:06:00 (0) ** Environment: ........................................................................................................ OK.
.1477 05:06:00 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1478 05:06:00 (1) !! ERROR: The WMI repository folder is missing or you do not have access to it at: ..................................... C:\WINDOWS\SYSTEM32\WBEM\Repository.
.1479 05:06:00 (1) !! ERROR: The following WMI repository file(s) is/are missing: ......................................................... 4 ERROR(S)!
.1480 05:06:00 (0) ** - INDEX.BTR
.1481 05:06:00 (0) ** - MAPPING1.MAP
.1482 05:06:00 (0) ** - MAPPING2.MAP
.1483 05:06:00 (0) ** - OBJECTS.DATA
.1484 05:06:00 (0) ** => To fix this issue:
.1485 05:06:00 (0) ** - ENSURE you have all access rights to the WMI repository folder.
.1486 05:06:00 (0) ** - ENSURE you run WMIDiag as an Administrator.
.1487 05:06:00 (0) ** => If the issue is not due to a lack of privileges, and folder/files are really missing, while
.1488 05:06:00 (0) ** the WMI service successfully started, then WMI will rebuild the repository based on the
.1489 05:06:00 (0) ** auto-recovery mechanism. In such a case, WMI repository files shoud be available after the execution
.1490 05:06:00 (0) ** of WMIDiag. Check WMIDiag LOG.
.1491 05:06:00 (0) ** => If the issue is NOT due to a lack of privileges, and folder/files are really missing, while
.1492 05:06:00 (0) ** the WMI service does not start, then additional errors should be displayed (i.e. registry, DCOM, service hosts).
.1493 05:06:00 (0) ** You must fix those issues first!
.1494 05:06:00 (0) ** => After fixing issues, if the files are still missing and if you do not want WMI to rebuild
.1495 05:06:00 (0) ** the WMI repository, then you must restore the WMI repository from a previous backup.
.1496 05:06:00 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1497 05:06:00 (0) ** of the WMI repository.
.1498 05:06:00 (0) ** => If no backup is available, you must rebuild the repository.
.1499 05:06:00 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1500 05:06:00 (0) ** otherwise some applications may fail after the reconstruction.
.1501 05:06:00 (0) ** This can be achieved with the following command:
.1502 05:06:00 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1503 05:06:00 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1504 05:06:00 (0) ** registry key will be excluded from the WMI repository reconstruction.
.1505 05:06:00 (0) ** This may imply the lost of WMI registration information.
.1506 05:06:00 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1507 05:06:00 (0) ** ALL fixes previously mentioned.
.1508 05:06:00 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1509 05:06:00 (0) ** => To rebuild the WMI repository, you must:
.1510 05:06:00 (0) ** - Reset the WMI repository
.1511 05:06:00 (0) ** (The WMI repository rebuilt is based on auto-recovery)
.1512 05:06:00 (0) ** i.e. 'WINMGMT /ResetRepository'
.1513 05:06:00 (0) ** OR
.1514 05:06:00 (0) ** - Salvage the WMI repository if you want to attempt the retrieval of good data from the
.1515 05:06:00 (0) ** inconsistent repository
.1516 05:06:00 (0) ** (The repository rebuilt is based on auto-recovery + salvage)
.1517 05:06:00 (0) ** i.e. 'WINMGMT /SalvageRepository'
.1518 05:06:00 (0) **
.1519 05:06:00 (0) ** WMI repository state: ............................................................................................... N/A.
.1520 05:06:00 (0) ** AFTER running WMIDiag:
.1521 05:06:00 (0) ** - Disk free space on 'C:': .......................................................................................... 128511 MB.
.1522 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1523 05:06:00 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
.1524 05:06:00 (0) ** Windows Firewall Profile: ........................................................................................... PRIVATE.
.1525 05:06:00 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
.1526 05:06:00 (0) ** => This will prevent any WMI remote connectivity to this computer except
.1527 05:06:00 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
.1528 05:06:00 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
.1529 05:06:00 (0) ** - 'Windows Management Instrumentation (WMI-In)'
.1530 05:06:00 (0) ** - 'Windows Management Instrumentation (ASync-In)'
.1531 05:06:00 (0) ** Verify the reported status for each of these three inbound rules below.
.1532 05:06:00 (0) **
.1533 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
.1534 05:06:00 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
.1535 05:06:00 (0) ** - You can adjust the configuration by executing the following command:
.1536 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
.1537 05:06:00 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
.1538 05:06:00 (0) ** You can also enable each individual rule instead of activating the group rule.
.1539 05:06:00 (0) **
.1540 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. DISABLED.
.1541 05:06:00 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
.1542 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1543 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
.1544 05:06:00 (0) **
.1545 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... DISABLED.
.1546 05:06:00 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine.
.1547 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1548 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES'
.1549 05:06:00 (0) **
.1550 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ DISABLED.
.1551 05:06:00 (0) ** => This will prevent any WMI inbound connectivity to this machine.
.1552 05:06:00 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
.1553 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1554 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
.1555 05:06:00 (0) **
.1556 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... DISABLED.
.1557 05:06:00 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
.1558 05:06:00 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
.1559 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1560 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
.1561 05:06:00 (0) **
.1562 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1563 05:06:00 (0) ** DCOM Status: ........................................................................................................ OK.
.1564 05:06:00 (0) ** WMI registry setup: ................................................................................................. OK.
.1565 05:06:00 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1566 05:06:00 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1567 05:06:00 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
.1568 05:06:00 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1569 05:06:00 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
.1570 05:06:00 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
.1571 05:06:00 (0) ** this can prevent the service/application to work as expected.
.1572 05:06:00 (0) **
.1573 05:06:00 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1574 05:06:00 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1575 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1576 05:06:00 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1577 05:06:00 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 2 WARNING(S)!
.1578 05:06:00 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPMIPRV.DLL (\CLSID\{FD209E2E-813B-41C0-8646-4C3E9C917511}\InProcServer32)
.1579 05:06:00 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SERVERCOMPPROV.DLL (\CLSID\{9042E1B1-8FD4-4008-89FE-4040CC74575A}\InProcServer32)
.1580 05:06:00 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1581 05:06:00 (0) ** fail depending on the operation requested.
.1582 05:06:00 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1583 05:06:00 (0) **
.1584 05:06:00 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1585 05:06:00 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1586 05:06:00 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1587 05:06:00 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1588 05:06:00 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1589 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1590 05:06:00 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.1591 05:06:00 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.1592 05:06:00 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
.1593 05:06:00 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.1594 05:06:00 (0) ** selecting 'Run as Administrator'.
.1595 05:06:00 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
.1596 05:06:00 (0) ** in the Task Scheduler within the right security context.
.1597 05:06:00 (0) **
.1598 05:06:00 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1599 05:06:00 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1600 05:06:00 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1601 05:06:00 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
.1602 05:06:00 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1603 05:06:00 (0) **
.1604 05:06:00 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1605 05:06:00 (0) ** Overall WMI security status: ........................................................................................ OK.
.1606 05:06:00 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1607 05:06:00 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1608 05:06:00 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1609 05:06:00 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1610 05:06:00 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1611 05:06:00 (0) **
.1612 05:06:00 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
.1613 05:06:00 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1614 05:06:00 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1615 05:06:00 (0) ** - Root/subscription, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1616 05:06:00 (0) ** - Root/DEFAULT, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1617 05:06:00 (0) ** - Root/CIMV2, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1618 05:06:00 (0) ** - Root/CIMV2/Security, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1619 05:06:00 (0) ** - Root/CIMV2/Applications, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1620 05:06:00 (0) ** - Root/nap, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1621 05:06:00 (0) ** - Root/SECURITY, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1622 05:06:00 (0) ** - Root/WMI, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1623 05:06:00 (0) ** - Root/directory, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1624 05:06:00 (0) ** - Root/directory/LDAP, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1625 05:06:00 (0) ** - Root/SecurityCenter, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1626 05:06:00 (0) ** - Root/Microsoft, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1627 05:06:00 (0) ** - Root/Microsoft/HomeNet, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1628 05:06:00 (0) ** - Root/aspnet, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1629 05:06:00 (0) **
.1630 05:06:00 (0) ** WMI GET operations: ................................................................................................. OK.
.1631 05:06:00 (0) ** WMI MOF representations: ............................................................................................ OK.
.1632 05:06:00 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1633 05:06:00 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1634 05:06:00 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1635 05:06:00 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1636 05:06:00 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1637 05:06:00 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1638 05:06:00 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1639 05:06:00 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1640 05:06:00 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1641 05:06:00 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1642 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1643 05:06:00 (0) **
.1644 05:06:00 (0) ** 17 error(s) 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred.
.1645 05:06:00 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:
.1646 05:06:00 (0) ** - Failing WMI system components (see any missing WMI system files or DCOM registration
.1647 05:06:00 (0) ** issues previously mentioned).
.1648 05:06:00 (0) ** - Failing WMI providers (see any DCOM registration issues previously mentioned).
.1649 05:06:00 (0) ** - a WMI repository corruption.
.1650 05:06:00 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1651 05:06:00 (0) ** to validate the WMI repository operations.
.1652 05:06:00 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1653 05:06:00 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1654 05:06:00 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
.1655 05:06:00 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1656 05:06:00 (0) ** the WMI repository must be reconstructed.
.1657 05:06:00 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1658 05:06:00 (0) ** otherwise some applications may fail after the reconstruction.
.1659 05:06:00 (0) ** This can be achieved with the following command:
.1660 05:06:00 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1661 05:06:00 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1662 05:06:00 (0) ** ALL fixes previously mentioned.
.1663 05:06:00 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1664 05:06:00 (0) **
.1665 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1666 05:06:00 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1667 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1668 05:06:00 (0) ** => The Auto-Recovery key is missing! If the WMI repository is rebuilt,
.1669 05:06:00 (0) ** none of the WMI definitions will be recreated. In such a case, two options are possible:
.1670 05:06:00 (0) ** - You must restore a backup copy of the repository.
.1671 05:06:00 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1672 05:06:00 (0) ** of the WMI repository.
.1673 05:06:00 (0) ** - On Windows Vista, a fresh copy of the WMI repository can be manually reloaded from the CD.
.1674 05:06:00 (0) **
.1675 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1676 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1677 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1678 05:06:00 (0) **
.1679 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1680 05:06:00 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1681 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1682 05:06:00 (0) **
.1683 05:06:00 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\M7MD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN7_.CLI.SP1.64_M7MD-PC_2017.12.25_05.05.58.LOG' for details.
.1684 05:06:00 (0) **
.1685 05:06:00 (0) ** WMIDiag v2.2 ended on Monday, December 25, 2017 at 05:06 (W:22 E:35 S:1).
ياليت فزعتكم و المعذرة على الأطالة
سلام عليكم ورحمة الله وبركاته ,
لآهنتم مشكلتي موضوعها عن Windows Management Instrumentation (WMI)
بعد تحميلي لبرنامج Ccleaner ونظفت الجهاز , صار عندي عطل في هذي الخدمة
مدري ايش المشكلة بالظبط , المهم عندي تقرير قدرت اجيبه من الـ cmd عن الخدمة
وجاني خطأ و ظهرلي التقرير التالي:-
.1453 05:06:00 (0) ** WMIDiag v2.2 started on Monday, December 25, 2017 at 05:05.
.1454 05:06:00 (0) **
.1455 05:06:00 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1456 05:06:00 (0) **
.1457 05:06:00 (0) ** This script is not supported under any Microsoft standard support program or service.
.1458 05:06:00 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1459 05:06:00 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1460 05:06:00 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1461 05:06:00 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1462 05:06:00 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1463 05:06:00 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1464 05:06:00 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1465 05:06:00 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1466 05:06:00 (0) ** of the possibility of such damages.
.1467 05:06:00 (0) **
.1468 05:06:00 (0) **
.1469 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1470 05:06:00 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1471 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1472 05:06:00 (0) **
.1473 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1474 05:06:00 (0) ** Windows 7 - Service Pack 1 - 64-bit (7601) - User 'M7MD-PC\M7MD' on computer 'M7MD-PC'.
.1475 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1476 05:06:00 (0) ** Environment: ........................................................................................................ OK.
.1477 05:06:00 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1478 05:06:00 (1) !! ERROR: The WMI repository folder is missing or you do not have access to it at: ..................................... C:\WINDOWS\SYSTEM32\WBEM\Repository.
.1479 05:06:00 (1) !! ERROR: The following WMI repository file(s) is/are missing: ......................................................... 4 ERROR(S)!
.1480 05:06:00 (0) ** - INDEX.BTR
.1481 05:06:00 (0) ** - MAPPING1.MAP
.1482 05:06:00 (0) ** - MAPPING2.MAP
.1483 05:06:00 (0) ** - OBJECTS.DATA
.1484 05:06:00 (0) ** => To fix this issue:
.1485 05:06:00 (0) ** - ENSURE you have all access rights to the WMI repository folder.
.1486 05:06:00 (0) ** - ENSURE you run WMIDiag as an Administrator.
.1487 05:06:00 (0) ** => If the issue is not due to a lack of privileges, and folder/files are really missing, while
.1488 05:06:00 (0) ** the WMI service successfully started, then WMI will rebuild the repository based on the
.1489 05:06:00 (0) ** auto-recovery mechanism. In such a case, WMI repository files shoud be available after the execution
.1490 05:06:00 (0) ** of WMIDiag. Check WMIDiag LOG.
.1491 05:06:00 (0) ** => If the issue is NOT due to a lack of privileges, and folder/files are really missing, while
.1492 05:06:00 (0) ** the WMI service does not start, then additional errors should be displayed (i.e. registry, DCOM, service hosts).
.1493 05:06:00 (0) ** You must fix those issues first!
.1494 05:06:00 (0) ** => After fixing issues, if the files are still missing and if you do not want WMI to rebuild
.1495 05:06:00 (0) ** the WMI repository, then you must restore the WMI repository from a previous backup.
.1496 05:06:00 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1497 05:06:00 (0) ** of the WMI repository.
.1498 05:06:00 (0) ** => If no backup is available, you must rebuild the repository.
.1499 05:06:00 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1500 05:06:00 (0) ** otherwise some applications may fail after the reconstruction.
.1501 05:06:00 (0) ** This can be achieved with the following command:
.1502 05:06:00 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1503 05:06:00 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1504 05:06:00 (0) ** registry key will be excluded from the WMI repository reconstruction.
.1505 05:06:00 (0) ** This may imply the lost of WMI registration information.
.1506 05:06:00 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1507 05:06:00 (0) ** ALL fixes previously mentioned.
.1508 05:06:00 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1509 05:06:00 (0) ** => To rebuild the WMI repository, you must:
.1510 05:06:00 (0) ** - Reset the WMI repository
.1511 05:06:00 (0) ** (The WMI repository rebuilt is based on auto-recovery)
.1512 05:06:00 (0) ** i.e. 'WINMGMT /ResetRepository'
.1513 05:06:00 (0) ** OR
.1514 05:06:00 (0) ** - Salvage the WMI repository if you want to attempt the retrieval of good data from the
.1515 05:06:00 (0) ** inconsistent repository
.1516 05:06:00 (0) ** (The repository rebuilt is based on auto-recovery + salvage)
.1517 05:06:00 (0) ** i.e. 'WINMGMT /SalvageRepository'
.1518 05:06:00 (0) **
.1519 05:06:00 (0) ** WMI repository state: ............................................................................................... N/A.
.1520 05:06:00 (0) ** AFTER running WMIDiag:
.1521 05:06:00 (0) ** - Disk free space on 'C:': .......................................................................................... 128511 MB.
.1522 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1523 05:06:00 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
.1524 05:06:00 (0) ** Windows Firewall Profile: ........................................................................................... PRIVATE.
.1525 05:06:00 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
.1526 05:06:00 (0) ** => This will prevent any WMI remote connectivity to this computer except
.1527 05:06:00 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
.1528 05:06:00 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
.1529 05:06:00 (0) ** - 'Windows Management Instrumentation (WMI-In)'
.1530 05:06:00 (0) ** - 'Windows Management Instrumentation (ASync-In)'
.1531 05:06:00 (0) ** Verify the reported status for each of these three inbound rules below.
.1532 05:06:00 (0) **
.1533 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
.1534 05:06:00 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
.1535 05:06:00 (0) ** - You can adjust the configuration by executing the following command:
.1536 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
.1537 05:06:00 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
.1538 05:06:00 (0) ** You can also enable each individual rule instead of activating the group rule.
.1539 05:06:00 (0) **
.1540 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. DISABLED.
.1541 05:06:00 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
.1542 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1543 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
.1544 05:06:00 (0) **
.1545 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... DISABLED.
.1546 05:06:00 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine.
.1547 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1548 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES'
.1549 05:06:00 (0) **
.1550 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ DISABLED.
.1551 05:06:00 (0) ** => This will prevent any WMI inbound connectivity to this machine.
.1552 05:06:00 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
.1553 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1554 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
.1555 05:06:00 (0) **
.1556 05:06:00 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... DISABLED.
.1557 05:06:00 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
.1558 05:06:00 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
.1559 05:06:00 (0) ** - You can adjust the configuration of this rule by executing the following command:
.1560 05:06:00 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
.1561 05:06:00 (0) **
.1562 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1563 05:06:00 (0) ** DCOM Status: ........................................................................................................ OK.
.1564 05:06:00 (0) ** WMI registry setup: ................................................................................................. OK.
.1565 05:06:00 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1566 05:06:00 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1567 05:06:00 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
.1568 05:06:00 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1569 05:06:00 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
.1570 05:06:00 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
.1571 05:06:00 (0) ** this can prevent the service/application to work as expected.
.1572 05:06:00 (0) **
.1573 05:06:00 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1574 05:06:00 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1575 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1576 05:06:00 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1577 05:06:00 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 2 WARNING(S)!
.1578 05:06:00 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPMIPRV.DLL (\CLSID\{FD209E2E-813B-41C0-8646-4C3E9C917511}\InProcServer32)
.1579 05:06:00 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SERVERCOMPPROV.DLL (\CLSID\{9042E1B1-8FD4-4008-89FE-4040CC74575A}\InProcServer32)
.1580 05:06:00 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1581 05:06:00 (0) ** fail depending on the operation requested.
.1582 05:06:00 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1583 05:06:00 (0) **
.1584 05:06:00 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1585 05:06:00 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1586 05:06:00 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1587 05:06:00 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1588 05:06:00 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1589 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1590 05:06:00 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.1591 05:06:00 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.1592 05:06:00 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
.1593 05:06:00 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.1594 05:06:00 (0) ** selecting 'Run as Administrator'.
.1595 05:06:00 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
.1596 05:06:00 (0) ** in the Task Scheduler within the right security context.
.1597 05:06:00 (0) **
.1598 05:06:00 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1599 05:06:00 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1600 05:06:00 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1601 05:06:00 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
.1602 05:06:00 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1603 05:06:00 (0) **
.1604 05:06:00 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1605 05:06:00 (0) ** Overall WMI security status: ........................................................................................ OK.
.1606 05:06:00 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1607 05:06:00 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1608 05:06:00 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1609 05:06:00 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1610 05:06:00 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1611 05:06:00 (0) **
.1612 05:06:00 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
.1613 05:06:00 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1614 05:06:00 (0) ** - Root, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1615 05:06:00 (0) ** - Root/subscription, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1616 05:06:00 (0) ** - Root/DEFAULT, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1617 05:06:00 (0) ** - Root/CIMV2, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1618 05:06:00 (0) ** - Root/CIMV2/Security, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1619 05:06:00 (0) ** - Root/CIMV2/Applications, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1620 05:06:00 (0) ** - Root/nap, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1621 05:06:00 (0) ** - Root/SECURITY, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1622 05:06:00 (0) ** - Root/WMI, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1623 05:06:00 (0) ** - Root/directory, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1624 05:06:00 (0) ** - Root/directory/LDAP, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1625 05:06:00 (0) ** - Root/SecurityCenter, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1626 05:06:00 (0) ** - Root/Microsoft, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1627 05:06:00 (0) ** - Root/Microsoft/HomeNet, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1628 05:06:00 (0) ** - Root/aspnet, 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred..
.1629 05:06:00 (0) **
.1630 05:06:00 (0) ** WMI GET operations: ................................................................................................. OK.
.1631 05:06:00 (0) ** WMI MOF representations: ............................................................................................ OK.
.1632 05:06:00 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1633 05:06:00 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1634 05:06:00 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1635 05:06:00 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1636 05:06:00 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1637 05:06:00 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1638 05:06:00 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1639 05:06:00 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1640 05:06:00 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1641 05:06:00 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1642 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1643 05:06:00 (0) **
.1644 05:06:00 (0) ** 17 error(s) 0x8004100A - (WBEM_E_CRITICAL_ERROR) Internal critical and unexpected error occurred.
.1645 05:06:00 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:
.1646 05:06:00 (0) ** - Failing WMI system components (see any missing WMI system files or DCOM registration
.1647 05:06:00 (0) ** issues previously mentioned).
.1648 05:06:00 (0) ** - Failing WMI providers (see any DCOM registration issues previously mentioned).
.1649 05:06:00 (0) ** - a WMI repository corruption.
.1650 05:06:00 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1651 05:06:00 (0) ** to validate the WMI repository operations.
.1652 05:06:00 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1653 05:06:00 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1654 05:06:00 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
.1655 05:06:00 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1656 05:06:00 (0) ** the WMI repository must be reconstructed.
.1657 05:06:00 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1658 05:06:00 (0) ** otherwise some applications may fail after the reconstruction.
.1659 05:06:00 (0) ** This can be achieved with the following command:
.1660 05:06:00 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1661 05:06:00 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1662 05:06:00 (0) ** ALL fixes previously mentioned.
.1663 05:06:00 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1664 05:06:00 (0) **
.1665 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1666 05:06:00 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1667 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1668 05:06:00 (0) ** => The Auto-Recovery key is missing! If the WMI repository is rebuilt,
.1669 05:06:00 (0) ** none of the WMI definitions will be recreated. In such a case, two options are possible:
.1670 05:06:00 (0) ** - You must restore a backup copy of the repository.
.1671 05:06:00 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1672 05:06:00 (0) ** of the WMI repository.
.1673 05:06:00 (0) ** - On Windows Vista, a fresh copy of the WMI repository can be manually reloaded from the CD.
.1674 05:06:00 (0) **
.1675 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1676 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1677 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1678 05:06:00 (0) **
.1679 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1680 05:06:00 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1681 05:06:00 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1682 05:06:00 (0) **
.1683 05:06:00 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\M7MD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN7_.CLI.SP1.64_M7MD-PC_2017.12.25_05.05.58.LOG' for details.
.1684 05:06:00 (0) **
.1685 05:06:00 (0) ** WMIDiag v2.2 ended on Monday, December 25, 2017 at 05:06 (W:22 E:35 S:1).
ياليت فزعتكم و المعذرة على الأطالة
