Trend Micro keeps thinking OR is "ransomware"

[stlsf4003]

And it keeps terminating the install every time I try to install OR.
Y'all have any idea how to work around this?

[baldwin]

Most AV programs have an exceptions facility. Add the OR install file to it.

[stlsf4003]

Most AV programs have an exceptions facility. Add the OR install file to it.

No dice. I put the installer application into the exceptions list, then tried to run it again, only for it to throw up the same warning halfway through the install process.
Something about it trying change...something that has to do with the PDF manual.

[derekmorton]

You have to put the folder in the exceptions list.

[stlsf4003]

You have to put the folder in the exceptions list.

The installer didn't come in a folder; it was just the installer app.
I've totally messed up somewhere, haven't I?

[derekmorton]

Put the folder the app sits in in the exceptions list

[stlsf4003]

Unless you're talking about the downloads folder that the app showed up in after downloading it, the app didn't come in anything.
Here's how it looks

[stlsf4003]

P.S. I don't know how to make these images any bigger as well ^^;

[derekmorton]

Yes, the downloads folder, but remove the exception after.

[stlsf4003]

Yes, the downloads folder, but remove the exception after.

I tried it again, and the same thing happened.
__________
My Trend Micro exception list with the offending file added




And the aftermath of my AV terminating the install once more.

[derekmorton]

Ok, we are getting to the end of things.

See if you can turn Trend off, failing that, its an uninstall of trend.

[stlsf4003]

Ok, we are getting to the end of things.

See if you can turn Trend off, failing that, its an uninstall of trend.

OK, after temporarily shutting down a few things with Trend and running the installer again, it finally successfully completed the install! ^^

Many thanks for the help, Derek!

[pwillard]

This is all likely due to Trend checking for the Windows "signing" certificate and not finding one. Something major developers pay Microsoft for, but hobbyists don't. It's a mechanism that ensures the code hasn't been tampered with... which is why you have to turn it off in cases like this. You are getting the program directly from a trusted source, which is why it's mostly safe to shut it off and turn it back on afterward.