AVAST 2015 R3 SP1 (2015.10.3.2225)

heikwith · 2015-09-01T12:45:15.000Z

Asyn post:106:

heikwith post:105:

Via the ticket we found the cause of these severe problem.
The cause is a collision between Avast 10.3.2225 and HitmanPro Alert 3.0.48.196.

Thanks for the info, good to know.

I got this answer in the ticket:

We do not recommend you to use more than one security application on one computer. This can cause a lot of conflict.
You should uninstall HitmanPro.
…
Miroslav Jenšík
Technical Support Engineer
AVAST Software s.r.o.

Where is the service we got in the future from Avast when we had severe problems.
As we see in this forum how many problems there are still in Avast 10.3.2225, I expect this is also a bug in Avast.

bob3160 · 2015-09-01T13:53:12.000Z

heikwith post:116:

Asyn post:106:

heikwith post:105:

Via the ticket we found the cause of these severe problem.
The cause is a collision between Avast 10.3.2225 and HitmanPro Alert 3.0.48.196.

Thanks for the info, good to know.

I got this answer in the ticket:

We do not recommend you to use more than one security application on one computer. This can cause a lot of conflict.
You should uninstall HitmanPro.
…
Miroslav Jenšík
Technical Support Engineer
AVAST Software s.r.o.

Where is the service we got in the future from Avast when we had severe problems.
As we see in this forum how many problems there are still in Avast 10.3.2225, I expect this is also a bug in Avast.

No it’s a conflict with HitmanPro. Remove it and your problem will most likely be gone.

heikwith · 2015-09-01T14:52:28.000Z

bob3160 post:117:

heikwith post:116:

Asyn post:106:

heikwith post:105:

Via the ticket we found the cause of these severe problem.
The cause is a collision between Avast 10.3.2225 and HitmanPro Alert 3.0.48.196.

Thanks for the info, good to know.

I got this answer in the ticket:

We do not recommend you to use more than one security application on one computer. This can cause a lot of conflict.
You should uninstall HitmanPro.
…
Miroslav Jenšík
Technical Support Engineer
AVAST Software s.r.o.

Where is the service we got in the future from Avast when we had severe problems.
As we see in this forum how many problems there are still in Avast 10.3.2225, I expect this is also a bug in Avast.

No it’s a conflict with HitmanPro. Remove it and your problem will most likely be gone.

My problem with Avast 10.3.2225 was gone after uninstall of HitmanPro Alert and now it’s a conflict with HitmanPro.
But I did not remove HitmanPro and my Vista in still happy with 10.3.2225.
Can you explain this something more.

essexboy · 2015-09-01T16:41:05.000Z

There is no difference the low level drivers have probably changed in Avast

system · 2015-09-03T10:57:06.000Z

paul.baynton post:50:

I am also having problems with Avast Free 10.3.2225 update clashing with Microsoft Office 2003.
The mouse right click menu now no longer works in Outlook, I haven’t noticed if I am also suffering from some of the other mentioned issues.
I confirmed the problem is definitely with Avast Free 10.3.2225 update, because I restored the PC to before this Avast update then Office 2003 was OK again, but as soon as the Avast update 10.3.2225 was re-installed the problem came back.

I am using Windows 7 SP1 and Microsoft Firewall. What is the solution to get Office working normally again?

The same probelm as on my machine!

My configuration is only a little bit different: Windows XP SP3 - Outlook 2002 - The effect, respectively the bug is the same: The mouse right click menu now no longer works in Outlook!! Additionally I have no more access to the Outlook 2002 address book.

Since many years I’ve used avast. But since yesterday no more longer. In all this years there were similar huge bugs. But the most bugs were gone with a new release.

In principle I want use avast furthermore. The avast advantage is that ist works more or less good in combination of an old Pentium Mobile with only 2000 Ghz and only 1GB RAM. In contrast the Avira is nearly not usable with my old machine (Avira takes appox. 400-500 MB of my 1GB RAM - that’s frenzy and crazy! - Avast makes the same job for the half of the ressources)

