I keep seeing articls about how to disable UAC like this one:

http://blogs.msdn.com/tims/archive/2...20/763275.aspx

but the instructions do not work for me. when i click start there is
no "Start search bar" anywhere that I can see.

Also I found:

http://technet2.microsoft.com/Window....mspx?mfr=true

which says run secpol.msc from the run menu but when i try this it
does not work either.

I know it is Microsoft policy to hide everything from the user and
make all interfaces a total pain in the backside - but can someone
help me with this stupid one please.

On Thu, 06 Sep 2007 08:45:06 -0700, (E-Mail Removed) wrote:

>I keep seeing articls about how to disable UAC like this one:
>
>http://blogs.msdn.com/tims/archive/2...20/763275.aspx
>
>but the instructions do not work for me. when i click start there is
>no "Start search bar" anywhere that I can see.
>
>Also I found:
>
>http://technet2.microsoft.com/Window....mspx?mfr=true
>
>which says run secpol.msc from the run menu but when i try this it
>does not work either.
>
>I know it is Microsoft policy to hide everything from the user and
>make all interfaces a total pain in the backside - but can someone
>help me with this stupid one please.

Would it really shock you to discover the crap on Microsoft's own web
pages is in error and doesn't always work? The second link above is a
classic example of Microsoft incompetence where they claim you can
elevate an application to ALWAYS run elevated. The truth is it only
works SOMETIMES for SOME applications and only if SOME conditions are
met otherwise it doesn't work.

Expect a barrage of clueless feces throwing fanboy monkeys to claim I
don't know what I'm talking about. They always do because they can't
stand me exposing Vista flaws or that I know the typical fanboy while
pretending to be "expert" in reality knows about as much about
computers as George Bush knows about public speaking without mauling
the English language. Nada.

If you want to turn off UAC do this:

1. Start button
2. Control Panel
3. User Accounts
4. Click where it says turn User Control on and off, then uncheck.

As far as if you should or shouldn't disable UAC, this topic has been
hotly debated up and down the Internet and all over newsgroups like
this one ever since Microsoft dumped this poorly implemented garbage
on unsuspecting users of Windows.

There is no one answer that fits every user. For some it is better to
leave it on, others turn it off because after awhile you just can't
take the constant nag screens.

While the fanboy losers club will try to pretend that UAC nag screens
go away over time after you've installed your applications and Vista
settles down into a normal routine. However that claim like most
things fanboys claim isn't totally true.

How often you need to endure UAC nag screens depends on how you use
your computer. Some older applications because of how they were
written (unsigned drivers is one example) refuse to behave even if you
follow the steps on the Microsoft page linked above to the letter
UNLESS you disable UAC. Otherwise they will just nag, nag, nag. If you
happen to use such an application daily after awhile you may decide it
isn't worth the annoyance since UAC doesn't do anything much other
than nag in the first place. The minor benefits it provides behind the
scenes when surfing for example is easily equaled with a decent
firewall anti virus application which you should have running anyway.

If you set up your user account as a member of the Administrators Group and
want to get rid of the nag screen but not completely turn off UAC go to this
reg key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"ConsentPromptBehaviorAdmin"=dword:00000002
"ConsentPromptBehaviorUser"=dword:00000001
"EnableInstallerDetection"=dword:00000001
"EnableLUA"=dword:00000001
"EnableSecureUIAPaths"=dword:00000001
"EnableVirtualization"=dword:00000001
"PromptOnSecureDesktop"=dword:00000001
"FilterAdministratorToken"=dword:00000000
"LocalAccountTokenFilterPolicy"=dword:00000001

Now set the ConsentPromptBehaviorAdmin value to zero (0) from 2 and the nag
screen should go away.


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I keep seeing articls about how to disable UAC like this one:
>
> http://blogs.msdn.com/tims/archive/2...20/763275.aspx
>
> but the instructions do not work for me. when i click start there is
> no "Start search bar" anywhere that I can see.
>
> Also I found:
>
> http://technet2.microsoft.com/Window....mspx?mfr=true
>
> which says run secpol.msc from the run menu but when i try this it
> does not work either.
>
> I know it is Microsoft policy to hide everything from the user and
> make all interfaces a total pain in the backside - but can someone
> help me with this stupid one please.
>

