Since 1.19.414 also has this issue, that means the minor change I made in the installer didn't break Windows 11 support. It just didn't work to begin with... I will try digging around to see whether I can find something about NSIS installers that Windows 11 doesn't like.
Are you able to try running the installer from an elevated command prompt and tell me whether it outputs an error message?
I will also see whether I can setup a Windows 11 dev VM and duplicate the issue.