Vista - found UAC bug in Vista

i have found a bug in Vista related with UAC setting.

there are two ways to turn on UAC setting:
1. from user accounts in Control Panel
2. from windows security center

the first one works well and asks for system restart.
the second one does not.

i used the second one recently and then i logged in as plain user. UAC
setting was not changed and did not work.
i had to solve the problem by using the first way: control panel.

Marco

Are you using the built-in System Administrator when you turn UAC on from
the Security Center?

I did some testing and here's what I found.

If UAC is turned OFF and you turn it back ON from within Security Center,
and you are logged on with the Built-in System Administrator account, you
will not be prompted for a restart although UAC WILL be turned ON for all
user accounts.

I believe this behavior is due to the fact that the "Elevate for
administrator privilege" is turned off, by default on this account in the
Security Policy for the machine.

If you are logged on with any other administrator or standard user account
and turn UAC ON from the Security Center, you will be prompted to reboot as
expected.

If you are logged on with the Built-in System Administrator account and turn
the UAC OFF, you will still be prompted to reboot.

When using the Built-in System Administrator account, you may see some
unexpected behavior since this account uses a completely different set of
permissions than all the other account types.

--

Ronnie Vernon
Microsoft MVP
Windows Shell/User


"Marco Almenta" <marco.almenta@elsendero.es> wrote in message
news:FEEC2CCA-EE84-4F96-87F7-2DDE3B69DA04@microsoft.com...
>i have found a bug in Vista related with UAC setting.
>
> there are two ways to turn on UAC setting:
> 1. from user accounts in Control Panel
> 2. from windows security center
>
> the first one works well and asks for system restart.
> the second one does not.
>
> i used the second one recently and then i logged in as plain user. UAC
> setting was not changed and did not work.
> i had to solve the problem by using the first way: control panel.
>