Vista Tutorial - CA EZ AntiVirus and Vista Windows Defender

I have installed CA EZ AntiVirus as they have provided one year suscription
free to Vista beta users, and I don't want to use Vista without an
antivirus.

But everytime that Vista starts, Windows Defender blocks it and I must
manually select "run blocked program".

Is there a way to autorize it for ever ? Thanks,

Just goto control panel Windows firewal advance add programes

"Lars" wrote:

> I have installed CA EZ AntiVirus as they have provided one year suscription
> free to Vista beta users, and I don't want to use Vista without an
> antivirus.
>
> But everytime that Vista starts, Windows Defender blocks it and I must
> manually select "run blocked program".
>
> Is there a way to autorize it for ever ? Thanks,
>
>

> Just goto control panel Windows firewal advance add programes

I have done that but Windows Defender keeps blocking it.

Any hints ?

Right click on the icon on the taskbar for defender.
select allow in the popup

"Lars" wrote:

> > Just goto control panel Windows firewal advance add programes
>
> I have done that but Windows Defender keeps blocking it.
>
> Any hints ?
>

Hi - try this: Left click Start menu icon in taskbar, go to "Administrative
Tools", then left click on "Computer Management", then click "Local Users and
Groups", then double click the "Users" folder, then right click
"Administrator" and left click "Properties" - then uncheck box: Account is
disabled. Do NOT apply a password while in that module. Good luck!

"Lars" wrote:

> I have installed CA EZ AntiVirus as they have provided one year suscription
> free to Vista beta users, and I don't want to use Vista without an
> antivirus.
>
> But everytime that Vista starts, Windows Defender blocks it and I must
> manually select "run blocked program".
>
> Is there a way to autorize it for ever ? Thanks,
>
>

In a similar case the only options I see are remove and disable, enable is
greyed out. How do I tell it to allow always instead of having to manually
run the blocked startup app?

Wow! That solved the AVG problem!

But I'm not sure what's going on. After a Restart I got the option for the
first time to sign in as me or Admin. I chose Admin and discovered Quark
wasn't under All Programs. (I had to permit it each times I launched it, a
pain)

So I reinstalled Quark as Admin -- and no permissions are needed to run it.
And for the first time, CuteFTP worked with Quark.

Back to signing in as me, AVG is fine, but I still get a prompt to permit
Quark to run.

<<Puzzled in Palm Beach>>




"mozesrph" <mozesrph@discussions.microsoft.com> wrote in message
news:B7F83639-2243-4B16-95F2-69157FD5B263@microsoft.com...
> Hi - try this: Left click Start menu icon in taskbar, go to
> "Administrative
> Tools", then left click on "Computer Management", then click "Local Users
> and
> Groups", then double click the "Users" folder, then right click
> "Administrator" and left click "Properties" - then uncheck box: Account is
> disabled. Do NOT apply a password while in that module. Good luck!
>
> "Lars" wrote:
>
>> I have installed CA EZ AntiVirus as they have provided one year
>> suscription
>> free to Vista beta users, and I don't want to use Vista without an
>> antivirus.
>>
>> But everytime that Vista starts, Windows Defender blocks it and I must
>> manually select "run blocked program".
>>
>> Is there a way to autorize it for ever ? Thanks,
>>
>>

"Lars" wrote:

> I have installed CA EZ AntiVirus as they have provided one year suscription
> free to Vista beta users, and I don't want to use Vista without an
> antivirus.
>
> But everytime that Vista starts, Windows Defender blocks it and I must
> manually select "run blocked program".
>
> Is there a way to autorize it for ever ? Thanks,
>
> Windows Vista does not allow kernal modification henceforth why your security programs do not work. All 3rd party software is having issues with obatining access to the code for Vista! That means that the majority of 3rd party software relying on the Kernal of Vista will not work until the software developers come up with a work around for the restriction of Kernal access! Good Luck... In other words no micromanagement allowed!