I was wondering if it was easy/worthwhile adding 64-bit (x64) support to to Notepad++ similar to what you've done with portable Firefox.
I'm asking because the latest 7.3.3 update to Notepad++ doesn't work on my 64-bit Windows 10 OS machine.
Notepad++ 7.3.3 runs fine on my 32-bit Windows 10 OS laptop.
On my 64-bit Desktop, Notepad++ 7.3.3 fails start due to issues with the SciLexer.dll certificate.
Below are the Windows 10 (x64) warning messages about the SciLexer.dll certificate problem when I try to start Notepad++ 7.3.3
http://imgur.com/jJKNU9l
http://imgur.com/l8AdVjd
I downloaded the 64-bit Notepad++ 7.3.3 x64 portable from the Notepad++ homepage and it works fine on my 64-bit OS machine.
I reverted back to the prior Notepad++ 7.3.2 version from sourceforge: https://sourceforge.net/projects/portableapps/files/Notepad%2B%2B%20Port... and everything works great again on both the x86 and x64 machines.
I haven't seen anyone else discussing this in the forums, so it might be some problem with my x64 machine... but I don't think so, since it ran the x64 version of Notepad++ just fine!
Thanks!
Visit the Community page
Join 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
Notepad++ 7.3.3 32-bit works fine on 64-bit machines. Notepad++ does, however, add a specific certificate check to that file as it is vulnerable to replacement as indicated in the recent wikileaks vault7 cia dump. As Notepad++ starts up, it checks the certificate of that file to ensure it is valid. If it is not, you will see that error. The file included with Notepad++ Portable 7.3.3 is the correct file with the correct certificate and will run fine on a 64-bit version of Windows 10. If it is not running on your machine, it would appear one of the following is happening: (1) something on your machine is infecting or replacing that file after Notepad++ Portable is installed, (2) there are logical errors on your storage device and the file is being corrupted as it is installed, (3) that file is somehow locked by the OS and can't be replaced on upgrade, (4) something else is amiss with Windows itself. You can rule out some of these by trying to install a fresh copy of Notepad++ Portable 7.3.3 to your Desktop directory temporarily and scanning your drive for errors. If 3, try manually deleting that file and then reinstalling Notepad++ Portable (without uninstalling so your data stays).
Sometimes, the impossible can become possible, if you're awesome!
In case someone else is having the same issues with latest Notepad++ 7.3.3 32-bit on Windows 10 x64 ...
The solution that worked for me was provided by GlacialManYT on the notepad-plus-plus.org community forum: http://tinyurl.com/lnyzprs
Details of application assisted 'fix' ...
http://imgur.com/qo7Td2V
One could do the four fixes shown 'by-hand.'
Or do them one at a time.
However, this was easy and effective and whatever the exact issue I was having with Notepad++ 7.3.3 32-bit has disappeared.
My W10 OS must be broken.
The fully installed official 32-bit 7.3.3 version (running from program files and AppData) produces the same certificate complaint as your 7.3.3 portable app.
The OEM 64-bit 7.3.3 portable version and your prior 7.3.2 32-bit portable work fine.
I'm planning on doing a clean install of W10 on this PC in the next few weeks which will hopefully solve my problem.
Thanks again for your advice and for all you do maintaining this site and the other portable apps!
If I recall correctly, windows 10 supports a repair install in place without messing up your apps or data. You could also try the sfc file check tool. If you're planning on a clean windows 10 install anyway that would probably do it. But if you'd like to avoid the hassle, those first two ideas might work. Just be sure to back up first.
Sometimes, the impossible can become possible, if you're awesome!
Do you mean "sfc /scannow"? Or is there a portable apps "sfc file check tool"?
I keep forgetting to run the "sfc /scannow" command when I re-start my PC. I'll try that soon and tell you if that fixes anything.
I did run PowerShell: "Repair-WindowsImage -Online -ScanHealth" which said that all was fine.
Ran sfc /scannow which found/fixed an error in opengl, but that didn't solve my problem running newest 7.3.3 32-bit notepad++
I'll see if clean install of the upcoming 'creators' W10 edition fixes this issue.
Until then I'll keep running the NSA/CIA's favorite edition of 32-bit notepad++ (version 7.3.2)
P.S. I have seen a smattering of other users having identical trouble with 7.3.3 32-bit notepad++ running on W10 x64. And an equal number of responses saying they are not having any problems ... at least I'm not feeling so alone ...