"Adam Albright" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Thu, 06 Sep 2007 08:45:06 -0700, (E-Mail Removed) wrote:
>
>>I keep seeing articls about how to disable UAC like this one:
>>
>>http://blogs.msdn.com/tims/archive/2...20/763275.aspx
>>
>>but the instructions do not work for me. when i click start there is
>>no "Start search bar" anywhere that I can see.
>>
>>Also I found:
>>
>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>
>>which says run secpol.msc from the run menu but when i try this it
>>does not work either.
>>
>>I know it is Microsoft policy to hide everything from the user and
>>make all interfaces a total pain in the backside - but can someone
>>help me with this stupid one please.
>
> Would it really shock you to discover the crap on Microsoft's own web
> pages is in error and doesn't always work? The second link above is a
> classic example of Microsoft incompetence where they claim you can
> elevate an application to ALWAYS run elevated. The truth is it only
> works SOMETIMES for SOME applications and only if SOME conditions are
> met otherwise it doesn't work.

What is there appears to be correct (and may be useful to some users YMMV).
I suspect that you misunderstand what part two actually says.

It says that to mark an application to run as admin do this.
It does not say that it makes the application run as admin.

It should make the application prompt for permission to run as admin.. are
you saying that it doesn't?

HTH

On Thu, 6 Sep 2007 19:07:56 +0100, "dennis@home"
<(E-Mail Removed)> wrote:

>
>"Adam Albright" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> On Thu, 06 Sep 2007 08:45:06 -0700, (E-Mail Removed) wrote:
>>
>>>I keep seeing articls about how to disable UAC like this one:
>>>
>>>http://blogs.msdn.com/tims/archive/2...20/763275.aspx
>>>
>>>but the instructions do not work for me. when i click start there is
>>>no "Start search bar" anywhere that I can see.
>>>
>>>Also I found:
>>>
>>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>>
>>>which says run secpol.msc from the run menu but when i try this it
>>>does not work either.
>>>
>>>I know it is Microsoft policy to hide everything from the user and
>>>make all interfaces a total pain in the backside - but can someone
>>>help me with this stupid one please.
>>
>> Would it really shock you to discover the crap on Microsoft's own web
>> pages is in error and doesn't always work? The second link above is a
>> classic example of Microsoft incompetence where they claim you can
>> elevate an application to ALWAYS run elevated. The truth is it only
>> works SOMETIMES for SOME applications and only if SOME conditions are
>> met otherwise it doesn't work.
>
>What is there appears to be correct (and may be useful to some users YMMV).
>I suspect that you misunderstand what part two actually says.
>
>It says that to mark an application to run as admin do this.
>It does not say that it makes the application run as admin.
>
>It should make the application prompt for permission to run as admin.. are
>you saying that it doesn't?

Which is the problem! The Microsoft page IMPLIES if you follow the
steps they outline it will FIX this issue since the subhead is titled:
"Mark an application to ALWAYS RUN elevated"

I don't know, maybe the boys of Redmond need a remedial class in basic
English grammar.

I would infer from the wording on Microsoft's page that if you follow
the steps it lists that an application will ALWAYS RUN elevated, after
all that is what the subhead says! If all it does is force a UAC nag
screen prompting you to ask if you want to run as administrator THAT
is what the subhead should say, but of course if it did, nothing
really is changed, other than substituting one moronic UAC nag screen
for another one.

So I'm trying to get the "benefit" of bringing up a new UAC prompt
when the whole point would be to get RID OF the nag screen completely
once you jump through all those hoops to change how Vista responds by
drilling deep down into Vista's guts. The point being you still have
to click through so totally useless since it just replaces the
original UAC nag screen with another one.

Only Microsoft is stupid enough to think this would be a "solution".

You see it is things like this that separates me from the fanboy
crowd. They blindly accept whatever crap Microsoft comes up with and
at best just shrug their shoulders when they encounter something dumb
like this. I CHALLENGE why Microsoft sometimes does obviously bone
headed things. This is just one of many examples.