Please, does anyone know what is to do now? I only want to use my Outook 2002 on a proper way again. Does there exist a new release or a new patch to solve this issue?

Asyn · 2015-09-03T11:06:13.000Z

Archey post:120:

Please, does anyone know what is to do now? I only want to use my Outook 2002 on a proper way again. Does there exist a new release or a new patch to solve this issue?

You can try the latest beta: https://forum.avast.com/index.php?topic=175753.0

system · 2015-09-03T11:23:02.000Z

Asyn post:121:

Archey post:120:

Please, does anyone know what is to do now? I only want to use my Outook 2002 on a proper way again. Does there exist a new release or a new patch to solve this issue?

You can try the latest beta: https://forum.avast.com/index.php?topic=175753.0

Thank you for your fast response!

But first one question: Do you think this beta is safe? (safe for my 12 years properly working XP)

I’ve read in this thread about many frozen Windows Systems. I would prefer to avoid such experiences.

Has anyone tried to install this beta, and solved it problems like I have mentioned above?

Asyn · 2015-09-03T11:27:13.000Z

Archey post:122:

But first one question: Do you think this beta is safe? (safe for my 12 years properly working XP)

It works well on my XP here. If you want to test it is up to you.

MartinZ · 2015-09-03T14:15:24.000Z

Hi in beta this should be solved and we also work for small update for non-beta versions fixing this issue. It should be released in few days.

beegolden · 2015-09-03T16:38:51.000Z

MartinZ post:124:

Hi in beta this should be solved and we also work for small update for non-beta versions fixing this issue. It should be released in few days.

so glad that an update for x.2225 will be available soon. I sure hope that it works in correcting the problems I (and others) encountered with the first release

system · 2015-09-04T10:09:38.000Z

Now I’ve installed the BETA 10.4.2227 - “in memory of Jan Koubek”. And everything works fine! I’m happy again.

In Outlook 2002 the right click menus are available again, and also the access to the internal Outlook 2002 address book is recovered!

After many years of using avast, now is the time to give thanks for the avast-team for providing a fast and lean antivirus programm.

In the last years I’ve tried many different AV (Norton, Comodo, Avira), but Avast is the only one which works with an efficient usage of Memory and CPU.

To compare: Avira needs approx. 600 MB Memory, and each call of a website produces a high CPU usage. In my case, I work with an old 2000 Ghz Pentium Mobile Processor, with 1GB RAM, this is not practicable and usable. Imagine, the Windows XP itself needs about 230 MB RAM, now a AV like Avira takes further 600 MB Memory - this remains only 170 MB Memory for executing of programms. That’s absurd.

On the other side, avast need only approx. 90 MB Memory, and it doesn’t retard and strain the CPU very much. I hope this efficient usage of Memory and CPU will be persist in the next years.

Sadly, I’ve to say avast has produced in the past years from time to time some huge bugs. To be fair, the others (e.g. Norton) do the same. Especially, the avast automatic programm updates of some past releases caused serious Windows XP problems from time to time.

For instance, since a few years it’s no more possible to disable the avast addin inside the Outlook 2002 for test purposes in an emergency, because there is no more avast entry in the Outlook-addin area.

Maybe my post should be better stored in the Beta Release section?

Finally, I want to ask if I have to deinstall the Beta Release, if I want to use the next regular avast version? Or could I receive the next regular avast version about the automatic programm update function of my current beta release?

Asyn · 2015-09-04T10:12:54.000Z

Archey post:126:

Finally, I want to ask if I have to deinstall the Beta Release, if I want to use the next regular avast version? Or could I receive the next regular avast version about the automatic programm update function of my current beta release?

The beta version will update to the final when it’s ready.

system · 2015-09-04T11:06:42.000Z

Thanks for your fast response.

Sorry, but in this circumstance I don’t understand this both statements:

Asyn post:127:

The beta version will update to the final when it’s ready.

bob3160:

If you simply update from the beta to the full version, you’ll receive the next beta once it’s released.

