Only IE6 ? no IE8 ? And netframework ?
Edit:
Might that be the pointno doubt
No, IE8 is the latest IE version on XP SP3.
Although IE is used for many things in the OS, windows explorer, etc. I don’t know if the avast UI uses IE or any specific browser interface.
I think that there used to be a C++ requirement some time ago, but again I don’t know if this is still the case.
Hm, interesting. Well, all of my XP machines have IE6 and no .NET framework. And this cannot / should not be changed. The question is, if somebody really knows that these (IE7+ and presence of .NET framework) are mandatory requirements. And C++?
Can anybody state this for sure?
Thanks for involving!
Just to add some more fuel to the fire, IE6 and IE8 aren’t secure and really shouldn’t be used.
@fuel on fire:
We all know that. Please stay on-topic, thank you.
Is there really nobody able to help? I’m so desperate.
I admin a couple of XP SP3 computers, all with IE6 and without .NET framework, some Home and some Pro. I run tons of sensible scientific software on them. I really like avast - but now it’s kicking me out in favor of a new oh-so-fancy design of the main GUI window. That’s it?
I don’t want to say goodbye to avast, but I don’t see another way.
Please, this is my last call for help.
The Avast UI utilizes CEF (Chronium Embedded Framework).
I’m pretty sure C++ is required. IE8 may also be required but I would recommend you to install C++ and then see if that helps.
@Alikhan:
Thanks for posting. I had a look at this and found, that in systemroot\WinSxS there are v11 and v14 of msvcpx.dll. That appears usual to me.
Every new dot rev of Avast seems to have a different GUI. Features are rearranged just to ginger up the user? What other rationale can there be? It’s like Avast enjoys playing games with its users. This has been going on, apparently pointlessly, for years. Changing the GUI doesn’t improve the effectiveness of the product. It just makes it harder for users to make Avast software work for them as they would wish it to every time the GUI wheel is reinvented
Having said all this, Avast Free 17.7.2314 works very well with Windows XP SP3 (fully patched with POSReady updates and running Agnitum Outpost Firewall Pro 9.3, MalwareBytes Anti-Exploit beta and Comodo Memory Firewall).
Two Firewalls ???
Comodo Memory Firewall is actually buffer overflow detection/prevention software for computers which lack hardware DEP support of which my Athlon XP 3000+ processor powered PC is an example.
Thanks. Good to know.
Good to hear it works for you, loungehake.
The magic question is still: Why does it work on some XP Pro SP3, and on some other XP Pro SP3 it doesn’t?
As I already mentioned, besides my XP Pro SP3 machines I have also one (but only one) XP Home SP3 in my small park, that is also kicked by avast GUI. Does anyone have experiences on this?
I don't want to say goodbye to avast, but I don't see another way.Well, keep avast and say goodbye to XP ;D
Yes, if the mountain doesn’t come to the prophet…
If it just would be so easy…
So, a couple of reinstallations later we are not wiser than before.
What we know so far is:
The problem occurs on “relatively native” XP SP3 machines, i. e. equipped with IE6 and without .NET framework (which is due to its version variety and overall bugginess unlikey to be base for a serious antivirus program at all).
The problem occurs both on XP SP3 Pro and Home editions (of the latter one we have just one machine in the park).
Simultaneously other XP users (with at least partially “unnative” systems such as IE8 being present there) stated Avast being working.
The problem occurs with Avast 17.7.
The problem doesn’t occur with Avast 17.5. (and most likely not with 17.6.).
The result of the problem is the inaccessibility of the main GUI window, which results in the inaccessibility of the virus container, manual scans and Avast tools.
The configuration GUI is still fully accessible.
I did as much testing as my boss allowed me. Deadline is end of October - if Avast doesn’t work then again, I’m forced to leave Avast. Which I really would like to avoid, because I like Avast. So please anybody help.
@bob3160:
Nice one. Virus container access. When in panic (panicking, because I’m afraid due to a lack of virus container accessibility I cannot reverse a false alarm resulting in quarantining important files), I get blind. Thanks for this hint.
You’re welcome.
It’s time for a conclusion, to have an easy overview of the bug status.
Bug description:
The main GUI window hangs on the “Status” page. Avast has then to be killed by a task man and manually be restarted.
Bug occurrence:
- The bug occurs with Avast 17.7.
- The bug doesn’t occur with Avast 17.5. (and most likely not with 17.6.).
- Reinstallation and cleaning doesn’t help. It’s a bug in Avast.
- The bug occurs on “relatively native” XP SP3 machines, i. e. equipped with IE6 and without .NET framework (which is due to its version variety and overall bugginess unlikely to be base for a serious antivirus program at all).
- The bug occurs both on XP SP3 Pro and Home editions (of the latter one we have just one machine in the park).
- Simultaneously other XP users (with at least partially “unnative” systems such as IE8 being present there) stated Avast being working.
- After one month already, there is still no official statement from Avast company’s side.
Known workarounds so far:
- Access to the virus container: Use SysTray icon context menu. This brings you to the main GUI window, “Virus Container” page, which works as normal.
- Access to Avast tools: Open “Virus Container” page as described above; from there go to “Tools” page.
- Access to messages: Open “Virus Container” page as described above; from there go to “Messages” page.
- Access to settings: Use SysTray icon context menu. This brings you directly to the settings window, which works as normal.
Still needed workarounds:
- Currently there is no access to the “Manual Scans” page. Therefore, manual scans can’t be started or even configured.
Solutions welcome!