Issue in windows portable mode version 3.18.0

[lopcarlo]

Hi got this error from this version in windows that didn't got in 3.17

[HenriWahl]

Never seen... what source this comes from? Do you mean the ZIP-file? WHich one did you use?

[HenriWahl]

I now tested the files Nagstamon-3.18.0-win64.zip and Nagstamon-3.18.0-win64_debug.zip without experiencing problems. Maybe some antivirus software is disturbing in your setup?

[lopcarlo]

It was this the source Nagstamon-3.18.0-win64.zip but also tested the debug version and got the same error.
I have no admin privs, and I check the windows defender is blocking this source, but it does not do the same on 3.17-20260121.
What has changed?

[HenriWahl]

Sounds like a false positive detection. I guess there is some process in your organization to report such cases to Microsoft. I can't do this.

[HenriWahl]

According to VirusTotal even Microsoft Defender is fine with the ZIP file: https://www.virustotal.com/gui/file/72a67914063cda41fce449104720ef5d366a73a2dc64512f2fd4fb07067914f7

Looks like your local admins should try to help you.

[Ph1eG]

Hi,
It seems I'm experiencing the same thing here:

I didn't have this problem when testing the latest 3.17.

[HenriWahl]

This is really strange, beause the file Nagstamon.exe got signed:

121301 INFO: Build complete! The results are available in: D:\a\Nagstamon\Nagstamon\build\dist

    Directory: D:\a\Nagstamon\Nagstamon\build\build\Nagstamon

SignerCertificate                         Status                    StatusMessage             Path
-----------------                         ------                    -------------             ----
E7FC5F1AA2029D3019DD2A818D7136E5689A1733  Valid                     Signature verified.       Nagstamon.exe

I almost suspect this is the wrong path 🤔

[HenriWahl]

Please check latest testing release 3.19-20260301. This will surely go into 3.18.1 too.

[Ph1eG]

I'm afraid the result is the same for now.
The publisher seems to be recognised, but Smartscreen prevents nagstamon from starting. I ran my tests with the portable version. If necessary, I can run the tests via the setup tomorrow.

[HenriWahl]

This is the typical smartscreen behaviour, as long as not enough times people were fine with it, there might be that warning. As far as I remember you can choose here to run it anyway.

[HenriWahl]

Can I close this issue?

[Ph1eG]

Hello Henri!
Well, I’ve just had to put up with it, but it seems I still have to launch Nagstamon manually (even though it’s set to start automatically) and click on:

Am I the only one experiencing this now? Or are others having the same issue? Thank you for your feedback.

[HenriWahl]

It usually takes some time or successfull installations until this Defender Smartscreen thingy feels enough trust not to disturb users. I have no clue about how many thousands or millions need to succeed. Signing is the most I can do here. I don't know if there is a way to report false positives.