Poorly programmed isn't the same as crapware. In this case, it's about not following design guidelines that have been around since, oh I dunno, NT4 or so. It's not about "satisfying the UAC program", stuff throwing UAC prompts simply wouldn't have worked on XP (or win200 or NT4 or anything non-Win9x) when not running with an account with administrative privileges.
And for the case of Everything, it's perfectly fixable: as mentioned before, the program needs to be split into a service running with admin privileges that have access to the MFT, and a GUI frontend that runs privilege-less and communicates with the service. Presto, problem solved. It's been the proper way to handle this kind of thing at least NT4 (I don't have experience with pre-NT4.)
ACDSee breaking probably has nothing to do with UAC but everything to do with poor programming practices... hardcoding locations, doing tings in nonstandard ways, whatever.
What I don't understand is why MS didn't simply make the choice of making all new user accounts default to user level security (and they could have done that back from Windows XP). Most of these issues would have been ironed out long ago. Seems to me that they are too lily livered to do the write thing so they introduce UAC as a kludge to fix something that isn't basically broken - just a bad choice.
-Carol Haynes
I agree fully that MS should have made the default user non-admin a long time ago - preferably at the time of Win2000, and definitely no later than WinXP when people
really started migrating from Win9x. Also, WinMe should never have seen the light of day, Win98 should have been the last 9x Windows.
I find UAC to be a pretty nice system, though - the alternative would be having to run applications in admin mode and always supplying an admin password in order to be able to do so...