Notepad++ 8.8.8 release

donho

@Lukas-Mayr said in Notepad++ 8.8.8 release:

@PeterJones
Parsing the installer with Orca shows no proberties that could be changed into that direction and also replacing the .exe options in .msi writing doesn’t seem to work either.

i.e. instead of /noUpdater a noUpdater=“1”

OK, I will add this option for the next release.

donho

@Lukas-Mayr
Please check if it’s what you need:
https://download.notepad-plus-plus.org/MISC/npp.Installer.x64.msi

Command line: msiexec /i Notepad++.msi NOUPDATER=1

donho

FYI: The auto-update has been triggered for v8.8.8.

Lukas Mayr

@donho said in Notepad++ 8.8.8 release:

Please check if it’s what you need:
https://download.notepad-plus-plus.org/MISC/npp.Installer.x64.msi

Command line: msiexec /i Notepad++.msi NOUPDATER=1

that seems to do the trick 👍

i will roll it out for about 100 Users - if i get any feedback, i will relay that, otherwise thank you very much!

Garrett

I am switching to the msi installer from exe installer for our deployments. I have noticed in my initial testing that using the .msi installer does not remove the previous version (.exe installed) on the device.

I have also noticed that there are two separate .msi installers for v8.8.8 with different Product Codes https://github.com/notepad-plus-plus/notepad-plus-plus/releases/download/v8.8.8/npp.8.8.8.Installer.x64.msi and https://download.notepad-plus-plus.org/MISC/npp.Installer.x64.msi

Do I need to add to my PSADT scripts to uninstall previous versions in my Pre-Install block, or should the .msi (as intended) remove earlier versions? In addition will the duplicate installers be consolidated to a new single Product Code in an updated installer?

Thank you for giving us the .msi for enterprise deployments, I’m looking forward to using them over the .exe installers.

Garrett

@Garrett I have added the following in my Pre-Install block

<Perform Pre-Installation tasks here>

$uninstallPath = Join-Path $env:ProgramFiles “Notepad++\uninstall.exe”

if (Test-Path $uninstallPath) {
Write-Host “Uninstaller found. Running silent uninstall…”
Start-ADTProcess -FilePath $uninstallPath -ArgumentList ‘/S’
}
else {
Write-Host “Uninstaller not found. Skipping uninstall.”
}

Daniel Richter

@Garrett
Which deployment software do you use?

Garrett

@Daniel-Richter I am using PSADT 4.1.7 for packaging and deploying with both Intune & MECM

Sinsearach

Greetings,
Just updated after quite a long while, and on Windows 10, TextFX (NppTextFX2) plugin will not work (appear at all), whether installed manually or through plugin admin, with this latest version, neither on 32 nor 64 bit versions. Both portable, not installed through setup.

Yes I ran as admin.

Had to revert back to v8.1.5, works fine there.

-Laters

PeterJones

@Sinsearach said in Notepad++ 8.8.8 release:

Just updated after quite a long while, and on Windows 10, TextFX (NppTextFX2) plugin will not work …

It might be that it was caused specifically by Notepad++ v8.8.8… but more likely, it’s a setup issue on your side, or a bug in the plugin as it relates to your setup and v8.8.8.

But there needs to be some debug work, so I will duplicate your post to a separate Topic in Help Wanted (I will crosslink this post ~~to there in a few minutes~~: new post here), and the discussion can happen there, until we can prove whether it’s really a bug/regression in v8.8.8, or whether it’s just something that should be handled by fixing something on your side, or by fixing something in the plugin itself.

Update: Wait, you said “after quite a long while”, so that means it wasn’t just v8.8.8 that you had the problem with. Please only use the “Notepad++ x.y.z release” announcement topics for changes between immediately-previous version and this version. For example, this v8.8.8 topic should only mention regressions that changed behavior between v8.8.7 and v8.8.8. Any other problems you find when you jump from v8.1.5 (for example) to v8.8.8 should go in “help wanted”, and if can be confirmed as a bug in Notepad++, we will direct you on where to put in the official bug report. But it’s not an immediate regression with v8.8.8, so doesn’t belong in this discussion.