search

ottozumkeller / QR-Code-Reader

QR-Code Reader with integrated keyboard-shortcut, tray icon and notification using Windows Snipping Tool, the ZXing.Net library and AutoHotkey
MIT License
8 stars 1 forks source link

Considered a virus by windows defender [BUG] #2

Open Marwans12 opened 3 months ago

Marwans12 commented 3 months ago

Not sure if this is the forum for it since it's not really a 'bug'. Anyhow, windows defender detected and deleted the x64 msi installer(QR-Code-Reader-1.1.2-x64.msi) as soon as I downloaded it. These are the details provided by windows defender. image

ottozumkeller commented 3 months ago

Unfortunately, there is nothing I can do about Windows Defender except send a false positive report to the Microsoft Security Intellegence Team. However, Virustotal is not complaining. https://www.virustotal.com/gui/file/e8e2d43277b675a534bf9e920b1daf4e67b691ef05391a87bb687f3071111ea0?nocache=1 Try switching windows Defender off temporarily. You can also get QR-Code Reader via Winget or Chocolatey. Sorry for the inconvenience.

ishaan-kapoor commented 2 months ago

About VirusTotal: https://www.virustotal.com/gui/file/30f0c649a760e2e09047ac5b0407813d7bf67a5f46a3177cb81a01b334de5f23

24/62 security vendors flagged this file as malicious

MaverickMartyn commented 2 months ago

@ottozumkeller I can confirm I am having the same issue, when trying to update to 1.1.2 through WinGet. Hopefully MS resolves the issue sometime soon. It worked fine when I initially installed 1.1.0 (though I'm not sure I used WinGet back then. Doubt it matters.).

blue-pine commented 1 month ago

Screenshot 2024-05-06 174022 Virus. Until this is resolved I am not going to use this but i want the developer to be supported and continue developing this app Update: I just found that this virus issue is only with the x64 version . So use the 32 bit or x86 version as that doesn't report viruses. I am now using 32 bit / x86 version only

MaverickMartyn commented 1 month ago

While using the x86 build is a fine workaround, it doesn't really solve the issue, and running non-64-bit isn't ideal. I know the Minecraft Forge team has had similar issues with their installer in the past, and reporting the false positive to MS eventually does result in them removing it.

blue-pine commented 1 month ago

While using the x86 build is a fine workaround, it doesn't really solve the issue, and running non-64-bit isn't ideal. I know the Minecraft Forge team has had similar issues with their installer in the past, and reporting the false positive to MS eventually does result in them removing it.

Then why doesn't the developer report to microsoft for false positive ?

ottozumkeller commented 1 month ago

While using the x86 build is a fine workaround, it doesn't really solve the issue, and running non-64-bit isn't ideal. I know the Minecraft Forge team has had similar issues with their installer in the past, and reporting the false positive to MS eventually does result in them removing it.

Then why doesn't the developer report to microsoft for false positive ?

I've actually already done that several times. Unfortunately, false positives are a known problem with many open source projects. Unfortunately there is nothing I can do except wait until or if MS adjusts the detection algorithms.

blue-pine commented 1 month ago

running non-64-bit isn't ideal.

Why it isn't ideal ? I want to know about it. Please tell me

blue-pine commented 1 month ago

except wait until or if MS adjusts the detection algorithms.

Does Microsoft inform you about the progress of your report and when its going to be corrected (the false positive) ?

MaverickMartyn commented 1 month ago

running non-64-bit isn't ideal.

Why it isn't ideal ? I want to know about it. Please tell me

Realistically, it probably won't make any real difference for this particular app, but other applications will suffer performance hits from doing that. And 32 bit programs are limited to using (if I recall correctly) a maximum of 4GB RAM.

except wait until or if MS adjusts the detection algorithms.

Does Microsoft inform you about the progress of your report and when its going to be corrected (the false positive) ?

I highly doubt it.

blue-pine commented 1 month ago

running non-64-bit isn't ideal.

Why it isn't ideal ? I want to know about it. Please tell me

Realistically, it probably won't make any real difference for this particular app, but other applications will suffer performance hits from doing that. And 32 bit programs are limited to using (if I recall correctly) a maximum of 4GB RAM.

except wait until or if MS adjusts the detection algorithms.

Does Microsoft inform you about the progress of your report and when its going to be corrected (the false positive) ?

I highly doubt it.

Thank you. That was needed info