Author Topic: Win XP Not Recognizing Avast  (Read 2001 times)

0 Members and 1 Guest are viewing this topic.

Offline MiguelHP

  • Newbie
  • *
  • Posts: 2
Win XP Not Recognizing Avast
« on: May 15, 2013, 04:22:48 PM »
It appears that Win XP is not recognizing Avast.  The Avast icon does appear in the Task Bar and if I mouse over it displays a message that Avast is running and that my system is secure.  Yet, the Windows Security Alerts shield also appears, in red with an X through it.  When I launch it, the Windows Security Centre indicates that my Virus Protection is OFF.  To the best of my recollection, this was never the case previously.  Can anyone shed some light on this.

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 72875
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Win XP Not Recognizing Avast
« Reply #1 on: May 15, 2013, 04:24:12 PM »
No problems here.
A clean reinstall might help.
Win 8.1 [x64] - Avast PremSec 21.11.6787.IBC [UI.679] - EEK - Firefox ESR 91.3 [NS/uBO/PB] - TB 91.3.2
Avast-Tools: Secure Browser 96.0 - Cleanup 21.3 - SecureLine 5.14 - Driver Updater 21.4 - CCleaner 5.87
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 85960
  • No support PMs thanks
Re: Win XP Not Recognizing Avast
« Reply #2 on: May 15, 2013, 04:45:31 PM »
- Windows Security Center not recognising avast!
Windows XP SP2, SP3 Start, Run, type cmd and click OK from the command prompt type 'rundll32 wbemupgd, RepairWMISetup' without the quotes and enter.

Quote
Microsoft Windows XP, Service Pack 2 or 3

If you are running Windows XP, Service Pack 2 or 3 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 at 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.

- OR
Quote
* Click Start, Run and type CMD.EXE

* Type this command and press Enter:

net stop wscsvc
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
net start wscsvc

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.9.2494 (build 21.9.6698.703) UI 1.0.672/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security