windows defender false positive

New day, new informations, thoughts, questions.

I have found our issuer among the trusted certificates, but in the short name section:

Previously I have tested the download on Windows 10 and downloading in Chrome.

Now I tested on Windows 11 and Edge.

In Edge the download process is a nightmare.

And then keep anyway, three strange clicks after download.

And as you can see windows in 2024 can not handle not English letters.

And It was not me who cut the button at the bottom, not to mention...

Now in the properties panel you can see the suspicious checkbox with unblock.

BUT at starting the application you can not get the smartscreen protection blue window, the application starts normally.

I found the same edge download process under windows 10, so it is independent from the OS version.

Two options:

1. Downloading in Chrome without issue, but starting the setup blue smartscreen is coming with scary warning.

2. Downloading in Edge and clicking 3 times in strange windows to keep the file, then start normally.

Dont you have an expert in this field to help us what we are doing wrong?

We have sectigo certificate which is not a noname company.

So what to do not to scare our users with downloads or startup warnings?

We are using Innosetup setup packaging system. Tested with an "empty", "doing nothing" setup as well.

So not the setup file content which makes the warnings.

We have some administration issues but still not sure what it is.

My apologies on this and if replacing the certificate is the one that will resolve the issue then the best option is to go that path.

From the new certificate chain none of the Sectigo authorities from our certificate exist in the trusted list in Windows.

So the problem is certificate problem. It would be great if the Windows could show relevant information about it.

We have been in this hole of pain for a year.

How can it be that a highest level Sectigo authority is not trusted by windows?

Why is "no problem with the certificate" written if not so?

Now we have to get another certificate which is in the list.

Of course this result was not supported by Microsoft.

The likely solution found by us in the darkness around us.

I send this solution for the future darkness walkers.

Bests

We are investigating the issue. Further information is that we had to change the exe signing process, and the issue is related with that change.

The singing seems valid. We have only sha256 signing, previously we had sha1 as well, but as I know it is normal.

The old certificate chain is:

The new certificate chain is:

Both of them is saying "No issue with the certicate".

In the old one we had sha256 algorithm.

In the new one we have ECC algorithm.

The question is that which property of the digital signature of the setup could cause

"The Windows protected the computer" screen?

(false, since we have valid signature)

Good day Duzmath, thanks for your question. I am glad to be able to provide assistance to you today. Sorry to know about this and I understand that Windows Security/Defender is causing an issue on the program that you are using and for this you can head over to the link below and go through the steps on how you submit this for review and for this to be considered to be tagged as a false positive.

https://docs.microsoft.com/en-us/windows/securi...

For the time being as a workaround, I would suggest to have this to be exempted from the scanning of Windows Security/Defender for users and this is the way for to be able to go through the file without any intervention.

https://support.microsoft.com/en-us/windows/add...

Regards,

Paul R.