And for some reason, Defender stopped caring about the exclusion and went from \\localhost\A$\OctoWoW to catch it instead.
Not here to j'accuse... Just interested if there were any changes that triggered this all of a sudden. Other than, maybe Defender's DB updating.
EDIT 1:

Yep, DB update, but that doesn't make my question a moot point.
Still super weird, that it would skip the exclusion to hop to the file through \\localhost\ .
Typically when something is ran this way, it feels more of avoiding something. Why should you use localhosts as the installation method?
EDIT 2:
I did some testing - I still had the old TurtleWoW's version of WoW.exe , that one doesn't get flagged. OctoWoW's version gets flagged for direct modifications to the executable (Now note, that I am NOT talking about vanillafixes or any other mods, that do the same thing).
Consider this as a request to know what has been done to the executable, that makes it targeted by Defender all of a sudden? But then TurtleWoW's similar executable does not get flagged.
Also, you can play with TurtleWoW's 1.18.1 WoW.exe , Octo's version isn't required.
The reason why I'm tiny bit questioning this, is most of us has seen dev activity through AIO recently, and I'm sure this is being used as a method to push live updates.
In this form:
