> And those who set up Windows with limited user accounts often find that their non-Microsoft apps break.
Generally speaking:
1. Install and initially configure all applications as Administrator.
2. Run the applications as a normal (limited) user.
3. Do updates and system-wide configuration changes only as Administrator.
Most applications will play nice, with the above.
Not all -- InstallShield still requires that the user be at least a member of the "Administrators" group; prior to 2008 the user could only be The Administrator. Ridiculous!!
The problems are multiple. Windows used to work on the assumption that everybody runs admin for apps, so developers made their software along those lines. The infamous UAC popping up all the time was because apps were used to having admin, and continuously needed to do admin stuff to run. Many of the Windows problems are with legacy, and this is a prime example.
A modern, well-written app under Win7 will run just fine as a very limited user, and IIRC you can install with just having to type in the admin password as on a Mac.
But not all apps require admin. There is an account-level install method for applications that cannot make any system changes, just installs the app in the user’s profile folder.