The problem that I'm having is that I'm unable to get the command line
secpol.msc program to run. I'm logged on as admin and it still tells me it
cannot find the program. Something to that effect.
I can still navigate in control panel to run the app but why does it not run
from the run box or cmd box?
Have I messed up my ENV variables and it is just not in the path statement
or what?
Any clues....Anybody?
Thanks in advance for a reply, Sid

To perform the following procedure, you must be able to log on with or
provide the credentials of a member of the localAdministrators group.

To enable or disable application setup detection in UAC
Click Start, click All Programs, click Accessories, click Run, type
secpol.msc in the Open box, and then click OK.



From the Local Security Policy tree, click Local Policies, and then
double-click Security Options.

Scroll down and double-click User Account Control: Detect application
installations and prompt for elevation.

Choose the appropriate setting:

To enable application setup detection, click Enabled.

To disable application setup detection, click Disabled.

Click OK.

Close the Local Security Policy window.


--
Sid
"The force be with you"

Sid wrote:

> The problem that I'm having is that I'm unable to get the command line
> secpol.msc program to run. I'm logged on as admin and it still tells me it
> cannot find the program. Something to that effect.
> I can still navigate in control panel to run the app but why does it not run
> from the run box or cmd box?
> Have I messed up my ENV variables and it is just not in the path statement
> or what?
> Any clues....Anybody?

Do you have one of the Home versions? Just like XP Home, Vista Home
doesn't have secpol.msc or gpedit.msc.

If you're trying to turn off UAC, here's another way from MVP John
Barnett that doesn't require secpol.msc.

http://vistasupport.mvps.org/turn_of...nt_control.htm


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Does your path include %SystemRoot%\system32 ? That's where secpol.msc
resides.

The initial path statement in Vista should include
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem


"Sid" <Sid@xxxxxx> wrote in message
news:A0561AB7-917D-43AB-BC1D-CC51E0D32D77@xxxxxx

> The problem that I'm having is that I'm unable to get the command line
> secpol.msc program to run. I'm logged on as admin and it still tells me it
> cannot find the program. Something to that effect.
> I can still navigate in control panel to run the app but why does it not
> run
> from the run box or cmd box?
> Have I messed up my ENV variables and it is just not in the path statement
> or what?
> Any clues....Anybody?
> Thanks in advance for a reply, Sid
>
> To perform the following procedure, you must be able to log on with or
> provide the credentials of a member of the localAdministrators group.
>
> To enable or disable application setup detection in UAC
> Click Start, click All Programs, click Accessories, click Run, type
> secpol.msc in the Open box, and then click OK.
>
> From the Local Security Policy tree, click Local Policies, and then
> double-click Security Options.
>
> Scroll down and double-click User Account Control: Detect application
> installations and prompt for elevation.
>
> Choose the appropriate setting:
>
> To enable application setup detection, click Enabled.
>
> To disable application setup detection, click Disabled.
>
> Click OK.
>
> Close the Local Security Policy window.
>
>
> --
> Sid
> "The force be with you"

I don't believe it's available in Vista Home versions...


"GTS" <x@xxxxxx> wrote in message
news:u$YQKCxFIHA.2268@xxxxxx

> Does your path include %SystemRoot%\system32 ? That's where secpol.msc
> resides.
>
> The initial path statement in Vista should include
> %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
>
>
> "Sid" <Sid@xxxxxx> wrote in message
> news:A0561AB7-917D-43AB-BC1D-CC51E0D32D77@xxxxxx

>> The problem that I'm having is that I'm unable to get the command line
>> secpol.msc program to run. I'm logged on as admin and it still tells me
>> it
>> cannot find the program. Something to that effect.
>> I can still navigate in control panel to run the app but why does it not
>> run
>> from the run box or cmd box?
>> Have I messed up my ENV variables and it is just not in the path
>> statement
>> or what?
>> Any clues....Anybody?
>> Thanks in advance for a reply, Sid
>>
>> To perform the following procedure, you must be able to log on with or
>> provide the credentials of a member of the localAdministrators group.
>>
>> To enable or disable application setup detection in UAC
>> Click Start, click All Programs, click Accessories, click Run, type
>> secpol.msc in the Open box, and then click OK.
>>
>> From the Local Security Policy tree, click Local Policies, and then
>> double-click Security Options.
>>
>> Scroll down and double-click User Account Control: Detect application
>> installations and prompt for elevation.
>>
>> Choose the appropriate setting:
>>
>> To enable application setup detection, click Enabled.
>>
>> To disable application setup detection, click Disabled.
>>
>> Click OK.
>>
>> Close the Local Security Policy window.
>>
>>
>> --
>> Sid
>> "The force be with you"

>

That's correct. However, the fact that the poster says he can run secpol
from from Control Panel (admin tools) indicates that he is not using a Home
version.
--

"Dave" <dave@xxxxxx> wrote in message
news:uEoEsOyFIHA.748@xxxxxx

>I don't believe it's available in Vista Home versions...
>
>
> "GTS" <x@xxxxxx> wrote in message
> news:u$YQKCxFIHA.2268@xxxxxx

>> Does your path include %SystemRoot%\system32 ? That's where secpol.msc
>> resides.
>>
>> The initial path statement in Vista should include
>> %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
>>
>>
>> "Sid" <Sid@xxxxxx> wrote in message
>> news:A0561AB7-917D-43AB-BC1D-CC51E0D32D77@xxxxxx

>>> The problem that I'm having is that I'm unable to get the command line
>>> secpol.msc program to run. I'm logged on as admin and it still tells me
>>> it
>>> cannot find the program. Something to that effect.
>>> I can still navigate in control panel to run the app but why does it not
>>> run