Originally posted by: mooseracing
Originally posted by: SilentRunning
Originally posted by: Smilin
I still find this whole thread very ironic.
The OP is trying to disable UAC because it's bugging him when it's stopping some misbehaving or malicious app. He WANTS the misbehaving or malicous app to run.
Boggles my mind. There are a lot of competent people on this forum and only a few on this thread have pointed this out. What's going on?
OP: You want Microsoft to "let admins be admins"? You sir should not be an admin at all.
You forgot to mention that they will be back claiming Vista "sucks" as the malware and viruses overtake their systems creating unstable behavior.
I haven't run into a single problem with UAC disable since beta testing Vista.
People just need to understand what they are installing and clickin gon its that simple. You can run as the admin account (not jsut admin privealages) and not have a problem.
I've had programs that refuse to work correctly until actually unlocking the admin account and installing them through that.
People just take no responsibility from their actions, then sue the other for damages. Ridiculous.
That's the absolute biggest mistake when writing any kind of code/software. Never ever assume anything about the user, what they will
try to do with the code, or what inputs they will give to the code. Think of UAC like a child proof pill bottle; it's very easy to deal with, yet it prevents a large amount of problems.
IMO, any OS that is accessing information and systems in the public domain
needs to have a security policy that prevents spyware, viruses, and other general OS exploits from happening built into the OS.
Microsoft's problem is that since the beginning of their OS's they have not followed that idea, and now it's stuck in everyones head that it's okay to use a computer for daily tasks as an administrator to the machine. At least they have started moving in the right direction
The other problem with Microsoft's OS's are the software writers for 3rd party programs. Many programs simply require administrative privileges because they are poorly written. It's a lot easier to force a user to run the program in Admin mode so that it can write that temporary file to C:\TEMP instead of fixing their code and doing things the proper way. So if more software was written properly the 'headache' of UAC would be a lot less. I could go on and on about how poorly some software is written but I won't!
Back to your post, I agree that people should take responsibility for their actions in an OS, but until the average user understands how an Operating System really works they won't even understand what they should be taking responsibility for! Since that level of education will never happen, there needs to be another way to protect the computer from it's user.