bug windows vista avast professional

Hello all, This is for a BUG in Windows Vista 5342 and Avast! Professional, an antivirus program. It so happens that when I install Avast! Professional, it all works fine and everything is good and dandy. When I update Avast! Professional via Internet to the latest version, it all goes smooth as silk... Until I restart the computer. When I commit that "mistake," I find myself with a broken wireless network that will not connect no matter how hard I try to install new drivers, setup networking again... you name it, I've tried it. The only thing left for me to do is to (sigh) do the Three-step of Dread: Reboot, Format, Reinstall. Any thoughts?

Actually, its a compatibility issue with Avast!, its been giving problems since build 5112, Avast needs to fix this issue, not Microsoft. We are months away from RTM, so as more builds are released, its likely to break Avast. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Carlos Manuel Pires" wrote in message

Hello all, This is for a BUG in Windows Vista 5342 and Avast! Professional, an antivirus program. It so happens that when I install Avast! Professional, it all works fine and everything is good and dandy. When I update Avast! Professional via Internet to the latest version, it all goes smooth as silk... Until I restart the computer. When I commit that "mistake," I find myself with a broken wireless network that will not connect no matter how hard I try to install new drivers, setup networking again... you name it, I've tried it. The only thing left for me to do is to (sigh) do the Three-step of Dread: Reboot, Format, Reinstall. Any thoughts?

Why do you call a problem with a software package that was written BEFORE an unreleased operating system a compatibility issue with that software? It is actually a compatibility issue with Vista.
This is exactly the problem -- software is written based on a certain set of standards, then MS rewrites those standards and breaks everything that worked before, then it's up to software publishers/coders/etc to scramble to get their once working software working again. Yet everyone blames the software for not working correctly, when most likely it DID work correctly on the OS it was written for.
"Andre Da Costa [Extended64]" wrote in message | Actually, its a compatibility issue with Avast!, its been giving problems | since build 5112, Avast needs to fix this issue, not Microsoft. We are | months away from RTM, so as more builds are released, its likely to break | Avast. | -- | -- | Andre | Windows Connected | http://www.windowsconnected.com | Extended64 | http://www.extended64.com | Blog | http://www.extended64.com/blogs/andre | http://spaces.msn.com/members/adacosta | | "Carlos Manuel Pires" wrote in message | | > Hello all, | > This is for a BUG in Windows Vista 5342 and Avast! Professional, an | > antivirus program. | > It so happens that when I install Avast! Professional, it all works fine | > and everything is good and dandy. When I update Avast! Professional via | > Internet to the latest version, it all goes smooth as silk... Until I | > restart the computer. When I commit that "mistake," I find myself with a | > broken wireless network that will not connect no matter how hard I try to | > install new drivers, setup networking again... you name it, I've tried it. | > The only thing left for me to do is to (sigh) do the Three-step of Dread: | > Reboot, Format, Reinstall. | > Any thoughts? | |

So, you are saying we should still be using the NT 3.1 codebase to sacrifice security over application compatibility? These things are always expected with new releases of Windows, especially when it involves a new kernel. XP was not a major upgrade in terms of changes to the kernel from 2000 (5.0) to XP (5.1) and it required new versions of popular AV software utilities such as Norton and Mcafee. Like I also said before, Windows Vista is still in development, at periods during the development certain parts of the code become obselete (whether for security or performance reasons), because AV software tend to have hooks into the kernel, those obselete parts will break the software requiring that it (AV) to also be updated. Symantec also noted that we can expect a new version of its retail Antivirus utility for Vista, 30 days after its release. I expect similar approach from Avast for Vista also. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Guess Who" wrote in message