"Adam Albright" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Thu, 6 Sep 2007 19:07:56 +0100, "dennis@home"
> <(E-Mail Removed)> wrote:
>
>>
>>"Adam Albright" <(E-Mail Removed)> wrote in message
>>news:(E-Mail Removed)...
>>> On Thu, 06 Sep 2007 08:45:06 -0700, (E-Mail Removed) wrote:
>>>
>>>>I keep seeing articls about how to disable UAC like this one:
>>>>
>>>>http://blogs.msdn.com/tims/archive/2...20/763275.aspx
>>>>
>>>>but the instructions do not work for me. when i click start there is
>>>>no "Start search bar" anywhere that I can see.
>>>>
>>>>Also I found:
>>>>
>>>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>>>
>>>>which says run secpol.msc from the run menu but when i try this it
>>>>does not work either.
>>>>
>>>>I know it is Microsoft policy to hide everything from the user and
>>>>make all interfaces a total pain in the backside - but can someone
>>>>help me with this stupid one please.
>>>
>>> Would it really shock you to discover the crap on Microsoft's own web
>>> pages is in error and doesn't always work? The second link above is a
>>> classic example of Microsoft incompetence where they claim you can
>>> elevate an application to ALWAYS run elevated. The truth is it only
>>> works SOMETIMES for SOME applications and only if SOME conditions are
>>> met otherwise it doesn't work.
>>
>>What is there appears to be correct (and may be useful to some users
>>YMMV).
>>I suspect that you misunderstand what part two actually says.
>>
>>It says that to mark an application to run as admin do this.
>>It does not say that it makes the application run as admin.
>>
>>It should make the application prompt for permission to run as admin.. are
>>you saying that it doesn't?
>
> Which is the problem! The Microsoft page IMPLIES if you follow the
> steps they outline it will FIX this issue since the subhead is titled:
> "Mark an application to ALWAYS RUN elevated"

Lots of programs are marked to run as admin.. but you have to click the uac
prompt first.. are you saying that they don't prompt but still run?

>
> I don't know, maybe the boys of Redmond need a remedial class in basic
> English grammar.
>
> I would infer from the wording on Microsoft's page that if you follow
> the steps it lists that an application will ALWAYS RUN elevated, after
> all that is what the subhead says! If all it does is force a UAC nag
> screen prompting you to ask if you want to run as administrator THAT
> is what the subhead should say, but of course if it did, nothing
> really is changed, other than substituting one moronic UAC nag screen
> for another one.

So you now understand what it says and are being argumentative.

> So I'm trying to get the "benefit" of bringing up a new UAC prompt
> when the whole point would be to get RID OF the nag screen completely
> once you jump through all those hoops to change how Vista responds by
> drilling deep down into Vista's guts. The point being you still have
> to click through so totally useless since it just replaces the
> original UAC nag screen with another one.
>

While I would also like to be able to get rid of the nag on a couple of
programs the fact is that the page is correct.. it is written in English and
does what it says. It is instructions on how to make sure a program always
runs as admin not on how to stop a program nag when you run it as admin.

> Only Microsoft is stupid enough to think this would be a "solution".

It is a solution to the problem.
You want a solution to a different problem but didn't read what it said the
first time.

>
> You see it is things like this that separates me from the fanboy
> crowd. They blindly accept whatever crap Microsoft comes up with and
> at best just shrug their shoulders when they encounter something dumb
> like this. I CHALLENGE why Microsoft sometimes does obviously bone
> headed things. This is just one of many examples.

This is not an example of anything wrong except maybe that you didn't read
it the first time.

>
>

Adam Albright wrote:


_--drunken stupidity deleted---

Look you moron, sober up and re-read the damn thing, ok?
You're awfully stupid for supposed "genius"...hahaha...yeah...right!
Frank

On Thu, 6 Sep 2007 21:37:18 +0100, "dennis@home"
<(E-Mail Removed)> wrote:

