y'a un problème, mais lequel?

system · 2008-02-03T09:19:13.000Z

windows xp me dit que avast 4.7 est désactivé. ma clef de license est valide jusqu’a juillet 2008.
avast n’exécute que 3 services sur 24 total. y’a un problème, mais lequel?
merci de m’aider.

system · 2008-02-03T17:19:37.000Z

since most admins and others speak english on this forum i will translate to the best of my ability (although i only know french from school):

“Windows xp indicated to me that avast 4.7 is inactive. My license key is valid until july 2008. Avast does not run three out of 24 services (although my translation could be wrong for this sentence. I’m not sure if that translates to 3 out of 24). It has a problem, but what is it? Thank you for helping me.”

system · 2008-02-03T22:22:01.000Z

Your translation seems quite correct, the last thing thast full57 is asking is how to fix it because there is obviously a problem.

Al968

system · 2008-02-05T01:58:04.000Z

My suggestion would be to do a repair of avast through the Add/Remove Programs.

Ma suggestion devrait faire une réparation d’avast par les programmes d’Add/Remove.

Edited to remove what may not be needed and to add French translation.

DavidR · 2008-02-05T15:36:16.000Z

By all accounts it is no longer a requirement to be connected as avast can repair using .vpu files in the setup folder. Unless of course the setup folder is missing files, in which case a reinstall would be required.

However if winXP Security Centre reports avast inactive, it could be a problem with the Security Centre WMI Repository, etc.

If you are running Windows XP, Service Pack 2 you can use a single command to detect and repair a corrupted WMI Repository. To do so, type the following from the command prompt (note that the parameter UpgradeRepository is case-sensitive and must be typed exactly as shown):

rundll32 wbemupgd, UpgradeRepository

After running UpgradeRepository you can verify the results by looking ay the Setup log. If inconsistencies are detected and if the operating system was able to rebuild the Repository you should see information in Setup.log similar to this:

(Wed Oct 12 13:46:36 2005): ===========================================================================
(Wed Oct 12 13:46:36 2005): Beginning WBEM Service Pack Installation
(Wed Oct 12 13:46:36 2005): Current build of wbemupgd.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:36 2005): Current build of wbemcore.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:52 2005): Inconsistent repository detected; it will be recreated
…
…
(Wed Oct 12 13:47:33 2005): Wbemupgd.dll Service Security upgrade succeeded (XP SP update).
(Wed Oct 12 13:47:33 2005): WBEM Service Pack Installation completed.
(Wed Oct 12 13:47:33 2005): ===========================================================================

Note. There will probably be other entries in the log as well, but you should specifically look for the ones shown above.
[/quote]

OR

* Click Start, Run and type CMD.EXE

Type this command and press Enter:

net stop winmgmt

Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad.). %windir% represents the path to the Windows directory, which is typically C:\Windows.

Switch to Command Prompt window, and type the following and press ENTER after each line:

net start winmgmt

EXIT
Reboot

system · 2008-02-05T16:09:00.000Z

um…i think you guys might want to translate ur advice back into French, but i cant help you there (especially with david’s answer).

DavidR · 2008-02-05T17:18:03.000Z

I would use babelfish to translate, but technical stuff doesn’t seem to translate well.

The main part is the Windows Start, Run and type rundll32 wbemupgd, UpgradeRepository (or copy and paste the command) and click OK.

If that didn’t work use the quoted text to open a CMD window, stop the service, rename the troublesome Repository folder and restart the services and hopefully windows will rebuild the repository on reboot.

system · 2008-02-05T21:45:47.000Z

DavidR post:5:

By all accounts it is no longer a requirement to be connected as avast can repair using .vpu files in the setup folder. Unless of course the setup folder is missing files, in which case a reinstall would be required.

However if winXP Security Centre reports avast inactive, it could be a problem with the Security Centre WMI Repository, etc.

If you are running Windows XP, Service Pack 2 you can use a single command to detect and repair a corrupted WMI Repository. To do so, type the following from the command prompt (note that the parameter UpgradeRepository is case-sensitive and must be typed exactly as shown):

rundll32 wbemupgd, UpgradeRepository

