Avast says vassal 3.5.1 and java are infected

I have been working on a module all day, and just before going to bed, I decided to run my mod one last time. Avast responded with a popup warning saying java.exe is blocked because it was infected with IDP.Generic. It moved it (java.exe I presume) to a virus chest.

I tried downloading the latest 64-bit java and not the entire vassal 3.5.1. It installed, but vassal crashed when I tried running afterwards. (A dump went to the bug tracker.)

So I figured vassal didn’t see this installation, and I didn’t know how to connect them, so I decided to install vassal-3.5.1-windows-64.exe. In short order Avast popped up again, but this time it blocked saying vassal-3.5-1-windows-64.exe was infected with IDP.Generic. It asked if I wanted to move it to a virus vault; I left the popup message up and went to bed.

I am dead in the water here.

Thus spake shilinski:

I have been working on a module all day, and just before going to bed, I
decided to run my mod one last time. Avast responded with a popup
warning saying java.exe is blocked because it was infected with
IDP.Generic. It moved it (java.exe I presume) to a virus chest.

This is almost certanily a false alarm. (Check the file yourself at
virustotal.com if you’re worried.)

I tried downloading the latest 64-bit java and not the entire vassal
3.5.1. It installed, but vassal crashed when I tried running afterwards.
(A dump went to the bug tracker.)

This is because (1) VASSAL 3.3+ uses its own bundled Java, not any Java
you have intalled, and (2) java.exe is now missing from VASSAL’s bundled
Java because Avast swiped it.

So I figured vassal didn’t see this installation, and I didn’t know how
to connect them, so I decided to install vassal-3.5.1-windows-64.exe. In
short order Avast popped up again, but this time it blocked saying
vassal-3.5-1-windows-64.exe was infected with IDP.Generic. It asked if I
wanted to move it to a virus vault; I left the popup message up and went
to bed.

The solution is to restore java.exe from Avast’s virus vault, and possibly
add it to Avast’s exclusions.


J.

Thanks Joel. That worked. You know, I used to work in software my entire career, and I seemed to specialize in frameworks just like Vassal. But I put down my shovel (retired) more than 15 years ago, so I’m pretty rusty on the details, and things change all the time. If I were 30 years younger, I’d be hip-deep in the Vassal code.

I’ve also had it up to here with Avast, and maybe it’s time for me to put it down.