Pat said:Installing Apps,Running some apps,changing any minor system setting (network etc.),copying files at times etc. etc.Its a PITA! I have no doubt that disabling UAC is the first thing most home users would be doing on Vista!
Hold on - so according to you anyone should be allowed to install s/w on a computer, whether they are admin or not? Then you cry about spyware. I have no respect for that complaint, especially since half of the people who say that then say Ubuntu is wonderful (UAC is pretty much like sudo for the most part, and apt-get requires sudo).
Copying files - only if to restricted locations. Once again, this prevents malware from overwriting your boot sector and/or system files. SP1 now fixes the one (and very big) problem that was there - that of multiple prompts for the same action.
Running some apps - here I partly agree with you. However, I argue that only a badly written app requires system privileges for the most part, or a system utility. System utlities SHOULD require admin passwords (and they always have - if you ran as a non-admin in XP, try shutting down your antivirus and see if you can manage that). Other apps should not require system privileges - for example, when I first installed Vista, WinRAR used to throw UAC prompts - now it doesn't. I don't know what got fixed (Vista and/or WinRAR) but everything is fine now.
And most home users are not going to be disabling UAC. Largely because they have no idea what UAC is (even if it does throw prompts at them) and because they wouldn't know how. It is more likely that some false geek goes and does it for them.
UAC does have a problem, and that is a security issue in which it wrongly identifies programs as being trusted - and IIRC, STILL asks you for a password (which is still a fallback, though seeing the "trusted" rating you may go ahead and give it the password when you shouldn't).
I love the fact that UAC finally allows proper non-admin running. I tried that on XP - too many apps didn't work. Vista does a better job of that (perhaps thanks to file and registry virtualization), and UAC means that you don't have to switch to an admin account when you want to install something (run as admin didn't always work in XP, it does now). This is very useful - I know longer have to worry about my parents infecting the machine by downloading something by mistake or visiting the wrong webpage. The moment they see a password prompt they press cancel. They only proceed with the password prompt if I tell them to - and I tell them to do that if I need them to install some app or the other. Makes my life as a remote admin with non-login access much easier. My previous XP computer was full of spyware once I left the house because my cousin downloaded all sorts of crap (smileys!!!!!). Now she has her own account, and it is non-privileged...
I actually did have what I think is a genuine problem with UAC - I was writing an app that required access to performance counters and it didn't run unless it was run as administrator. I think that is silly. It is much too restrictive, and sometimes I think I should send that complaint in..