After running UpgradeRepository you can verify the results by looking ay the Setup log. If inconsistencies are detected and if the operating system was able to rebuild the Repository you should see information in Setup.log similar to this:

(Wed Oct 12 13:46:36 2005): ===========================================================================
(Wed Oct 12 13:46:36 2005): Beginning WBEM Service Pack Installation
(Wed Oct 12 13:46:36 2005): Current build of wbemupgd.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:36 2005): Current build of wbemcore.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:52 2005): Inconsistent repository detected; it will be recreated
…
…
(Wed Oct 12 13:47:33 2005): Wbemupgd.dll Service Security upgrade succeeded (XP SP update).
(Wed Oct 12 13:47:33 2005): WBEM Service Pack Installation completed.
(Wed Oct 12 13:47:33 2005): ===========================================================================

(Wed Oct 12 13:46:36 2005): ===========================================================================
(Wed Oct 12 13:46:36 2005): Beginning WBEM Service Pack Installation
(Wed Oct 12 13:46:36 2005): Current build of wbemupgd.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:36 2005): Current build of wbemcore.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:52 2005): Inconsistent repository detected; it will be recreated
…
…
(Wed Oct 12 13:47:33 2005): Wbemupgd.dll Service Security upgrade succeeded (XP SP update).
(Wed Oct 12 13:47:33 2005): WBEM Service Pack Installation completed.
(Wed Oct 12 13:47:33 2005): ===========================================================================
/quote]

OR

* Click Start, Run and type CMD.EXE

Type this command and press Enter:

net stop winmgmt

Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad.). %windir% represents the path to the Windows directory, which is typically C:\Windows.

Switch to Command Prompt window, and type the following and press ENTER after each line:

net start winmgmt

EXIT
Reboot

Traduction en Francais:

Maintenant, il n’est plus nécessaire d’être connecté vu qu’Avast peut faire une reparation en utilisant les fichiers .Vpu dans le répertoire d’installation. À moins bien sûr qu’il manque des fichiers dans le dossier d’installation. Le cas echeant, une réinstallation sera nécessaire.

Toutefois, si le Centre de Sécurité WinXP montre qu’Avast est inactif, cela pourrait être un problème avec le Centre de sécurité WMI Repository, ou autre.

Si vous utilisez Windows XP, Service Pack 2, vous pouvez utiliser une commande simple pour détecter et réparer un référentiel WMI corrompu. Pour ce faire, tapez la commande suivante à partir de l’invite de commande (notez que le paramètre UpgradeRepository est sensible à la frappe et doit être dactylographié exactement comme montré):

Rundll32 wbemupgd, UpgradeRepository

Après l’exécution de UpgradeRepository vous pouvez vérifier les résultats de la recherche dans le log de l’installation. Si des incohérences sont détectées et que le système d’exploitation a été en mesure de reconstruire le référentiel, vous devriez voir l’information dans le Setup.log similaire à ceci:

(Wed Oct 12 13:46:36 2005): ===========================================================================
(Wed Oct 12 13:46:36 2005): Beginning WBEM Service Pack Installation
(Wed Oct 12 13:46:36 2005): Current build of wbemupgd.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:36 2005): Current build of wbemcore.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:52 2005): Inconsistent repository detected; it will be recreated
…
…
(Wed Oct 12 13:47:33 2005): Wbemupgd.dll Service Security upgrade succeeded (XP SP update).
(Wed Oct 12 13:47:33 2005): WBEM Service Pack Installation completed.
(Wed Oct 12 13:47:33 2005): ===========================================================================

Note: Il y aura probablement d’autres entrées dans le journal, mais vous devriez recherche en particulier celles qui sont affichées ci-dessus.

Autre possibilitees:

Click sur Demarer, Execute et taper CMD.EXE
Taper cette commande et presser Entree:

net stop winmgmt

Utiliser Windows Explorer, et renommer le fichier %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad.). %windir%
Représente le chemin vers le répertoire Windows, ce qui est généralement C:\Windows.
Passer à la fenêtre d’invite de commande et tapez la commande suivante, puis appuyez sur ENTRÉE après chaque ligne:

net start winmgmt

EXIT
Reboot

DavidR · 2008-02-05T22:21:48.000Z

Thank you, hopefully it will help full57.

Announcements