User Account Control: Password Required?

Thanks BarMan... From what I briefly skimmed in that article, the main reason to use a standard account is so that when you attempt a process which requires administrative access, you're confronted by a password requirement.

Well, that is exactly what I've done to my account. Instead of being able to launch an elevated command prompt by just a right click and a "Yes", now I have to enter a password in order to open the window. In other words, my administrator account now functions exactly like a standard account, except without the headaches that I somehow ran into.

If my standard account worked properly I would just use that, as it can still perform all of the administrative functions, you just need a password. But, since it doesn't, I've converted my admin account to function like a standard account.

EDIT: Another good security tip for user accounts.
Force users to log in with both the username and password: Log On with User Name and Password
Force users to press ctrl-alt-dlt to log in: Secure Logon - Press CTRL + ALT + DELETE to log on

One problem with the correct operation of the UAC is the fact that not all applications are written correctly to take advantage of it.

Due to the long run of XP some developers simply assume that the user is an administrator, and code accordingly, without performing the required checks.

Although win7 has certain traps in place for this type of code there are so many variations that it cannot catch them all. This is what causes the occasional Run as administrator catch-all prompt.

As win7 and UAC matures hopefully more programs will be updated to comply with the current procedures :)