get any false positive with Virustotal for said 5.13.0 anymore! Cheers, Dominik Dominik Niedenzu schrieb am Mittwoch, 2. August 2023 um 09:41:20 UTC+2: > Hey Hartmut, > >

as a false positive. Signing the exe file can also help prevent this from happening. Jasper Harrison, aka Legorooj Core Developer on PyInstaller ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

a possible false positive to Microsoft and they said this: >>> "Analyst comments: The submitted files do not meet our criteria for >>> detection. No detection

fix the false positive. On Sunday, May 3, 2020 at 11:40:03 AM UTC-5, Robert L wrote: > > > Hi all - > > Just for fun I thought I would try this with my project compiled using

as a false positive. We do sign our binaries. Strangely, three of the binaries produced by pyinstaller get false positives even though the code they are compiled from do very different

to report false positives, it may be worth a > try. (AVG response was fast, don't know about Kaspersky) http://support.kaspersky.com/virlab/helpdesk.html One of the options

On Thu, Oct 11, 2012 at 4:35 PM, claudio canepa <ccanepacc@gmail.com> wrote: Today antivirus

Hi, The changes to hook-pywintypes.py since 1.6/2.0 seem relevant. Here is the code in the dev

Hi, I rebuilt the spec and made the following changes but they didn't prevent the message about

exclude_binaries=False, > name='C:\\dev\\sofastats.exe', > icon='C:\\dev\\images\\sofa_32x32.ico', > strip=False, > upx=False, > debug

basically a false positive. PyInstaller now automatically handles ctypes dependencies (eg: if you use ctypes to access a custom dynamic library, it will be automatically bundled

>> false positive warning in the file. Is there a way to know which >> warning was actually a problem (simply not found) ? > > Alas, it's not possible, because