Linked by Thom Holwerda on Thu 22nd Oct 2009 21:53 UTC
Thread beginning with comment 390629
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2005-07-06
Which are exactly the ONLY use cases for UAC, too.
True, but MS failed to separate the user completely from the underlying system. E.g in Vista there was a mix of user files and global files on the desktop. While UAC responded correctly to actions which required elevated privileges, the context in which these prompts occured were illogical.
When I'm messing about on my own desktop or in my own user folder, I don't want to see privilege escalation prompts. What is in my account, should be my files with permissions set to my privilege level.
Vista's UAC was right on the money in the need for privelege escalation for certain actions, but Vista failed to cleanly separate the users own environment from the system. Which resulted in vexing prompts which seemed to make no sense.