UPDATE: Microsoft says that they have now removed the detection from the latest malware definitions.
It seems like Windows Defender just got an update that mistakes Looking Glass host (reported version: B2-rc4-0-g969effedde) for a “Wacatac” trojan or something. I’ve had the current version of LG installed for some time so this is quite clearly a Windows Defender false positive.
So beware when installing Windows updates! You might want to allowlist LG before this happens to you too.
I would not wonder if they have automated the whole process for cost reasons or outsourced that to some 3rd world country, and the only way to override the systems detection is for a larger number of people to report this until the machine learning system has enough data for it to make the correct predictions.
I though exactly the same. I am totally not in the Microsoft ecosystem but if you have a stable version, how hard would it be to put that in the MS Store. Since I also firmly believe everything in there gets and immediate exception from the MS Defender.
I wanted to proactively create an exclusion for LG. I am using B2-rc4 (with the installer file). Can you give me more specific instructions here how I would create an exclusion for that? I am not even sure if I need to create an exclusion for a file and if so which one, or a process.
The default install folder is C:\Program Files\Looking Glass (host). I hope just adding an exclusion for that folder would be fine. I have never had Looking Glass trigger windows defender at all, not even if I scan the binary specifically, so someone else would have to make sure it works.
I should have come up with a simple solution like that myself! In my defense it is quite late . Thank you. I wanted to avoid not being able to use my VM when I need it. Windows has the habit of refusing to work when you really, really need it.