Avast not recognized by Windows security center

Avast Free Antivirus / Premium Security
1

Hello,

I’m having this problem with Windows Vista Ultimate 32-bit and Avast Home Edition (version 4.8.1282). Yet, on my laptop, running 64-bit Vista Ultimate the anti-virus is detected fine.

I have tried everything I could find on the Internet so far, I have applied every guide found on this forum - all with no success.

Things I have done so far:

  • Re-installing Avast several times.
  • Starting/stopping WMI (and its dependent Security Service) as well as pausing it using both the GUI and a bat file.
  • Renaming/deleting repository folder several times while the service was stopped/paused.
  • Even restoring value of PATH environmental variable to its default as suggested by someone on this board.

Any advice on how this could be fixed?

Thank you very much!

2

Please try restarting the avast antivirus service (Control Panel → Administrative Tools → Services).

3

Thanks!

Now the anti-virus is reported as turned off in WSC and when I try to turn it on I get:

“avast! Unknown error. Program cannot activate resident part (Standard Shield provider not found)” message.

Avast seems to be running fine.

4

It works now!!!

Not sure what happened, but I re-installed Avast again and then re-started Avast service as recommended. Upon rebooting the system - voila, all is running well!

Thank you so much! ;D

5

Vlk, it seems it’s not an isolated incident (remember mine yesterday).
Any idea why this happens?

6

Yes, I have a very good idea, and it is: because the new Vista SP1 WSC APIs suck big time.
It’s the worst crap MS has come up with for a very long time…

7

So they’ve changed it? Funny, because last official version of avast! worked like a charm on Vista SP1…

8

From the Vista SP1 Change Log:

Improves the trustworthiness of data presented in Windows Security Center (WSC) by ensuring that only authenticated security applications can communicate with WSC.

I think the old one is going to be turned of shortly - it has some timeout hardcoded in it. Vlk will surely know more details.

9

Yes, the official announcement was that the old API will stop working 270 days after the release of Vista SP1. :slight_smile:

So maybe some other AV vendors (who haven’t migrated to the new APIs yet) can prepare for some extra traffic for their support departments ;D

10

Aaaah, thats why you rushed a bit and implimented this before timebomb goes off :slight_smile:
Makes sense.

11

So that would put the timeout at …when?

12

Well, given the quality of this API, it’s questionable whether migrating to the new API won’t have a similar effect :wink:

13

h

14

I’d like to now