Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Fernando 1 on August 25, 2006, 05:59:45 PM
-
I had no problem to install and run Avast! Home v. 4.7.871 on earlier Vista versions, but it doesn't work with the new Build 5536.
Any idea?
-
Which is the error message?
Anything into Windows Events and/or avast logs that allow to debug this?
Any firewall installed?
-
Which is the error message?
Anything into Windows Events and/or avast logs that allow to debug this?
Any firewall installed?
It just doesn't work (without any message).
When I try to update manually, I get the message, that this Vista Beta version is not supported by Avast.
No, I have no firewall installed.
-
When I try to update manually, I get the message, that this Vista Beta version is not supported by Avast.
By the icon?
It's known that the icon does not have enough rights to update in Vista.
You need to open the antivirus (right click the 'a' blue icon, start avast antivirus) and update.
You can set - it works ok - the automatic update for both program and antivirus ;)
-
It's known that the icon does not have enough rights to update in Vista.
You need to open the antivirus (right click the 'a' blue icon, start avast antivirus) and update.
You can set - it works ok - the automatic update for both program and antivirus ;)
Vista does not work with my system.
When I try to update the way you proposed, I get a message, that Avast has a known compatibilty issue with this Windows version.
The problem could not be resolved.
Edit:
When I start Avast I get the message:
Avast!: The AAVM sub system has detected an PRC error.
The operation could not be finished.
-
When I start Avast I get the message:
Avast!: The AAVM sub system has detected an PRC error.
The operation could not be finished.
It's an RPC error (Remote Procedure Call, a windows necessary service...).
Are you running any other antivirus in this Vista installation?
Did you try to 'repair' avast installation through Control Panel?
-
getting similar errors, even after trying a repair and rebooting
-
Are you running any other antivirus in this Vista installation?
No, I always use only Avast!
Did you try to 'repair' avast installation through Control Panel?
Yes, but this didn't help.
-
Can you please post the files <avast>\data\log\error.log and warning.log (if they exist on your system)?
And, do I understand it correctly that when you boot, the avast tray icon has the red mark on it, and when you click it, you get the RPC related error?
If so, can you please check if the "avast! Antivirus" service is running (Control Panel -> Administrative Tools -> Services), and if not, if it can be started?
Thanks
Vlk
-
Can you please post the files <avast>\data\log\error.log and warning.log (if they exist on your system)?
And, do I understand it correctly that when you boot, the avast tray icon has the red mark on it, and when you click it, you get the RPC related error?
If so, can you please check if the "avast! Antivirus" service is running (Control Panel -> Administrative Tools -> Services), and if not, if it can be started?
1. There is only a SETUP.LOG file, nothing else.
2. The avast tray icon has a red mark. When I click it, I get the RPC related error.
3. The Avast Antivirus Service cannot be started (Error 1068).
By the way: I heard from a lot of Betatesters, that Avast! does not work with Vista 5536. So you can really believe me.
-
1. There is only a SETUP.LOG file, nothing else.
Can you post its contents?
At least, the last lines of it?
Thanks.
-
1. There is only a SETUP.LOG file, nothing else.
Can you post its contents?
At least, the last lines of it?
Thanks.
Sorry, I just have deinstalled Avast, because I could not use it and I need a working Antivirus programme.
If it's really important for you, I will reinstall it.
-
If it's really important for you, I will reinstall it.
In fact, it could be important to Alwil to debug the problem...
I can't help further as I'm not using this particular build of Vista.
-
If it's really important for you, I will reinstall it.
In fact, it could be important to Alwil to debug the problem...
I can't help further as I'm not using this particular build of Vista.
So I deinstalled the other Antivirus programme and reinstalled Avast.
It still doesn't work at all. Within the LOG folder there is neither an error.log nor a warning.log file.
Here are the last lines of the setup.log file:
26.08.2006 20:04:53.000 1156615493 package Transferred files: 10
26.08.2006 20:04:53.000 1156615493 package Transferred bytes: 11132333
26.08.2006 20:04:53.000 1156615493 package Transfer time: 592 ms
26.08.2006 20:04:53.000 1156615493 file NeedReboot=true
26.08.2006 20:04:53.000 1156615493 system Reboot set by filRenameOnReboot(J:\Program Files\Alwil Software\Avast4\Setup\reboot.txt,)
26.08.2006 20:04:53.000 1156615493 file MoveFileEx(J:\PROGRA~1\ALWILS~1\Avast4\Setup\reboot.txt, NULL)
26.08.2006 20:04:53.000 1156615493 general Return code: 0x20000000 [Something done]
26.08.2006 20:04:53.000 1156615493 general Stopped: 26.08.2006, 20:04:53
I doubt, that this really will help you.
I resume: The installation was fine, but after the reboot Avast did not begin its work at all. Hitting on the redly signed Avast tray button produced the RPC error message - that's all I can report.
-
Error 1068 means "The dependency service or group failed to start.". Can you please open the Windows Event Viewer, and look up the respective entry describing which dependency service failed to start?
BTW We will install Vista 5536 on Monday and test it in-house, too...
Thanks
Vlk
-
Error 1068 means "The dependency service or group failed to start.". Can you please open the Windows Event Viewer, and look up the respective entry describing which dependency service failed to start?
The Windows Event Viewer is full of entries.
Do you know how I can find these special event details? Which kind of event is it?
-
5536 comes up with a compatability error for Avast when I boot up stopping it loading a driver.
Looking at the Event log the following driver is being blocked by the OS:
Driver aswMon2.SYS has been blocked from loading.
-
5536 comes up with a compatability error for Avast when I boot up stopping it loading a driver.
Looking at the Event log the following driver is being blocked by the OS:
Driver aswMon2.SYS has been blocked from loading.
Thank you for transmitting these details. It enhances the chance to get a modified Avast version which is working with the upcoming and public Vista RC1.
-
This is ridiculous, why the hell are they blocking it? Let me get in touch with our contacts in Microsoft, hopefully I'll be able to find out more about this asap.
-
HI,
I have the same Vista blocking problem...just moved to Vista 5536. Avast 4.7.81 was working fine on previous Vista builds.
The avast! Standard Shield Support service failed to start due to the following error:
This driver has been blocked from loading
The avast! Antivirus service depends on the avast! Standard Shield Support service which failed to start because of the following error:
This driver has been blocked from loading
Any fix yet?
Thanks in advance,
Dwight
-
Same thing happens to me too.
In fact the latest Vista build seems to be causing alot more problems for me than fixing them. My 2Wire H1800 USB modem used to work fine in the previous 5472 build but now it works on and off and I get the Code 10 error
-
I'm downloading 5536 now...
But for what I can see, I won't delete the old build I have :'( ::)
-
I'm having the same error.
Windows is blocking Avast from starting the service. If I try to start the service I get Driver is blocked due to compatibility issues.
Please advise when you have a work around or an update.
Thanks
-
Maybe Microsoft have dicided that antivrus software is no longer necessary in Vista ;)
http://news.bbc.co.uk/1/hi/technology/5271386.stm
-
sorry no speak english
idem proble for same user
on vista 5536 avast not run driver .... AAVM detect RPC error....
from previous build vista avast work fine
AVAST RULEZZZZZ
"nod32 trial for the moment bug avast LOL"
-
OK folks, I just got some feedback from MS, it seems that the avast driver was "hard blocked" BY MISTAKE, hopefully, the issue will be remedied in the next Vista build. ;)
Thanks
Vlk
-
OK folks, I just got some feedback from MS, it seems that the avast driver was "hard blocked" BY MISTAKE, hopefully, the issue will be remedied in the next Vista build. ;)
Are you saying that is useless to try to use Vista 5536?
I think I've downloaded it without any other reason than test it... and, of course, I want avast with it...
Should we wait for the next version? Is it the only solution?
-
Well, it's not useless, but avast won't run on it. Its driver is simply blocked from loading (and I don't mean to find out how to hack this stuff as the blocking is not intentional)
-
Well, it's not useless, but avast won't run on it.
I can't use avast, so, for me, as you know, it's useless... :'(
What can I do without avast? ;)
Its driver is simply blocked from loading (and I don't mean to find out how to hack this stuff as the blocking is not intentional)
Well, hope this blocking theach you how to 'prevent' this kind of block by a malware or other anti-antivirus piece of software...
-
it seems that the avast driver was "hard blocked" BY MISTAKE
This is a very stupid MISTAKE by MS.
-
Anyway, there is not a possibility to new beta testers... :-\
-
I like totally have the same problem too. =(
-
so there is NO way we can fix this problem so that we can do system test?
will it be fixed for the actual RC1 coming up... or is that code already frozen?
-
so there is NO way we can fix this problem so that we can do system test?
No... :'( :'(
will it be fixed for the actual RC1 coming up... or is that code already frozen?
I'm not sure... I hope RC1 won't have this stupid error :(
-
I've got a message that avast! is not compatible with this Vista RC1. Same thing when I tried to install NOD32. It won't even install.
Different story with AVG though... installation went perfect and AVG works flawlessly on new Vista build.
Compatibility report regarding avast! :
(http://img219.imageshack.us/img219/2357/untitled2bn4.jpg)
AVG installed and working (click on thumbnail for full size image):
(http://img216.imageshack.us/img216/87/untitleddy1.th.jpg) (http://img216.imageshack.us/my.php?image=untitleddy1.jpg)
-
I see AVG still has that ugly GUI ...
-
Yes, 1970s-cartoon-style ;D ;D ;D However, it works with new Vista build, and we still need something to protect our PCs... it's free and it's working... what can I ask more ? ;D
-
I've got a message that avast! is not compatible with this Vista RC1.
Sasha, is this Vista 5552 version?
-
No that's 5536 RC1... as far as I know, the latest one. I just downloaded it directly from Microsoft server yesterday. I don't think they would put some old version. Bob posted a link somewhere in this forum. I was Beta tester, so I used my old registration number as suggested by Microsoft.
It's from here:
http://download.windowsvista.com/preview/prerc1/en/download.html
EDIT: You can see Vista's build number on my second screenshot I posted up there...
-
No that's 5536 RC1... as far as I know, the latest one. I just downloaded it directly from Microsoft server yesterday. I don't think they would put some old version. Bob posted a link somewhere in this forum. I was Beta tester, so I used my old registration number as suggested by Microsoft.
Thanks Sasha... some users in other forums posted 5552... it could be a typo...
You can see Vista's build number on my second screenshot I posted up there...
No I can't... It was into shadows...
-
So must we conclude that there is NO way to make avast! work in Build 5526 of Vista? Is there anything we can do with Application Compatibility or anything like that?
Rgds,
Edmund
-
So must we conclude that there is NO way to make avast! work in Build 5526 of Vista?
No way... Vista blocked the driver, whitout it, no avast :'( :'(
-
...
...
No I can't... It was into shadows...
Strange... even covered with that light shadow, I am still able to see those numbers. See here:
(http://img65.imageshack.us/img65/2558/untitled1jl1.jpg)
Maybe your monitor contrast/brightness is not properly set. In that case you need to calibrate your monitor ( http://www.easyrgb.com/calibrate.php )
-
there IS a 5552 build out, per the Vista Support Forum, and Avast is still blocked, as well as Kxxxxxx, Bitxxxxxxxx, and AntVxxxxxx, ....... AXX is not blocked on either of these builds... curiously Microsoft One Care Live works ;)
Avast dudes: this is an emergency... you've got two builds in a row where the product doesn't work and MS is going to release RC1 and start printing a zillion DVDs any second...... love your product and want to use it... but if I can't test the environment, I can't put it on machines when Vista goes gold....
-
Read Vlk's comment, this is a MS cock-up, they hard coded the block of avast, when there wasn't a compatibility issue, it is outside Alwils gift to resolve this, only MS can resolve this by unblocking avast in the next build.
OK folks, I just got some feedback from MS, it seems that the avast driver was "hard blocked" BY MISTAKE, hopefully, the issue will be remedied in the next Vista build. ;)
Thanks
Vlk
-
The bug will not be present in the real RC1 build. That is, the driver will NOT be blocked in Vista RC1, and avast WILL work. I have this confirmed from MS (I had a phonecall with responsible people yesterday).
As a matter of fact, they were very polite, probably realizing that if this happened with a RELEASE build of Windows, we could actually SUE them for this!
Greetings from Madeira,
Vlk
-
DavidR, thanks... but I didn't say it was Avast's fault... it clearly is MS's.... but from the customer perspective, it really doesn't matter whose fault it is, it doesn't work......I've dealt with MS before on stuff like this and know where it can lead unless the third party (Avast) pushes it all the way through
Vlk, thanks for the additional info, I'll try moving back when RC1 comes out...
-
DavidR, thanks... but I didn't say it was Avast's fault... it clearly is MS's....
Whilst there is no direct blame (to me it read like it was implied, sorry) there is heavy onus for "avast dudes" to sort it "emergency" when they are in the hands of MS. I would hate to be in their position waiting for MS to pull their finger out and resolve the problem. I'm sure the Alwil team their pulling their hair out and no mater how much they shout they still have to wait for MS to fix it (easy remove the block) and release the next build which MS will do in their own good time along with the other fixes that are scheduled for the next build.
Avast dudes: this is an emergency... you've got two builds in a row where the product doesn't work and MS is going to release RC1 and start printing a zillion DVDs any second...... love your product and want to use it... but if I can't test the environment, I can't put it on machines when Vista goes gold....
-
My problem is worst! Avast that I have used on all other versions wont even install, I get a window telling me that this software is incompatible with this version of windows, I clicked on the button to find a solution and for the last hor I get a message saying "avast! antivirus is blocked due to compatibility problems" and it has been searching the internet for a solution for more then an hour now, guess what no solution yet. If your gonna install Vista 5536 on Monday then please post what antivirus software you are using on it so we can get some protection out here!
-
If you read the previous posts in this thread, you'll find out that your problem is exactly the same as the one described here. The problem is in the current builds of Vista - so the only solution is to wait for Microsoft to fix it for the next builds.
-
OK, so now we know that AVAST will not load because of MS blocking. MS would love to have you purchase their RECOMMENDED virus scanner which is not blocked however. Maybe MS intentionally blocked this driver knowing that they could not be sued until the final public release of RC1.
Anyway, it is good to know that AVG will work in the mean time.
-
I really doubt that Microsoft deliberately blocked avast as part of any strategy and left AVG working. Let's get real here. The Redmond team do make plain simple mistakes from time to time just as all of us in the IT business do.
Recent experience in this forum in avast beta updates makes me wonder if some of the folks who play in the beta world really understand what they are getting into. Playing with betas means that you will experience problems - some of which you will have to wait a while for a fix.
Don't whine when this happens (and that is what some are doing here) - if you cannot deal with these issues don't play with non-production releases of software.
-
Hi guys I just installed VISTA build 5552 RC1 and am getting the same problem with my avast pro 4.7.869.0 how ever if I right click on the icon in the tsk bar and click "start avast anti virus I get the same message as posted before "software is incompatible with this version of windows", however I can then choose to run it anyway and it runs. But the Online Virus Protection will definately wont work at all. This is serious!!! :o
-
Hi guys I just installed VISTA build 5552 RC1 and am getting the same problem with my avast pro 4.7.869.0 how ever if I right click on the icon in the tsk bar and click "start avast anti virus I get the same message as posted before "software is incompatible with this version of windows", however I can then choose to run it anyway and it runs. But the Online Virus Protection will definately wont work at all. This is serious!!! :o
Then kick up a stink via any vista beta problem reporting method, whilst MS have acknowledged the fault is theirs, the more that complain the quicker MS are likely to push out another build as they said they would to rectify the error of blocking avast.
-
Then kick up a stink via any vista beta problem reporting method, whilst MS have acknowledged the fault is theirs, the more that complain the quicker MS are likely to push out another build as they said they would to rectify the error of blocking avast.
Is there a form (or a link to it) to complain?
An email address?
-
Previously beta testers had access to report bugs, the whole point of beta testing I would have thought that there would have been something for the Consumer Preview and or pre-RC1 versions, etc.
A google search returns many hits a couple of blogs, etc. which may reveal more information http://www.google.co.uk/search?q=vista+beta+test+bug+reporting
However, it is like trying to find a needle in a haystack to try and report a vista bug.
-
Vista RC1 (Build 5600) is out for betatesters. So we will see, if MS enabled the installation of the Avast drivers.
-
Avast! does not work with Vista RC1!
I just have tested it- the same thing as with Build 5536.
-
Avast! does not work with Vista RC1!
I just have tested it- the same thing as with Build 5536.
Do you mean 5600 is useless for avast? >:( :(
Sometimes we come very upset with MS >:( :(
-
Do you mean 5600 is useless for avast? >:( :(
Yes, exactly this is what I mean.
The needed Avast driver is still blocked by Vista RC1 (=Build 5600).
-
I have just installed 5600 (RC1), the build no longer says that Avast has been disabled due to an incompatability in the gui, it does throw the RPC error details above.
The Event Log still shows:
Driver aswMon2.SYS has been blocked from loading.
and
The avast! Standard Shield Support service failed to start due to the following error:
This driver has been blocked from loading
-
I have 5552 build and I get the same error as with 5536. I can use Avast to scan my system but I cant use the Online Protection.
Also just an interesting fact to note that on any microsoft site I have been to including themarket place . They make no mension of AVAST or recomend it , where as they list a whole heap of other programs including AVG. mmmm!?!?
Please notify me once you check this out on Monday
-
Also just an interesting fact to note that on any microsoft site I have been to including themarket place . They make no mension of AVAST or recomend it , where as they list a whole heap of other programs including AVG. mmmm!?!?
I guess you didn't look hard enough ...
http://windowsmarketplace.com/results.aspx?text=avast%21&tabid=1
-
so Vlk did MS say when they're going to fix the problem ?? ???
Because if they didn't say it then fixing it is at no pint there priority :(
Al968
-
Guys, could you please try this driver?
http://public.avast.com/~vlk/vista/aswMon2.sys
Download it, place it to the \windows\system32\drivers folder (overwrite existing) and restart the computer.
Does that resolve the problem? (i.e. no more "driver blocked" event log entries, and no red cross on the avast tray icon)?
Thanks
Vlk
-
I just tested Avast with Vista RC1 x64 - it works!!!!
Maybe MS had "forgotten" to block the Avast drivers within the 64-version, because there was no Vista Pre-RC1 x64...............
Conclusion: There is only an Avast problem with the 32-bit Version of Vista RC1.
-
Well, that's not a suprise actually, the 64bit version uses different (64bit) drivers.
The question is: does the updated file from Vlk's post here work in 32bit version of Vista RC1?
-
I copied the new aswMon2.sys driver and now I get a BSOD with a BAD_POOL_HEADER. After I uninstall and reinstall without the file, I'm back to the original problem we all seem to be having. So I'm certain it's the new file causing my BSOD.
-
Same here!, BSOD after copying driver into system32. Bad_Pool_header! Had to uninstall and now no problem.
Thanks
-
Interesting... Could you please send me the file \windows\minidump\<something>.mdmp that got generated during the crash?
Thanks
Vlk
-
I can't upload the dump file. The forum software says I can't send that type of file so I emailed it to you.
-
1. send the file to my email address, please (it's in my profile)
2. I have been informed that avast (with the original driver) STARTS WORKING with Vista RC1 as soon as you perform Windows Defender 9/2 update. Could you guys please confirm this?
Thanks
Vlk
-
I have been informed that avast (with the original driver) STARTS WORKING with Vista RC1 as soon as you perform Windows Defender 9/2 update. Could you guys please confirm this?
No, I tried to reinstall Avast after having done Windows Update, but Avast still does not work.
-
If Windows Defender is the cause of the problem then you can temporarily disable Windows Defender via Windows Defender itself: Tools > Software Explorer > Startup Programs > Windows Defender > Disable.
Because I don't have Windows Vista myself, I cannot test this unfortunately.
Don't forget to enable it again when the problems are fixed!
-
2. I have been informed that avast (with the original driver) STARTS WORKING with Vista RC1 as soon as you perform Windows Defender 9/2 update. Could you guys please confirm this?
Hmm, seems that the person who suggested this spoke too soon. This does NOT seem to be the case - sorry for the confusion.
I guess you'll all have to wait until I come back from the holidays - I only have 2 days left, the sun is shining, the beach is welcoming and I don't want to spend the 2 days calling Microsoft tech support!! ;D
-
So is there any antivirus at all that actually works in Windows Vista RC1 ?
-
So is there any antivirus at all that actually works in Windows Vista RC1 ?
Isn't avast the only one that is NOT working?
I suppose AVG, TrendMicro, NAV, Kaspersky, NOD32, etc. etc. are working...
What I did not find is a solution for the avast problem...
-
AntiVir is working great even though Vista is nagging all the time, but i just can't update it. It always says everything is up to date even though it's oclearly not. Guess i'll try NOD32, though i was counting on AntiVir since it looked so good so far...
EDIT:
Great, NOD32 can't even be installed ::) AVG here i come. Hope at least this thing is working...
-
Well, Microsoft did something completely insane - they changed a prototype of a system exported function in Vista RC1. I guess it doesn't sound that bad to most of you, but it's really crazy - you are not expected to do that, ever, and certainly not in RC1 build!
It's like a pharmaceutical company changing the formula for their medicament, without changing its name, or actually telling anybody about it. So, everybody using the good old dosage, as they are used to, suddenly dies from overdose :-\
So, even though the blocking of avast! driver was probably done by mistake or bug in Vista, the latest official build of avast! wouldn't work anyway in the RC1 build of Vista (it causes bluescreen, as some found a few posts above). I think Vlk will release an updated version when he comes back from holiday.
-
Ok, for those who want antivirus in Vista RC1, AVG Free is the only choice.
It's the only AV that works without any problems or conflicts what so ever.
Just tried with EICAR and worked fine. Tried updating, worked fine. There were also no problems or warnings during installation. So unfortunatelly i have to recommend it for now (at least till Alwil guys manage to solve the problem).
-
RC1 (5600) and 5536 are two different releases. I am currently running 5600 and Avast is not "compatible" with this most recent version. The service IS running. However, as soon as I log into the system, I am told the avast driver is not compatible and is stopped.
The only log file present is the setup log. There is no warning or error log in the avast directory or subfolders.
Attached, fine a screen shot of the error message about avast and the icon in the system tray.
This is a fresh install in a bare partition.
-
RC1 is 5600. All lower than 5600 are pre-RC1.
-
Ok, for those who want antivirus in Vista RC1, AVG Free is the only choice.
It's the only AV that works without any problems or conflicts what so ever.
Just tried with EICAR and worked fine. Tried updating, worked fine. There were also no problems or warnings during installation. So unfortunatelly i have to recommend it for now (at least till Alwil guys manage to solve the problem).
Yes I posted about AVG working properly in this same thread:
http://forum.avast.com/index.php?topic=23102.msg191586#msg191586
-
I think Vlk will release an updated version when he comes back from holiday.
So, is there any possibility of releasing a new 'avast driver' that works with this Vista RC1 5600 or, on contrary, we need to wait a new Vista build?
Sometimes MS drives me mad :P
-
I think Vlk will release an updated version when he comes back from holiday.
So, is there any possibility of releasing a new 'avast driver' that works with this Vista RC1 5600 or, on contrary, we need to wait a new Vista build?
Sometimes MS drives me mad :P
My guess would be that because MS moved the goal posts the driver might not work, etc.
Well, Microsoft did something completely insane - they changed a prototype of a system exported function in Vista RC1. I guess it doesn't sound that bad to most of you, but it's really crazy - you are not expected to do that, ever, and certainly not in RC1 build!
So if Alwil can redo or modify the driver to comply with MS's changes hopefully we should have a compliant driver ???
-
So if Alwil can redo or modify the driver to comply with MS's changes hopefully we should have a compliant driver ???
If possible, I would like this: a compliand driver with this *damaged* Vista last release...
-
Does anyone have a link for latest build, I belive 5600 or something like that ? I still have Vista Pre-RC1 and I would really like to try this new one. Is it even public release ?
-
Does anyone have a link for latest build, I belive 5600 or something like that ? I still have Vista Pre-RC1 and I would really like to try this new one. Is it even public release ?
Sasha, the beta test seems to be closed.
I mean, there is not a legal link to download the RC1.
Only beta testers will receive this link.
There are P2P files available anyway ::)
-
This is wandering far off topic, but the Vista Beta program is open to Beta Testers and people with MSDN and MS TechNet subscriptions. They can download the latest build (presently 5536, and the first one I have kept on a box for more than ten minutes) and the keys necessary to install/activate it.
It is too bad that Avast! doesn't work under this version; the same is true of many of the utilities my systems depend on (WS_FTP, for one).
Other utility developers are showing the same attitude - 'we don't support betas' - in their forums, but I'm sure the developer(s) is(are) looking into just what kind of hairball the Vole has handed them.
So, all we can do is wait....and use AVG (gag) as our AV until somebody figures out the 'exported function' (or whatever it is) problem...
While we are waiting, there are lots of things to poke and prod in Vista, such as - how do you access 'Documents and Settings'?
ss
-
Error log
8/31/2006 11:32:27 PM 1157085147 SYSTEM 1552 AAVM - scanning error: Aavm: FetchGlobalCounters cannot open mapping - server DOWN???, 00000002.
Warning log
7/31/2006 7:10:37 AM 1154347837 Pierre 7600 Sign of "Win32:Lineage-197 [Trj]" has been found in "D:\found.001\dir0031.chk\p2psetup.exe\[UPX]" file.
-
I had no problem to install and run Avast! Home v. 4.7.871 on earlier Vista versions, but it doesn't work with the new Build 5536.
Any idea?
BTW, RC1 is 5600
-
BTW, RC1 is 5600
What do you mean?
Did you manage to install avast in a Vista RC1 5600 installation? :o
-
From Igors Post It seems the ALWIL team i snot happy with Microsoft's RC1 build
Lets Hope Apple's beta of Leopard is not giving them as much trouble with the Mac Version
-
BTW, RC1 is 5600
What do you mean?
Did you manage to install avast in a Vista RC1 5600 installation? :o
I upgraded from 5472, not officially supported, but everything is working so far (except for avast).
-
I upgraded from 5472, not officially supported, but everything is working so far (except for avast).
5472?
Do you mean 5672?
-
5472 was the release bulid before 5536 which was a quick, one week, test build before the offical release of RC1, build 5600.
-
I can now announce that there will be a pre-release version of avast Home/Pro compatible with Vista RC1 available on Friday.
Thanks :)
Vlk
-
I can now announce that there will be a pre-release version of avast Home/Pro compatible with Vista RC1 available on Friday.
Thanks Vlk... I'll test it as soon as I can, I mean, if you're refering to a new *corrected* version of avast to work with the monster-wrong-Vista-RC1-5600 :P
Welcome back from your vacations ;D
-
...avast to work with the monster-wrong-Vista-RC1-5600 :P
...
...
I wouldn't go that far to call it "monster-wrong-Vista". Everything else works wonderful, and that "glitch" that happened with few antiviruses, as far as I can see Microsoft does not have to do anything to fix it. All those antiviruses that didn't or still don't work with latest Vista release, their developers need to apply some changes. Of course I am sure Microsoft knows exactly why they took that step, and it could be that it has to do something with how new OS will deal with security related applications and security threats as well.
It was always like that... You have to build your application accordingly to the OS requirements, not backwards.
AVG worked immediatelly as soon as it was installed on my end, so it must be that AVG developers counted with that from the beginning.
-
Whilst I agree that application developers have to conform, but when major things are changed at such a critical time, you would at least expect MS to give the companies working with them to integrate important applications like AVs a heads up. Rather than find suddenly that things no longer work.
When this first reared its ugly head, and Alwil contacted MS it was thought the only problem was the hard coded block on a number of AVs avast included. No mention of the other issue that has now come to light during those enquiries with MS.
Well, Microsoft did something completely insane - they changed a prototype of a system exported function in Vista RC1. I guess it doesn't sound that bad to most of you, but it's really crazy - you are not expected to do that, ever, and certainly not in RC1 build!
It's like a pharmaceutical company changing the formula for their medicament, without changing its name, or actually telling anybody about it. So, everybody using the good old dosage, as they are used to, suddenly dies from overdose :-\
-
Whilst I agree that application developers have to conform, but when major things are changed at such a critical time, you would at least expect MS to give the companies working with them to integrate important applications like AVs a heads up. Rather than find suddenly that things no longer work.
Remember, Vista RC1 Build 5600 is not even public. They are still developing it and no one forces people to test it untill all these things are fixed. That's why it takes so long to release it. I am sure if they rushed it, everybody (ok, not everybody just those anti-MS dudes) would keep complaining and bitching about how unsecure another MS product is...
It takes a lot of work and a lot of planning, and I am sure we will see a lot more problems untill everything is fixed and works how it's supposed to work.
-
I wouldn't go that far to call it "monster-wrong-Vista".
I'm not an anti-MS, on contrary. You know that 8)
But in this particular case I believe and trust Igor - which called MS insane - and Vlk - which say sue MS - so...
Well, Microsoft did something completely insane - they changed a prototype of a system exported function in Vista RC1. I guess it doesn't sound that bad to most of you, but it's really crazy - you are not expected to do that, ever, and certainly not in RC1 build!
It's like a pharmaceutical company changing the formula for their medicament, without changing its name, or actually telling anybody about it. So, everybody using the good old dosage, as they are used to, suddenly dies from overdose :-\
So, even though the blocking of avast! driver was probably done by mistake or bug in Vista, the latest official build of avast! wouldn't work anyway in the RC1 build of Vista (it causes bluescreen, as some found a few posts above). I think Vlk will release an updated version when he comes back from holiday.
The bug will not be present in the real RC1 build. That is, the driver will NOT be blocked in Vista RC1, and avast WILL work.
I have this confirmed from MS (I had a phonecall with responsible people yesterday).
As a matter of fact, they were very polite, probably realizing that if this happened with a RELEASE build of Windows, we could actually SUE them for this!
-
Public Release of RC1 is today (to everybody in public Beta 2) ... functional til June 1, 2007....
MS site outlining "Vista RC1 Antivirus Providers"
http://www.microsoft.com/athome/security/update/windowsvistaRC1AV.mspx
Again... Avast Guys, this is an emergency... I know about your announcement for Friday..... I read a buncha posts and I know it's not your fault about driver changes, lack of notification, and promises from MS you would be fixed... but it is what it is.....
-
...
...
As a matter of fact, they were very polite, probably realizing that if this happened with a RELEASE build of Windows, we could actually SUE them for this!
Tech, you are taking things out of their context... spot something inside Vlk's reply and you will see what he really said:
Quote by Vlk:
"...that if this happened with a RELEASE build of Windows, we could actually SUE them for this!..."
Well exactly what I wrote up there in my previous reply. It is NOT a Public Release ;)
-
...
...
As a matter of fact, they were very polite, probably realizing that if this happened with a RELEASE build of Windows, we could actually SUE them for this!
Tech, you are taking things out of their context... spot something inside Vlk's reply and you will see what he really said:
"...that if this happened with a RELEASE build of Windows, we could actually SUE them for this!..."
Well exactly what I wrote up there in my previous reply. It is NOT a Public Release ;)
Ok... you're right.
Igor speaks technically... and I agree with him in this point.
-
BTW, you could spend a buncha time / resources suing MS with very shaky results (unreleased product, hard to prove damages, huge well financed defendant) , or you could spend a lot less and just fix it...... I really like your product and am not pro or con MS or Avast, just trying to illuminate the urgency re: people qualifying corporate / resller products....
-
Exactly my point too. I like your voice of wisdom and how objective you are. ;)
Thanks for info from your previous reply. Do you by any chance have any download link for RC1 Build 5600 ?
-
http://download.windowsvista.com/preview/rc1/en/download.htm
-
Thanks Chocholo ! I could swear that I tried exactly the same link few minutes ago and it gave me some error that server was down or something similar.
Downloading it now... :)
-
Remember, Vista RC1 Build 5600 is not even public. They are still developing it and no one forces people to test it untill all these things are fixed. That's why it takes so long to release it. I am sure if they rushed it, everybody (ok, not everybody just those anti-MS dudes) would keep complaining and bitching about how unsecure another MS product is...
It takes a lot of work and a lot of planning, and I am sure we will see a lot more problems untill everything is fixed and works how it's supposed to work.
The fact that it isn't public makes no difference, we aren't just talking about people using beta products but companies trying to develop programs that are compatible with vista. One of the reasons for beta and Release Candidates, etc. is so that developers, application programmers can try to integrate their products with it and up until this issue avast was one of the very few AVs that did work with vista beta. This has nothing to do with being anti-ms but fairly laying the blame at the correct doorstep nothing more.
The reason I quoted Igor's comments were because avast was actively working with MS to have avast work with vista and out of the blue a huge surprise, in his words 'completely insane.'
-
People need to realize that MS can't please everybody and it's never gonna be like that. Not just with MS, but with all other large companies as well. But as always it's easier to blame on MS than to be quiet and work on bugs/errors regardless of who caused them. MS, Alwil, AVG guys, Eset and many others need to work together on solving these issues, not against each other. They are taking money out of our pockets, customer's pockets, not other way around, so they need to work their buts off to make everything work as it should. ;)
MS is just a large ship, and all these av/firewall companies are small businesses like those little shops, coffee shops, boutiques, restaurants etc. that you get on that boat when you board. If I board some ship and I pay for everything, I expect that boat to be safe as well as good service provided by those small firms. Also, if some parts of the boat needs to be redesigned for any reason, and you need to relocate some of those businesses to some other location, I don't believe that boat will have to make huge changes to satisfy that particular small shop. Small shop will have to adapt to those changes, that's the only way.
-
I just installed RC1 build 5600, and it work great. No issues so far. I just want to report that AVG is no longer working properly. Services failed to start and Windows security center reports that it didn't find any antivirus installed...
EDIT: I just tried uninstalling AVG and installing it from the scratch and it worked without problems. It's up and running again, and also it just updated its virus database.
Screenshot when AVG failed to start (after the Vista upgrade from 5536 to 5600):
(http://img220.imageshack.us/img220/4507/untitled1gr7.jpg)
-
Public Release of RC1 is today (to everybody in public Beta 2) ... functional til June 1, 2007....
MS site outlining "Vista RC1 Antivirus Providers"
http://www.microsoft.com/athome/security/update/windowsvistaRC1AV.mspx
Again... Avast Guys, this is an emergency... I know about your announcement for Friday..... I read a buncha posts and I know it's not your fault about driver changes, lack of notification, and promises from MS you would be fixed... but it is what it is.....
I just noticed they mentioned TrendMicro... is that their favorite AV solution ? Maybe all these problems with other antiviruses are not just a conicidence ? ::) Like; "...all other AV solutions failed to work and this is the only one that actually works... we will not force anyone to use it, but you can see yourself that the fact is, this is the only AV that actually works in Vista..." ::)
(http://img221.imageshack.us/img221/9062/untitled1lr0.jpg)
-
I can now announce that there will be a pre-release version of avast Home/Pro compatible with Vista RC1 available on Friday.
I can't stand to test it 8)
My Vista is unprotected ;D
-
It is interesting that I talked in a board and ppl there seems not to want any Antivirus. Anyway I like to have one installed. AVG is worked in 5536 but got some issue in 5600. I'm looking forward to the release in Friday...
-
It is interesting that I talked in a board and ppl there seems not to want any Antivirus. Anyway I like to have one installed. AVG is worked in 5536 but got some issue in 5600. I'm looking forward to the release in Friday...
AVG just needs to be uninstalled and reinstalled once your RC1 Build 5600 is installed and configured. I also found similar advice on one of those Microsoft support forums.
I posted about it in this same thread, just few posts above:
http://forum.avast.com/index.php?topic=23102.msg192843#msg192843
AVG works perfectly once you uninstall and reinstall it.
-
I can now announce that there will be a pre-release version of avast Home/Pro compatible with Vista RC1 available on Friday.
Thanks :)
Vlk
I'm ready! Not going online with 5600 (RC1) until I have avast! on my side. ;D
-
It's Friday! Are we good to go with the fixed version now?
Colin.
-
It's Friday! Are we good to go with the fixed version now?
Vlk, uh uh... we're waiting ;D
-
It is interesting that I talked in a board and ppl there seems not to want any Antivirus. Anyway I like to have one installed. AVG is worked in 5536 but got some issue in 5600. I'm looking forward to the release in Friday...
AVG just needs to be uninstalled and reinstalled once your RC1 Build 5600 is installed and configured. I also found similar advice on one of those Microsoft support forums.
I posted about it in this same thread, just few posts above:
http://forum.avast.com/index.php?topic=23102.msg192843#msg192843
AVG works perfectly once you uninstall and reinstall it.
Well, I always start new build of Vista with a fresh install (format and install). BTW I got it work now. (though I'd love avast! installed.)
^
^
I mean AVG... Avast still not work.
-
BTW I got it work now. (though I'd love avast! installed.)
What?
avast over Vista RC1 5600 ?
I was not brave enough to test and have to install Vistal all over again..., but if you manage installing and working with avast at the Vista RC1, well... maybe I'll try too 8)
-
Does Avast 4.7.871 works now under Vista RC1?
-
I wonder that same thing right now ... burning my RC1 at the moment and would like to know if I can use avast now :)
re
OrlyTM
-
I'm running off Vista RC1 right now, and have tried the Avast updates, and it still doesnt work. I'll try again later today though and let you guys know
-
ok ... tnx :)
re
OrlyTM
-
avast! does not work for me on vista rc 1 (5600)x86 :(
-
that AVG antivirus that you ppl are using ... is it standard windows version or Vista specialized?
tnx
re
OrlyTM
-
that AVG antivirus that you ppl are using ... is it standard windows version or Vista specialized?
As far I know, the XP version.
-
Just to add my twopennys worth...Avast is being blocked by Program Compatability Wizard in Vista RC1 5600. ??? Nice one Billy boy..another bitch of an O/S :D
-
Here it is: http://forum.avast.com/index.php?topic=23424 :)
(a promise is a promise - let's only hope it won't ruin my marriage ;) ;D)
Cheers
Vlk
-
Avast will not install on Vista RC1 Build 5600. I get an error message that says that it is not compatible. Is Awil ever going to fix this issue??
-
Gary, YES. :)
See my post above.
-
Gary, YES. :)
See my post above.
Yes The Beta from your link will, however I still got the compatibility error but I ignored it. Seems to be working OK now. The build that is on Awil's website will not install.
-
I have now uninstalled the Avast antivirus i had installed earlier on Vista RC1 (5600), and have installed the Avast beta mentioned a few posts back http://forum.avast.com/index.php?topic=23424
Avast now works on Vista RC1!
,although there is a little bug, where if you try to update the avast program through it's updatye function then it actually downgrades to the last version (the one which was incompatible with RC1). So I have just set the program update to manual check/update, and the database update I have set to automatic. All is working well!
-
cache-man, the problem with downgrading has already been fixed (a few hours ago) - but I think you'll have to download the installer again and reinstall the program.
-
cache-man, the problem with downgrading has already been fixed (a few hours ago) - but I think you'll have to download the installer again and reinstall the program.
I just re-tested this Igor, and can confirm that it no longer downgrades. So have set program update back to auto now.
So all those wanting to get avast working on thieir RC1 install, you guys now can, just see the link a few posts back. :)
-
VLK--it worx flawlessly for me. Thanx!! And thank your wife for me too for being understanding.
Here it is: http://forum.avast.com/index.php?topic=23424 :)
(a promise is a promise - let's only hope it won't ruin my marriage ;) ;D)
Cheers
Vlk
-
The "normal" Avast Home version (downloadable from the Avast homepage) still does not work with Vista RC2.
-
The "normal" Avast Home version (downloadable from the Avast homepage) still does not work with Vista RC2.
What exactly does it mean?
-
Fernando please make sure you have build 892
-
The "normal" Avast Home version (downloadable from the Avast homepage) still does not work with Vista RC2.
Like Igor asked, which is the exactly message? or the problems (describing them)... ::) ???
-
The "normal" Avast Home version (downloadable from the Avast homepage) still does not work with Vista RC2.
Like Igor asked, which is the exactly message? or the problems (describing them)... ::) ???
The problem is the following:
The day before yesterday (October 11th) I installed Vista RC2 x86. After having access to the internet I downloaded the German version of Avast! 4 Home from this site:
http://www.avast.at/download.htm
After the install of this "actual" Avast! version I hat a red circle within the Avast try icon. After a double click onto this icon I got the following message:
Das AAVM Sub-System hat einen PCR-Fehler festgestellt.
Operation konnte nicht beendet werden.I just tested the Avast! version: It's Build 871 from August 5th!
To verify, that I really get an old Avast! version from an Avast homepage, I just downloaded again the same file. Result: it is still Build 871!
So please give me a link where I can get an actual German Avast! version usable for Vista RC2.
CU
Fernando
EDIT: I solved my problem myself by downloading and installing Avast Build 892 (got it at http://www.avast.com)
My advice: The Austrian Avast team should not offer old Avast versions!
-
My advice: The Austrian Avast team should not offer old Avast versions!
Do you mean a reseller? An Austrian reseller?
Or did you download an old version of avast? Where?
-
Do you mean the download page http://www.avast.at/download.htm ?
That would be strange as the download links on that page are pointing to our official download sites (that contain the latest version).
Cheers
Vlk
-
Do you mean the download page http://www.avast.at/download.htm ?
Exactly, as I have written within my last post.
Try to download the German version of Avast from that server and look, which Build you get.
-
Do you mean the download page http://www.avast.at/download.htm ?
That would be strange as the download links on that page are pointing to our official download sites (that contain the latest version).
It doesn't - the download link for the German version points to a local file (at www.avast.at) - which is probably obsolete.
It's better to download the installer from our pages (http://www.avast.com/eng/download-avast-home.html).