Why do you call a problem with a software package that was written BEFORE an unreleased operating system a compatibility issue with that software? It is actually a compatibility issue with Vista.
This is exactly the problem -- software is written based on a certain set of standards, then MS rewrites those standards and breaks everything that worked before, then it's up to software publishers/coders/etc to scramble to get their once working software working again. Yet everyone blames the software for not working correctly, when most likely it DID work correctly on the OS it was written for.
"Andre Da Costa [Extended64]" wrote in message | Actually, its a compatibility issue with Avast!, its been giving problems | since build 5112, Avast needs to fix this issue, not Microsoft. We are | months away from RTM, so as more builds are released, its likely to break | Avast. | -- | -- | Andre | Windows Connected | http://www.windowsconnected.com | Extended64 | http://www.extended64.com | Blog | http://www.extended64.com/blogs/andre | http://spaces.msn.com/members/adacosta | | "Carlos Manuel Pires" wrote in message | | > Hello all, | > This is for a BUG in Windows Vista 5342 and Avast! Professional, an | > antivirus program. | > It so happens that when I install Avast! Professional, it all works fine | > and everything is good and dandy. When I update Avast! Professional via | > Internet to the latest version, it all goes smooth as silk... Until I | > restart the computer. When I commit that "mistake," I find myself with a | > broken wireless network that will not connect no matter how hard I try to | > install new drivers, setup networking again... you name it, I've tried it. | > The only thing left for me to do is to (sigh) do the Three-step of Dread: | > Reboot, Format, Reinstall. | > Any thoughts? | |

Also, I can't picture using Norton SystemWorks 3.0 on Vista right now. ;) -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Andre Da Costa [Extended64]" wrote in message

So, you are saying we should still be using the NT 3.1 codebase to sacrifice security over application compatibility? These things are always expected with new releases of Windows, especially when it involves a new kernel. XP was not a major upgrade in terms of changes to the kernel from 2000 (5.0) to XP (5.1) and it required new versions of popular AV software utilities such as Norton and Mcafee. Like I also said before, Windows Vista is still in development, at periods during the development certain parts of the code become obselete (whether for security or performance reasons), because AV software tend to have hooks into the kernel, those obselete parts will break the software requiring that it (AV) to also be updated. Symantec also noted that we can expect a new version of its retail Antivirus utility for Vista, 30 days after its release. I expect similar approach from Avast for Vista also. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Guess Who" wrote in message Why do you call a problem with a software package that was written BEFORE an unreleased operating system a compatibility issue with that software? It is actually a compatibility issue with Vista.
This is exactly the problem -- software is written based on a certain set of standards, then MS rewrites those standards and breaks everything that worked before, then it's up to software publishers/coders/etc to scramble to get their once working software working again. Yet everyone blames the software for not working correctly, when most likely it DID work correctly on the OS it was written for.
"Andre Da Costa [Extended64]" wrote in message | Actually, its a compatibility issue with Avast!, its been giving problems | since build 5112, Avast needs to fix this issue, not Microsoft. We are | months away from RTM, so as more builds are released, its likely to break | Avast. | -- | -- | Andre | Windows Connected | http://www.windowsconnected.com | Extended64 | http://www.extended64.com | Blog | http://www.extended64.com/blogs/andre | http://spaces.msn.com/members/adacosta | | "Carlos Manuel Pires" wrote in message | | > Hello all, | > This is for a BUG in Windows Vista 5342 and Avast! Professional, an | > antivirus program. | > It so happens that when I install Avast! Professional, it all works fine | > and everything is good and dandy. When I update Avast! Professional via | > Internet to the latest version, it all goes smooth as silk... Until I | > restart the computer. When I commit that "mistake," I find myself with a | > broken wireless network that will not connect no matter how hard I try to | > install new drivers, setup networking again... you name it, I've tried it. | > The only thing left for me to do is to (sigh) do the Three-step of Dread: | > Reboot, Format, Reinstall. | > Any thoughts? | |

I have to agree with Andre on this. If you run a product on a beta OS, there is a good chance you will run into a problem with running that program. Also, currently the requirements for avast 4 pro state that the program only runs on the following platforms:
a.. Windows 95 a.. Windows 98 a.. Windows Me a.. Windows NT 4 (No Server) a.. Windows 2000 (No Server) a.. Windows XP (No Server)
I do not see Windows Vista Beta listed for avast! 4 Professional Edition. If you try to run this software, it is run at your own risk.
-- Jason
Applied but still waiting to be accepted for the Vista Beta Testing group. Can't wait to be able to play and help make it even better.
http://www.orderpcs4free.com/?r=878
MS Windows XP Pro, IE 7.0.5335.5 Beta 2
"Guess Who" wrote in message

