This has already been reported before http://forum.pspad.com/read.php?4,46504,47661#msg-47661, but I noticed that my build (4.5.4 (2356)) does not contain the manifest entries for UAC-awareness (anymore?). I've been wondering why? (is it maybe because of http://forum.pspad.com/read.php?4,48095,48095#msg-48095?
Anyway, editing files that are in protected folders like "c:\program files" etc leads to nasty behind-the-scenes juggling of files where you seemingly succeeded modifying a file from PSPad's point of view, where in reality the modified version gets stored at <systemdrive>:\users\<your_user>\appdata\local\virtualstore\<path_as_before>. If an UAC-aware, elevated app now reads in and processes this file, it gets the old version as the original file never has been touched by PSPad in the first place. Moreover, once you start double-checking why changes to -say, an ini file- don't seem to have any effect at all, and again open it in PsPad, you get the modified version, as the UAC-unaware PSPad gets to see the virtualized version. Of course you'll never suspect your text editor being the culprit unless you open the file in an UAC-aware one like MS own Editor... Any chances you guys can fix the manifest declaration? Of course, the manifest is just one step towards a "true" UAC-aware application (see the guide at http://msdn.microsoft.com/en-us/library/bb756929.aspx. Also, I'm not sure whether the manifest declaration alone would fully fix the issue when PsPad gets started from the shell (via context menu), which I believe is mostly the case. -- <http://forum.pspad.com/read.php?4,51494,51494> PSPad freeware editor http://www.pspad.com
