The latest version of Windows 11, 24H2, is now officially available and is rolling out gradually. Microsoft is calling this a “full operating system replacement,” so it’s no surprise that there were a few issues that had to be addressed. However, the latest one is equipped with CrowdStrike’s Falcon sensor, the security software responsible for the worldwide IT outage in July.
According to Microsoft (By PC World), “after installing Windows 11 24H2, first-party and third-party applications may stop responding when anti-malware solutions enable certain features. “Office applications such as Word and Excel may be affected.”
While Microsoft says the issue is related to “antimalware solutions,” it explains that “affected devices have CrowdStrike’s Falcon sensor software” and certain policy settings are enabled.
To support address the issue for now, Microsoft says CrowdStrike has “temporarily disabled the Enhanced Exploit Prevention Policy setting on Windows 11 24H2 hosts.”
In the longer term, the two companies are “collaborating on a solution.”
Prior to this interim fix, organizations using CrowdStrike Falcon as a cybersecurity solution were apparently experiencing crashes in Office applications such as Word or Excel when updating their systems to 24H2.
I say “organizations” and not “home users” because CrowdStrike Falcon is designed primarily for organizations, so most home users don’t have to worry about their personal devices being affected. It’s a cloud-based anti-malware solution that monitors systems and networks for possible malicious activity – an endpoint detection solution (EDS).
Earlier this year, a Falcon software update that was bypassed by a faulty content checker caused memory readings to be exceeded on Windows computers, ultimately leading to BSOD errors on computer systems around the world. It was one feeble link in the chain that led to chaos.
Fortunately, the latest problem isn’t like that: it only causes crashes in certain Office programs, and it already has a fleeting solution, even if it involves completely disabling the problematic policy setting. And to be clear, we don’t know if this latest issue is more the fault of Microsoft, CrowdStrike, neither, or both.
All we know is that 24H2 is already being implemented it wasn’t completely polished. And despite some frigid but non-revolutionary features – file dragging improvements in File Explorer and a Wi-Fi refresh button, anyone? – unless I’m someone who goes all in on the AI computer hype, I’ll probably stick with 23H2 for now.
But that’s just me. For those of you who are more adventurous than me – well, that is, as soon as the update rolls out for your device and location.
