<![CDATA[GETOVERX FORUM Community Support - Setup & Deployment]]> https://forum.getoverx.com/ Wed, 10 Jun 2026 09:35:53 +0000 MyBB <![CDATA[Windows Defender false positive with Get Over [X] Shield 3.0.4.1 — workaround]]> https://forum.getoverx.com/showthread.php?tid=156 Tue, 02 Jun 2026 23:14:53 +0000 mrwebfeeder]]> https://forum.getoverx.com/showthread.php?tid=156
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 ExclusionProcess

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 ExclusionProcess

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]]> <![CDATA[PRIORITY UPDATE: GET OVER X SHIELD v3.0.4.1 (Core & Pro)]]> https://forum.getoverx.com/showthread.php?tid=150 Thu, 02 Apr 2026 23:54:22 +0000 mrwebfeeder]]> https://forum.getoverx.com/showthread.php?tid=150
We are officially announcing the deployment of version 3.0.4.1 for both GET OVER X SHIELD CORE and GET OVER X SHIELD PRO. This iteration represents a significant leap in the response and control capabilities of our security suite.

In an ever-evolving threat landscape, keeping detection engines up to date is not optional. We strongly urge all users to upgrade immediately to ensure maximum defense efficiency across their systems.
What’s New in v3.0.4.1?

This release focuses on refining our detection algorithms and enhancing the operator's control experience:

    EDR & EDR-Lite Engine Optimization: We have fine-tuned heuristics and behavioral analysis to reduce false positives while increasing response speed against suspicious thread executions.
    New Internal Encryption System: We’ve implemented a robust encryption layer for internal module communication within the Shield, hardening the application against external tampering attempts.
    Device Management: Critical improvements to the secure USB ejection protocol, ensuring data integrity and closing potential leak vectors during hardware dismounting.
    Security Contexts (PRO Exclusive): Introduction of advanced security contexts for more granular isolation of critical processes.
    EDR Pause Control (CORE): Responding to community feedback, the Core version now allows on-demand pausing of the EDR engine for specific system maintenance tasks.

Why You Should Update Immediately

While this is not a response to an active breach, v3.0.4.1 substantially improves your overall Security Posture. Running legacy versions means operating with outdated detection engines against the latest evasion techniques.

Update Steps:

    Log in to your download portal at getoverx.com.
    Download the installer corresponding to your license (Core or Pro).
    Run the update; the system will seamlessly migrate your current configurations.

Keeping your Shield Core or Pro updated is the only way to guarantee that application behavior remains reliable under stress or attack conditions.

Best regards,
The GET OVER X Engineering Team]]>
We are officially announcing the deployment of version 3.0.4.1 for both GET OVER X SHIELD CORE and GET OVER X SHIELD PRO. This iteration represents a significant leap in the response and control capabilities of our security suite.

In an ever-evolving threat landscape, keeping detection engines up to date is not optional. We strongly urge all users to upgrade immediately to ensure maximum defense efficiency across their systems.
What’s New in v3.0.4.1?

This release focuses on refining our detection algorithms and enhancing the operator's control experience:

    EDR & EDR-Lite Engine Optimization: We have fine-tuned heuristics and behavioral analysis to reduce false positives while increasing response speed against suspicious thread executions.
    New Internal Encryption System: We’ve implemented a robust encryption layer for internal module communication within the Shield, hardening the application against external tampering attempts.
    Device Management: Critical improvements to the secure USB ejection protocol, ensuring data integrity and closing potential leak vectors during hardware dismounting.
    Security Contexts (PRO Exclusive): Introduction of advanced security contexts for more granular isolation of critical processes.
    EDR Pause Control (CORE): Responding to community feedback, the Core version now allows on-demand pausing of the EDR engine for specific system maintenance tasks.

Why You Should Update Immediately

While this is not a response to an active breach, v3.0.4.1 substantially improves your overall Security Posture. Running legacy versions means operating with outdated detection engines against the latest evasion techniques.

Update Steps:

    Log in to your download portal at getoverx.com.
    Download the installer corresponding to your license (Core or Pro).
    Run the update; the system will seamlessly migrate your current configurations.

Keeping your Shield Core or Pro updated is the only way to guarantee that application behavior remains reliable under stress or attack conditions.

Best regards,
The GET OVER X Engineering Team]]> <![CDATA[Help Installing Windows 2012R2 Get Over X Server]]> https://forum.getoverx.com/showthread.php?tid=141 Mon, 23 Feb 2026 03:00:04 +0000 LucasReed]]> https://forum.getoverx.com/showthread.php?tid=141 GetOverX Shield Server Edition on Windows Server 2012 R2 (64-bit), but the antivirus components don’t start correctly. During the update step, freshclam.exe throws missing runtime DLL errors (e.g., VCRUNTIME140.dll / api-ms-win-crt-runtime-l1-1-0.dll). What are the required prerequisites for Server 2012 R2, and what is the recommended fix to complete the installation successfully? Thanks

[Image: Captura-de-pantalla-2026-02-22-192755.png]


[Image: Captura-de-pantalla-2026-02-22-193158.png]]]> GetOverX Shield Server Edition on Windows Server 2012 R2 (64-bit), but the antivirus components don’t start correctly. During the update step, freshclam.exe throws missing runtime DLL errors (e.g., VCRUNTIME140.dll / api-ms-win-crt-runtime-l1-1-0.dll). What are the required prerequisites for Server 2012 R2, and what is the recommended fix to complete the installation successfully? Thanks

[Image: Captura-de-pantalla-2026-02-22-192755.png]


[Image: Captura-de-pantalla-2026-02-22-193158.png]]]>