Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: hectic-mmv on December 28, 2017, 11:52:47 AM
-
Update:
29. 12. 2017 12:30 CET fix via uupdate channel has been released.
Fix is applied to all users automatically during 12h, during update process or during fresh installation.
Hello,
we are sorry about hearing of crashing Outlook due to Avast outlook plugin.
This version has been 5 weeks in beta channel for testing and no one from our beta users complained about this problem.
For those having a problem we have a temporary solution now. Proper fix is in development.
As a temporary solution please install older version of our product:
Download links:
- Avast Free http://public.avast.com/~vanek/17.8/avast_free_antivirus_setup_offline.exe
- Avast Pro http://public.avast.com/~vanek/17.8/avast_pro_antivirus_setup_offline.exe
- Avast Internet Security - http://public.avast.com/~vanek/17.8/avast_internet_security_setup_offline.exe
- Avast Premier - http://public.avast.com/~vanek/17.8/avast_premier_antivirus_setup_offline.exe
How to install:
- download Avast version
- uninstall previous version of Avast
- disconnect temporary from network
- start Avast installation and install Avast
- open Avast UI | settings | Update | set Program update to option - Ask when update available
- connect to network again
We are sorry about troubles again. Proper fix will be out soon. We will inform you here.
thank you,
-
The link for Avast Pro Antivirus?
-
The link for Avast Pro Antivirus?
added
-
What a waste of time to have to go through forums to get some answer to a question asked days ago to support without the slightest answer, not even a confirmation of reception >:(
That's what I call no support.
I have one year left of licence and will probably upgrade my avg tuneup to full security including what avast does less and less efficiently
-
I have one year left of licence and will probably upgrade my avg tuneup to full security including what avast does less and less efficiently
OK ;) https://blog.avast.com/avast-and-avg-become-one
-
Thanks
That explain a lot. In that kind of deal generally a product is gradually replaced by the other.
And some signs, when you have both can give you a hint. Avg has a support which answers and react so....
-
I too have issue with this "temporary fix". I would like to know HOW LONG it will take to get this bug ironed out. I too made both a telephone call complaint and a complaint through the avast UI issue link, and nothing. No reply, nothing. When I called in, i got some guy that treated me like I was an idiot and know nothing about computers or software telling me they knew of no issue (and this was a couple days after my initial complaints and online forums were filling daily with complaints about the issue).
better service would be appreciated regarding the fact your customers are being treated like mushrooms (kept in the dark and being fed poo poo).
-
This version has been 5 weeks in beta channel for testing and no one from our beta users complained about this problem.
You need more and/or more diverse beta users.
-
This version has been 5 weeks in beta channel for testing and no one from our beta users complained about this problem.
You need more and/or more diverse beta users.
Doesn't Avast also test on several different types of software installed systems ???
-
Outlook 2016 crashes on my Win 10 machine and disables the add in.
On my Win 7 - Outlook 2010 It disabled and took the icons off the toolbar.
This is not good at all.
-
Hi guys,
we have troubles with releasing the fix, we will deliver it asap next week.
-
Started to use the work around, but keep getting b86362a5.exe has encountered a problem and needs to close, so can't seem to re-install a pre problem version!
-
Guys,
we have listened your feedback. Fix is already released. To apply it just reinstall Avast and reboot or fix is automatically applied in approx 12h.
We're sorry for your troubles.
-
Hello,
thank you for fix, although for me nothing changed yet. I have program update set to manual so it need program update to fix this problem or it will be fixed by VPS/Emergency updater automaticaly? Change this fix version number? Thank you.
-
where is this fix?? I am so disgusted I am looking for another antivirus at this point - every program update screws up my outlook 2010- this time so bad it is barely functioning and i have spent hours applying other fixes, re-installs ETC
TERRIBLE SUPPORT as well.
-
where is this fix?? I am so disgusted I am looking for another antivirus at this point - every program update screws up my outlook 2010- this time so bad it is barely functioning and i have spent hours applying other fixes, re-installs ETC
TERRIBLE SUPPORT as well.
Did you read the reply ???
https://forum.avast.com/index.php?topic=212301.msg1437964#msg1437964
Do a manual update and reboot.
-
I only noticed new AsOutExt.dll, so this is that fix? Avast still not scan attached files in Outlook 2010. "Scan attachment when attaching" enabled.
-
I only noticed new AsOutExt.dll, so this is that fix? Avast still not scan attached files in Outlook 2010. "Scan attachment when attaching" enabled.
I suggest you start your own topic since that's not related to the problem addressed in this thread.
-
yes i did - made no difference - avast is causing explorer.exe and outlook 2010 issues as well as preventing/dramatically slowing shutdowns and restarts
when i uninstall avast the computer is back to brand new - install avast and it is a boat anchor at this point
where is this fix?? I am so disgusted I am looking for another antivirus at this point - every program update screws up my outlook 2010- this time so bad it is barely functioning and i have spent hours applying other fixes, re-installs ETC
TERRIBLE SUPPORT as well.
Did you read the reply ???
https://forum.avast.com/index.php?topic=212301.msg1437964#msg1437964
Do a manual update and reboot.
-
Update:
29. 12. 2017 12:30 CET fix via uupdate channel has been released.
Fix is applied to all users automatically during 12h, during update process or during fresh installation.
I am a bit confused by hectic's words as he says fix has been released that can be implemented via update or fresh install, then offers previous version as temprary fix. Does that mean if update fix doesn't work, then the ultimate backup is to remove and install 17.8?
My experience of 17.9.2322 with Outlook 2010 has been strangely mixed. On my Win10 1709 machine the Avast Add-On did not cause Outlook to disable it. However, on my WINXP SP3 Outlook 2010 combo, Outlook failed to start unless Avast Add-on was agreed to be disabled.
Today, on reading this post, I tried Update Avast on my XP machine. Nothing appeared to update. Anyhow, I then did Repair of Avast and reboot. After that Outlook 2010 started with the Avast Add-on enabled.
I dont know if that is just a fluke or whether something has been updated. I cant tell, as Version of Avast reported on both my Win10 and XP machines is exactly the same. 17.9.2322 (17.9.3761.0).
Have avast kept the same version number although the Avast add-on has been altered? If true, then Avast's attitude to software versions control is poor. I for one would get shot by the quality department if I did that sort of thing.
If someone can somehow explian my observations, then maybe others can benefit.
Happy New Year
Ed
-
Update:
29. 12. 2017 12:30 CET fix via uupdate channel has been released.
Fix is applied to all users automatically during 12h, during update process or during fresh installation.
I am a bit confused by hectic's words as he says fix has been released that can be implemented via update or fresh install, then offers previous version as temprary fix. Does that mean if update fix doesn't work, then the ultimate backup is to remove and install 17.8?
<snip>
There is nothing I can see in what you have quoted that suggests offering a previous version.
He has given a Date Time Group of the release to the update channel. The fix being released within the regular 12 hour program update check.
At least that is my understanding of what you quoted. Whilst something would appear to be confused by the transcription into English.
EDIT: Fixed incorrect formatting of quoted text.
-
I only noticed new AsOutExt.dll, so this is that fix? Avast still not scan attached files in Outlook 2010. "Scan attachment when attaching" enabled.
I suggest you start your own topic since that's not related to the problem addressed in this thread.
Hi Bob,
I believe AsOutExt.dll is relevant to this thread. It appears listed as Avast Add-On when Outlook starts up and also shows in list of Outlook Add-on's, whether or not it is enabled or disabled.
I have looked at Avast files on both my machines. It appears that AsOutExt.dll is more recent date (29/12/17) than other files from 17.9 update. So somehow that has been applied somehow on both my machines, although I have not done a program update on my Win10 machine only on my XP machine. Neither are set to automatically update. The version of Avast that I now have is same as mentioned in my earlier post today.
Anyhow, net result is Outlook runs with Avast Add-On listed as enabled on both machines. So I'm am happy about that. But less happy about seemingly no change to Avast version or build numbers.
Also bit unclear if this is the real fix or just a temporary fix. Are we still expecting another update for this next week regardless?
Ed
-
Only Avast can answer those questions. I'm a product user just like you. :)
I don't even use Outlook. :) Perfectly happy with Gmail. :)
-
I too have this Outlook crash problem. I find it very problematic that after requesting support on 3 occasions that i have had confirmation that my request has left me but then complete silence from Avast! And then i read answers on this blog that say no-one has reported a problem - read your mail!!!!
When can i get my outlook working properly again please?
-
I too have this Outlook crash problem. I find it very problematic that after requesting support on 3 occasions that i have had confirmation that my request has left me but then complete silence from Avast! And then i read answers on this blog that say no-one has reported a problem - read your mail!!!!
When can i get my outlook working properly again please?
Please restart yuur PC, the fix will be applied.
-
I only noticed new AsOutExt.dll, so this is that fix? Avast still not scan attached files in Outlook 2010. "Scan attachment when attaching" enabled.
I suggest you start your own topic since that's not related to the problem addressed in this thread.
Hi Bob,
I believe AsOutExt.dll is relevant to this thread. It appears listed as Avast Add-On when Outlook starts up and also shows in list of Outlook Add-on's, whether or not it is enabled or disabled.
I have looked at Avast files on both my machines. It appears that AsOutExt.dll is more recent date (29/12/17) than other files from 17.9 update. So somehow that has been applied somehow on both my machines, although I have not done a program update on my Win10 machine only on my XP machine. Neither are set to automatically update. The version of Avast that I now have is same as mentioned in my earlier post today.
Anyhow, net result is Outlook runs with Avast Add-On listed as enabled on both machines. So I'm am happy about that. But less happy about seemingly no change to Avast version or build numbers.
Also bit unclear if this is the real fix or just a temporary fix. Are we still expecting another update for this next week regardless?
Ed
Hi Ed,
yes, the change was in file - AsOutExt.dll. Because it was very small isolated change we updated this via micro update channel without major version change.
This is a real fix. It is already merged into next major update version.
-
17.9.2322 is still not working with my version of Outlook 2016. I have to disable shields to send / receive emails.
-
Have you tried rebooting???
-
Many Times...
-
I only noticed new AsOutExt.dll, so this is that fix? Avast still not scan attached files in Outlook 2010. "Scan attachment when attaching" enabled.
I suggest you start your own topic since that's not related to the problem addressed in this thread.
Hi Bob,
I believe AsOutExt.dll is relevant to this thread. It appears listed as Avast Add-On when Outlook starts up and also shows in list of Outlook Add-on's, whether or not it is enabled or disabled.
I have looked at Avast files on both my machines. It appears that AsOutExt.dll is more recent date (29/12/17) than other files from 17.9 update. So somehow that has been applied somehow on both my machines, although I have not done a program update on my Win10 machine only on my XP machine. Neither are set to automatically update. The version of Avast that I now have is same as mentioned in my earlier post today.
Anyhow, net result is Outlook runs with Avast Add-On listed as enabled on both machines. So I'm am happy about that. But less happy about seemingly no change to Avast version or build numbers.
Also bit unclear if this is the real fix or just a temporary fix. Are we still expecting another update for this next week regardless?
Ed
Hi Ed,
yes, the change was in file - AsOutExt.dll. Because it was very small isolated change we updated this via micro update channel without major version change.
This is a real fix. It is already merged into next major update version.
Still not working for me. When i go into Avast settings the Program version shows as 17.9.2322 build 17.9.3671.0 dated 21/12/17. If i try to update manually, it reports back that I have the latest version installed. I have tried re-booting several times and no change. My version of AsOutExt.dll is dated 22/12/17.
Still causing Outlook to crash.... Any ideas please
-
@hectic. Thanks for explaining how you achieved the sneaky update and that it is a "real fix".
@Mickskull. I don't know which Windows version you are running. Have you tried doing Repair of Avast or failing that a reinstall of Avast. Repair of Avast worked for me on one of my machines.
If all else fails see links to previous 17.8 offline version that were posted by hectic at the top of this thread.
Ed
-
@hectic. Thanks for explaining how you achieved the sneaky update and that it is a "real fix".
@Mickskull. I don't know which Windows version you are running. Have you tried doing Repair of Avast or failing that a reinstall of Avast. Repair of Avast worked for me on one of my machines.
If all else fails see links to previous 17.8 offline version that were posted by hectic at the top of this thread.
Ed
Thanks rocksteady, the repair option worked for me. The Program and Build No's remain the same, but the AsOutExt.dll file now has a date of 02/01/18. Outlook now works as it should with no crashes. PS, Windows 10 pro 64 bit for reference with Outlook 2016.
-
Where is the repair option?
-
Where is the repair option?
Control Panel > Programs & Features > Avast Antivirus > Change > Repair.
-
@DavidR. Thanks for the suggestion but it didn't work for me. I guess I'll have to keep disabling shields whilst I check my email... :(
-
@DavidR. Thanks for the suggestion but it didn't work for me. I guess I'll have to keep disabling shields whilst I check my email... :(
If Repair doesn't fix the problem, try the following:
Clean Install of Avast:
https://goo.gl/4Ptzkf
-
@DavidR. Thanks for the suggestion but it didn't work for me. I guess I'll have to keep disabling shields whilst I check my email... :(
For me, exactly the same(W10 Outlook 2016)
-
@DavidR. Thanks for the suggestion but it didn't work for me. I guess I'll have to keep disabling shields whilst I check my email... :(
You're welcome - if after trying the clean reinstall the issue is still there - are you actually getting any errors displayed to the screen ?
If so please post a screenshot of the error window.
-
@DavidR. Thanks for the suggestion but it didn't work for me. I guess I'll have to keep disabling shields whilst I check my email... :(
For me, exactly the same(W10 Outlook 2016)
Have you followed the posts from MartinZ and hectic-mmv (avast team members) above as a fix has been released for this. You may need to try the clean reinstall suggested by bob3160
Unfortunately not something I can check as I don't use MS Outlook.
-
I've decided to wait for the official fix as I can easily disable the shields for a minute whilst I collect my emails. I've attached the error messages for btconnect.com and Gmail.com. My internet emails (I.e. from website contact pages), are still coming through. Very strange.
-
I've decided to wait for the official fix as I can easily disable the shields for a minute whilst I collect my emails. I've attached the error messages for btconnect.com and Gmail.com. My internet emails (I.e. from website contact pages), are still coming through. Very strange.
So you would rather expose your system to a possible infection thanuse the fix that's available by turning off your protection ??? Your computer.
-
agreed still not working - causing all kinds of issues with Outlook even with that shield customized or disabled, also shutdowns and rebooting - hard shutdowns are the new "norm" - drastic overall computer performance improvements when avast is uninstalled I for one have gone with another antivirus - this is just too much and don't have time for the nonsense and time involved
-
@Bob3160 Give over. I switch the shields off for less than 1 minute. How do I know it's a fix? I tried the repair and that didn't work. I have to uninstall Avast to apply the "fix" thereby exposing my my system to a possible infection for longer than the time it takes to receive my emails. It's probably less than a minute in reality.
-
@Bob3160 Give over. I switch the shields off for less than 1 minute. How do I know it's a fix? I tried the repair and that didn't work. I have to uninstall Avast to apply the "fix" thereby exposing my my system to a possible infection for longer than the time it takes to receive my emails. It's probably less than a minute in reality.
You don't need to be online to remove Avast. :) Again, your computer. :)
-
I had some issues with the Fix - not complaining, but rather documenting to maybe help other folks and developers at AVAST:
1) the automatic update of the plugin (AsOutExt.dll) will not apply until the system is rebooted.
Not a big issue, but it would be helpful if Avast would prompt for a reboot.
2) My Outlook had automatically disabled the plugin and I had to manually load the (fixed) plugin in Outlook.
The solution to this is to regedit
HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\Avast.AsOutExt\LoadBehavior
and set the value to 3
3) While searching for solution for 2) I uninstalled Mail Shield component and re-installed again including reboot after.
After this Outlook plugin crashed again and it appeared that the AsOutExt.dll file size had changed to a different value
from the fixed version.
Is it possible that install Mail shield component pulls the original broken AsOutExt.dll ?
I was able to fix this with a repair from Control Panel\Programs and Features.
Anyway after a few hick-ups it's working for me now...
-
We the customers should not have to do this. Why can't Avast (Large Company) update us with the fix? How many Avast customers in the world are having problems because they chose to use another large company's (Microsoft) email client? By the way, as a matter of interest. Avast Business AV is not causing this problem. Maybe they should look to that version for an answer... :)
-
Avast has issued a fix (patch) which will wind up as part of the regular install with the next update of the program.
Until the next update, you can either install the fix that was released or wait till the next program update.
It's like installing a patch from Microsoft to fix a problem or, waiting till the next Version release to receive the fix.
Your choice.
-
Have we been advised when the next program update will be?
-
Have we been advised when the next program update will be?
No. When it's ready and only Avast can answer that.
-
The official update with fix should be released immediately! Now (after 2 weeks), Avast still do nothing with this bug and nobody kwnow when somebody fix this shit. It's very sad... choose paid Avast and waste your money! Over 400 million users and what developers do? Nothing!!! Shame on you, Avast! SHAME :-(
-
Agreed. I posted a temporary fix 2 weeks ago and it's still working and yet, Avast has not issued an update for this huge problem. I just keep wondering to my self why there are not pre-release "beta tester" offers to check things out BEFORE they release an update to warn of these kinds of issues. I'm a member of the "Windows Insider Program" that let's me test new updates and upgrades to Window releases.
I have never been asked by AVAST to check out a new update release. Ever! Very bad change control protocols to make sure their updates work with all systems.
The developers ARE completely asleep on and uncommunicative on this issue.
-
Avast has issued a fix (patch) which will wind up as part of the regular install with the next update of the program.
Until the next update, you can either install the fix that was released or wait till the next program update.
It's like installing a patch from Microsoft to fix a problem or, waiting till the next Version release to receive the fix.
Your choice.
The fix work's fine for me (W10+Outlook 2016), after : 1/repair Avast (by Control Panel), 2/reboot et 3/reactivation of the add'in
-
The hotfix has been released less than 24 hours after the wrong update.
-
Why is it necessary to Uninstall Avast via control panel and then Run the Uninstall Utility?
Disconnect from the internet
Uninstall Avast via control panel and follow the directions.
Run the Uninstall Utility and accept the reboot to safe mode
Once complete reboot your system
Go back on-line
Reinstall Avast
-
@bob3160 I've done exactly as instructed and it STILL DOES NOT WORK! See attachment... I've wasted hours on this to no avail!!!
Avast Premier
(https://www.avast.com/download-thank-you.php?product=PRE&locale=en-ww)
Disconnect from the internet
Uninstall Avast via control panel and follow the directions.
Run the Uninstall Utility and accept the reboot to safe mode
Once complete reboot your system
Go back on-line
Reinstall Avast
Upon completion, please reboot your system to make sure all changes have been completed.
-
With shields disabled...
-
The hotfix has been released less than 24 hours after the wrong update.
What hotfix? Its's a joke?! Go to settings -> Updates -> and the last version is 17.9.2322
There is no official patch for this!!!
When this lazy Avast depelopers realse fu****g fix for this mistake?
-
The hotfix has been released less than 24 hours after the wrong update.
What hotfix? Its's a joke?! Go to settings -> Updates -> and the last version is 17.9.2322
There is no official patch for this!!!
<snip>
It is unlikely the actual program version would change, more likely would be a different build number.
Since I don't have MS Outlook, it would be unlikely I would get this micro fix, so I should have the current version and build number - 17.9.2322 (build 17.9.3761.0) - is your build number the same ?
-
It is unlikely the actual program version would change, more likely would be a different build number.
Since I don't have MS Outlook, it would be unlikely I would get this micro fix, so I should have the current version and build number - 17.9.2322 (build 17.9.3761.0) - is your build number the same ?
Yet i have the same bulid version. Date of publication: 21.12.2017 09:18:14 and this is a version with a bug! Since that time, there were no more updates ;-( How long do we have to wait for help from Avast lazy support? Is there anybody who cares?
-
As an avast user like yourself I can't speak for Avast and don't have any more information than what I have gathered in the forums.
Have you tried manually running the AvEmUpdate.exe (this file also gets used during program updates to see if there is anything outside of a program update) file under Administrator privileges.
I ran this on this win10 system that was on 17.8.2318 and I followed that up with a program update and a reboot.
Checking the asOutExt.dll, which I believe is the Outlook email extension and that file appears to have a different build number/file version 17.9.2322.3761.270.
-
It is unlikely the actual program version would change, more likely would be a different build number.
Since I don't have MS Outlook, it would be unlikely I would get this micro fix, so I should have the current version and build number - 17.9.2322 (build 17.9.3761.0) - is your build number the same ?
Yet i have the same bulid version. Date of publication: 21.12.2017 09:18:14 and this is a version with a bug! Since that time, there were no more updates ;-( How long do we have to wait for help from Avast lazy support? Is there anybody who cares?
As far as I am aware..when a microupdate is released, the program version/build number does not change. Only the file(s) which have been updated will have a different build/version.
-
<snip quotes>
When a microupdate is released, the program version/build number does not change. Only the file(s) which have been updated will have a different build/version.
Which is why I went through the processes and attached the file properties screenshot.
-
We already know since yesterday (https://forum.avast.com/index.php?topic=212301.msg1438939#msg1438939) on this subject that neither the version number nor the built-in has changed for this fix ... only asOutExt.dll has been updated.
If "avast_User_461" had read, he would not have asked the question. :)
-
I have this and it Outlook still cannot send or receive some emails unless I drop the shields... >:( >:( >:(
-
Hello
Update:
How to install:
- download Avast version
- uninstall previous version of Avast
- disconnect temporary from network
- start Avast installation and install Avast
- open Avast UI | settings | Update | set Program update to option - Ask when update available
- connect to network again
just a question that is not related to the subject , sorry.
How to install avast when you get an error message that says you have to be connected to the net for the installation to be done ?
Edit:maybe by "Offline" version rather than "Online" ?
-
You can try this, but it didn't work for me...
Avast Premier
(https://www.avast.com/download-thank-you.php?product=PRE&locale=en-ww)
Disconnect from the internet
Uninstall Avast via control panel and follow the directions.
Run the Uninstall Utility and accept the reboot to safe mode
Once complete reboot your system
Go back on-line
Reinstall Avast
Upon completion, please reboot your system to make sure all changes have been completed.
-
It's working...
-
Having been a professional software developer, I have a few thoughts on this MS Outlook crash issue subject:
1) Often the company behind the developer does not want to invest time, equipment, or manpower into adequate testing. Shame on such companies! I do not know for certain if this applies to Avast.
2) Beta testing should not be expected to replace #1 above, EVER! If a company or developer starts blaming release errors on beta testing, then their whole testing and release process is a scam, and is out of control. The products of such companies should be avoided like the disease that they are. Neither a person nor a business can afford the time, cost, and frustration of companies that rely on such business practices. I do not know for certain if this applies to Avast.
3) When any software item is revised in any way and released for testing or production, it gets a new version number, and the package(s) which contain it get new revision numbers. Period. Period. Period. Any company that does not follow this model is prone to stupid, foolish, and accidental internal errors, will breed internal confusion, and the company is certain to confuse customers trying to maintain solid systems. I do not know for certain if this applies to Avast.
4) A company should have developers that deal with development planning, problems and issues. Sometimes issues that developers are confronted with are difficult to estimate a time of resolution, especially if resources are limited (see #1 above) and change control and documentation (see #3 above) are not well managed. Doing problem identification, development of a solution, completion of the development, and complete testing requires time, effort, and well planned behavior. Likely one or more of these things were missing to have allowed the problem to exist in the first place.
5) It is the company's management, sales and communication staff (THE customer support team) that should respond to customers about issues in the field, not the developers. If the company doesn't have a properly trained and functional customer support team, then customers are left in the dark when problems arise. In some cases, a company's customer support team will lie to customers about problems and estimated fix times. The customer should be given clear and truthful answers about problems that exist, and be advised about estimated problem resolution dates. If a release date is flat out unknown, then say so, and give a reasonable guess of range. This can help the customer make decisions to minimize down time. A customer wants to know quickly to install an older version if that will reduce their down time. Getting no feedback from company about a known problem that causes customer down time shows total lack of respect for the customer.
MY EXPERIENCE included a long (too long) silence, followed by an heart felt apology, with unclear (to me) instructions on how to implement the resolution.
It is my hope that Avast will learn from this failed occurrence and quickly implement the needed corporate changes. I hope that the changes needed are minor, as otherwise I think that a re-occurrence will contribute to a major thinning of their customer base and provide an opportunity for some other company.
-
@ferush Very well said. I couldn't have put it better myself.
-
i am currently in the position of having performed a "clean" Install. the anti-spam option is RED in the components section and will not change! what alternative solutions to this problem do you have?
this is a problem that i have encountered many times since taking out a subscription for your product. i find this very annoying and a poor level of service from your company.
-
My Outlook 2016 still crashing...
How log we have to wait to official update? Months, years?
This is pathetic! Avast has worst support ever :(
Now, i really regret that I bought this corrupt product.
Who will give me money back?! :-\
-
My Outlook 2016 still crashing...
How log we have to wait to official update? Months, years?
This is pathetic! Avast has worst support ever :(
Now, i really regret that I bought this corrupt product.
Who will give me money back?! :-\
Refund request: https://support.avast.com/support/tickets/new?form=2
-
It is now February and still no update.
What is happening ??????????
-
It is now February and still no update.
What is happening ??????????
Try this beta!.https://forum.avast.com/index.php?topic=214411.0 (https://forum.avast.com/index.php?topic=214411.0)
Here is the list of bugs fixed:
Bug fixes
Fixed bug when games were minimizing themselves every 30 minutes
Fixed problems with Outlook plugin
Fixed name of Avast window in task bar
Fixed Help screen (help was not displaying proper page on some places in UI - typically in settings)
Fixed Boot Time Scan
Fixed bug which caused that Last computer scan time was not displayed correctly
-
I have Outlook 2010 on Windows 10 64bit and Avast Pro Antivirus. Since 3-4 months it keeps crashing when I start Outlook 2010 due to Avast Outlook plugin. When I disable the plugin Outlook mail client starts correctly, but then I'm not protected against viruses thru e-mails!!
I use Avast Pro Antivirus since many years without any problems until this issue. And I think there is still no fix even when the Avast engine is updated on my computer: 18.2.2328 build 18.2.2327.307 released on March 1st 2018.
What a terrible software yours transformed into!