let me get this straight: You are worried that an user who has the credentials of an admin-user, could expose data of other users on the same pc? Hmm, I *think* that user can do that anyway.
I think it's more dangerous to start a newly installed application as an admin user. Why? The standard-user thinks he has not the right or power to do any real damage to the OS. But the first "playing around" with a new application could possibly kill of the OS or can do real damage because it's the enviroment of an admin-user.
From this point of view, the UAC is not much more than a nicer "run as ..." feature. Why can't the "UAC-Service" sense the end of an installation and the first start of the application?
Hi, this video was very interesting. I'm using Vista as a standard user since I got my new notebook and found the UAC-popups annoying in the beginning but since most of the installations are done, it's ok for me.
My proplem with UAC is: When I install an application I have to provide the credentials of an administrator. After doing so, the installer runs as administrator-user.
Why is that? Shouldn't the standard user getting an "admin-token" and run the installation?
The next problem is the little checkbox at the end of the installer saying: "Launch Application now". If this checkbox is set, the first start of the new application runs as admin-user. I did have to configure some software twice because the first time I did
it with the wrong user! That's at least annoying.
Maybe I'm getting this completly wrong but after watching the video I find this behaviour strange.