Thanks. Everything looks good except with version 11 I have to install additional language (English) again after the update.
I don’t know why language settings (Croatian & English) are not preserved.
Hello,
Are there any reports of this new version causing BSOD on Win7 machines? I installed the update yesterday afternoon (Nov 30) and since then my PC has given me the BSOD three or four times and I’ve noticed Outlook 2013 and Sourceforge’s Go Contact Sync Mod application will hang.
XP Pro SP3 - Removed the last beta 2244, rebooted and installed 2245 install appeared to complete (tray icon was present), but there was no reboot request. I left this for a while and still no reboot request. Checking or rather trying to check Task Manager nothing on the toolbar worked everything appeared to be frozen, no right click functionality or keystroke commands. Even the restart key (soft restart, closes open programs before restart) on the keyboard failed to work.
Hard restart - after reboot system started loading but never got to the avast tray icon being present and the system locked, hard restart again. This happened again after the hard restart. At this point I was considering a boot into safe mode and uninstall, but I gave it one more shot.
It did get further this time but got some desktop hassle no doubt due to the Hard restarts, resolved that and avast was finally up and running.
Tested the Scan for network threats and the previous bug (one device still scanning after success) appears to have been squashed.
Updated ok from within the GUI on 2 machines. On a Toshiba Laptop with Win 10 Home 64 it tried to install Chrome. Easy to opt of. On a Dell 8200 with XP PRO SP3 no Chrome, but background service did not start at first. That happens now and then on an update, but is ok after the second reboot.
Found a bug error in AIS when using SafeZone Browsers and ALL Avast protection shields was automatically turn off when I start using the SafeZone Browers, after I finished using SafeZone Browsers I click on resolved all and all Avast protection shields was automatically turn on.
Please investigate this bug issue before somebody wasn’t fully aware of this issue.