Recently i am getting detection of the Win32:patched Trojan from an exe with the Ojosoft Total Video Converter install. This is specifically the convert.exe, anyone else getting this. If i quarenten this file i lose functionality and its not repairable.
Could this be a false positive?
I have contacted Ojosoft and searched here but found nothing so far
Can you inform the file as being a false positive? (click on the bottom right of the virus warning message).
To know if a file is a false positive, please submit it to VirusTotal and let us know the result. VirusTotal has a file size limit of 10Mb. You can use VirScan also.
If it is indeed a false positive, send it in a password protected zip to virus@avast.com. Please, mention in the body of the message why you think it is a false positive and the password used. Thanks.
I received the same Avast warning when trying to run the OJOSoft video converter. Curiously, I have been running the app for months with no problems… until yesterday.
When I launched the app, Avast identified Convert.EXE as a Trojan and put it in the ‘chest’. Consequently, but nor surprisingly, the application no longer functions properly.
Before I came onto this forum, I uninstalled the OJOSoft converter and then reinstalled it from a saved install file. The very same Trojan warning came up as earlier reported by another forum member.
So, this tells me that whatever Avast is reading as a Trojan is contained in the OJOSoft install file from when I purchased their application back in November 2010.
If the file is less then 20mb then upload to www.virustotal.com and test it with 43 malware scanners
when you have the result, copy the URL in the address bar and post it here
I am working within Avast now and I can see from the Avast “File System Shield Scan Logs” that Convert.EXE has been moved to Chest. The Help tells me that I can right click on this log entry in order to send the file. This doesn’t work (cannot righjt click).
Any other way that I can find the file in question in order to upload as per your suggestion?
File is detected correctly. There is added section ‘.Silvana’ which contains part of import table. Such imported library has random name and random method name. In this case the library name is ‘GetChar2.dll’ and the method is ‘GetChar’. It seems to me like Win32:Induc few years later.