Why do you call a problem with a software package that was written BEFORE an unreleased operating system a compatibility issue with that software? It is actually a compatibility issue with Vista.
This is exactly the problem -- software is written based on a certain set of standards, then MS rewrites those standards and breaks everything that worked before, then it's up to software publishers/coders/etc to scramble to get their once working software working again. Yet everyone blames the software for not working correctly, when most likely it DID work correctly on the OS it was written for.
"Andre Da Costa [Extended64]" wrote in message | Actually, its a compatibility issue with Avast!, its been giving problems | since build 5112, Avast needs to fix this issue, not Microsoft. We are | months away from RTM, so as more builds are released, its likely to break | Avast. | -- | -- | Andre | Windows Connected | http://www.windowsconnected.com | Extended64 | http://www.extended64.com | Blog | http://www.extended64.com/blogs/andre | http://spaces.msn.com/members/adacosta | | "Carlos Manuel Pires" wrote in message | | > Hello all, | > This is for a BUG in Windows Vista 5342 and Avast! Professional, an | > antivirus program. | > It so happens that when I install Avast! Professional, it all works fine | > and everything is good and dandy. When I update Avast! Professional via | > Internet to the latest version, it all goes smooth as silk... Until I | > restart the computer. When I commit that "mistake," I find myself with a | > broken wireless network that will not connect no matter how hard I try to | > install new drivers, setup networking again... you name it, I've tried it. | > The only thing left for me to do is to (sigh) do the Three-step of Dread: | > Reboot, Format, Reinstall. | > Any thoughts? | |

I can't picture using Norton.... ;)
Scøtt Live Messenger FAQs - http://wlm.scottisafool.co.uk/
Andre Da Costa [Extended64] wrote: > Also, I can't picture using Norton SystemWorks 3.0 on Vista right now. ;)

UPDATE: After a _new_ fresh install I got tired of this waltz and changed AV to AVG Free. Works fine so far.

"Carlos Manuel Pires" wrote in message

Hello all, This is for a BUG in Windows Vista 5342 and Avast! Professional, an antivirus program. It so happens that when I install Avast! Professional, it all works fine and everything is good and dandy. When I update Avast! Professional via Internet to the latest version, it all goes smooth as silk... Until I restart the computer. When I commit that "mistake," I find myself with a broken wireless network that will not connect no matter how hard I try to install new drivers, setup networking again... you name it, I've tried it. The only thing left for me to do is to (sigh) do the Three-step of Dread: Reboot, Format, Reinstall. Any thoughts?

Avast needs to fix this issue, not Microsoft Your arrogance is enormous! Avast works great on XP, so its Vista's problem!

They where the people who changed an element..... not avast.
If you are a developer on vista, you must know that there is an uproar on the internet with complaints about how bad vista seems to be going....
Let MS be warned.. consumers of 2006+ are not forgiving at all....
"Andre Da Costa [Extended64]" wrote in message

Actually, its a compatibility issue with Avast!, its been giving problems since build 5112, Avast needs to fix this issue, not Microsoft. We are months away from RTM, so as more builds are released, its likely to break Avast. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Carlos Manuel Pires" wrote in message Hello all, This is for a BUG in Windows Vista 5342 and Avast! Professional, an antivirus program. It so happens that when I install Avast! Professional, it all works fine and everything is good and dandy. When I update Avast! Professional via Internet to the latest version, it all goes smooth as silk... Until I restart the computer. When I commit that "mistake," I find myself with a broken wireless network that will not connect no matter how hard I try to install new drivers, setup networking again... you name it, I've tried it. The only thing left for me to do is to (sigh) do the Three-step of Dread: Reboot, Format, Reinstall. Any thoughts?

