This patch is no longer necessary with NSIS 2.45 and up
I have posted a patch for NSIS which fixes the issue in the Windows 7 Release Candidate (as well as build 7057 / 7068 / 7077 which were leaked early) where it would trigger a Program Compatibility Assistant warning. Only makensis.exe is altered... just replace it in the NSIS program directory. The updated manifest.p is included so you can build it yourself, too.
NSIS 2.44 Windows 7 Patch 1 by portableapps.sitesunblocked.org
MD5: 596dcf7c786ab4238682c3343f8a0dc2
Details on the bug are posted in this NSIS issue:
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=2725883&gro...
Visit the Community page
our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Thanks for this. Should we recompile the launchers for all of our apps as a more immediate solution than waiting for the new releases to include compatible launchers?
Quamquam omniam nescio, nec nihil scio.
because there is still a lot that can change and then you'd have to do it all again. Windows 7 is early beta so it doesnt affect many people.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
We're already using it for our official releases.
Sometimes, the impossible can become possible, if you're awesome!
So, should this patch make it into the next official NSIS release or will you have to patch it too? I would guess something like this probably will go into the official release right, just waiting for a major release to put it in?
Quamquam omniam nescio, nec nihil scio.
I don't think anything is going to change, since this affects the Release Candidate, something that isn't likely to change any under the hood before RTM. Also, it's not a bug, but a result of improved legacy installer detection in Win7. So again, not something that's going to change.