J
John A Grandy
How to turn off User Account Control ?
The endless prompts are driving me batty ...
The endless prompts are driving me batty ...
John said:How to turn off User Account Control ?
The endless prompts are driving me batty ...
John A Grandy said:How to turn off User Account Control ?
The endless prompts are driving me batty ...
John Barnett MVP said:See this link from my website:
http://www.winuser.co.uk/windows_vista_faq/08_turn_off_user_account_control.html
John Barnett MVP said:I have simply answered the OP's specific question which was how to turn UAC
off. As far as the OP is concerned the prompts are 'driving him batty.' If
there was a specific problem I would imagine that the OP would have pointed
that out, in which case we could have elaborated a little more.
While I agree, Yes we could have asked 'what is your specific problem' but
I have found that, in many cases, a reply to ones specific questioning
isn't always forthcoming. We spend a lot of time answering questions, not
only on this newsgroup, but many others, and although most posts answered
by me are flagged I don't always have the time to keep going back over old
posts to see if someone has answered my specific question.
Your own signature line says it all. We can only answer the question posed
by the poster, if all the information isn't there we can only give an
'approximate' answer and hope that that solves the problem. We certainly
are not infallible, but we also do not get paid for our contributions to
users problems and, in the end, we do have to juggle between a full time
job and voluntary support technicians. We are not super human, we can't
read minds, all we can do is answer the original question posed.
Hank J. said:Then "Gordon" the nanny probably pisses you off a lot.
Gordon said:Should we not be finding out why the OP is getting endless prompts rather
than just showing him how to turn UAC off?
--
Asking a question?
Please tell us the version of the application you are asking about,
your OS, Service Pack level
and the FULL contents of any error message(s)
Mike Hall - MVP said:UAC is a love/hate function with no grey area in-between. I have it turned
OFF..
DonQ said:IIRC, not too long ago you were saying that anyone who ran with UAC
off was part of the rabble that was responsible for all the malware
and virus infestations world wide.
Somehow Mike escaped that, hmm?
Jack the Ripper said:Mark said:How did we ever live without UAC?
If you didn't have problems with malware before UAC, you probably don't
need
UAC now.
With any other detection scheme, all those prompts would be called "false
positives" and leads to ignoring the prompt.
In that sense only, UAC is garbage.
Is it protecting me? Not unless you actually pay attention to all those
prompts and recognize who started the process.
Nothing beats safe hex.
You are wrong, and with UAC on one is practicing safehex.
Saucy said:Justin wrote:
Jack the Ripper wrote:
Justin wrote:
Jack the Ripper wrote:
+Bob+ wrote:
On Sun, 15 Feb 2009 15:43:31 -0500, Jack the Ripper
<[email protected]>
wrote:
Nothing is bulletproof, but one doesn't see a lot of posts by
Vista users about virus or malware issues, not like you see on
XP.
No, but you do see a lot of posts about how UAC sucks. Good
idea, bad
implementation.
It's the posts of the ignorant. I would rather have it enabled
so that I am not on the Internet with full admin rights, like
the previous versions of the NT based O/S(s,) which are open by
default O/S(s) and wide-open to attack/compromise by default.
Is that so hard for you or anyone else to understand?
As long as you're not logged on as admin you should be fine. At
most I keep users at Power User rights.
While I understand running as admin is unsafe, simply having the
account enabled is not a security risk.
I am going to try to explain this again. The out of the box admin
account on Vista that is given to a user or any subsequent admin
account that is created on Vista with UAC enabled is NOT a
full-rights-admin account. It's only a Standard user account,
which must be escalated to a use the full-adminrights token to do
anything requiring admin-full-rights as an administrator.
I get it.
I don't need any escalation to admin. The problem is, what if
there's some malware. Some malware named "winenhancer." The user
sees the UAC prompt "Winenhancer must access the internet!" and the
user clicks on yes.
So UAC only works when the user knows everything about the PC,
which is unrealistic for a standard dumb user whose job is to type
out proposals and reports.
Oh, I get it. It's not the responsibility of the dumb user to know
what he or she is dumbly clicking on as they point and click. It's
their responsibly to know the situation, but they don't and most
never will.
However, network admins take that responsibly for this type of
worker by using a network proxy that only allows the users to go to
approved sites closing the attack vector and mitigating such damage,
as its their responsibility to protect company's interest and not
some office clerk, lock them down.
Just like with Linux which has the same kind of an approval process
within its O/S, they point, click, approve and it's all bets are
off. But with UAC enabled when one does this, the damages are
mitigated to a certain degree as UAC protects critical areas and
also not allowing the malware to continuously run under the context
of the user-admin full-rights access token, to spread damage.
But rather with UAC enabled, the compromise runs under the context
of the admin's Standard user token, because admin user on Vista is
returned to using that token upon privileged escalation completion,
and it's a limit rights token, which mitigates/limits damage.
Like I said, nothing is bulletproof not even god's O/S Linux, but
UAC on the MS platform is better than have nothing at all, which is
the case in fact with the previous versions of the NT based O/S
platform, open by default O/S(s), to help protect the O/S.
Real time scanning by (even free) third party programs provides (in
many cases) superior protection with less annoyance.
So why put something in the OS that just pisses many people off and
is (by MS admission) made irritating on purpose?
Didn't he just explain it to you? Re-read his post:
"But rather with UAC enabled, the compromise runs under the context
of the admin's Standard user token, because admin user on Vista is
returned to using that token upon privileged escalation completion,
and it's a limit rights token, which mitigates/limits damage."
Combining secutity features such as UAC and real time scanning makes
systems more difficult to compromise both directly and indirectly
[say, by social engineering].
EXCELLENT!
Mark said:Well, you missed it completely.
The point is not what an AV or Firewall does, it's that UAC produces too
many false positive responses to be considered anything but a nuisance.
I believe that in a company environment where standard setups are the
only allowed software, you would hardly or never see the prompts. That's
not me. I test software, restoring backups between every test to revert
back to a "standard" machine. So, I see the prompts 20 to 30 times a
day. And, yes, I just click Continue since I already know what is
driving the prompt.
I don't turn UAC off, because it would invalidate the testing and it
tends to cause other errors with permissions during installation of
files when turned off and I have to know what the customer is going to
run into as they would experience it.
Yes, I typically operate as an admin over 50% of the time since I am not
part of a greater network with a bunch of people who would install
garbage for me if I didn't right the rules to block it. And, despite
this, I still don't get malware. I do use an AV, Firewall, Router and
occasionally scan for the garbage, but seldom find anything more than
"spyware" cookies. (The "more" is still classified as spyware, not
malware.)
Jack the Ripper said:They are NOT false positive responses. Whatever you are trying to do
requires escalated privileges to use the user-admin account's full- rights
access token to perform the task or allow a program to run that needs
full-admin-rights to execute, with UAC enabled.