F-4E Not Authorized?

[HotTom]

It's been working fine but all of a sudden, when I log in, I get a message that F-4E is disabled on my computer. WTF? Can I fix it?

[Tom Kazansky]

Chances are good this could help:

 

[Bravo020]

I had the same issue happen last week.  My AV decided to quarantine a jester dll, upon restoring the quarantined file and adding an exception to the file I had no issues with running the F4 again.  I've heard that this can sometimes happen, and was the first time in a very long time that I've had this issue.

It happens, sometimes AV s/w generates false positives.  It's your own call as to what to do, trust or not trust, or see if anything else unusual starts happening.  While no s/w company intends to ship infected s/w, I've seen it happen numerous times over the past 30+ years that I've been working in the s/w industry.  From PC magazine publishers releasing infected disks to their readers, to s/w getting hacked via their supply chain (Solarwinds style).  Then again even with the vulnerability of Intel chips with Meltdown and Spectre, didn't stop anyone from turning on their PCs...

But in a nutshell, looks like it is purely a false positive, I've seen no unexpected behaviour on my PC, and I'm reasonably confident that everything is fine, but it isn't ideal when you get false positives, but I'd rather get false positives than missed alerts imho.

 

[HotTom]

Well, I can't seem to fix it. What exclusions should I add to my AV software?

It appears it was the Jester dll that was causing the problem but I don't know how to exclude or replace it. Thanks in advance!

HotTom aka tttiger

Edited July 10, 2024 by HotTom

[HotTom]

After fiddling with it all afternoon, I did what I shudda done in the first place: Deleted the module and reinstalled it. Works fine now.

Thanks, folks!