Let me invite you to new Beta challenge. We never did beta testing of the update process before. We encourage you to try the whole upgrade path that almost whole our userbase will have to pass when they want to migrate to the latest greatest avast 2014.
As this path is critical for users, please report any issues (and as I promised there will be some awards for Blocker issues).
Steps of the update process
download and install avast8 R3.1 Beta - this is a copy of the regular a8r3 release but with the ability to update to avast 2014
[list]
[li]please finish the installation correctly E.g. reboot before updating…
[li]there are several ways how to invoke the update process
[list]
[li]click the “Update” button in GUI
click the “toaster” that should appear about available update
insert a license
register program and accept the offer for 30 days Trial of Internet Security
[/li]
[/list]
[/li]
[/list]
The update process should be smooth and easy. You will be updated to the latest 2014 Beta build (current latest “beta” build # 2014.9.0.2003 (aka RC1)). All components from given avast edition should be present in the updated instance of avast. If there is valid license/not expired registration then all services should be running (or not if you turned them off in avast 8). In other words the setting should be preserved after the update.
If you feel that you found any issue please let us know. We will be interested in setup.logs - they are in two locations now 1) new logs - C:\ProgramData\AVAST Software\Persistent Data\Avast\Logs and 2) old logs - c:\ProgramData\AVAST Software\Avast\log\setup.log You can either report them to the feedback.avast.com or directly to my email address hasik (a t) avast (d o t) com. Please report avast edition, update path and your OS in the report too, please.
Known issue:
aswRegSvr.exe reports “Unable To locate Component atl110.dll” after reboot - already FIXED internally - in Beta3+1 - fixed with RC1 release
Tried to download but again blocked downloads (from avast_a8r3IS) for about 1min (holding_1sec) then downloaded but corrupted file (a8r3) screenshot. blocked from windows.
Reported here: https://feedback.avast.com/responses/corrupted-downloads-not-solved-avastis-2014-b3
PS. I go to my other PC to download avast8r3. I hope that after upgrading from a8r3 to a2014 everything will be fine.
Removed previous B3 Premier with uninstall + avastclear and then installed version 8 (free).
Everything went smooth. Just for the sake of testing, I disconnected from the internet in the middle of the update (85MB downloaded, was mostly updating definitions if I got it right). Update obviously failed (Host unreachable). So it asked for restart. Did it, and then ran update again. Worked fine :)!
(I was updating from free to IS trial)
Upgraded from avast!IS_a8r3 from UI. Everything went good but problem with downloads not solved.
I made some screenshots here: https://skydrive.live.com/?cid=61459e31facb0aa8#cid=61459E31FACB0AA8&id=61459E31FACB0AA8!113&v=3
Every screenshot in link above taken through uninstallation of avast!IS 2014_B3 and installation through avast!ISa8r3 UI shows important points.
This screenshot shows that downloading problem persists.
Overal upgrading without problems.
Downloaded Avast free r3beta.1, (removed MSE from Secondary Laptop), installed Avast after that in Admin Account, rebooted after each program update, Successfully upgraded to 9.0.2002 without any issues seen so far on that PC
Windows XP 32bit
Previous Av
Microsoft Security Essentials
Now Running Avast 9.0.2002 beta 3
That doesn’t make much sense. MMX is present on like 90% of CPU’s. I think they started dropping it on latest series of CPU’s in favor of SSE and later instructions…
Current Beta won’t run on CPUs that don’t support SSE2 instruction set (Pentium 3 and Athlon XP generation). For RC, we intend to relax this requirement to just MMX instruction set and that’s virtually everyone (the last CPU not supporting MMX was something like Pentium 200 MHz).
Found a pretty big bug ill be unable to upload logs of any sort untill saturday but on my machine (win 7 64bit sp1) with beta 3 installed windows media player will not start at all and trying to run a media file (mp4 in my case) returns the error “C:\Users\desktop\documents ect. Server execution failed)” adding exclusions for wmp to avast doesnt fix it and neither does reboots or uninstalling beta 3. System restore does fix the issue but upon reinstall of beta 3 the issue is present again.
Here my results from my first try with Beta3 (updated from 1497 to 2002). At first everything went well and it did look OK, but found some problems later on:
System restore didn’t work anymore (Related to the known issue: “Unable To locate Component atl110.dll”)
Windows search didn’t work anymore (No error message.)
Some programs, that are installed since years couldn’t start anymore. (Also related to atl110.dll)
Sorry, no logs, as I did a clean reinstall afterwards, which fixed all issues.
Hi Justin_22 I have the same issues as you with beta 3 and windows media player, I have manged to get mine working again, what I did was completely unistall beta 3 then reinstalled it my windows media player still would not start at all.
Try this http://support.microsoft.com/mats/windows_media_player_diagnostic I followed instructions and my windows media starts and everything works again.
I would recommend intalling beta 3 first, I have the same machine as you:) and then follow the link for windows media player
I hope this helps you:)
happy avast user
I hope avast will look into this issue
We just released RC1 (http://forum.avast.com/index.php?topic=135736.0).
If you’ll try the update from a8r3.1beta now then you should be updated to RC1. The issue “Unable To locate Component atl110.dll” is fixed
I have done a clean install of FREE Avast RC1 and issues I have are as follows:
Avast Boot-Time scan, at the start of boot-time scan this comes up:
Avast Softwere/Avast/resources/resources.pak/resourses.pak Error 42125 (zip archive is corrupted) WHY? I never had any issues with Boot-Time Scan in Avast 8.
I have reported this issue since beta 3 and not resolved as yet.
Hope this issue will be resolved in next release:)
Other issue I have is with the VPS updates all Avast sounds and popups are enabled and update options all boxes have check marks in them.
VPS update is set default (Automatic update) but I don’t get any alert NO sound or popup alert when VPS is updated and I don’t know why.
I do get silent updates, does anyone else have this issue? English language
I hope these small issues will be looked at and resolved before final release