Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7093391 By: msec
There's a fairly straightforward workaround: in the same folder as patch.exe, add a file named 'patch.exe.manifest' which has the following content: <pre> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2"> <security> <requestedPrivileges> <requestedExecutionLevel level="asInvoker"/> </requestedPrivileges> </security> </trustInfo> </assembly> </pre> Two things need to be borne in mind: you need elevated privileges to create this file in the right place (otherwise it ends up in your personal virtual store, which is not the same folder); also, check there is no 'run in compatibility mode' setting on patch.exe before you create the manifest. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=74807 ------------------------------------------------------------------------------ _______________________________________________ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users