I do run "all" my software from the Program Files, since I appreciate the protection by UAC. I do not want any user program to insert or alter any files in there without telling me beforehand, and being granted permission to do so. All software and scripts properly written for modern Windows environments should be able to handle that. Next to that, PF usually is excluded from the regular backup schemes.

So content should be in Users of any dedicated environment that is included in the backup schemes.

The only issue comes when running scripts which do require to be in the Poser executable environment (I can put them there, say Yes to the UAC message) AND which want to write in their own folder or so (instead of the User...AppData which is dedicated for that) AND don't handle the AppData redirection (as in: not well written for modern Windows). Only when all three hold, Poser cannot be in Program Files and hence is taken out of UAC protection. Old Poser versions themselves fall in this category as well. So does all (other) kind of software that wants to write in its own folder and does not adhere the Windows standards. This usually happens with some OpenSource where Linux code is translated into a Windows executable.

Any deviation from this is fine, for people who really know what they're up to. Novices, especially in PC / Windows usage, should not be encouraged to deviate. From performing professional systems maintenance on a regular basis I can assure you that the Biggest Bug sits between the chair and the keyboard, not behind the screen. Me myself included. It's that bug which is not captured by scanners, and that UAC is protecting us from. Help it to help you.

Just my opinion.

- - - - - 

Usually I'm wrong. But to be effective and efficient, I don't need to be correct or accurate.

visit www.aRtBeeWeb.nl (works) or Missing Manuals (tutorials & reviews) - both need an update though