Problem: Windows 11 “Hardware-enforced Stack Protection” blocks BattlEye (BEDaisy.sys) — games won’t launch or kick you instantly
Published: 2026-01-01 12:00 (local time)
Quick Summary
- Many Windows 11 players are suddenly unable to launch BattlEye-protected games (or get kicked immediately) after enabling a Windows security feature.
- The common error points to BattlEye failing to load its driver (BEDaisy.sys), often shown as “Driver Load Error (1275)” or “A driver cannot load on this device.”
- This is widespread because BattlEye is used across multiple popular online games, and Windows 11 actively prompts users to enable the feature.
- There is no universal “clean fix” yet; BattlEye states Windows 11 can still block their driver while the feature is enabled, pending Microsoft-side changes.
- Practical workarounds exist (mainly disabling the specific feature), but they come with security tradeoffs you should understand.
What’s happening
Players on Windows 11 are reporting that BattlEye-protected games fail to start or fail to connect because the BattlEye kernel driver (commonly referenced as BEDaisy.sys) can’t load. In many cases, Windows Security displays a warning that a driver “cannot load on this device” due to a security mitigation called Hardware-enforced Stack Protection (also shown as Kernel-mode Hardware-enforced Stack Protection inside Windows Security > Device security > Core isolation). BattlEye then throws launch-time errors such as “Failed to initialize BattlEye Service: Driver Load Error (1275)”.
This affects PC players on Windows 11 across multiple BattlEye-enabled games (for example, community reports frequently reference Destiny 2 and Escape From Tarkov, among others). While the exact moment it begins varies by user, the pattern is consistent: it often starts right after the user enables the Windows security toggle (sometimes prompted by Windows), or after certain Windows updates where the prompt appears again.
What makes it especially frustrating is that users can do “standard troubleshooting” (verify files, reinstall the game, reinstall BattlEye) and still hit the same block, because the underlying issue is Windows refusing to load the driver while the security feature remains enabled.
Likely causes (what research suggests)
-
Windows 11 kernel mitigation incompatibility / blocking behavior. BattlEye’s own FAQ explains that enabling Hardware-enforced Stack Protection can prevent the BattlEye driver from loading, and that—even after BattlEye-side work—Windows 11 may still block the driver when the feature is enabled, pending a Windows update to unblock it.
-
Policy/security posture mismatch between Microsoft and kernel-level anti-cheat drivers. BattlEye describes this as a “complexities involved in security software” situation, where kernel-level tools can conflict with new OS mitigations.
-
Secondary contributors that can look identical. Some BattlEye help pages also note that update failures, firewall restrictions, corrupted local BattlEye folders, or broken Windows certificates can cause BattlEye initialization errors too. These aren’t the main “widespread” trigger for the BEDaisy.sys + stack protection pop-up, but they can produce similar symptoms.
Solutions & Workarounds
1) Disable Kernel-mode Hardware-enforced Stack Protection (most reliable workaround right now)
Who it helps: Windows 11 players seeing BEDaisy.sys “cannot load” warnings and/or BattlEye Driver Load Error (1275).
Steps:
- Open Windows Security (Start menu > type “Windows Security”).
- Go to Device security > Core isolation details.
- Find Kernel-mode Hardware-enforced Stack Protection and toggle it Off.
- Restart your PC.
- Launch the game again.
Risks / tradeoffs: You are disabling a Windows security mitigation. BattlEye claims this is a new feature that wasn’t previously enabled on devices, but it is still a reduction in your system’s security posture compared to having it enabled.
Stop and contact support if: The error persists even with the setting Off, or you never see the stack protection warning but still get (1275). At that point you may be dealing with a different BattlEye initialization issue.
2) Use the Windows pop-up “Disable” button when prompted (quick path to the same result)
Who it helps: Anyone who gets a Windows warning explicitly naming BEDaisy.sys and offering a “Disable” option.
Steps:
- When Windows shows the driver warning, click Disable.
- Reboot when prompted (or restart manually right away).
- Retry launching the game.
Risks / tradeoffs: Same as above—this turns off the mitigation.
Stop and contact support if: You click Disable, reboot, and Windows re-enables it automatically or the error returns immediately.
3) Ensure BattlEye can update/download (fixes “Update failed …” cases that look like a launch failure)
Who it helps: Players getting BattlEye “Update failed …” messages or stuck initialization that appears network-related.
Steps:
- Temporarily disable overly strict firewall rules, or add an allow-rule for the game’s BattlEye launcher executable (often named something like [GameName]_BE.exe).
- If you use third-party security software, add BattlEye components to its allowlist.
- Retry launch so BattlEye can fetch updates.
Risks / tradeoffs: Allowlisting increases exposure if you allow too broadly. Keep rules as narrow as possible (only the BattlEye/game executables).
Stop and contact support if: BattlEye updates still fail on a clean network and after you confirm no proxy/VPN/security tool is blocking it.
4) Reinstall BattlEye (and clear the game’s local BattlEye folder) to address corrupted local state
Who it helps: Users without the specific stack protection warning, or users who disabled stack protection but still can’t initialize BattlEye.
Steps:
- Close the game and its launcher (Steam/Epic/etc.).
- Locate the game’s BattlEye installer in the game folder (commonly a BattlEye subfolder) and run the installer/repair option.
- Also delete the game-specific BattlEye folder under your user profile’s local app data (BattlEye notes this can fix permission/corruption issues), then retry launch.
Risks / tradeoffs: Minimal; you may need admin rights. Deleting local folders can reset certain local settings.
Stop and contact support if: Reinstalling doesn’t change anything and you still see Driver Load Error (1275) specifically—then the Windows mitigation conflict is the more likely root cause.
5) If you must keep the mitigation enabled: consider alternative play options (not a fix, but a practical workaround)
Who it helps: Players who refuse to disable the Windows mitigation for security/compliance reasons.
Steps:
- Play the same title on a console (if you own it there) until the Microsoft/BattlEye compatibility situation changes.
- If the game supports it, use a separate Windows installation or separate PC dedicated to gaming where you’re comfortable disabling the mitigation.
Risks / tradeoffs: Cost, inconvenience, and potentially losing mods/settings. Not all titles support cross-progression.
Stop and contact support if: You need a formal statement for an enterprise-managed device; your IT/security admin may require vendor confirmation.
Prevention (so it doesn’t come back)
- If you play multiple BattlEye games, be cautious when Windows prompts you to enable new kernel-level mitigations; enabling them may break anti-cheat until vendors update and the OS allows the updated drivers.
- After major Windows updates, re-check Windows Security > Core isolation to confirm the setting didn’t re-enable automatically.
- Keep Windows fully updated; BattlEye explicitly indicates they are waiting on a Windows update to resolve the “still blocked” condition when the mitigation is enabled.
- Keep firewall/security software rules narrow but consistent so BattlEye can update.
FAQ
Q: Is this a “my PC is broken” issue?
A: Usually no. The strongest signal is the explicit Windows warning naming BEDaisy.sys plus BattlEye Driver Load Error (1275). That points to a compatibility/blocking issue rather than a failing GPU/CPU or corrupt Windows install.
Q: Does reinstalling the game fix it?
A: Often not, if Hardware-enforced Stack Protection is still enabled. The driver can remain blocked regardless of reinstall.
Q: Is disabling Kernel-mode Hardware-enforced Stack Protection dangerous?
A: It reduces your security posture relative to leaving it enabled. BattlEye says it’s a new mitigation that wasn’t previously enabled on devices, but it is still a security tradeoff you should decide on knowingly.
Q: Why do I see this only on Windows 11?
A: BattlEye’s guidance specifically calls out Windows 11 enabling/promoting this mitigation and blocking their driver when it’s turned on.
Q: Can I keep the mitigation enabled and still play?
A: BattlEye indicates Windows 11 can still block their driver while it’s enabled (pending a Windows update). So for many players, “keep it enabled and play” is not currently reliable.
Q: I don’t see the stack protection warning, but BattlEye still fails. What then?
A: You may be hitting a different BattlEye issue (update failure, permissions, certificates, firewall). Try the network/repair steps and then contact official support for your game or BattlEye.
Q: When will this be fixed permanently?
A: BattlEye’s FAQ suggests the remaining blocker is Windows-side (“waiting for Microsoft to release a Windows update to unblock”). There isn’t a firm public date in the referenced guidance.