You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release (1.25.9) is dedicated to Windows Defender. I'll try to keep it short.
249
-
250
-
In the past week alone, ***I've seen over 300 reports*** of false positive virus detections
251
-
affecting users. At peak, around ***4 issue reports an hour***.
252
-
253
-
This is because Defender suddenly started flagging a small part of Reloaded related to DLL Injection
254
-
that I wrote (and haven't changed at all) in almost 4 years.
255
-
256
-
This was not easy for anyone. I respond to all issues, usually within 10 minutes if awake.
257
-
Likewise, volunteers in game specific modding servers also take their time out of their day to help
258
-
troubleshoot users' issues. It was a heavy burden on everyone.
259
-
260
-
### This was Rough
261
-
262
-
As this coincided with 2 game releases, where people starting Reloaded, the timing could not have been
263
-
any more unfortunate. Many new users had to experience an absolute trainwreck of a first impression;
264
-
whether it be due to defender, some longstanding rare bugs, or silent antivirus treatment.
265
-
266
-
Worseover, I could not even fix these bugs. Because the virus detections were made by the 'machine learning'
267
-
side of Defender, releasing ***ANY UPDATE AT ALL*** means that 1000s of users would get new false positives.
268
-
[Dolphin Emulator was in the same predicament a few years ago](https://dolphin-emu.org/blog/2019/11/07/dolphin-progress-report-october-2019/#windows-defender-yelling-at-a-cloud-ai).
269
-
270
-
This was a result of the releases not being 'deterministic', the files in each Reloaded build/version
271
-
would change, even if the code didn't, and Defender would flag it. Reporting a false positive therefore
272
-
would be ineffective; defender would see it as a 'different file'. ***I COULD NOT RELEASE ANY UPDATES AT ALL***.
273
-
274
-
Needless to say, the situation was so dire, I booked a day off work and spent around 50 hours this week
275
-
so far towards fixing the issue (10+ hours per day). I've spent almost every hour of every day out
276
-
of my bed getting this resolved.
277
-
278
-
-----
279
-
280
-
# So what's been done so far to mitigate this issue?
281
-
282
-
## Replaced DLL Injection logic
283
-
284
-
R2 now uses my fork of [dll-syringe](https://github.com/Sewer56/dll-syringe), a Rust library based
285
-
on my old [Reloaded.Injector](https://github.com/Reloaded-Project/Reloaded.Injector).
286
-
287
-
Extra care has been taken to ensure this hopefully works as expected.
288
-
289
-
For the people running on Linux, I've even *found, reported and worked around* two new WINE bugs
0 commit comments