CrowdStrike and Windows are *gulp* having problems again but thankfully just with 24H2 and just in some Office programs

Windows 11’s latest build, 24H2, is officially here and rolling out gradually. Microsoft calls it a “full OS swap“, so it’s no surprise that there have been a fair few kinks to work out. The latest one of these, however, is with none other than CrowdStrike’s Falcon sensor, the security software responsible for the worldwide IT outage back in July.

According to Microsoft (via PC World), “after installing Windows 11, version 24H2, first and third-party apps might stop responding when antimalware security solutions enable certain features. Office applications such as Word and Excel might be affected.”

Although Microsoft says the problem is with “antimalware security solutions”, it clarifies that “affected devices have CrowdStrike’s Falcon sensor software” and a particular policy setting enabled.

To help fix the issue for the time being, according to Microsoft, CrowdStrike has “temporarily disabled the Enhanced Exploitation Visibility Prevention Policy setting on hosts running Windows 11, version 24H2”.

In the longer term, the two companies are “collaborating on a solution”.

Prior to this temporary fix, organisations using CrowdStrike Falcon as their cybersecurity solution were apparently facing crashes in Office applications such as Word or Excel if their systems upgraded to 24H2.

I say “organisations” rather than “home users” because CrowdStrike Falcon is primarily for organisations, so most home users’ won’t need to worry about their personal devices being affected. It’s a cloud-based antimalware solution that monitors systems and networks for possible malicious activity—an Endpoint Detection Solution (EDS).

Earlier in the year, an update for the Falcon software, which was passed over by a buggy Content Validator, caused out-of-bounds memory reads on Windows machines and ultimately resulted in BSODs on computer systems across the world. It was one weak link in the chain that led to chaos.

Thankfully, this latest issue is nothing like that: it’s caused crashes in just some Office programs and does already have a temporary fix, even if that fix is to disable the problematic policy setting entirely. And to be clear, we don’t know whether this latest issue is more the fault of Microsoft or CrowdStrike, or neither, or both.

What we do know is that 24H2’s roll-out hasn’t been completely smooth. And despite it having some neat but non-revolutionary features—File Explorer file dragging improvements and a Wi-Fi refresh button, anyone?—unless I’m someone who’s going all-in on the AI PC hype I’m probably sticking with 23H2 for now.

That’s just me, though. Those of you more adventurous than I can have at it—well, as soon as the update rolls out for your device and location, that is.