BIG problem: Avast Net Client Service is making PCs Freeze when loading desktop!

[studio_two]

Just want to say that we were bitten by this last week. In total 4 computers got hung at "Please Wait".

It's was even less fun when it happened on our network server (SBS 2008). I had almost 50 users unable to access email / fileshares. 

[1tb]

We have seen this many times and we think it always happens when updating from old Business Protection client to Endpoint Protection client.  We have found so far the only solution:

1. Boot into Safe Mode with Networking.
2. Uninstall avast Endpoint Protection client (if on the server you can leave SOA installed) - don't restart yet.
3. Before you restart, download and run ASWCLEAR.EXE from the avast website.
4. When you run this removal tool, tell it you are uninstalling "avast business protection" and select the folders "C:\program files\avast software"
5. Reboot and check you can now load windows normally.
6. Deploy the Endpoint Protection Client to the pc again.

[InMyName]

We have seen this many times and we think it always happens when updating from old Business Protection client to Endpoint Protection client.  We have found so far the only solution:

1. Boot into Safe Mode with Networking.
2. Uninstall avast Endpoint Protection client (if on the server you can leave SOA installed) - don't restart yet.
3. Before you restart, download and run ASWCLEAR.EXE from the avast website.
4. When you run this removal tool, tell it you are uninstalling "avast business protection" and select the folders "C:\program files\avast software"
5. Reboot and check you can now load windows normally.
6. Deploy the Endpoint Protection Client to the pc again.

Thanks for that information. I'm now in two minds whether to go round and do this on 150 PCs or wait to see if there is going to be a fix.

[Martech]

I'm seeing the same freezing problem on about 20 Win7 Pro, 64bit, Clients.
This is extremely annoying, and I urge avast to fix this. I already regret buying those licenses...

Just tried for more than two hours to get a freshly bought HP ProBook 6570b to work, but after installing Avast I wasn't able to boot anymore.
Uninstalled avast, now it runs like a charm. Really disappointing.

[1tb]

BUMP!

This is a still a huge problem for us. We find it is affecting dozens of workstations across multiple sites. Windows XP machines can't have services set to delayed start, and in any event as noted by earlier posts- these settings are overwritten.  Supposedly in Win7 and above this problem can be worked around by using a GPO during login.  Seriously are you suggesting we need to use these types of hacks to make avast a viable corporate antivirus solution? 

Avast needs to step up and take the corporate world seriously. Please!

[kc0mlp]

Same Here. We are a school running about 120 desktop machines of which about half reliably experience this issue. We are enrolled in the excellent Endpoint Protection for Schools program but I cannot keep using this system. I'd like to thank the Avast team for their outreach to education but we have the same effective issues as most enterprise institutions and this has cost us far too much time and trouble already.

Attempted 'fixes':

• Start Avast services after others (troubleshooting)
• Delayed service start for either avastsrvc, enterprise management service or both
• Delayed start via user login script and machine startup script. (both local and via AD sysvol)
• Disabling Enterprise management service.
• Installing via the webpackage.
• Installing via the deployment package manually.

At this point the only fix for us is to boot into safe mode and uninstall. I will keep an eye out for the time this seems to be stable but for now it's just not a solution for us.

Edit: Spelling

[.: Mac :.]

Ive been trying to find time to get the v8 beta running on some systems that do this, if its not fixed in v8 we will have to explore other options.

[bbehrendtmsj]

Please report on weather this is still an issue on Version 8.   My version 7 install is having major issues.

[Michael Due]

I'd very much love an official response also, but as far as i understand, the reason of the lack of response or updates on this issue is partially because Avast has been unable to replicate the issue in their environment.

Anyways - Ive updated to v8 beta and last friday to v8 RC... So far initial tests are looking good.

I have not yet seen a v8 rc or beta machine freeze.

But again, i'd also very much love an official response...

[.: Mac :.]

I'd very much love an official response also, but as far as i understand, the reason of the lack of response or updates on this issue is partially because Avast has been unable to replicate the issue in their environment.

Anyways - Ive updated to v8 beta and last friday to v8 RC... So far initial tests are looking good.

I have not yet seen a v8 rc or beta machine freeze.

But again, i'd also very much love an official response...

Can confirm this, early tests show that this has not yet occurred on a machine running the v8 client. But it would be a good thing to get a official response.

[avast@@dvantage77.com]

I had several clients with Windows XP, Pentium 4, either 512MB or 1GB of RAM that were locking up, managed EPS ver. 7.  Converted to EPS ver. 8 RC, custom install, removed all virtualization components, and now for the 1st time, had an install with no ASWSNX, and they are GREAT NOW! I like ver. 8, now with another of my recommendations: Global Exclusion!



Sincerely,
 
J.R. "AutoSandbox Guy" Guthrie

"At this point in time, the Internet should be regarded as an Enemy Weapons System!"
 

[woronick]

I have two Windows XP computers, both running Avast 8.0.1489. I am having lockup problems with the first computer. I have to boot into safe mode in order to get the computer to work. The second computer was bought second hand. I had problems getting my name into the computer as owner and administrator and owner. It has 2 different profiles in the documents and settings folder, with my name in the two folders. I was not able to delete the one I thought was unnecessary. This is probably why I don't have trouble with the second computer.