>
>"Adam Albright" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> On Thu, 6 Sep 2007 19:07:56 +0100, "dennis@home"
>> <(E-Mail Removed)> wrote:
>>
>>>
>>>"Adam Albright" <(E-Mail Removed)> wrote in message
>>>news:(E-Mail Removed)...
>>>> On Thu, 06 Sep 2007 08:45:06 -0700, (E-Mail Removed) wrote:
>>>>
>>>>>I keep seeing articls about how to disable UAC like this one:
>>>>>
>>>>>http://blogs.msdn.com/tims/archive/2...20/763275.aspx
>>>>>
>>>>>but the instructions do not work for me. when i click start there is
>>>>>no "Start search bar" anywhere that I can see.
>>>>>
>>>>>Also I found:
>>>>>
>>>>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>>>>
>>>>>which says run secpol.msc from the run menu but when i try this it
>>>>>does not work either.
>>>>>
>>>>>I know it is Microsoft policy to hide everything from the user and
>>>>>make all interfaces a total pain in the backside - but can someone
>>>>>help me with this stupid one please.
>>>>
>>>> Would it really shock you to discover the crap on Microsoft's own web
>>>> pages is in error and doesn't always work? The second link above is a
>>>> classic example of Microsoft incompetence where they claim you can
>>>> elevate an application to ALWAYS run elevated. The truth is it only
>>>> works SOMETIMES for SOME applications and only if SOME conditions are
>>>> met otherwise it doesn't work.
>>>
>>>What is there appears to be correct (and may be useful to some users
>>>YMMV).
>>>I suspect that you misunderstand what part two actually says.
>>>
>>>It says that to mark an application to run as admin do this.
>>>It does not say that it makes the application run as admin.
>>>
>>>It should make the application prompt for permission to run as admin.. are
>>>you saying that it doesn't?
>>
>> Which is the problem! The Microsoft page IMPLIES if you follow the
>> steps they outline it will FIX this issue since the subhead is titled:
>> "Mark an application to ALWAYS RUN elevated"
>
>Lots of programs are marked to run as admin.. but you have to click the uac
>prompt first.. are you saying that they don't prompt but still run?
>
>>
>> I don't know, maybe the boys of Redmond need a remedial class in basic
>> English grammar.
>>
>> I would infer from the wording on Microsoft's page that if you follow
>> the steps it lists that an application will ALWAYS RUN elevated, after
>> all that is what the subhead says! If all it does is force a UAC nag
>> screen prompting you to ask if you want to run as administrator THAT
>> is what the subhead should say, but of course if it did, nothing
>> really is changed, other than substituting one moronic UAC nag screen
>> for another one.
>
>So you now understand what it says and are being argumentative.
>
>> So I'm trying to get the "benefit" of bringing up a new UAC prompt
>> when the whole point would be to get RID OF the nag screen completely
>> once you jump through all those hoops to change how Vista responds by
>> drilling deep down into Vista's guts. The point being you still have
>> to click through so totally useless since it just replaces the
>> original UAC nag screen with another one.
>>
>
>While I would also like to be able to get rid of the nag on a couple of
>programs the fact is that the page is correct.. it is written in English and
>does what it says. It is instructions on how to make sure a program always
>runs as admin not on how to stop a program nag when you run it as admin.
>
>> Only Microsoft is stupid enough to think this would be a "solution".
>
>It is a solution to the problem.
>You want a solution to a different problem but didn't read what it said the
>first time.
>
>>
>> You see it is things like this that separates me from the fanboy
>> crowd. They blindly accept whatever crap Microsoft comes up with and
>> at best just shrug their shoulders when they encounter something dumb
>> like this. I CHALLENGE why Microsoft sometimes does obviously bone
>> headed things. This is just one of many examples.
>
>This is not an example of anything wrong except maybe that you didn't read
>it the first time.

Typical fanboy subterfuge. No matter what, you'll go right on
defending Microsoft even when doing so you look ridiculous.

Adam Albright wrote:


>
> Typical fanboy subterfuge. No matter what, you'll go right on
> defending Microsoft even when doing so you look ridiculous.
>
>
You are just one totally clueless as*hole aren't you?
Grow the fukk up and STFU!
Loser.
Frank

"Adam Albright" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

> Typical fanboy subterfuge. No matter what, you'll go right on
> defending Microsoft even when doing so you look ridiculous.
>
>

You have it wrong.
I am only too happy to state that M$ has done things in a way I would not
have done them.
However that has nothing to do with the fact that your statement was based
on your error not someone else's.
Calling me names won't make you correct no matter how many times you say it.