You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I use noScribe 0.5 without any issues. No when I installed v0.6 my Avast One virus scanner ringed the alarm and quarantined the "diarize.exe" file.
This was confirmed via Virustotal.
I don't mind items like "Bkav pro" with their generic AI driven detection as these often raise false alarms, but Avast so far is pretty spot on.
The noscribe.exe also has some issues, but I am less worried here:
Maybe someone can verify what is going on?
My question is also, how one can extract the files from the installer files on windows. This ".nsisbin" thing does not help checking its contents. I had to install everything in a VM to grab the diarize.exe file.
The text was updated successfully, but these errors were encountered:
Google "Win64:malware-gen". It's a generic, heuristic-based malware detection by Avast, not a confirmed virus. You will find reports that even official Windows update files have been flagged by this heuristic.
Thanks for the quick reply. I suspected a false positive and have reported the file to Avast. Now I hope they fix it quick.
With regards to getting to extract the nsisbin contents: I tried old 7zips (according to the discussion any version <15.06 should work) and sadly they do not work.
Hi,
I use noScribe 0.5 without any issues. No when I installed v0.6 my Avast One virus scanner ringed the alarm and quarantined the "diarize.exe" file.
This was confirmed via Virustotal.
I don't mind items like "Bkav pro" with their generic AI driven detection as these often raise false alarms, but Avast so far is pretty spot on.
The noscribe.exe also has some issues, but I am less worried here:
Maybe someone can verify what is going on?
My question is also, how one can extract the files from the installer files on windows. This ".nsisbin" thing does not help checking its contents. I had to install everything in a VM to grab the diarize.exe file.
The text was updated successfully, but these errors were encountered: