Bonjours à tous,
Donc voila mon problème, voulant installer le nouveau driver de ma carte graphique nvidia gforce gtx 770 j'ai rencontrer une erreur d’installation qui me mettait échec d’installation du pilote. évidament j'ai supprimer mon ancien pilote. et a se jours je ne peux plus en installer aucun ! tous me sorte une erreur d’installation. en farfouillant un peux sur le forum j'ai rencontrer un topic similaire avec une personne qui avais le même problème que moi http://forum.hardware.fr/hfr/Hardw [...] 0601_1.htm . en suivant se qu'il dit je site " Alors en fait ce qui c'est passé : j'ai donc vu qu'en fait c'était le service Infrastructure de gestion Windows qui n'était pas lancé, et quand j'essayais de le lancer manuellement j'avais l'erreur 126 qui me disait que c'était la merde. J'ai donc dl le logiciel de diagnostic de Windows spécialement conçu pour ce service (si si ça existe) et après fouille dans le LOG pendant 5 minutes j'ai vu que c'était une clé registre qui avait été changé... PAR LE PUTAIN DE VIRUS QUE J'AVAIS EU Y A 2 MOIS!! J'ai donc remis la bonne clé + redémarrage, le service est reparti et hop je peux installer mes pilotes normalement!
Alors au cas ou le problème arrive à d'autre gens qui tomberait sur ce message, l'outil de diagnostic est ici : http://www.microsoft.com/en-us/dow [...] px?id=7684 Le fonctionnement est simple, il faut lancer le .vbs et attendre un peu, cela génère un log dans le fichier TEMP standard de Windows. Il y a un gros "ERROR" devant les lignes qui ne vont pas avec le moyen de réparer si besoin. "
suivant sa demarche je trouve bien des erreurs
29944 12:33:38 (0) ** WMIDiag v2.1 started on samedi 31 mai 2014 at 12:30.
29945 12:33:38 (0) **
29946 12:33:38 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
29947 12:33:38 (0) **
29948 12:33:38 (0) ** This script is not supported under any Microsoft standard support program or service.
29949 12:33:38 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
29950 12:33:38 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
29951 12:33:38 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
29952 12:33:38 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
29953 12:33:38 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
29954 12:33:38 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
29955 12:33:38 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
29956 12:33:38 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
29957 12:33:38 (0) ** of the possibility of such damages.
29958 12:33:38 (0) **
29959 12:33:38 (0) **
29960 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
29961 12:33:38 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
29962 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
29963 12:33:38 (0) **
29964 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
29965 12:33:38 (0) ** Windows 7 - Service Pack 1 - 64-bit (7601) - User 'MALTOROF\MALTOROFS' on computer 'MALTOROF'.
29966 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
29967 12:33:38 (0) ** Environment: ........................................................................................................ OK.
29968 12:33:38 (0) ** System drive: ....................................................................................................... C: (Disque n° 1 partition n° 1).
29969 12:33:38 (0) ** Drive type: ......................................................................................................... IDE (Maxtor 6V250F0 SCSI Disk Device).
29970 12:33:38 (0) ** There are no missing WMI system files: .............................................................................. OK.
29971 12:33:38 (0) ** There are no missing WMI repository files: .......................................................................... OK.
29972 12:33:38 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
29973 12:33:38 (0) ** AFTER running WMIDiag:
29974 12:33:38 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
29975 12:33:38 (0) ** - Disk free space on 'C:': .......................................................................................... 138009 MB.
29976 12:33:38 (0) ** - INDEX.BTR, 5521408 bytes, 31/05/2014 11:55:40
29977 12:33:38 (0) ** - MAPPING1.MAP, 69644 bytes, 31/05/2014 11:49:10
29978 12:33:38 (0) ** - MAPPING2.MAP, 69644 bytes, 31/05/2014 11:55:40
29979 12:33:38 (0) ** - OBJECTS.DATA, 21651456 bytes, 31/05/2014 11:55:39
29980 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
29981 12:33:38 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
29982 12:33:38 (0) ** Windows Firewall Profile: ........................................................................................... PRIVATE.
29983 12:33:38 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
29984 12:33:38 (0) ** => This will prevent any WMI remote connectivity to this computer except
29985 12:33:38 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
29986 12:33:38 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
29987 12:33:38 (0) ** - 'Windows Management Instrumentation (WMI-In)'
29988 12:33:38 (0) ** - 'Windows Management Instrumentation (ASync-In)'
29989 12:33:38 (0) ** Verify the reported status for each of these three inbound rules below.
29990 12:33:38 (0) **
29991 12:33:38 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
29992 12:33:38 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
29993 12:33:38 (0) ** - You can adjust the configuration by executing the following command:
29994 12:33:38 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
29995 12:33:38 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
29996 12:33:38 (0) ** You can also enable each individual rule instead of activating the group rule.
29997 12:33:38 (0) **
29998 12:33:38 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. DISABLED.
29999 12:33:38 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
30000 12:33:38 (0) ** - You can adjust the configuration of this rule by executing the following command:
30001 12:33:38 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
30002 12:33:38 (0) **
30003 12:33:38 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ DISABLED.
30004 12:33:38 (0) ** => This will prevent any WMI inbound connectivity to this machine.
30005 12:33:38 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
30006 12:33:38 (0) ** - You can adjust the configuration of this rule by executing the following command:
30007 12:33:38 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
30008 12:33:38 (0) **
30009 12:33:38 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... DISABLED.
30010 12:33:38 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
30011 12:33:38 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
30012 12:33:38 (0) ** - You can adjust the configuration of this rule by executing the following command:
30013 12:33:38 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
30014 12:33:38 (0) **
30015 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30016 12:33:38 (0) ** DCOM Status: ........................................................................................................ OK.
30017 12:33:38 (0) ** WMI registry setup: ................................................................................................. OK.
30018 12:33:38 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
30019 12:33:38 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
30020 12:33:38 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
30021 12:33:38 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
30022 12:33:38 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
30023 12:33:38 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
30024 12:33:38 (0) ** this can prevent the service/application to work as expected.
30025 12:33:38 (0) **
30026 12:33:38 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
30027 12:33:38 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
30028 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30029 12:33:38 (0) ** WMI service DCOM setup: ............................................................................................. OK.
30030 12:33:38 (0) ** WMI components DCOM registrations: .................................................................................. OK.
30031 12:33:38 (0) ** WMI ProgID registrations: ........................................................................................... OK.
30032 12:33:38 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
30033 12:33:38 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
30034 12:33:38 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
30035 12:33:38 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
30036 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30037 12:33:38 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
30038 12:33:38 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
30039 12:33:38 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
30040 12:33:38 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
30041 12:33:38 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
30042 12:33:38 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
30043 12:33:38 (0) **
30044 12:33:38 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
30045 12:33:38 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
30046 12:33:38 (0) ** - REMOVED ACE:
30047 12:33:38 (0) ** ACEType: &h0
30048 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30049 12:33:38 (0) ** ACEFlags: &h0
30050 12:33:38 (0) ** ACEMask: &h3
30051 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30052 12:33:38 (0) ** DCOM_RIGHT_ACCESS_LOCAL
30053 12:33:38 (0) **
30054 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30055 12:33:38 (0) ** Removing default security will cause some operations to fail!
30056 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30057 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30058 12:33:38 (0) **
30059 12:33:38 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
30060 12:33:38 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
30061 12:33:38 (0) ** - REMOVED ACE:
30062 12:33:38 (0) ** ACEType: &h0
30063 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30064 12:33:38 (0) ** ACEFlags: &h0
30065 12:33:38 (0) ** ACEMask: &h7
30066 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30067 12:33:38 (0) ** DCOM_RIGHT_ACCESS_LOCAL
30068 12:33:38 (0) ** DCOM_RIGHT_ACCESS_REMOTE
30069 12:33:38 (0) **
30070 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30071 12:33:38 (0) ** Removing default security will cause some operations to fail!
30072 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30073 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30074 12:33:38 (0) **
30075 12:33:38 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
30076 12:33:38 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
30077 12:33:38 (0) ** - REMOVED ACE:
30078 12:33:38 (0) ** ACEType: &h0
30079 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30080 12:33:38 (0) ** ACEFlags: &h0
30081 12:33:38 (0) ** ACEMask: &h7
30082 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30083 12:33:38 (0) ** DCOM_RIGHT_ACCESS_LOCAL
30084 12:33:38 (0) ** DCOM_RIGHT_ACCESS_REMOTE
30085 12:33:38 (0) **
30086 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30087 12:33:38 (0) ** Removing default security will cause some operations to fail!
30088 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30089 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30090 12:33:38 (0) **
30091 12:33:38 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
30092 12:33:38 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
30093 12:33:38 (0) ** - REMOVED ACE:
30094 12:33:38 (0) ** ACEType: &h0
30095 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30096 12:33:38 (0) ** ACEFlags: &h0
30097 12:33:38 (0) ** ACEMask: &h1F
30098 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30099 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30100 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30101 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30102 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30103 12:33:38 (0) **
30104 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30105 12:33:38 (0) ** Removing default security will cause some operations to fail!
30106 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30107 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30108 12:33:38 (0) **
30109 12:33:38 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
30110 12:33:38 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
30111 12:33:38 (0) ** - REMOVED ACE:
30112 12:33:38 (0) ** ACEType: &h0
30113 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30114 12:33:38 (0) ** ACEFlags: &h0
30115 12:33:38 (0) ** ACEMask: &h1F
30116 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30117 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30118 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30119 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30120 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30121 12:33:38 (0) **
30122 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30123 12:33:38 (0) ** Removing default security will cause some operations to fail!
30124 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30125 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30126 12:33:38 (0) **
30127 12:33:38 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
30128 12:33:38 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
30129 12:33:38 (0) ** - REMOVED ACE:
30130 12:33:38 (0) ** ACEType: &h0
30131 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30132 12:33:38 (0) ** ACEFlags: &h0
30133 12:33:38 (0) ** ACEMask: &h1F
30134 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30135 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30136 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30137 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30138 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30139 12:33:38 (0) **
30140 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30141 12:33:38 (0) ** Removing default security will cause some operations to fail!
30142 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30143 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30144 12:33:38 (0) **
30145 12:33:38 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
30146 12:33:38 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
30147 12:33:38 (0) ** - REMOVED ACE:
30148 12:33:38 (0) ** ACEType: &h0
30149 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30150 12:33:38 (0) ** ACEFlags: &h0
30151 12:33:38 (0) ** ACEMask: &h1F
30152 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30153 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30154 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30155 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30156 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30157 12:33:38 (0) **
30158 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30159 12:33:38 (0) ** Removing default security will cause some operations to fail!
30160 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30161 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30162 12:33:38 (0) **
30163 12:33:38 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
30164 12:33:38 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
30165 12:33:38 (0) ** - REMOVED ACE:
30166 12:33:38 (0) ** ACEType: &h0
30167 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30168 12:33:38 (0) ** ACEFlags: &h0
30169 12:33:38 (0) ** ACEMask: &h1F
30170 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30171 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30172 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30173 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30174 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30175 12:33:38 (0) **
30176 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30177 12:33:38 (0) ** Removing default security will cause some operations to fail!
30178 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30179 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30180 12:33:38 (0) **
30181 12:33:38 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
30182 12:33:38 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
30183 12:33:38 (0) ** - REMOVED ACE:
30184 12:33:38 (0) ** ACEType: &h0
30185 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30186 12:33:38 (0) ** ACEFlags: &h0
30187 12:33:38 (0) ** ACEMask: &hB
30188 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30189 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30190 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30191 12:33:38 (0) **
30192 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30193 12:33:38 (0) ** Removing default security will cause some operations to fail!
30194 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30195 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30196 12:33:38 (0) **
30197 12:33:38 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
30198 12:33:38 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
30199 12:33:38 (0) ** - REMOVED ACE:
30200 12:33:38 (0) ** ACEType: &h0
30201 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30202 12:33:38 (0) ** ACEFlags: &h0
30203 12:33:38 (0) ** ACEMask: &h1F
30204 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30205 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30206 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30207 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30208 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30209 12:33:38 (0) **
30210 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30211 12:33:38 (0) ** Removing default security will cause some operations to fail!
30212 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30213 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30214 12:33:38 (0) **
30215 12:33:38 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
30216 12:33:38 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
30217 12:33:38 (0) ** - REMOVED ACE:
30218 12:33:38 (0) ** ACEType: &h0
30219 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30220 12:33:38 (0) ** ACEFlags: &h0
30221 12:33:38 (0) ** ACEMask: &h1F
30222 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30223 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30224 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30225 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30226 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30227 12:33:38 (0) **
30228 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30229 12:33:38 (0) ** Removing default security will cause some operations to fail!
30230 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30231 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30232 12:33:38 (0) **
30233 12:33:38 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
30234 12:33:38 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
30235 12:33:38 (0) ** - REMOVED ACE:
30236 12:33:38 (0) ** ACEType: &h0
30237 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30238 12:33:38 (0) ** ACEFlags: &h0
30239 12:33:38 (0) ** ACEMask: &h1F
30240 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30241 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30242 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30243 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30244 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30245 12:33:38 (0) **
30246 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30247 12:33:38 (0) ** Removing default security will cause some operations to fail!
30248 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30249 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30250 12:33:38 (0) **
30251 12:33:38 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
30252 12:33:38 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
30253 12:33:38 (0) ** - REMOVED ACE:
30254 12:33:38 (0) ** ACEType: &h0
30255 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30256 12:33:38 (0) ** ACEFlags: &h0
30257 12:33:38 (0) ** ACEMask: &h1F
30258 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30259 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30260 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30261 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30262 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30263 12:33:38 (0) **
30264 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30265 12:33:38 (0) ** Removing default security will cause some operations to fail!
30266 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30267 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30268 12:33:38 (0) **
30269 12:33:38 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
30270 12:33:38 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
30271 12:33:38 (0) ** - REMOVED ACE:
30272 12:33:38 (0) ** ACEType: &h0
30273 12:33:38 (0) ** ACCESS_ALLOWED_ACE_TYPE
30274 12:33:38 (0) ** ACEFlags: &h0
30275 12:33:38 (0) ** ACEMask: &h1F
30276 12:33:38 (0) ** DCOM_RIGHT_EXECUTE
30277 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
30278 12:33:38 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
30279 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
30280 12:33:38 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
30281 12:33:38 (0) **
30282 12:33:38 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
30283 12:33:38 (0) ** Removing default security will cause some operations to fail!
30284 12:33:38 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
30285 12:33:38 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
30286 12:33:38 (0) **
30287 12:33:38 (0) **
30288 12:33:38 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
30289 12:33:38 (0) ** DCOM security error(s) detected: .................................................................................... 14.
30290 12:33:38 (0) ** WMI security warning(s) detected: ................................................................................... 0.
30291 12:33:38 (0) ** WMI security error(s) detected: ..................................................................................... 0.
30292 12:33:38 (0) **
30293 12:33:38 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
30294 12:33:38 (0) ** Overall WMI security status: ........................................................................................ OK.
30295 12:33:38 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
30296 12:33:38 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
30297 12:33:38 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
30298 12:33:38 (0) ** 'select * from MSFT_SCMEventLogEvent'
30299 12:33:38 (0) **
30300 12:33:38 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
30301 12:33:38 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 4 NAMESPACE(S)!
30302 12:33:38 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
30303 12:33:38 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTVOLUMEENCRYPTION.
30304 12:33:38 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
30305 12:33:38 (0) ** - ROOT/SERVICEMODEL.
30306 12:33:38 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
30307 12:33:38 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
30308 12:33:38 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
30309 12:33:38 (0) ** i.e. 'WMIC.EXE /NODE:"MALTOROF" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
30310 12:33:38 (0) **
30311 12:33:38 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
30312 12:33:38 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
30313 12:33:38 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 30 ERROR(S)!
30314 12:33:38 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30315 12:33:38 (0) ** MOF Registration: ''
30316 12:33:38 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30317 12:33:38 (0) ** MOF Registration: ''
30318 12:33:38 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30319 12:33:38 (0) ** MOF Registration: ''
30320 12:33:38 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30321 12:33:38 (0) ** MOF Registration: ''
30322 12:33:38 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30323 12:33:38 (0) ** MOF Registration: ''
30324 12:33:38 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30325 12:33:38 (0) ** MOF Registration: ''
30326 12:33:38 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30327 12:33:38 (0) ** MOF Registration: ''
30328 12:33:38 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30329 12:33:38 (0) ** MOF Registration: ''
30330 12:33:38 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30331 12:33:38 (0) ** MOF Registration: ''
30332 12:33:38 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30333 12:33:38 (0) ** MOF Registration: ''
30334 12:33:38 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30335 12:33:38 (0) ** MOF Registration: ''
30336 12:33:38 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30337 12:33:38 (0) ** MOF Registration: ''
30338 12:33:38 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30339 12:33:38 (0) ** MOF Registration: ''
30340 12:33:38 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30341 12:33:38 (0) ** MOF Registration: ''
30342 12:33:38 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30343 12:33:38 (0) ** MOF Registration: ''
30344 12:33:38 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30345 12:33:38 (0) ** MOF Registration: ''
30346 12:33:38 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30347 12:33:38 (0) ** MOF Registration: ''
30348 12:33:38 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30349 12:33:38 (0) ** MOF Registration: ''
30350 12:33:38 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30351 12:33:38 (0) ** MOF Registration: ''
30352 12:33:38 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30353 12:33:38 (0) ** MOF Registration: ''
30354 12:33:38 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30355 12:33:38 (0) ** MOF Registration: ''
30356 12:33:38 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30357 12:33:38 (0) ** MOF Registration: ''
30358 12:33:38 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30359 12:33:38 (0) ** MOF Registration: ''
30360 12:33:38 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30361 12:33:38 (0) ** MOF Registration: ''
30362 12:33:38 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30363 12:33:38 (0) ** MOF Registration: ''
30364 12:33:38 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30365 12:33:38 (0) ** MOF Registration: ''
30366 12:33:38 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30367 12:33:38 (0) ** MOF Registration: ''
30368 12:33:38 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30369 12:33:38 (0) ** MOF Registration: ''
30370 12:33:38 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30371 12:33:38 (0) ** MOF Registration: ''
30372 12:33:38 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
30373 12:33:38 (0) ** MOF Registration: ''
30374 12:33:38 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
30375 12:33:38 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
30376 12:33:38 (0) ** You can refresh the WMI class provider buffer with the following command:
30377 12:33:38 (0) **
30378 12:33:38 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
30379 12:33:38 (0) **
30380 12:33:38 (0) ** WMI MOF representations: ............................................................................................ OK.
30381 12:33:38 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
30382 12:33:38 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
30383 12:33:38 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 2 WARNING(S)!
30384 12:33:38 (0) ** - Root/CIMV2, 'Select * From Win32_VideoController' did not return any instance while AT LEAST 1 instance is expected.
30385 12:33:38 (0) ** - Root/CIMV2, 'Select * From Win32_DesktopMonitor' did not return any instance while AT LEAST 1 instance is expected.
30386 12:33:38 (0) **
30387 12:33:38 (1) !! ERROR: WMI GET VALUE operation errors reported: ..................................................................... 1 ERROR(S)!
30388 12:33:38 (0) ** - Root/CIMV2, Instance: Win32_Service='WSCSVC', Property: Displayname='Centre de sécurité' (Expected default='Security Center').
30389 12:33:38 (0) **
30390 12:33:38 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
30391 12:33:38 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
30392 12:33:38 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
30393 12:33:38 (0) ** WMI static instances retrieved: ..................................................................................... 1792.
30394 12:33:38 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
30395 12:33:38 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
30396 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30397 12:33:38 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
30398 12:33:38 (0) ** DCOM: ............................................................................................................. 0.
30399 12:33:38 (0) ** WINMGMT: .......................................................................................................... 0.
30400 12:33:38 (0) ** WMIADAPTER: ....................................................................................................... 0.
30401 12:33:38 (0) **
30402 12:33:38 (0) ** # of additional Event Log events AFTER WMIDiag execution:
30403 12:33:38 (0) ** DCOM: ............................................................................................................. 0.
30404 12:33:38 (0) ** WINMGMT: .......................................................................................................... 0.
30405 12:33:38 (0) ** WMIADAPTER: ....................................................................................................... 0.
30406 12:33:38 (0) **
30407 12:33:38 (0) ** 30 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
30408 12:33:38 (0) ** => This error is typically a WMI error. This WMI error is due to:
30409 12:33:38 (0) ** - a missing WMI class definition or object.
30410 12:33:38 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
30411 12:33:38 (0) ** You can correct the missing class definitions by:
30412 12:33:38 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
30413 12:33:38 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
30414 12:33:38 (0) ** (This list can be built on a similar and working WMI Windows installation)
30415 12:33:38 (0) ** The following command line must be used:
30416 12:33:38 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
30417 12:33:38 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
30418 12:33:38 (0) ** with WMI by starting the ADAP process.
30419 12:33:38 (0) ** - a WMI repository corruption.
30420 12:33:38 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
30421 12:33:38 (0) ** to validate the WMI repository operations.
30422 12:33:38 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
30423 12:33:38 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
30424 12:33:38 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
30425 12:33:38 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
30426 12:33:38 (0) ** the WMI repository must be reconstructed.
30427 12:33:38 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
30428 12:33:38 (0) ** otherwise some applications may fail after the reconstruction.
30429 12:33:38 (0) ** This can be achieved with the following command:
30430 12:33:38 (0) ** i.e. 'WMIDiag ShowMOFErrors'
30431 12:33:38 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
30432 12:33:38 (0) ** ALL fixes previously mentioned.
30433 12:33:38 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
30434 12:33:38 (0) **
30435 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30436 12:33:38 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
30437 12:33:38 (0) ** INFO: Unexpected registry key value:
30438 12:33:38 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
30439 12:33:38 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
30440 12:33:38 (0) ** From the command line, the registry configuration can be corrected with the following command:
30441 12:33:38 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
30442 12:33:38 (0) **
30443 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30444 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30445 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30446 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30447 12:33:38 (0) **
30448 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30449 12:33:38 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
30450 12:33:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
30451 12:33:38 (0) **
30452 12:33:38 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\MALTOROFS.MALTOROF\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_WIN7_.CLI.SP1.64_MALTOROF_2014.05.31_12.30.08.LOG' for details.
30453 12:33:38 (0) **
30454 12:33:38 (0) ** WMIDiag v2.1 ended on samedi 31 mai 2014 at 12:33 (W:87 E:51 S:1).
le problème, j'arrive pas a comprendre comment les réparer, je vous en suplies a genoux si qu'elle qu'un a une solution pour refaire marcher mon installation de drivers aidez moi :*(
