You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NotepadNext-v0.9 opened the binary patch file in text mode instead of installing it after downloading the update patch using automatic updates on Windows.
I re-downloaded and reinstalled NotepadNext-v0.9 can reproduce the problem stably.
The logs don't seem to give any more useful information. Further debugging is required.
Try more versions.
The problem didn't start with v0.9, it was present in the previous one or two releases as well,
and the approximate range of releases in which the regression was introduced needs to be determined.
Use source build version
with debug mode
Steps to Reproduce
Install NotepadNext using Installer
(For All user, but not use default install path)
Open NotepadNext, waiting for update popup or click check update
Click Yes to download update, then click Yes to install update
Unfortunately, there was a bug in the QSimpleUpdater package which did not properly rename the downloaded file correctly and Windows tries to "open" the bin file rather than execute it. This has been fixed now (#710) by simply updating that 3rd party library. I'll pin this issue for anyone else running across this.
Note to future readers
If you are running v0.9 you will have to manually update Notepad Next this time. This is fixed for future releases. Apologies for any inconveniences.
Operating System and Version
Win11 24H2
Distribution
NotepadNext-v0.9-Installer.exe
Description
NotepadNext-v0.9 opened the binary patch file in text mode instead of installing it after downloading the update patch using automatic updates on Windows.
I re-downloaded and reinstalled NotepadNext-v0.9 can reproduce the problem stably.
The logs don't seem to give any more useful information. Further debugging is required.
The problem didn't start with v0.9, it was present in the previous one or two releases as well,
and the approximate range of releases in which the regression was introduced needs to be determined.
Steps to Reproduce
(For All user, but not use default install path)
check update
Yes
to download update, then clickYes
to install updateQSUUpdate.bin
as binary fileAdditional Details
screenshots:

logs:
Check for update
Install / Open QSU_Update.bin
The text was updated successfully, but these errors were encountered: