[GNC] ANNOUNCE: (Re) GnuCash 5.14 Released

[David G. Pickett]

 I found it in "Norton Security->security history->recent history->quarantine->...->Create Exclusion and restore", and restored it with exclusion, dismissed the dialog the second time that might have been before the exclusion is established so it failed the first time, did run as administrator, and it installs OK.
    On Monday, December 22, 2025 at 12:47:58 PM EST, David G. Pickett <dgpickett at aol.com> wrote:   

  I reported it but have not had this in the past (new filter?) and am not sure how to override this yet!
    On Monday, December 22, 2025 at 12:08:52 PM EST, John Ralls <jralls at ceridwen.us> wrote:   

 

On Dec 22, 2025, at 08:31, David G. Pickett via gnucash-user <gnucash-user at gnucash.org> wrote:
 ____________________________
Details
Threat name: FileRepMalware [Trj]Threat type: Trojan Horse - This threat pretends to be something else (e.g., picture, document, or other file) to trick you into running it and infecting your computer.Status: Moved to QuarantineOptions: Report false detectionDetected by: Auto-ProtectOn PC from: 12/22/25, 11:28 AMLast Used: 12/22/25, 11:29 AMStartup Item: No
UnknownIt is unknown how many users in the Norton Community have used this file.
UnknownThe file release is currently unknown
HighThe file risk is high.____________________________
Origin
Downloaded from: https://psychz.dl.sourceforge.net/project/gnucash/gnucash%20%28stable%29/5.14/gnucash-5.14.setup.exe?viasf=1____________________________
Activity
Path | Type | StatusC:\Users\david\Downloads\gnucash-5.14.setup.exe | File | RepairedC:\USERS\DAVID\DOWNLOADS\GNUCASH-5.14.SETUP.EXE | Process | Terminated


    On Monday, December 22, 2025 at 11:19:23 AM EST, David G. Pickett <dgpickett at aol.com> wrote:   

 Norton says it contains a trojan, quarantines the win version.  


https://bugs.gnucash.org/show_bug.cgi?id=799709 reports the same issue from Avast. It just means that it’s not signed (because it’s hard and expensive for individuals to get Windows code signing certificates) or that Norton doesn’t trust the signing certificate holder (so even if we did code-sign it it wouldn’t do any good). The long-term solution is for users like you to report it as a false positive, instructions at https://support.norton.com/sp/en/us/home/current/solutions/kb20100222230832EN.

Regards,John Ralls