Rainmeter activates EAC (EasyAntiCheat) protection in games using the system (The Division 2, etc)

[DJBiograd]

Is there a chance this bug will ever be solved? Or is the only option closing rainmeter prior to launching any games that use EAC?

[balala]

Is there a chance this bug will ever be solved? Or is the only option closing rainmeter prior to launching any games that use EAC?

Not sure this might help, however did you try Game Mode?

[DJBiograd]

Not sure this might help, however did you try Game Mode?

Will try. It should work. But that's not a fix it's a workarround!

[DJBiograd]

it doesn't work game mode only unloads skins rainmeter is still present and triggers eac atleast it happens in the division 2.

[balala]

But that's not a fix it's a workarround!

I didn't say it's a fix. Was just an idea when read you post. Sorry didn't help.

[Brian]

It's pretty laughable that an anti-cheat software would flag Rainmeter.

The only reason I could think of that might trigger eac is a skin running an external program (via RunCommand) that somehow provides input or read memory from the game (or worse, writes directly to memory). This seems highly unlikely.

You may have to exit Rainmeter to play your game.

-Brian

EDIT - There might be an issue if you are launching your game directly with Rainmeter instead of Steam (assuming you are using Steam). Apparently you need to use the steam:// protocol. See here (it is a little old, but hopefully the information is still good).

So, if your skin is launching the game itself, the command might need to look like this: steam://rungameid/2221490
AppID found here.

[balala]

The only reason I could think of that might trigger eac is a skin running an external program (via RunCommand) that somehow provides input or read memory from the game (or worse, writes directly to memory). This seems highly unlikely.

If this is the case (only if this one is the case), the skin could be find and should be find.

@DJBiograd, if Brian's idea about launching the game doesn't help and there indeed are skins which you maybe don't really know if are running external programs which might cause the issue, you could try deactivating the activated skins one by one. After each deactivated skin, try launching the game and see if the issue still persist. If at a moment it's not anymore, you found the guilty skin, the last one deactivated. If you found it, you may want either not to use it anymore, or to come back with a skin name (and a link and so on).