[résolu] 0x80041003 Page blanche sur un site
Posté : 19 oct. 2012, 14:27
Bonjour.
J'ai l'erreur 0x80041003 et d'autres. J'ai fait une analyse avec WMIDiag. Je joins le résultat mais tout est en anglais, incompréhensible pour moi car en plus je ne suis pas informaticien. J'en ai réparé quelqu'unes.
Si quelqu'un pouvait m'aider à comprendre sur ces réparations.
25356 13:56:41 (0) ** WMIDiag v2.1 started on vendredi 19 octobre 2012 at 13:47.
25357 13:56:41 (0) **
25358 13:56:41 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
25359 13:56:41 (0) **
25360 13:56:41 (0) ** This script is not supported under any Microsoft standard support program or service.
25361 13:56:41 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
25362 13:56:41 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
25363 13:56:41 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
25364 13:56:41 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
25365 13:56:41 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
25366 13:56:41 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
25367 13:56:41 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
25368 13:56:41 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
25369 13:56:41 (0) ** of the possibility of such damages.
25370 13:56:41 (0) **
25371 13:56:41 (0) **
25372 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25373 13:56:41 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
25374 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25375 13:56:41 (0) **
25376 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25377 13:56:41 (0) ** Windows Vista - Service pack 2 - 32-bit (6002) - User 'PC-DE-FRANCIS\FRANCIS' on computer 'PC-DE-FRANCIS'.
25378 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25379 13:56:41 (0) ** Environment: ........................................................................................................ OK.
25380 13:56:41 (0) ** System drive: ....................................................................................................... C: (Disque n° 0 partition n° 1).
25381 13:56:41 (0) ** Drive type: ......................................................................................................... IDE (WDC WD1600BEVT-22ZCT0).
25382 13:56:41 (0) ** There are no missing WMI system files: .............................................................................. OK.
25383 13:56:41 (1) !! ERROR: The following WMI repository file(s) is/are missing: ......................................................... 4 ERROR(S)!
25384 13:56:41 (0) ** - INDEX.BTR
25385 13:56:41 (0) ** - MAPPING1.MAP
25386 13:56:41 (0) ** - MAPPING2.MAP
25387 13:56:41 (0) ** - OBJECTS.DATA
25388 13:56:41 (0) ** => To fix this issue:
25389 13:56:41 (0) ** - ENSURE you have all access rights to the WMI repository folder.
25390 13:56:41 (0) ** - ENSURE you run WMIDiag as an Administrator.
25391 13:56:41 (0) ** => If the issue is not due to a lack of privileges, and folder/files are really missing, while
25392 13:56:41 (0) ** the WMI service successfully started, then WMI will rebuild the repository based on the
25393 13:56:41 (0) ** auto-recovery mechanism. In such a case, WMI repository files shoud be available after the execution
25394 13:56:41 (0) ** of WMIDiag. Check WMIDiag LOG.
25395 13:56:41 (0) ** => If the issue is NOT due to a lack of privileges, and folder/files are really missing, while
25396 13:56:41 (0) ** the WMI service does not start, then additional errors should be displayed (i.e. registry, DCOM, service hosts).
25397 13:56:41 (0) ** You must fix those issues first!
25398 13:56:41 (0) ** => After fixing issues, if the files are still missing and if you do not want WMI to rebuild
25399 13:56:41 (0) ** the WMI repository, then you must restore the WMI repository from a previous backup.
25400 13:56:41 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
25401 13:56:41 (0) ** of the WMI repository.
25402 13:56:41 (0) ** => If no backup is available, you must rebuild the repository.
25403 13:56:41 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
25404 13:56:41 (0) ** otherwise some applications may fail after the reconstruction.
25405 13:56:41 (0) ** This can be achieved with the following command:
25406 13:56:41 (0) ** i.e. 'WMIDiag ShowMOFErrors'
25407 13:56:41 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
25408 13:56:41 (0) ** registry key will be excluded from the WMI repository reconstruction.
25409 13:56:41 (0) ** This may imply the lost of WMI registration information.
25410 13:56:41 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
25411 13:56:41 (0) ** ALL fixes previously mentioned.
25412 13:56:41 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
25413 13:56:41 (0) ** => To rebuild the WMI repository, you must:
25414 13:56:41 (0) ** - Reset the WMI repository
25415 13:56:41 (0) ** (The WMI repository rebuilt is based on auto-recovery)
25416 13:56:41 (0) ** i.e. 'WINMGMT /ResetRepository'
25417 13:56:41 (0) ** OR
25418 13:56:41 (0) ** - Salvage the WMI repository if you want to attempt the retrieval of good data from the
25419 13:56:41 (0) ** inconsistent repository
25420 13:56:41 (0) ** (The repository rebuilt is based on auto-recovery + salvage)
25421 13:56:41 (0) ** i.e. 'WINMGMT /SalvageRepository'
25422 13:56:41 (0) **
25423 13:56:41 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
25424 13:56:41 (0) ** - Disk free space on 'C:': .......................................................................................... 49830 MB.
25425 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25426 13:56:41 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
25427 13:56:41 (0) ** Windows Firewall Profile: ........................................................................................... PUBLIC.
25428 13:56:41 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
25429 13:56:41 (0) ** => This will prevent any WMI remote connectivity to this computer except
25430 13:56:41 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
25431 13:56:41 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
25432 13:56:41 (0) ** - 'Windows Management Instrumentation (WMI-In)'
25433 13:56:41 (0) ** - 'Windows Management Instrumentation (ASync-In)'
25434 13:56:41 (0) ** Verify the reported status for each of these three inbound rules below.
25435 13:56:41 (0) **
25436 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
25437 13:56:41 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
25438 13:56:41 (0) ** - You can adjust the configuration by executing the following command:
25439 13:56:41 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
25440 13:56:41 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
25441 13:56:41 (0) ** You can also enable each individual rule instead of activating the group rule.
25442 13:56:41 (0) **
25443 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
25444 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
25445 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
25446 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25447 13:56:41 (0) ** DCOM Status: ........................................................................................................ OK.
25448 13:56:41 (0) ** WMI registry setup: ................................................................................................. OK.
25449 13:56:41 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
25450 13:56:41 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
25451 13:56:41 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
25452 13:56:41 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
25453 13:56:41 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
25454 13:56:41 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
25455 13:56:41 (0) ** this can prevent the service/application to work as expected.
25456 13:56:41 (0) **
25457 13:56:41 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
25458 13:56:41 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
25459 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25460 13:56:41 (0) ** WMI service DCOM setup: ............................................................................................. OK.
25461 13:56:41 (0) ** WMI components DCOM registrations: .................................................................................. OK.
25462 13:56:41 (0) ** WMI ProgID registrations: ........................................................................................... OK.
25463 13:56:41 (2) !! WARNING: WMI provider DCOM registrations missing for the following provider(s): ..................................... 1 WARNING(S)!
25464 13:56:41 (0) ** - ROOT/MSAPPS12, OffProv12 ({DBF82DC7-E750-4CCF-B09C-D8AECEF7158E}) (i.e. WMI Class 'Win32_PowerPoint12Tables')
25465 13:56:41 (0) ** Provider DLL: ''
25466 13:56:41 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
25467 13:56:41 (0) ** while the DCOM registration is wrong or missing. This can be due to:
25468 13:56:41 (0) ** - a de-installation of the software.
25469 13:56:41 (0) ** - a deletion of some registry key data.
25470 13:56:41 (0) ** - a registry corruption.
25471 13:56:41 (0) ** => You can correct the DCOM configuration by:
25472 13:56:41 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>' command.
25473 13:56:41 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
25474 13:56:41 (0) ** (This list can be built on a similar and working WMI Windows installation)
25475 13:56:41 (0) ** The following command line must be used:
25476 13:56:41 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
25477 13:56:41 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
25478 13:56:41 (0) ** may not solve the problem as the DLL supporting the WMI class(es)
25479 13:56:41 (0) ** can be located in a different folder.
25480 13:56:41 (0) ** You must refer to the class name to determine the software delivering the related DLL.
25481 13:56:41 (0) ** => If the software has been de-installed intentionally, then this information must be
25482 13:56:41 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
25483 13:56:41 (0) ** the provider registration data.
25484 13:56:41 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MSAPPS12 path __Win32Provider Where Name='OffProv12' DELETE'
25485 13:56:41 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
25486 13:56:41 (0) ** the namespace and ALL its content can be ENTIRELY deleted.
25487 13:56:41 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='MSAPPS12' DELETE'
25488 13:56:41 (0) ** - Re-installing the software.
25489 13:56:41 (0) **
25490 13:56:41 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
25491 13:56:41 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
25492 13:56:41 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
25493 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25494 13:56:41 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
25495 13:56:41 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
25496 13:56:41 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
25497 13:56:41 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
25498 13:56:41 (0) ** selecting 'Run as Administrator'.
25499 13:56:41 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
25500 13:56:41 (0) ** in the Task Scheduler within the right security context.
25501 13:56:41 (0) **
25502 13:56:41 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
25503 13:56:41 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
25504 13:56:41 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
25505 13:56:41 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
25506 13:56:41 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
25507 13:56:41 (0) **
25508 13:56:41 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
25509 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
25510 13:56:41 (0) ** - REMOVED ACE:
25511 13:56:41 (0) ** ACEType: &h0
25512 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25513 13:56:41 (0) ** ACEFlags: &h0
25514 13:56:41 (0) ** ACEMask: &h3
25515 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25516 13:56:41 (0) ** DCOM_RIGHT_ACCESS_LOCAL
25517 13:56:41 (0) **
25518 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25519 13:56:41 (0) ** Removing default security will cause some operations to fail!
25520 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25521 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25522 13:56:41 (0) **
25523 13:56:41 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
25524 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
25525 13:56:41 (0) ** - REMOVED ACE:
25526 13:56:41 (0) ** ACEType: &h0
25527 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25528 13:56:41 (0) ** ACEFlags: &h0
25529 13:56:41 (0) ** ACEMask: &h7
25530 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25531 13:56:41 (0) ** DCOM_RIGHT_ACCESS_LOCAL
25532 13:56:41 (0) ** DCOM_RIGHT_ACCESS_REMOTE
25533 13:56:41 (0) **
25534 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25535 13:56:41 (0) ** Removing default security will cause some operations to fail!
25536 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25537 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25538 13:56:41 (0) **
25539 13:56:41 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
25540 13:56:41 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
25541 13:56:41 (0) ** - REMOVED ACE:
25542 13:56:41 (0) ** ACEType: &h0
25543 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25544 13:56:41 (0) ** ACEFlags: &h0
25545 13:56:41 (0) ** ACEMask: &h7
25546 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25547 13:56:41 (0) ** DCOM_RIGHT_ACCESS_LOCAL
25548 13:56:41 (0) ** DCOM_RIGHT_ACCESS_REMOTE
25549 13:56:41 (0) **
25550 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25551 13:56:41 (0) ** Removing default security will cause some operations to fail!
25552 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25553 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25554 13:56:41 (0) **
25555 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
25556 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
25557 13:56:41 (0) ** - REMOVED ACE:
25558 13:56:41 (0) ** ACEType: &h0
25559 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25560 13:56:41 (0) ** ACEFlags: &h0
25561 13:56:41 (0) ** ACEMask: &h1F
25562 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25563 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25564 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25565 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25566 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25567 13:56:41 (0) **
25568 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25569 13:56:41 (0) ** Removing default security will cause some operations to fail!
25570 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25571 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25572 13:56:41 (0) **
25573 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
25574 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
25575 13:56:41 (0) ** - REMOVED ACE:
25576 13:56:41 (0) ** ACEType: &h0
25577 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25578 13:56:41 (0) ** ACEFlags: &h0
25579 13:56:41 (0) ** ACEMask: &h1F
25580 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25581 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25582 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25583 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25584 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25585 13:56:41 (0) **
25586 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25587 13:56:41 (0) ** Removing default security will cause some operations to fail!
25588 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25589 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25590 13:56:41 (0) **
25591 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
25592 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
25593 13:56:41 (0) ** - REMOVED ACE:
25594 13:56:41 (0) ** ACEType: &h0
25595 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25596 13:56:41 (0) ** ACEFlags: &h0
25597 13:56:41 (0) ** ACEMask: &h1F
25598 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25599 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25600 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25601 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25602 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25603 13:56:41 (0) **
25604 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25605 13:56:41 (0) ** Removing default security will cause some operations to fail!
25606 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25607 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25608 13:56:41 (0) **
25609 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
25610 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
25611 13:56:41 (0) ** - REMOVED ACE:
25612 13:56:41 (0) ** ACEType: &h0
25613 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25614 13:56:41 (0) ** ACEFlags: &h0
25615 13:56:41 (0) ** ACEMask: &h1F
25616 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25617 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25618 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25619 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25620 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25621 13:56:41 (0) **
25622 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25623 13:56:41 (0) ** Removing default security will cause some operations to fail!
25624 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25625 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25626 13:56:41 (0) **
25627 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
25628 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
25629 13:56:41 (0) ** - REMOVED ACE:
25630 13:56:41 (0) ** ACEType: &h0
25631 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25632 13:56:41 (0) ** ACEFlags: &h0
25633 13:56:41 (0) ** ACEMask: &h1F
25634 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25635 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25636 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25637 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25638 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25639 13:56:41 (0) **
25640 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25641 13:56:41 (0) ** Removing default security will cause some operations to fail!
25642 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25643 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25644 13:56:41 (0) **
25645 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
25646 13:56:41 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
25647 13:56:41 (0) ** - REMOVED ACE:
25648 13:56:41 (0) ** ACEType: &h0
25649 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25650 13:56:41 (0) ** ACEFlags: &h0
25651 13:56:41 (0) ** ACEMask: &hB
25652 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25653 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25654 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25655 13:56:41 (0) **
25656 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25657 13:56:41 (0) ** Removing default security will cause some operations to fail!
25658 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25659 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25660 13:56:41 (0) **
25661 13:56:41 (0) ** DCOM security for 'Windows Management Instrumentation' (Launch & Activation Permissions): ........................... MODIFIED.
25662 13:56:41 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
25663 13:56:41 (0) ** - REMOVED ACE:
25664 13:56:41 (0) ** ACEType: &h0
25665 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25666 13:56:41 (0) ** ACEFlags: &h0
25667 13:56:41 (0) ** ACEMask: &h1F
25668 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25669 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25670 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25671 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25672 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25673 13:56:41 (0) **
25674 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25675 13:56:41 (0) ** Removing default security will cause some operations to fail!
25676 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25677 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25678 13:56:41 (0) **
25679 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25680 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
25681 13:56:41 (0) ** - REMOVED ACE:
25682 13:56:41 (0) ** ACEType: &h0
25683 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25684 13:56:41 (0) ** ACEFlags: &h0
25685 13:56:41 (0) ** ACEMask: &h1F
25686 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25687 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25688 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25689 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25690 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25691 13:56:41 (0) **
25692 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25693 13:56:41 (0) ** Removing default security will cause some operations to fail!
25694 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25695 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25696 13:56:41 (0) **
25697 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25698 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
25699 13:56:41 (0) ** - REMOVED ACE:
25700 13:56:41 (0) ** ACEType: &h0
25701 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25702 13:56:41 (0) ** ACEFlags: &h0
25703 13:56:41 (0) ** ACEMask: &h1F
25704 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25705 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25706 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25707 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25708 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25709 13:56:41 (0) **
25710 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25711 13:56:41 (0) ** Removing default security will cause some operations to fail!
25712 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25713 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25714 13:56:41 (0) **
25715 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25716 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
25717 13:56:41 (0) ** - REMOVED ACE:
25718 13:56:41 (0) ** ACEType: &h0
25719 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25720 13:56:41 (0) ** ACEFlags: &h0
25721 13:56:41 (0) ** ACEMask: &h1F
25722 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25723 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25724 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25725 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25726 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25727 13:56:41 (0) **
25728 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25729 13:56:41 (0) ** Removing default security will cause some operations to fail!
25730 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25731 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25732 13:56:41 (0) **
25733 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25734 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
25735 13:56:41 (0) ** - REMOVED ACE:
25736 13:56:41 (0) ** ACEType: &h0
25737 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25738 13:56:41 (0) ** ACEFlags: &h0
25739 13:56:41 (0) ** ACEMask: &h1F
25740 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25741 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25742 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25743 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25744 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25745 13:56:41 (0) **
25746 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25747 13:56:41 (0) ** Removing default security will cause some operations to fail!
25748 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25749 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25750 13:56:41 (0) **
25751 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25752 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
25753 13:56:41 (0) ** - REMOVED ACE:
25754 13:56:41 (0) ** ACEType: &h0
25755 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25756 13:56:41 (0) ** ACEFlags: &h0
25757 13:56:41 (0) ** ACEMask: &h1F
25758 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25759 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25760 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25761 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25762 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25763 13:56:41 (0) **
25764 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25765 13:56:41 (0) ** Removing default security will cause some operations to fail!
25766 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25767 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25768 13:56:41 (0) **
25769 13:56:41 (0) **
25770 13:56:41 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
25771 13:56:41 (0) ** DCOM security error(s) detected: .................................................................................... 15.
25772 13:56:41 (0) ** WMI security warning(s) detected: ................................................................................... 0.
25773 13:56:41 (0) ** WMI security error(s) detected: ..................................................................................... 0.
25774 13:56:41 (0) **
25775 13:56:41 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
25776 13:56:41 (0) ** Overall WMI security status: ........................................................................................ OK.
25777 13:56:41 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
25778 13:56:41 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
25779 13:56:41 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
25780 13:56:41 (0) ** 'select * from MSFT_SCMEventLogEvent'
25781 13:56:41 (0) **
25782 13:56:41 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
25783 13:56:41 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 6 ERROR(S)!
25784 13:56:41 (0) ** - ROOT/MICROSOFTDFS, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25785 13:56:41 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25786 13:56:41 (0) ** - ROOT/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25787 13:56:41 (0) ** - ROOT/RSOP/USER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25788 13:56:41 (0) ** - ROOT/RSOP/COMPUTER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25789 13:56:41 (0) ** - ROOT/SERVICEMODEL, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25790 13:56:41 (0) **
25791 13:56:41 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 7 ERROR(S)!
25792 13:56:41 (0) ** - ROOT/MICROSOFTDFS, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25793 13:56:41 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25794 13:56:41 (0) ** - ROOT/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25795 13:56:41 (0) ** - ROOT/RSOP/USER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25796 13:56:41 (0) ** - ROOT/RSOP/COMPUTER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25797 13:56:41 (0) ** - ROOT/SERVICEMODEL, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25798 13:56:41 (0) ** - Root/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25799 13:56:41 (0) **
25800 13:56:41 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 22 ERROR(S)!
25801 13:56:41 (0) ** - Root, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25802 13:56:41 (0) ** MOF Registration: ''
25803 13:56:41 (0) ** - ROOT/SUBSCRIPTION, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25804 13:56:41 (0) ** MOF Registration: ''
25805 13:56:41 (0) ** - ROOT/DEFAULT, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25806 13:56:41 (0) ** MOF Registration: ''
25807 13:56:41 (0) ** - ROOT/CIMV2, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25808 13:56:41 (0) ** MOF Registration: ''
25809 13:56:41 (0) ** - ROOT/CIMV2/SECURITY, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25810 13:56:41 (0) ** MOF Registration: ''
25811 13:56:41 (0) ** - ROOT/CIMV2/APPLICATIONS, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25812 13:56:41 (0) ** MOF Registration: ''
25813 13:56:41 (0) ** - ROOT/CIMV2/APPLICATIONS/WINDOWSPARENTALCONTROLS, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25814 13:56:41 (0) ** MOF Registration: ''
25815 13:56:41 (0) ** - ROOT/CIMV2/APPLICATIONS/GAMES, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25816 13:56:41 (0) ** MOF Registration: ''
25817 13:56:41 (0) ** - ROOT/CLI, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25818 13:56:41 (0) ** MOF Registration: ''
25819 13:56:41 (0) ** - ROOT/NAP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25820 13:56:41 (0) ** MOF Registration: ''
25821 13:56:41 (0) ** - ROOT/SECURITYCENTER2, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25822 13:56:41 (0) ** MOF Registration: ''
25823 13:56:41 (0) ** - ROOT/RSOP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25824 13:56:41 (0) ** MOF Registration: ''
25825 13:56:41 (0) ** - ROOT/WMI, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25826 13:56:41 (0) ** MOF Registration: ''
25827 13:56:41 (0) ** - ROOT/DIRECTORY, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25828 13:56:41 (0) ** MOF Registration: ''
25829 13:56:41 (0) ** - ROOT/DIRECTORY/LDAP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25830 13:56:41 (0) ** MOF Registration: ''
25831 13:56:41 (0) ** - ROOT/SECURITYCENTER, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25832 13:56:41 (0) ** MOF Registration: ''
25833 13:56:41 (0) ** - ROOT/MSAPPS12, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25834 13:56:41 (0) ** MOF Registration: ''
25835 13:56:41 (0) ** - ROOT/MICROSOFT, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25836 13:56:41 (0) ** MOF Registration: ''
25837 13:56:41 (0) ** - ROOT/MICROSOFT/HOMENET, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25838 13:56:41 (0) ** MOF Registration: ''
25839 13:56:41 (0) ** - ROOT/ASPNET, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25840 13:56:41 (0) ** MOF Registration: ''
25841 13:56:41 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
25842 13:56:41 (0) ** MOF Registration: ''
25843 13:56:41 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
25844 13:56:41 (0) ** MOF Registration: ''
25845 13:56:41 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
25846 13:56:41 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
25847 13:56:41 (0) ** You can refresh the WMI class provider buffer with the following command:
25848 13:56:41 (0) **
25849 13:56:41 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
25850 13:56:41 (0) **
25851 13:56:41 (0) ** WMI MOF representations: ............................................................................................ OK.
25852 13:56:41 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
25853 13:56:41 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 1 ERROR(S)!
25854 13:56:41 (0) ** - ROOT/WMI, InstancesOfAsync, 'MSMouse', 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25855 13:56:41 (0) ** MOF Registration: ''
25856 13:56:41 (0) **
25857 13:56:41 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
25858 13:56:41 (1) !! ERROR: WMI GET VALUE operation errors reported: ..................................................................... 1 ERROR(S)!
25859 13:56:41 (0) ** - Root/CIMV2, Instance: Win32_Service='WSCSVC', Property: Displayname='Centre de sécurité' (Expected default='Security Center').
25860 13:56:41 (0) **
25861 13:56:41 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
25862 13:56:41 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
25863 13:56:41 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
25864 13:56:41 (0) ** WMI static instances retrieved: ..................................................................................... 1511.
25865 13:56:41 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
25866 13:56:41 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
25867 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25868 13:56:41 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
25869 13:56:41 (0) ** DCOM: ............................................................................................................. 0.
25870 13:56:41 (0) ** WINMGMT: .......................................................................................................... 0.
25871 13:56:41 (0) ** WMIADAPTER: ....................................................................................................... 0.
25872 13:56:41 (0) **
25873 13:56:41 (0) ** # of additional Event Log events AFTER WMIDiag execution:
25874 13:56:41 (0) ** DCOM: ............................................................................................................. 0.
25875 13:56:41 (0) ** WINMGMT: .......................................................................................................... 0.
25876 13:56:41 (0) ** WMIADAPTER: ....................................................................................................... 0.
25877 13:56:41 (0) **
25878 13:56:41 (0) ** 34 error(s) 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action
25879 13:56:41 (0) ** => This error is typically due to insufficient or restricted permissions in the examined system.
25880 13:56:41 (0) ** => ENSURE you are a Full Administrator of the examined system, if the WMI provider or the
25881 13:56:41 (0) ** WMI system security do not enforce any restrictions.
25882 13:56:41 (0) **
25883 13:56:41 (0) **
25884 13:56:41 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
25885 13:56:41 (0) ** => This error is typically a WMI error. This WMI error is due to:
25886 13:56:41 (0) ** - a missing WMI class definition or object.
25887 13:56:41 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
25888 13:56:41 (0) ** You can correct the missing class definitions by:
25889 13:56:41 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
25890 13:56:41 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
25891 13:56:41 (0) ** (This list can be built on a similar and working WMI Windows installation)
25892 13:56:41 (0) ** The following command line must be used:
25893 13:56:41 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
25894 13:56:41 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
25895 13:56:41 (0) ** with WMI by starting the ADAP process.
25896 13:56:41 (0) ** - a WMI repository corruption.
25897 13:56:41 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
25898 13:56:41 (0) ** to validate the WMI repository operations.
25899 13:56:41 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
25900 13:56:41 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
25901 13:56:41 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
25902 13:56:41 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
25903 13:56:41 (0) ** the WMI repository must be reconstructed.
25904 13:56:41 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
25905 13:56:41 (0) ** otherwise some applications may fail after the reconstruction.
25906 13:56:41 (0) ** This can be achieved with the following command:
25907 13:56:41 (0) ** i.e. 'WMIDiag ShowMOFErrors'
25908 13:56:41 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
25909 13:56:41 (0) ** ALL fixes previously mentioned.
25910 13:56:41 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
25911 13:56:41 (0) **
25912 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25913 13:56:41 (0) ** WMI Registry key setup: ............................................................................................. OK.
25914 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25915 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25916 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25917 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25918 13:56:41 (0) **
25919 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25920 13:56:41 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
25921 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25922 13:56:41 (0) **
25923 13:56:41 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\FRANCIS\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_VISTA.CLI.SP2.32_PC-DE-FRANCIS_2012.10.19_13.47.18.LOG' for details.
25924 13:56:41 (0) **
25925 13:56:41 (0) ** WMIDiag v2.1 ended on vendredi 19 octobre 2012 at 13:56 (W:79 E:189 S:1).
J'ai l'erreur 0x80041003 et d'autres. J'ai fait une analyse avec WMIDiag. Je joins le résultat mais tout est en anglais, incompréhensible pour moi car en plus je ne suis pas informaticien. J'en ai réparé quelqu'unes.
Si quelqu'un pouvait m'aider à comprendre sur ces réparations.
25356 13:56:41 (0) ** WMIDiag v2.1 started on vendredi 19 octobre 2012 at 13:47.
25357 13:56:41 (0) **
25358 13:56:41 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
25359 13:56:41 (0) **
25360 13:56:41 (0) ** This script is not supported under any Microsoft standard support program or service.
25361 13:56:41 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
25362 13:56:41 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
25363 13:56:41 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
25364 13:56:41 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
25365 13:56:41 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
25366 13:56:41 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
25367 13:56:41 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
25368 13:56:41 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
25369 13:56:41 (0) ** of the possibility of such damages.
25370 13:56:41 (0) **
25371 13:56:41 (0) **
25372 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25373 13:56:41 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
25374 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25375 13:56:41 (0) **
25376 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25377 13:56:41 (0) ** Windows Vista - Service pack 2 - 32-bit (6002) - User 'PC-DE-FRANCIS\FRANCIS' on computer 'PC-DE-FRANCIS'.
25378 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25379 13:56:41 (0) ** Environment: ........................................................................................................ OK.
25380 13:56:41 (0) ** System drive: ....................................................................................................... C: (Disque n° 0 partition n° 1).
25381 13:56:41 (0) ** Drive type: ......................................................................................................... IDE (WDC WD1600BEVT-22ZCT0).
25382 13:56:41 (0) ** There are no missing WMI system files: .............................................................................. OK.
25383 13:56:41 (1) !! ERROR: The following WMI repository file(s) is/are missing: ......................................................... 4 ERROR(S)!
25384 13:56:41 (0) ** - INDEX.BTR
25385 13:56:41 (0) ** - MAPPING1.MAP
25386 13:56:41 (0) ** - MAPPING2.MAP
25387 13:56:41 (0) ** - OBJECTS.DATA
25388 13:56:41 (0) ** => To fix this issue:
25389 13:56:41 (0) ** - ENSURE you have all access rights to the WMI repository folder.
25390 13:56:41 (0) ** - ENSURE you run WMIDiag as an Administrator.
25391 13:56:41 (0) ** => If the issue is not due to a lack of privileges, and folder/files are really missing, while
25392 13:56:41 (0) ** the WMI service successfully started, then WMI will rebuild the repository based on the
25393 13:56:41 (0) ** auto-recovery mechanism. In such a case, WMI repository files shoud be available after the execution
25394 13:56:41 (0) ** of WMIDiag. Check WMIDiag LOG.
25395 13:56:41 (0) ** => If the issue is NOT due to a lack of privileges, and folder/files are really missing, while
25396 13:56:41 (0) ** the WMI service does not start, then additional errors should be displayed (i.e. registry, DCOM, service hosts).
25397 13:56:41 (0) ** You must fix those issues first!
25398 13:56:41 (0) ** => After fixing issues, if the files are still missing and if you do not want WMI to rebuild
25399 13:56:41 (0) ** the WMI repository, then you must restore the WMI repository from a previous backup.
25400 13:56:41 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
25401 13:56:41 (0) ** of the WMI repository.
25402 13:56:41 (0) ** => If no backup is available, you must rebuild the repository.
25403 13:56:41 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
25404 13:56:41 (0) ** otherwise some applications may fail after the reconstruction.
25405 13:56:41 (0) ** This can be achieved with the following command:
25406 13:56:41 (0) ** i.e. 'WMIDiag ShowMOFErrors'
25407 13:56:41 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
25408 13:56:41 (0) ** registry key will be excluded from the WMI repository reconstruction.
25409 13:56:41 (0) ** This may imply the lost of WMI registration information.
25410 13:56:41 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
25411 13:56:41 (0) ** ALL fixes previously mentioned.
25412 13:56:41 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
25413 13:56:41 (0) ** => To rebuild the WMI repository, you must:
25414 13:56:41 (0) ** - Reset the WMI repository
25415 13:56:41 (0) ** (The WMI repository rebuilt is based on auto-recovery)
25416 13:56:41 (0) ** i.e. 'WINMGMT /ResetRepository'
25417 13:56:41 (0) ** OR
25418 13:56:41 (0) ** - Salvage the WMI repository if you want to attempt the retrieval of good data from the
25419 13:56:41 (0) ** inconsistent repository
25420 13:56:41 (0) ** (The repository rebuilt is based on auto-recovery + salvage)
25421 13:56:41 (0) ** i.e. 'WINMGMT /SalvageRepository'
25422 13:56:41 (0) **
25423 13:56:41 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
25424 13:56:41 (0) ** - Disk free space on 'C:': .......................................................................................... 49830 MB.
25425 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25426 13:56:41 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
25427 13:56:41 (0) ** Windows Firewall Profile: ........................................................................................... PUBLIC.
25428 13:56:41 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
25429 13:56:41 (0) ** => This will prevent any WMI remote connectivity to this computer except
25430 13:56:41 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
25431 13:56:41 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
25432 13:56:41 (0) ** - 'Windows Management Instrumentation (WMI-In)'
25433 13:56:41 (0) ** - 'Windows Management Instrumentation (ASync-In)'
25434 13:56:41 (0) ** Verify the reported status for each of these three inbound rules below.
25435 13:56:41 (0) **
25436 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
25437 13:56:41 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
25438 13:56:41 (0) ** - You can adjust the configuration by executing the following command:
25439 13:56:41 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
25440 13:56:41 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
25441 13:56:41 (0) ** You can also enable each individual rule instead of activating the group rule.
25442 13:56:41 (0) **
25443 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
25444 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
25445 13:56:41 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
25446 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25447 13:56:41 (0) ** DCOM Status: ........................................................................................................ OK.
25448 13:56:41 (0) ** WMI registry setup: ................................................................................................. OK.
25449 13:56:41 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
25450 13:56:41 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
25451 13:56:41 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
25452 13:56:41 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
25453 13:56:41 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
25454 13:56:41 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
25455 13:56:41 (0) ** this can prevent the service/application to work as expected.
25456 13:56:41 (0) **
25457 13:56:41 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
25458 13:56:41 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
25459 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25460 13:56:41 (0) ** WMI service DCOM setup: ............................................................................................. OK.
25461 13:56:41 (0) ** WMI components DCOM registrations: .................................................................................. OK.
25462 13:56:41 (0) ** WMI ProgID registrations: ........................................................................................... OK.
25463 13:56:41 (2) !! WARNING: WMI provider DCOM registrations missing for the following provider(s): ..................................... 1 WARNING(S)!
25464 13:56:41 (0) ** - ROOT/MSAPPS12, OffProv12 ({DBF82DC7-E750-4CCF-B09C-D8AECEF7158E}) (i.e. WMI Class 'Win32_PowerPoint12Tables')
25465 13:56:41 (0) ** Provider DLL: ''
25466 13:56:41 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
25467 13:56:41 (0) ** while the DCOM registration is wrong or missing. This can be due to:
25468 13:56:41 (0) ** - a de-installation of the software.
25469 13:56:41 (0) ** - a deletion of some registry key data.
25470 13:56:41 (0) ** - a registry corruption.
25471 13:56:41 (0) ** => You can correct the DCOM configuration by:
25472 13:56:41 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>' command.
25473 13:56:41 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
25474 13:56:41 (0) ** (This list can be built on a similar and working WMI Windows installation)
25475 13:56:41 (0) ** The following command line must be used:
25476 13:56:41 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
25477 13:56:41 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
25478 13:56:41 (0) ** may not solve the problem as the DLL supporting the WMI class(es)
25479 13:56:41 (0) ** can be located in a different folder.
25480 13:56:41 (0) ** You must refer to the class name to determine the software delivering the related DLL.
25481 13:56:41 (0) ** => If the software has been de-installed intentionally, then this information must be
25482 13:56:41 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
25483 13:56:41 (0) ** the provider registration data.
25484 13:56:41 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MSAPPS12 path __Win32Provider Where Name='OffProv12' DELETE'
25485 13:56:41 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
25486 13:56:41 (0) ** the namespace and ALL its content can be ENTIRELY deleted.
25487 13:56:41 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='MSAPPS12' DELETE'
25488 13:56:41 (0) ** - Re-installing the software.
25489 13:56:41 (0) **
25490 13:56:41 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
25491 13:56:41 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
25492 13:56:41 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
25493 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25494 13:56:41 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
25495 13:56:41 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
25496 13:56:41 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
25497 13:56:41 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
25498 13:56:41 (0) ** selecting 'Run as Administrator'.
25499 13:56:41 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
25500 13:56:41 (0) ** in the Task Scheduler within the right security context.
25501 13:56:41 (0) **
25502 13:56:41 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
25503 13:56:41 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
25504 13:56:41 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
25505 13:56:41 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
25506 13:56:41 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
25507 13:56:41 (0) **
25508 13:56:41 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
25509 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
25510 13:56:41 (0) ** - REMOVED ACE:
25511 13:56:41 (0) ** ACEType: &h0
25512 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25513 13:56:41 (0) ** ACEFlags: &h0
25514 13:56:41 (0) ** ACEMask: &h3
25515 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25516 13:56:41 (0) ** DCOM_RIGHT_ACCESS_LOCAL
25517 13:56:41 (0) **
25518 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25519 13:56:41 (0) ** Removing default security will cause some operations to fail!
25520 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25521 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25522 13:56:41 (0) **
25523 13:56:41 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
25524 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
25525 13:56:41 (0) ** - REMOVED ACE:
25526 13:56:41 (0) ** ACEType: &h0
25527 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25528 13:56:41 (0) ** ACEFlags: &h0
25529 13:56:41 (0) ** ACEMask: &h7
25530 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25531 13:56:41 (0) ** DCOM_RIGHT_ACCESS_LOCAL
25532 13:56:41 (0) ** DCOM_RIGHT_ACCESS_REMOTE
25533 13:56:41 (0) **
25534 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25535 13:56:41 (0) ** Removing default security will cause some operations to fail!
25536 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25537 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25538 13:56:41 (0) **
25539 13:56:41 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
25540 13:56:41 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
25541 13:56:41 (0) ** - REMOVED ACE:
25542 13:56:41 (0) ** ACEType: &h0
25543 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25544 13:56:41 (0) ** ACEFlags: &h0
25545 13:56:41 (0) ** ACEMask: &h7
25546 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25547 13:56:41 (0) ** DCOM_RIGHT_ACCESS_LOCAL
25548 13:56:41 (0) ** DCOM_RIGHT_ACCESS_REMOTE
25549 13:56:41 (0) **
25550 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25551 13:56:41 (0) ** Removing default security will cause some operations to fail!
25552 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25553 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25554 13:56:41 (0) **
25555 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
25556 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
25557 13:56:41 (0) ** - REMOVED ACE:
25558 13:56:41 (0) ** ACEType: &h0
25559 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25560 13:56:41 (0) ** ACEFlags: &h0
25561 13:56:41 (0) ** ACEMask: &h1F
25562 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25563 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25564 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25565 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25566 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25567 13:56:41 (0) **
25568 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25569 13:56:41 (0) ** Removing default security will cause some operations to fail!
25570 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25571 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25572 13:56:41 (0) **
25573 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
25574 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
25575 13:56:41 (0) ** - REMOVED ACE:
25576 13:56:41 (0) ** ACEType: &h0
25577 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25578 13:56:41 (0) ** ACEFlags: &h0
25579 13:56:41 (0) ** ACEMask: &h1F
25580 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25581 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25582 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25583 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25584 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25585 13:56:41 (0) **
25586 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25587 13:56:41 (0) ** Removing default security will cause some operations to fail!
25588 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25589 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25590 13:56:41 (0) **
25591 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
25592 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
25593 13:56:41 (0) ** - REMOVED ACE:
25594 13:56:41 (0) ** ACEType: &h0
25595 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25596 13:56:41 (0) ** ACEFlags: &h0
25597 13:56:41 (0) ** ACEMask: &h1F
25598 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25599 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25600 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25601 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25602 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25603 13:56:41 (0) **
25604 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25605 13:56:41 (0) ** Removing default security will cause some operations to fail!
25606 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25607 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25608 13:56:41 (0) **
25609 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
25610 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
25611 13:56:41 (0) ** - REMOVED ACE:
25612 13:56:41 (0) ** ACEType: &h0
25613 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25614 13:56:41 (0) ** ACEFlags: &h0
25615 13:56:41 (0) ** ACEMask: &h1F
25616 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25617 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25618 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25619 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25620 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25621 13:56:41 (0) **
25622 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25623 13:56:41 (0) ** Removing default security will cause some operations to fail!
25624 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25625 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25626 13:56:41 (0) **
25627 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
25628 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
25629 13:56:41 (0) ** - REMOVED ACE:
25630 13:56:41 (0) ** ACEType: &h0
25631 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25632 13:56:41 (0) ** ACEFlags: &h0
25633 13:56:41 (0) ** ACEMask: &h1F
25634 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25635 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25636 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25637 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25638 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25639 13:56:41 (0) **
25640 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25641 13:56:41 (0) ** Removing default security will cause some operations to fail!
25642 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25643 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25644 13:56:41 (0) **
25645 13:56:41 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
25646 13:56:41 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
25647 13:56:41 (0) ** - REMOVED ACE:
25648 13:56:41 (0) ** ACEType: &h0
25649 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25650 13:56:41 (0) ** ACEFlags: &h0
25651 13:56:41 (0) ** ACEMask: &hB
25652 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25653 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25654 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25655 13:56:41 (0) **
25656 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25657 13:56:41 (0) ** Removing default security will cause some operations to fail!
25658 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25659 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25660 13:56:41 (0) **
25661 13:56:41 (0) ** DCOM security for 'Windows Management Instrumentation' (Launch & Activation Permissions): ........................... MODIFIED.
25662 13:56:41 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
25663 13:56:41 (0) ** - REMOVED ACE:
25664 13:56:41 (0) ** ACEType: &h0
25665 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25666 13:56:41 (0) ** ACEFlags: &h0
25667 13:56:41 (0) ** ACEMask: &h1F
25668 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25669 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25670 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25671 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25672 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25673 13:56:41 (0) **
25674 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25675 13:56:41 (0) ** Removing default security will cause some operations to fail!
25676 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25677 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25678 13:56:41 (0) **
25679 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25680 13:56:41 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
25681 13:56:41 (0) ** - REMOVED ACE:
25682 13:56:41 (0) ** ACEType: &h0
25683 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25684 13:56:41 (0) ** ACEFlags: &h0
25685 13:56:41 (0) ** ACEMask: &h1F
25686 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25687 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25688 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25689 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25690 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25691 13:56:41 (0) **
25692 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25693 13:56:41 (0) ** Removing default security will cause some operations to fail!
25694 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25695 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25696 13:56:41 (0) **
25697 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25698 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
25699 13:56:41 (0) ** - REMOVED ACE:
25700 13:56:41 (0) ** ACEType: &h0
25701 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25702 13:56:41 (0) ** ACEFlags: &h0
25703 13:56:41 (0) ** ACEMask: &h1F
25704 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25705 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25706 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25707 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25708 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25709 13:56:41 (0) **
25710 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25711 13:56:41 (0) ** Removing default security will cause some operations to fail!
25712 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25713 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25714 13:56:41 (0) **
25715 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25716 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
25717 13:56:41 (0) ** - REMOVED ACE:
25718 13:56:41 (0) ** ACEType: &h0
25719 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25720 13:56:41 (0) ** ACEFlags: &h0
25721 13:56:41 (0) ** ACEMask: &h1F
25722 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25723 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25724 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25725 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25726 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25727 13:56:41 (0) **
25728 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25729 13:56:41 (0) ** Removing default security will cause some operations to fail!
25730 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25731 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25732 13:56:41 (0) **
25733 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25734 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
25735 13:56:41 (0) ** - REMOVED ACE:
25736 13:56:41 (0) ** ACEType: &h0
25737 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25738 13:56:41 (0) ** ACEFlags: &h0
25739 13:56:41 (0) ** ACEMask: &h1F
25740 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25741 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25742 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25743 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25744 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25745 13:56:41 (0) **
25746 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25747 13:56:41 (0) ** Removing default security will cause some operations to fail!
25748 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25749 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25750 13:56:41 (0) **
25751 13:56:41 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
25752 13:56:41 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
25753 13:56:41 (0) ** - REMOVED ACE:
25754 13:56:41 (0) ** ACEType: &h0
25755 13:56:41 (0) ** ACCESS_ALLOWED_ACE_TYPE
25756 13:56:41 (0) ** ACEFlags: &h0
25757 13:56:41 (0) ** ACEMask: &h1F
25758 13:56:41 (0) ** DCOM_RIGHT_EXECUTE
25759 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
25760 13:56:41 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
25761 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
25762 13:56:41 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
25763 13:56:41 (0) **
25764 13:56:41 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
25765 13:56:41 (0) ** Removing default security will cause some operations to fail!
25766 13:56:41 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
25767 13:56:41 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
25768 13:56:41 (0) **
25769 13:56:41 (0) **
25770 13:56:41 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
25771 13:56:41 (0) ** DCOM security error(s) detected: .................................................................................... 15.
25772 13:56:41 (0) ** WMI security warning(s) detected: ................................................................................... 0.
25773 13:56:41 (0) ** WMI security error(s) detected: ..................................................................................... 0.
25774 13:56:41 (0) **
25775 13:56:41 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
25776 13:56:41 (0) ** Overall WMI security status: ........................................................................................ OK.
25777 13:56:41 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
25778 13:56:41 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
25779 13:56:41 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
25780 13:56:41 (0) ** 'select * from MSFT_SCMEventLogEvent'
25781 13:56:41 (0) **
25782 13:56:41 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
25783 13:56:41 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 6 ERROR(S)!
25784 13:56:41 (0) ** - ROOT/MICROSOFTDFS, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25785 13:56:41 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25786 13:56:41 (0) ** - ROOT/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25787 13:56:41 (0) ** - ROOT/RSOP/USER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25788 13:56:41 (0) ** - ROOT/RSOP/COMPUTER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25789 13:56:41 (0) ** - ROOT/SERVICEMODEL, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25790 13:56:41 (0) **
25791 13:56:41 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 7 ERROR(S)!
25792 13:56:41 (0) ** - ROOT/MICROSOFTDFS, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25793 13:56:41 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25794 13:56:41 (0) ** - ROOT/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25795 13:56:41 (0) ** - ROOT/RSOP/USER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25796 13:56:41 (0) ** - ROOT/RSOP/COMPUTER, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25797 13:56:41 (0) ** - ROOT/SERVICEMODEL, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25798 13:56:41 (0) ** - Root/SECURITY, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25799 13:56:41 (0) **
25800 13:56:41 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 22 ERROR(S)!
25801 13:56:41 (0) ** - Root, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25802 13:56:41 (0) ** MOF Registration: ''
25803 13:56:41 (0) ** - ROOT/SUBSCRIPTION, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25804 13:56:41 (0) ** MOF Registration: ''
25805 13:56:41 (0) ** - ROOT/DEFAULT, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25806 13:56:41 (0) ** MOF Registration: ''
25807 13:56:41 (0) ** - ROOT/CIMV2, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25808 13:56:41 (0) ** MOF Registration: ''
25809 13:56:41 (0) ** - ROOT/CIMV2/SECURITY, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25810 13:56:41 (0) ** MOF Registration: ''
25811 13:56:41 (0) ** - ROOT/CIMV2/APPLICATIONS, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25812 13:56:41 (0) ** MOF Registration: ''
25813 13:56:41 (0) ** - ROOT/CIMV2/APPLICATIONS/WINDOWSPARENTALCONTROLS, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25814 13:56:41 (0) ** MOF Registration: ''
25815 13:56:41 (0) ** - ROOT/CIMV2/APPLICATIONS/GAMES, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25816 13:56:41 (0) ** MOF Registration: ''
25817 13:56:41 (0) ** - ROOT/CLI, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25818 13:56:41 (0) ** MOF Registration: ''
25819 13:56:41 (0) ** - ROOT/NAP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25820 13:56:41 (0) ** MOF Registration: ''
25821 13:56:41 (0) ** - ROOT/SECURITYCENTER2, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25822 13:56:41 (0) ** MOF Registration: ''
25823 13:56:41 (0) ** - ROOT/RSOP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25824 13:56:41 (0) ** MOF Registration: ''
25825 13:56:41 (0) ** - ROOT/WMI, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25826 13:56:41 (0) ** MOF Registration: ''
25827 13:56:41 (0) ** - ROOT/DIRECTORY, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25828 13:56:41 (0) ** MOF Registration: ''
25829 13:56:41 (0) ** - ROOT/DIRECTORY/LDAP, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25830 13:56:41 (0) ** MOF Registration: ''
25831 13:56:41 (0) ** - ROOT/SECURITYCENTER, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25832 13:56:41 (0) ** MOF Registration: ''
25833 13:56:41 (0) ** - ROOT/MSAPPS12, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25834 13:56:41 (0) ** MOF Registration: ''
25835 13:56:41 (0) ** - ROOT/MICROSOFT, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25836 13:56:41 (0) ** MOF Registration: ''
25837 13:56:41 (0) ** - ROOT/MICROSOFT/HOMENET, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25838 13:56:41 (0) ** MOF Registration: ''
25839 13:56:41 (0) ** - ROOT/ASPNET, __SystemSecurity, 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25840 13:56:41 (0) ** MOF Registration: ''
25841 13:56:41 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
25842 13:56:41 (0) ** MOF Registration: ''
25843 13:56:41 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
25844 13:56:41 (0) ** MOF Registration: ''
25845 13:56:41 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
25846 13:56:41 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
25847 13:56:41 (0) ** You can refresh the WMI class provider buffer with the following command:
25848 13:56:41 (0) **
25849 13:56:41 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
25850 13:56:41 (0) **
25851 13:56:41 (0) ** WMI MOF representations: ............................................................................................ OK.
25852 13:56:41 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
25853 13:56:41 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 1 ERROR(S)!
25854 13:56:41 (0) ** - ROOT/WMI, InstancesOfAsync, 'MSMouse', 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action.
25855 13:56:41 (0) ** MOF Registration: ''
25856 13:56:41 (0) **
25857 13:56:41 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
25858 13:56:41 (1) !! ERROR: WMI GET VALUE operation errors reported: ..................................................................... 1 ERROR(S)!
25859 13:56:41 (0) ** - Root/CIMV2, Instance: Win32_Service='WSCSVC', Property: Displayname='Centre de sécurité' (Expected default='Security Center').
25860 13:56:41 (0) **
25861 13:56:41 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
25862 13:56:41 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
25863 13:56:41 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
25864 13:56:41 (0) ** WMI static instances retrieved: ..................................................................................... 1511.
25865 13:56:41 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
25866 13:56:41 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
25867 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25868 13:56:41 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
25869 13:56:41 (0) ** DCOM: ............................................................................................................. 0.
25870 13:56:41 (0) ** WINMGMT: .......................................................................................................... 0.
25871 13:56:41 (0) ** WMIADAPTER: ....................................................................................................... 0.
25872 13:56:41 (0) **
25873 13:56:41 (0) ** # of additional Event Log events AFTER WMIDiag execution:
25874 13:56:41 (0) ** DCOM: ............................................................................................................. 0.
25875 13:56:41 (0) ** WINMGMT: .......................................................................................................... 0.
25876 13:56:41 (0) ** WMIADAPTER: ....................................................................................................... 0.
25877 13:56:41 (0) **
25878 13:56:41 (0) ** 34 error(s) 0x80041003 - (WBEM_E_ACCESS_DENIED) Current user does not have permission to perform the action
25879 13:56:41 (0) ** => This error is typically due to insufficient or restricted permissions in the examined system.
25880 13:56:41 (0) ** => ENSURE you are a Full Administrator of the examined system, if the WMI provider or the
25881 13:56:41 (0) ** WMI system security do not enforce any restrictions.
25882 13:56:41 (0) **
25883 13:56:41 (0) **
25884 13:56:41 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
25885 13:56:41 (0) ** => This error is typically a WMI error. This WMI error is due to:
25886 13:56:41 (0) ** - a missing WMI class definition or object.
25887 13:56:41 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
25888 13:56:41 (0) ** You can correct the missing class definitions by:
25889 13:56:41 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
25890 13:56:41 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
25891 13:56:41 (0) ** (This list can be built on a similar and working WMI Windows installation)
25892 13:56:41 (0) ** The following command line must be used:
25893 13:56:41 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
25894 13:56:41 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
25895 13:56:41 (0) ** with WMI by starting the ADAP process.
25896 13:56:41 (0) ** - a WMI repository corruption.
25897 13:56:41 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
25898 13:56:41 (0) ** to validate the WMI repository operations.
25899 13:56:41 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
25900 13:56:41 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
25901 13:56:41 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
25902 13:56:41 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
25903 13:56:41 (0) ** the WMI repository must be reconstructed.
25904 13:56:41 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
25905 13:56:41 (0) ** otherwise some applications may fail after the reconstruction.
25906 13:56:41 (0) ** This can be achieved with the following command:
25907 13:56:41 (0) ** i.e. 'WMIDiag ShowMOFErrors'
25908 13:56:41 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
25909 13:56:41 (0) ** ALL fixes previously mentioned.
25910 13:56:41 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
25911 13:56:41 (0) **
25912 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25913 13:56:41 (0) ** WMI Registry key setup: ............................................................................................. OK.
25914 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25915 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25916 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25917 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25918 13:56:41 (0) **
25919 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25920 13:56:41 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
25921 13:56:41 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
25922 13:56:41 (0) **
25923 13:56:41 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\FRANCIS\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_VISTA.CLI.SP2.32_PC-DE-FRANCIS_2012.10.19_13.47.18.LOG' for details.
25924 13:56:41 (0) **
25925 13:56:41 (0) ** WMIDiag v2.1 ended on vendredi 19 octobre 2012 at 13:56 (W:79 E:189 S:1).