For instance, any program that attempts
to write files to the Program Files folder (even its own application
folder) will be denied access; this is why lots of older applications can??™t
save their settings on Vista, and some programs can??™t start up or even be
installed. And unless the software is UAC-aware, it won??™t attempt to
???elevate??? itself to the administrator level, and you??™ll never see the UAC
prompt; Windows just denies it. In short, you won??™t know why the program
doesn??™t work.
It??™s annoying. (OK, this one should be first, but that just seemed a bit selfserving.)
How many times today have you sat and watched your screen
go black while you waited...and waited...for the UAC prompt to
appear? And have you noticed that some features require two UAC
prompts: one that warns you that you??™re about to be asked for your permission,
and the other that actually makes the request? Couldn??™t
Microsoft have found a less cumbersome way to do this, such as a single
window that elevates the current session to administrator status for,
say, the next 20 minutes?
It??™s easily defeated. The UAC feature can be disabled with a single setting;
it??™s only a matter of time before some hacker figures out how to do this
without you knowing about it. And if you install software that registers
a Windows service (managed with services.msc), that service could be
used to carry out administrator-level requests by any program, even one
run under the lowly standard user account.
Pages:
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672