One more bad thing in Windows 7 (installing under limited user accounts)

[baja_yu]

I've been testing an application and it's installer under various scenarios to make sure everything is running smoothly, regardless of user account type (standard/admin) or wether UAC is turned off or on.

The setup is this, Windows 7, two user accounts, let's say main (admin one) called TestA and a standard user account called TestS. Both accounts have no password set.

Installing on the admin account works ok regardless of UAC state (on/off), but... and this is a BIG but (which I like and I can't deny), this is how it goes on the standard account.

Case 1 - standard user account (TestS) - UAC on: started installer, got a modern looking Run As prompt, TestA account selected (showing it's picture even), asking for password. Since it's not set, clicked ok, process got elevated and the installer ran fine.

Case 2 - standard user account (TestS) - UAC off: started installer, got a classic, XP looking Run As screen. Instead of one field (to type password) there are now two (username and password) with "Administrator" pre-entered. Clicking OK, or entering TestA and clicking OK shows an error "...blank passwords are not allowd" but the account doesn't have one. So you can't install. Setting a password and entering it will work.

The conclusion is that when all security features (UAC and a password) are set, you can install, but when none are set, you can't. Seems logical, right?