If you landed here, you probably saw a blue screen or a boot error saying something like “ENE.sys driver cannot be loaded” on Windows 11. I’ve dealt with this exact issue, and the short answer is: Windows 11 blocks ENE.sys because it lacks a valid digital signature or contains a known vulnerability. The fix depends on why it’s being blocked.
Why ENE.sys Gets Blocked at Startup
ENE.sys is a kernel-level driver developed by ENE Technology. It’s used by RGB lighting software like ASUS Aura Sync, MSI Mystic Light, and similar utilities to control hardware LEDs and fan speeds. It communicates directly with your system’s hardware at a very low level.
Windows 11 enforces something called Driver Signature Enforcement (DSE) and Hypervisor-Protected Code Integrity (HVCI). When ENE.sys fails to meet these security requirements, Windows refuses to load it. Sometimes it throws a BSOD. Sometimes your PC simply won’t boot past a certain screen.
Here’s what actually triggers the block:
- The ENE.sys file version you have is outdated and lacks a valid Microsoft WHQL signature
- Windows 11 added ENE.sys to its Vulnerable Driver Blocklist due to a known security flaw (CVE-2020-12446)
- A recent Windows Update pushed a new policy that flags the driver
- HVCI (Memory Integrity) is turned on in your security settings and rejects the unsigned driver
- Corrupted RGB software left a broken driver entry in your system
The most common scenario in 2026 is that Windows Security is actively blocking it because ENE.sys has a documented privilege escalation vulnerability. Microsoft updates its blocklist periodically and ENE.sys has been on it for a while.
Check If Memory Integrity Is the Cause
Before doing anything else, check this setting. It’s responsible for most ENE.sys blocks on Windows 11.
- Open Windows Security from the Start menu
- Click Device Security
- Click Core isolation details
- Look for Memory Integrity
If it’s ON and you recently installed or updated RGB software, that’s almost certainly your culprit. Windows will tell you directly: “A driver is incompatible” and may even show “ENE.sys” by name.
Don’t just turn Memory Integrity off and call it a day. That’s a security tradeoff. Understand what you’re doing first.
The Vulnerable Driver Blocklist
Microsoft maintains an official blocklist of drivers with known security holes. ENE.sys appears on this list because of CVE-2020-12446, a vulnerability that allows an attacker to gain kernel-level access through the driver. This affects older versions specifically.
You can review the Microsoft recommended driver block rules to confirm whether your version is listed.
The key detail: if your ENE.sys is an old version bundled with software from 2019-2021, it will almost certainly be on that list. Newer versions from updated software packages may not be.
Step-by-Step: How to Actually Fix This
I’ll go from the safest and most effective fix to the more advanced options.
Fix 1: Update or Reinstall the RGB Software
This is where I’d start. The driver file gets installed by your RGB software, so updating it is the cleanest fix.
For ASUS Aura Sync:
- Download the latest version from the official ASUS support page for your motherboard model
- Uninstall the current version completely using Revo Uninstaller (free) to catch leftover registry entries
- Restart your PC
- Install the new version
For MSI Mystic Light:
- Use MSI Dragon Center or the newer MSI Center app
- Check that you’re on the latest build
For other software like OpenRGB or SignalRGB:
- Check their GitHub or official site for driver-signed versions
After updating, check Device Manager. Search for ENE in the driver list and see if it loads without errors.
Fix 2: Remove ENE.sys Completely
If you don’t actually use or need RGB lighting control, just get rid of the driver entirely.
Open Command Prompt as Administrator and run:
sc stop ENEService
sc delete ENEServiceThen navigate to C:\Windows\System32\drivers\ and delete ENE.sys if it’s still there. You may need to boot into Safe Mode first if the file is locked.
Restart. The error should be gone.
Fix 3: Disable Memory Integrity Temporarily to Boot
If your PC won’t boot at all, boot into Windows Recovery Environment first:
- Hold Shift and click Restart from the login screen
- Go to Troubleshoot > Advanced Options > Startup Settings
- Press F7 to disable driver signature enforcement temporarily
This lets you get into Windows to then either update the driver or remove the software properly. Don’t leave DSE disabled permanently.
Fix 4: Use the Group Policy to Manage the Block
On Windows 11 Pro or Enterprise, you can check if an enterprise policy is blocking drivers.
- Press
Win + R, typegpedit.msc - Navigate to Computer Configuration > Administrative Templates > System > Driver Installation
- Look at Code signing for device drivers
If it’s set to block, and you’re on a managed work machine, talk to your IT team. You shouldn’t override this yourself.
Fix 5: Manual Driver Replacement (Advanced)
If you need ENE.sys specifically and have a newer signed version:
- Download the updated driver package from the manufacturer’s support page
- Open Device Manager
- Find the ENE device (usually under System devices or Unknown devices)
- Right-click > Update driver > Browse my computer > Let me pick from a list
- Point it to the new driver folder
Make sure the version you’re installing is newer than what’s on the blocklist. Installing an older version just repeats the problem.
ENE.sys Version Table: What’s Blocked vs What Works
| ENE.sys Version | Status on Windows 11 | Notes |
|---|---|---|
| 1.0.0.0 (2018) | Blocked | CVE-2020-12446, no WHQL |
| 1.0.2.0 (2020) | Blocked | Same vulnerability |
| 1.1.0.0 (2021) | Blocked on HVCI | Unsigned in some builds |
| 1.2.x and newer | Check your OEM | Some signed, verify first |
| OpenRGB alternative driver | Generally passes | Community-maintained |
The exact version on your system is in Device Manager > right-click driver > Properties > Driver tab.
What Is HVCI and Why It Matters Here
HVCI (Hypervisor-Protected Code Integrity) is a Windows 11 security feature that uses hardware virtualization to protect the kernel. Any driver that gets loaded must pass signature checks enforced at the hypervisor level, not just the OS level.
This is a step above old Driver Signature Enforcement. Even a driver that once worked with DSE may fail under HVCI.
Many PCs that shipped with Windows 11 have HVCI enabled by default. If you upgraded from Windows 10, it may have been turned on during the upgrade.
Disabling HVCI gives you more driver compatibility but reduces your security posture. It’s a personal choice, but for home users with a gaming rig who need RGB control, it’s a common tradeoff.
To check HVCI status:
- Open System Information (msinfo32)
- Scroll to Virtualization-based security
- Look for “Running” or “Not enabled”
When the Error Appears During Boot vs After Login
These are two different situations and they need different approaches.
Blue screen on boot or loop:
- Most likely the driver is set to load at startup and Windows is rejecting it before the desktop appears
- Boot into Safe Mode, disable or delete the ENE service, then restart normally
- In Safe Mode, third-party drivers don’t load, which is why it boots fine there
Error after login or in software:
- The driver loads but fails later, usually when the RGB software starts
- Update or reinstall the software, or set the application to not launch at startup via Task Manager > Startup apps
OpenRGB as a Replacement
If your RGB software keeps bundling the problematic ENE.sys, consider switching to OpenRGB, an open-source project that supports a huge range of RGB hardware without needing ENE.sys at all. It uses different access methods to control lighting on many ASUS, MSI, and Gigabyte boards.
Check openrgb.org for compatibility with your specific hardware. It’s not perfect for everything, but it resolves the ENE.sys issue entirely on supported boards.
Checking Event Viewer for the Exact Error
If you’re not sure what’s happening, Event Viewer tells you exactly why the driver failed.
- Press
Win + Xand open Event Viewer - Go to Windows Logs > System
- Filter by Error
- Look for entries with source “Service Control Manager” or “Kernel-PnP”
You’ll see something like:
- “The ENEService service failed to start due to the following error: This driver has been blocked…”
- Or a Code 39 error meaning Windows can’t load the driver
That exact message tells you whether it’s a blocklist issue, a signature issue, or something else.
Summary
ENE.sys fails to load on Windows 11 because it’s either on Microsoft’s vulnerable driver blocklist, lacks a valid signature under HVCI, or was left behind by outdated RGB software. The fastest fix is updating your RGB software to the latest version from your motherboard or peripheral manufacturer. If that doesn’t work, remove the driver and software entirely. If your PC won’t boot, get into Safe Mode or Recovery and delete the ENE service. For users who don’t need RGB at all, OpenRGB offers a cleaner alternative without ENE.sys dependency.
You don’t need to disable core security features permanently. In most cases, a software update or clean reinstall resolves it completely.
Frequently Asked Questions
Can I just copy ENE.sys from another PC to fix it?
Copying the file doesn’t help if the version is the same one on the blocklist. Windows checks the driver’s hash and version, not just the filename. You’d need a newer, Microsoft-signed version from an official software package, not a random copy from another machine. Copying unsigned drivers can also introduce security risks.
My RGB still works after I deleted ENE.sys. How?
Some motherboards and RGB controllers have multiple drivers. If your lighting still functions, your board is using a different driver path, possibly iCUE, Armoury Crate’s internal driver, or a USB-based controller that doesn’t rely on ENE.sys. The ENE.sys file specifically handles certain ENE chip-based controllers, not all RGB hardware.
I turned off Memory Integrity and now ENE.sys loads but it crashes randomly. What’s going on?
Random crashes after loading ENE.sys with Memory Integrity disabled usually mean the driver itself has a bug or incompatibility with your specific hardware revision. Try updating to the latest driver version from your manufacturer. If crashes continue, the driver is genuinely unstable on your system, not just blocked by policy.
Does this issue affect Windows 10 users too?
Windows 10 has looser enforcement by default. ENE.sys often loads fine there unless you specifically enabled HVCI or applied the Microsoft blocklist manually. That said, Microsoft has been pushing the blocklist to Windows 10 via updates too, so you may see it flagged eventually.
Will reinstalling Windows fix the ENE.sys error permanently?
A clean install removes ENE.sys, yes. But if you reinstall the same RGB software afterward, ENE.sys comes back and the same block applies. The problem comes from the software bundle, not the Windows installation itself. Fix the source by updating the software.
