The timing also matters. On the day Sophos announced its integration, Microsoft said the platform itself had reached general availability. Sophos's announcement is one of the first vendor features on a Windows security platform that is now finished and supported.
What Sophos actually announced
Sophos already blocks known malicious drivers at startup. It does this through Early Launch Antimalware (ELAM), a long-standing Windows feature. The new announcement adds an optional second method rather than replacing that one.
According to Sophos, Neil Watkiss, its VP of Engineering for Windows products, made these points in the announcement:
- Scope: customers running Windows 11
- Timing: starting in Q4 2026, with no exact date or product version given
- What it does: blocks malicious or untrusted drivers as Windows starts
- How it identifies drivers: by a unique digital fingerprint of each driver file, so renaming a malicious driver won't get it past the check
- Deployment model: customers choose whether to adopt the new method or keep their current startup protection
- Visibility: Sophos Fusion logs every startup block, and Endpoint Self Help, the Sophos troubleshooting tool, shows the installed driver version and the active policy settings
Sophos also says its latest Endpoint release includes drivers that Microsoft has certified and signed through the Windows Hardware Compatibility Program (WHCP). That signature shows the drivers passed the program's compatibility tests. It also lets Windows confirm that Sophos published them and that nobody has modified them.
The announcement leaves several things out:
- the fingerprint algorithm
- how Sophos decides which drivers are malicious or untrusted
- whether admins can write their own allow or deny rules
- how false positives are handled
- which licence tier includes the feature
- the specific Windows 11 build required
Admins should look for those answers in Sophos's release notes before rolling the feature out widely.
Section summary: This is a new, opt-in way of blocking drivers at boot on Windows 11. Sophos already had boot-time driver blocking, and the existing method remains available.
The old method: how ELAM works
Malware that loads as a driver can be running before most security software starts. Microsoft has addressed that problem since Windows 8 and Windows Server 2012, when it introduced ELAM.
Microsoft's Defender documentation explains how it works:
- An antimalware driver starts before other boot-start drivers.
- It checks each of those drivers.
- It helps the Windows kernel decide whether to load them.
Microsoft lists support as Windows 8 or later and Windows Server 2012 or later. ELAM's behaviour can be set through Group Policy under Computer Configuration > Administrative Templates > System > Early Launch Antimalware > Boot-Start Driver Initialization Policy.
Keep the two Windows support ranges separate. ELAM goes back to Windows 8, but Sophos names only Windows 11 for the new method. Windows 10 machines, and any servers you were hoping would get the new approach, aren't covered by what Sophos has announced.
Microsoft's platform reaches general availability
The bigger news is the platform underneath the Sophos feature. In its Ignite 2026 Windows post, Microsoft said that the Windows endpoint security platform is generally available. It lets security providers move critical protections from kernel mode to user mode, making Windows more resilient while preserving the protection customers expect.
Here is how the platform got there:
| Milestone | What happened |
|---|---|
| November 2024 | Microsoft launched the Windows Resiliency Initiative (WRI), whose goal is to enhance the resilience and reliability of the Windows platform |
| September 2024 summit onward | Sophos says it has worked with Microsoft on the platform since the Windows Endpoint Security Ecosystem Summit |
| June 2025 | Microsoft released the first private preview of the Windows endpoint security platform, which shifts AV enforcement from the kernel to user mode |
| November 17, 2026 | Microsoft declares general availability, and Sophos announces its first integration |
Sophos is one of several vendors involved. Windows Report lists partners including Bitdefender, CrowdStrike, ESET, SentinelOne, Sophos, Trellix, and TrendAI. SecurityWeek's earlier coverage also named WithSecure among the vendors Microsoft was working with.
The CrowdStrike outage behind all this
This effort followed the July 2024 CrowdStrike outage, when a faulty update to kernel-level security software crashed Windows machines around the world. SecurityWeek reported at the time that Microsoft has since been working with endpoint security vendors such as CrowdStrike, Bitdefender, ESET, SentinelOne, Sophos, Trellix, Trend Micro and WithSecure to find ways to improve reliability but without sacrificing security capabilities.
Microsoft has described the goal plainly: running AV in user mode prevents bugs from taking down Windows, instead impacting only the AV app, while preserving AV functionality and AV partners' ability to innovate.
Sophos makes the same argument. With less security code inside the kernel, a failure is less likely to affect the whole device. Sophos also says Windows includes recovery mechanisms meant to restore the system if a security product or protection rule causes a problem during startup. Sophos doesn't explain how that recovery works, and neither the recovery mechanisms nor user-mode design guarantees that a boot will never fail. The case is that the risk should be lower, not gone.
Should you turn it on? A sensible pilot plan
Sophos recommends a staged rollout and gives the outline. The following plan uses only what Sophos has published. Sophos hasn't released policy names or console steps yet, so none are invented here.
- Wait for the release. Check that the Sophos Endpoint build with the new method has reached your tenant. Sophos only says "starting in Q4 2026."
- Pick a small Windows 11 pilot group. Include machines with unusual hardware: docking stations, specialist peripherals, older storage controllers and VPN clients. Those are the devices most likely to load drivers you don't normally think about.
- Check each pilot machine with Endpoint Self Help. Confirm the installed driver version and that the new policy is active.
- Review Sophos Fusion after reboots. Every startup block is logged, so look at what was blocked and confirm none of it was legitimate business software.
- Widen the rollout gradually. If the pilot runs cleanly, add more devices in stages. If it doesn't, you can stay on the existing protection.
The main operational risk is a false positive. A legitimate but obscure driver flagged as "untrusted" could leave a device booting without its storage, network or a specialist peripheral. Sophos hasn't said how this new method treats such drivers, and the pilot is where you find out.
Caveats and open questions
Vendor claims are vendor claims. Sophos's figure of more than 300,000 organizations using Sophos Endpoint, and CTO John Peterson's statement that the feature strengthens startup protection while reducing the risk that an update disrupts a device, are the company's own claims. Neither has been independently measured.
Outside researchers are still examining the platform. In October, Elastic Security Labs published an analysis of the components that had appeared in Insider builds. It described a kernel driver, wesp.sys, built by Microsoft, and a user-mode API implemented in espclient.dll that EDR's user-mode service would use to connect and receive notifications of interest. In that pre-release code, the researchers found signs that user mode might not be able to block some events, such as process creation. That analysis covered an Insider build and was not about Sophos's boot-driver feature, so it doesn't show any weakness in what Sophos announced. It does show that what vendors can do from user mode is still being worked out publicly. Expect more of this analysis now that the platform is generally available.
The kernel isn't being emptied. Microsoft's own driver, wesp.sys, still runs in the kernel. Sophos is also still shipping kernel drivers, now WHCP-signed. The change is about how much third-party code runs in the kernel, not removing kernel code altogether.
The bottom line
The announcement is modest on its own: one opt-in feature, on one Windows version, arriving at some point this quarter. It still matters because it is a working example of the design change Microsoft started after CrowdStrike. Security vendors get access to the boot process through a Microsoft-built layer, and their own kernel code shrinks.
For Sophos customers on Windows 11:
- Nothing changes until you opt in.
- When the new method arrives, test it on a small group first.
- Check Fusion logs and Endpoint Self Help before expanding.
- Ask Sophos about false-positive handling and licensing before rolling it out widely.
For everyone else, other vendors are likely to make similar announcements. Bitdefender, CrowdStrike, ESET, SentinelOne, Trellix and TrendAI have all worked with Microsoft on the platform, so similar boot-protection and user-mode features will probably follow from them.
References
- Sophos Endpoint Now Blocks Malicious Drivers at Windows Startup - Sophos Sophos · 2026-11-17T00:00:00+00:00
- Microsoft to Preview New Windows Endpoint Security Platform After CrowdStrike Outage - SecurityWeek securityweek.com
- Windows Endpoint Security Platform: Inside wesp.sys elastic.co