Hi @twgiu I just downloaded the 32-bit version of Notepad++ from the official website (https://notepad-plus-plus.org/downloads/v7.9.1/) and sent notepad++.exe to virustotal. One of the 72 engines detected malware (Trojan.Generic.giteg). I also uploaded the 64-bit version and it was clean.
Being only one engine, named Jiangmin, that detected the virus I’d would be inclined to say that it is a false positive. If possible you can test the 64-bit version and if it results clean, then use that version?

For peace of mind you can also post an issue in github (https://github.com/notepad-plus-plus/notepad-plus-plus) where notepad++ developers could confirm whether the downloads are legit or not.

@A-Former-User said in user manual outdated.:

it also doesn’t work when I click proceed to npp-user-manual.org(unsafe)

I could open that link without problems in Google Chrome, it seems the certificate is valid since October. However, www.npp-user-manual.org was giving the same warning you saw… I cleared my browsing data, including ‘Passwords and other sign-in data’, restarted the browser and now it working proeprly. It happened the same with Firefox and I ‘fixed’ the issue by clearing all my browsing data and restarting…
I guess there must be some place in the network and/or in our browsers that is keeping our local certificates from updating?

@Alan-Robinsin ,

In general, to edit a file in administrator mode, the Notepad++ application has to be run in administrator mode. That is accomplished the same as any other Windows application, and is not unique to Notepad++.

An example sequence that worked for me

Exit all instances of Notepad++. Run one instance as administrator (you may have to browse to the notepad++.exe and right click, run as administrator). it should say [Administrator] at the end of the window title File > Open, and browse to the file you want to edit. You should be able to save, if it was really an administrator-mode issue.

I came across this today also. Very annoying to have exe and dll files not digitally signed. It really puts some doubt into the integrity of the files of the assembly.

Please digitally sign on next release please.

@Phil-Randal see here.

I really hope, that you are just “playin” a security analyst.

Access via network sharing requiers administrative rights so the person could copy the directly to ProgramFiles folder and the user is helpless.

@dinkumoil Thanks for catching that issue. The above posts have been edited and now point to the .org domain to keep users from mis-clicking.