If you run a product on a beta OS, there is a good chance you will run into a problem with running that program. Also, currently the requirements for avast 4 pro state that the program only runs on the following platforms:
a.. Windows 95 a.. Windows 98 a.. Windows Me a.. Windows NT 4 (No Server) a.. Windows 2000 (No Server) a.. Windows XP (No Server)
I do not see Windows Vista Beta listed for avast! 4 Professional Edition. If you try to run this software, it is run at your own risk.
-- Jason
Applied but still waiting to be accepted for the Vista Beta Testing group. Can't wait to be able to play and help make it even better.
http://www.orderpcs4free.com/?r=878
MS Windows XP Pro, IE 7.0.5335.5 Beta 2
"John Jay Smith" <-> wrote in message

Avast needs to fix this issue, not Microsoft Your arrogance is enormous! Avast works great on XP, so its Vista's problem! They where the people who changed an element..... not avast.
If you are a developer on vista, you must know that there is an uproar on the internet with complaints about how bad vista seems to be going....
Let MS be warned.. consumers of 2006+ are not forgiving at all....
"Andre Da Costa [Extended64]" wrote in message Actually, its a compatibility issue with Avast!, its been giving problems since build 5112, Avast needs to fix this issue, not Microsoft. We are months away from RTM, so as more builds are released, its likely to break Avast. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Carlos Manuel Pires" wrote in message Hello all, This is for a BUG in Windows Vista 5342 and Avast! Professional, an antivirus program. It so happens that when I install Avast! Professional, it all works fine and everything is good and dandy. When I update Avast! Professional via Internet to the latest version, it all goes smooth as silk... Until I restart the computer. When I commit that "mistake," I find myself with a broken wireless network that will not connect no matter how hard I try to install new drivers, setup networking again... you name it, I've tried it. The only thing left for me to do is to (sigh) do the Three-step of Dread: Reboot, Format, Reinstall. Any thoughts?

Actually I have to say... it isn't up to Microsoft to "work on issues" such as these. It's down to the manufacturer of the product.
It's down to Microsoft to build a good, reliable platform for other applications to run on it, but not down to Microsoft to change itself to make other applications work 100%.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "John Jay Smith" <-> wrote in message

Avast needs to fix this issue, not Microsoft Your arrogance is enormous! Avast works great on XP, so its Vista's problem! They where the people who changed an element..... not avast.
If you are a developer on vista, you must know that there is an uproar on the internet with complaints about how bad vista seems to be going....
Let MS be warned.. consumers of 2006+ are not forgiving at all....
"Andre Da Costa [Extended64]" wrote in message Actually, its a compatibility issue with Avast!, its been giving problems since build 5112, Avast needs to fix this issue, not Microsoft. We are months away from RTM, so as more builds are released, its likely to break Avast. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Carlos Manuel Pires" wrote in message Hello all, This is for a BUG in Windows Vista 5342 and Avast! Professional, an antivirus program. It so happens that when I install Avast! Professional, it all works fine and everything is good and dandy. When I update Avast! Professional via Internet to the latest version, it all goes smooth as silk... Until I restart the computer. When I commit that "mistake," I find myself with a broken wireless network that will not connect no matter how hard I try to install new drivers, setup networking again... you name it, I've tried it. The only thing left for me to do is to (sigh) do the Three-step of Dread: Reboot, Format, Reinstall. Any thoughts?

I can't get Avast to work either (however I am a MSDN OS Level Subscriber, so I am running Build 5308 CTP, but I remember reading other complaints about Build 5342 and Avast in this Newsgroup, so it is a Known Issue).
"Carlos Manuel Pires" wrote in message

Hello all, This is for a BUG in Windows Vista 5342 and Avast! Professional, an antivirus program. It so happens that when I install Avast! Professional, it all works fine and everything is good and dandy. When I update Avast! Professional via Internet to the latest version, it all goes smooth as silk... Until I restart the computer. When I commit that "mistake," I find myself with a broken wireless network that will not connect no matter how hard I try to install new drivers, setup networking again... you name it, I've tried it. The only thing left for me to do is to (sigh) do the Three-step of Dread: Reboot, Format, Reinstall. Any thoughts?