Author Topic: y'a un problème, mais lequel?  (Read 4171 times)

0 Members and 1 Guest are viewing this topic.

Offline full57

  • Newbie
  • *
  • Posts: 1
y'a un problème, mais lequel?
« on: February 03, 2008, 10:19:13 AM »
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.

Offline philly12

  • Full Member
  • ***
  • Posts: 156
  • Boring federal gov worker (slave)
Re: y'a un problème, mais lequel?
« Reply #1 on: February 03, 2008, 06:19:37 PM »
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." 
« Last Edit: February 04, 2008, 12:25:28 AM by philly12 »

Offline al968

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 847
Re: y'a un problème, mais lequel?
« Reply #2 on: February 03, 2008, 11:22:01 PM »
Your translation seems quite correct, the last thing thast full57 is asking is how to fix it because there is obviously a problem.

Al968

Offline CharleyO

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 7085
  • Be alert for error code - ID 10T
Re: y'a un problème, mais lequel?
« Reply #3 on: February 05, 2008, 02:58:04 AM »
***

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.

***
« Last Edit: February 05, 2008, 05:55:12 PM by CharleyO »
Self-built desktop (8 years old) - AMD64 3200+_Gigabyte GA-K8NS Ultra-939_4 gb RAM_GeForceFX 5800w/256 ram_XP/SP3_Avast 7_MBAM_ZA Free __and__ Toshiba Satellite Laptop_W7-64bit_ 4 gb Ram_Avast 8_MBAM

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84891
  • No support PMs thanks
Re: y'a un problème, mais lequel?
« Reply #4 on: February 05, 2008, 04:36:16 PM »
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
Quote
* 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
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline philly12

  • Full Member
  • ***
  • Posts: 156
  • Boring federal gov worker (slave)
Re: y'a un problème, mais lequel?
« Reply #5 on: February 05, 2008, 05:09:00 PM »
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). 

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84891
  • No support PMs thanks
Re: y'a un problème, mais lequel?
« Reply #6 on: February 05, 2008, 06:18:03 PM »
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.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Antarctica

  • Jr. Member
  • **
  • Posts: 40
Re: y'a un problème, mais lequel?
« Reply #7 on: February 05, 2008, 10:45:47 PM »
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
Quote
* 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
   
      

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84891
  • No support PMs thanks
Re: y'a un problème, mais lequel?
« Reply #8 on: February 05, 2008, 11:21:48 PM »
Thank you, hopefully it will help full57.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security