06-02-2026, 11:14 PM
Posted by Get Over [X] Support · June 2, 2026 — Affected Version: Get Over [X] Shield 3.0.4.1
We have confirmed that a new heuristic detection feature released by Microsoft on June 2, 2026 in Windows Defender is generating a false positive on GetOverXShield.exe, incorrectly classifying it as Trojan:Win32/Bearfoos.A!ml.
--- What is happening? ---
Windows Defender's machine learning engine flags Get Over [X] Shield as suspicious because, like any legitimate security software, it monitors system processes, accesses kernel structures, and actively protects memory. This does not mean the software is malicious — it is an incorrect detection based on behavioral patterns, not a real threat.
Get Over [X] Shield is digitally signed and its copyright is duly registered in the United States of America. This is a confirmed false positive.
--- Temporary fix — manually adding an exclusion in PowerShell ---
Step 1 — Open PowerShell as Administrator
Press Win + S, type PowerShell, right-click the result and select "Run as administrator".
Step 2 — Run the following commands
Step 3 — Verify the exclusion was applied
Expected output:
C:\Program Files\GetOverXShield
GetOverXShield.exe
No restart is required. The exclusion takes effect immediately.
If Defender has quarantined the executable, you will need to restore it manually before applying the exclusion.
Report: Windows 11 — 2026 Update · June 2, 2026
We have confirmed that a new heuristic detection feature released by Microsoft on June 2, 2026 in Windows Defender is generating a false positive on GetOverXShield.exe, incorrectly classifying it as Trojan:Win32/Bearfoos.A!ml.
--- What is happening? ---
Windows Defender's machine learning engine flags Get Over [X] Shield as suspicious because, like any legitimate security software, it monitors system processes, accesses kernel structures, and actively protects memory. This does not mean the software is malicious — it is an incorrect detection based on behavioral patterns, not a real threat.
Get Over [X] Shield is digitally signed and its copyright is duly registered in the United States of America. This is a confirmed false positive.
--- Temporary fix — manually adding an exclusion in PowerShell ---
Step 1 — Open PowerShell as Administrator
Press Win + S, type PowerShell, right-click the result and select "Run as administrator".
Step 2 — Run the following commands
Code:
Add-MpPreference -ExclusionPath "C:\Program Files\GetOverXShield"
Add-MpPreference -ExclusionProcess "GetOverXShield.exe"Step 3 — Verify the exclusion was applied
Code:
Get-MpPreference | Select-Object -ExpandProperty ExclusionPath
Get-MpPreference | Select-Object -ExpandProperty ExclusionProcessExpected output:
C:\Program Files\GetOverXShield
GetOverXShield.exe
No restart is required. The exclusion takes effect immediately.
If Defender has quarantined the executable, you will need to restore it manually before applying the exclusion.
Report: Windows 11 — 2026 Update · June 2, 2026