We’re on Avast 8. We just updated a few machines to Windows 8.1 Pro (through the Store upgrade process) that was released today. However, after the entire process is finished, Avast is gone. It’s completely removed from the system.
Anyone else have this problem? Is Avast 8 not compatible and Windows 8.1 removes it automatically as a precaution?
Even worse - if you have AEA push out Avast 8.0.1490 to a Windows 8.1 machine, it installs but comes up with compatibility errors. The next restart will blue-screen and you can’t be back into Windows.
DO NOT INSTALL 8.0.1490 on Windows 8.1
Thanks for the warning. You’ve saved us some trouble for sure. 
Team avast!: Please comment.
Did you run the actual Win8 or a preview version of 8.1?
If you're upgrading from Windows 8, Windows 8 Pro, Windows RT, Windows 8.1 Preview, Windows 8.1 Pro Preview or Windows RT 8.1 Preview, the process is basically the same: You launch the Upgrade installer from Windows Store, run the installer while the PC or device is offline, reboot a few times, and then emerge with the OS upgraded. Here's a visual guide to this process.Note: The only major difference between these installs, aside from the installer download size, is that those with Windows 8.1 or RT 8.1 Preview will need to reinstall all of their Metro-style apps and desktop applications when the upgrade is complete.
Having uploaded and installed the new version of avast internet security I still have same problem it gives error message, won’t uninstall and next restart locks me out of windows with no keyboard.
I too have completed the online upgrade from 8.0 pro to 8.1 and the avast free antivirus was knocked out having reinstalled the latest version avast free - it all functions ok apart from the browser is reporting that all the avast addon`s are incompatible
Name avast! Online Security
Publisher AVAST Software a.s.
Status Incompatible
Architecture 32-bit
Load time 0.01 s
Navigation time 0.00 s
Name avast! Online Security
Publisher AVAST Software a.s.
Status Incompatible
Architecture 64-bit
Name avast! Online Security
Publisher AVAST Software a.s.
Status Incompatible
Architecture 32-bit
Load time 0.01 s
Navigation time 0.00 s
Name avast! Online Security
Publisher AVAST Software a.s.
Status Incompatible
Architecture 64-bit
Is this avast or IE11 - disappointing
It’s an IE11 issue. I have fully updated Microsoft Office 2013 plugins that are showing incompatibility as well. They must have significantly changed IE’s compatibility requirements.
What’s strange is that I’ve been able to deploy Avast to my 64-bit machines, but my 32-bit clients fail.
Hello
I have version 8.0.1490 Protecrion End Point. After upgrade to Windows 8.1. Avast is uninstalled. I reinstalled Avast but is reported compatibility problem and after restarting Windows must be repair. Can anyone help me?
Hi,
I suggest you to try to install the avast 9.0.2006 (unmanaged)
http://files.avast.com/iavs9x/avast_pro_antivirus_setup.exe (if you haven’t bought the avast FW)
http://files.avast.com/iavs9x/avast_internet_security_setup.exe (if you have bought the avast FW)
Probably, you can insert the license file without problem. (I’ve tryed successfully in past)
until there’s a fix from avast to this.
I tried to install Internet security but I get the message The license for this product is not valid
Of course we can install the unmanaged Avast, or even the new Avast 2014 - but we’re using AEA server and pushing out installs. We need a new AEA console version and client version that works with Windows 8.1
To get browser plugins to work in the new IE11, you have to turn off the Enhanced Protection mode that is now enabled by default.
I tried to install Internet security but I get the message The license for this product is not valid. How do I do now? Besides, we are retailers. I have to find a solution for our customers
What really frustrates me is Awil is silent on this issue. We purchased a business product and our business relies on it and they remain silent. While deploying Windows 8.1 will take time, those of us responsible for determining that time frame are at risk due to incompatible/non functioning anti-virus protection. So the simple question to AWIL is not how do we work around this issue, how are you going to fix it and when? That’s really all I care about.
The problem is NOT avast, but the 8.1 update from Microsoft.
Microsoft is the one who should solve things.
It is not Alwill, but Avast for many years now.
And Avast is not silent about it as you can see in many other threads.
And the 8.1 update is not only messing up avast but also many other softwares.
I even have seen it removing Windows Media Player
The only thing that can be done is using Windows 8 and NOT 8.1 till Microsoft have fixed the bugs in the update.
Examples? I see nothing else in here to support the business customers???
I thought I had missed something as far as Business Support goes, but it appears I am not. I am not buying this product from Microsoft, I am buying it from Awil so I will look to Awil for answers to fix it.
It is easy for you to simply state stay with 8 until Microsoft fixes 8.1, but that is naive at best. Our company has supported Awil from the early Window NT SP3 days, so we are not new to this.
So with that said, is ANYONE at Awil going to address the BUSINESS SUITES incompatibility with Windows 8.1? Yes. no? I do not need an end user telling me it is someone else’s fault, that is worthless to me.
Also I do not care if they changed their business name to Avast – that is not my problem at hand.
Lastly, I was just notified by our AVAST re-seller they are having a hard time getting our license renewal processed as AVAST is in the middle of switching back end systems and cannot handle the request at this time – so it looks like this whole issue is moot as they appear to not be able to support our renewal request anyway. Pity.
As I said it is not a problem with avast but with the 8.1 update Microsoft rolled out.
Microsoft has messed up severely, hence why they removed the update in a real hurry just after 1 day after releasing it.
Avast is not responsible for screw-ups from Microsoft.
You should direct your complains to MS.