Hi, …
Avast with Windows 8 x64 compatibility, …
Did someone test Avast, with Alpha 3 ?, i will test Avast, with Beta end August 2011 (technet version).
Did it’s legal, to test an “Alpha” version of Windows 8 x64 ?
Don’t you think you’re getting a little bit ahead of yourself?
Why don’t you wait until w8 is actually released?
Then, I would worry about avast & w8…
avast! 7 is being designed for Windows 8
Both should be available for RTW by spring 2012.
The Avast! team has a rapport with MS, some of their guys are occasionally in Redmond. I would imagine they will be ready when it comes.
+1
avast should work on your leaked win8 except Behavior Shield and sandbox component (autosandbox/sandbox/SafeZone), so make sure you install it without these components. Self-protection was fixed in build 1203 to work on win8.
avast is also tested on newer win8 versions (I’m not allowed to say build numbers), but we’ll support only major releases (e.g. all Beta versions, RC/RTM versions) – and maybe only the latest one (if RC is available, we won’t support Beta anymore, etc). Those two components are heavily binded to win kernel components, so it’s quite hard to maintain all available versions.
I was able to install avast internet security 6 from file version
6.0.1000.0, feb. 2011 (sha 0d d6 d6 71 fe 03 64 d4 3b 63 21 31 41 7e 7b 3f) on windows 8
Microsoft Windows [Version 6.2.8102]
but after reboot avast starts with the signature updates + program updates.
The reboot after the following updates leads to a crash and the developer preview of
windows 8 can’t recover.
Is there already an existing version of avast that works with DP 6.2.8102?
I’m willing to test and I have a valid product license.
not yet, because DP 8102 doesn’t allow avast component to load itself - they block us, today I’ll speak with MS devs here at build conference how we can fix it; unfortunately, you will have to wait for the official win8 beta, because they have to remove blocking from their code
Windows 8 Preview Release is now available to download from Microsoft.
See here
let’s say I’m not very amused about the permanent connection of the windows explorer with redmond, no, no, no:
http://img5.imageshack.us/img5/5619/connectionlu.jpg
but as you can see here all protection systems are up:
http://img822.imageshack.us/img822/6800/securityup.jpg
I made only the signature updates - not the program itself - now I’ll risk a reboot and tell you if it worked.
UPDATED: works!! now I’m able to block this SSL connection.
Definition updates should be sufficient for the moment but the MetroUI connections are blocked completely!!