https://forum.avast.com/index.php?topic=175753.msg1247748#msg1247748

Isn’t it a contradiction?

NON · 2015-09-04T11:12:13.000Z

Archey post:128:

Thanks for your fast response.

Sorry, but in this circumstance I don’t understand this both statements:

Asyn post:127:

The beta version will update to the final when it’s ready.

bob3160:

If you simply update from the beta to the full version, you’ll receive the next beta once it’s released.

https://forum.avast.com/index.php?topic=175753.msg1247748#msg1247748

Isn’t it a contradiction?

Both are true, you can update your beta to final, but still you’re in the beta stream.
This means, when new beta is released, your final version will be updated to the latest beta.

beegolden · 2015-09-04T19:52:42.000Z

beegolden post:125:

MartinZ post:124:

Hi in beta this should be solved and we also work for small update for non-beta versions fixing this issue. It should be released in few days.

so glad that an update for x.2225 will be available soon. I sure hope that it works in correcting the problems I (and others) encountered with the first release

A few questions about the update:
What # will the update have? I don’t want to install x.2225 and go back to square one with problems. (I had to revert back to x.2218). Will I need to install x.2225 and then the update to that or will installing the update work by itself? And, when do you think the update will be released.

Thanks so much!

DavidR · 2015-09-04T20:58:03.000Z

beegolden post:130:

beegolden post:125:

MartinZ post:124:

Hi in beta this should be solved and we also work for small update for non-beta versions fixing this issue. It should be released in few days.

so glad that an update for x.2225 will be available soon. I sure hope that it works in correcting the problems I (and others) encountered with the first release

A few questions about the update:
What # will the update have? I don’t want to install x.2225 and go back to square one with problems. (I had to revert back to x.2218). Will I need to install x.2225 and then the update to that or will installing the update work by itself? And, when do you think the update will be released.

Thanks so much!

Monitor the latest beta topic, https://forum.avast.com/index.php?topic=176033.0, though there is no detailed info on what it fixes/introduces yet.

beegolden · 2015-09-05T07:09:55.000Z

https://forum.avast.com/index.php?topic=176033.0[/url], though there is no detailed info on what it fixes/introduces yet.

Thanks! I’ve asked my question there as well as marked the topic to notify me.

system · 2015-09-06T17:17:17.000Z

Pardon my ignorance, BIG thanks to all those who have already provided so much useful information, but…

What is the advantage of installing the Beta vs staying with an already working 2218?

I’ve read here that some (maybe all) of the Win XP problems associated with updates 2223 and above appear fixed in the Beta, but they weren’t broken in 2218.

I always heard that “IF it ain’t broke, don’t fix it”, so what’s to gain in going the Beta route? Why not stay with 2218, and wait for a fixed/fully functioning release with new benefits.

Thanks for listening.

DavidR · 2015-09-06T18:14:18.000Z

ragtop1998 post:133:

Pardon my ignorance, BIG thanks to all those who have already provided so much useful information, but…

What is the advantage of installing the Beta vs staying with an already working 2218?

I’ve read here that some (maybe all) of the Win XP problems associated with updates 2223 and above appear fixed in the Beta, but they weren’t broken in 2218.

I always heard that “IF it ain’t broke, don’t fix it”, so what’s to gain in going the Beta route? Why not stay with 2218, and wait for a fixed/fully functioning release with new benefits.

Thanks for listening.

The reason it wasn’t broken in 2218, is because XP couldn’t use the newly added scanning of HTTP sites.

So it isn’t a case of if it isn’t broken, the introduction of the new feature in 10.3.2225 that caused some XP systems problems, mainly those with XP SP2. It is that issue which the beta builds are trying to address.

system · 2015-09-07T09:15:09.000Z

Ahhhhh

Thanks. Now I understand.

Hopefully the problems generated in 2223 and up that ALSO affected SP3 like lost r-click on Outlook, etc will be resolved, as well.

I’ll keep “listening”/(hopefully) learning.

Announcements