Re: ça n'a pas changé

File System and Registry Virtualization
In Windows Vista, many legacy applications that were not designed to support standard user accounts can run without modification, using the built-in file/registry virtualization feature. File/registry virtualization gives an application its own "virtualized" view of a resource it is attempting to change using a copy-on-write strategy. For example, when the application attempts to write to a file in the program files directory, Windows Vista gives the application its own private copy of the file in the user's profile so the application will function properly.

Virtualization also provides logging by default for applications that attempt to write to protected areas.

Microsoft's early testing of legacy applications running in standard user mode using file/registry virtualization under Windows Vista has shown promising application compatibility results. Although virtualization allows the majority of legacy applications to run, it is a short-term measure—not a long-term solution. Not only can a lack of compliance with User Account Control affect the security of an application, but it can also reduce the application's performance, require additional end-user training, and cause application conflicts.

Interessant mais ca ne passera pas partout.
Si l'application ecris dans %windir%/system32 et verifie si le fichier est bien avec un truc dans ce genre:

exec("cmd.exe /k if NOT EXIST %windir%/system32/file THAN %systemdrive%/program file/legacy app/sanity-check.exe /failure ELSE exit")

UAC va rediriger cmd.exe dans le repertoire virtualisé ou laissé passé ?

ps: Oui j'ai déjà vu des applications (hyper spécifique) pourrite comme ça ...