Windows 11 24H2 did not make every application fail on computers running CrowdStrike Falcon Sensor. Some systems did experience application freezes or launch failures after particular updates, policies, or driver interactions. The best-documented example is ScanSnap Home after the April 8, 2025 update KB5055523. That is separate from the July 19, 2024 CrowdStrike outage, which primarily caused Windows blue screens and reboot loops.
Start by matching the symptom to the incident
“Apps stopped working” can describe several different failures. Identify which pattern you have before changing security settings:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
| Observed symptom | Most useful first investigation |
|---|---|
| One application will not launch or freezes during a particular operation | Check the application version, Windows build, recent KBs, Falcon policy events, and the application vendor’s advisory. |
| Only ScanSnap Home fails after KB5055523 | Follow PFU/Ricoh’s CrowdStrike-specific guidance for that application. |
| Several unrelated applications freeze | Investigate drivers, Windows servicing, resource exhaustion, and security-policy events rather than assuming Falcon is the cause. |
| Blue screen followed by repeated restarts | Investigate the July 2024 Falcon content incident or another kernel/driver fault; ordinary application troubleshooting is not sufficient. |
| Falcon services show stopped | Escalate to the organization’s security administrator. Do not delete or alter sensor files yourself. |
CrowdStrike lists Windows 11 24H2 as a supported operating system for Falcon Sensor, so there is no evidence of a blanket 24H2/Falcon incompatibility. Support for the operating system does not guarantee that every application, driver, protection policy, or Windows cumulative update will work together without defects. See CrowdStrike’s Falcon FAQ and Microsoft’s Windows 11 24H2 status page.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →What happened, and when?
July 19, 2024: the separate CrowdStrike outage
CrowdStrike began distributing a faulty Falcon Sensor content/configuration update to Windows hosts at 04:09 UTC on July 19, 2024. The affected sensor range included Falcon Sensor for Windows 7.11 and later on systems that received the content during the distribution window. CrowdStrike identified the reverted, good channel-file timestamp as 05:27 UTC or later. The failure produced kernel crashes, commonly reported as bugchecks 0x50 or 0x7E, followed by continual restarting—not merely one application refusing to open.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Read CrowdStrike’s technical explanation, its July 19 technical alert, and Microsoft’s KB5042421 recovery guidance. Windows 11 24H2 was released later, beginning general availability on October 1, 2024, so that outage was not caused by upgrading to 24H2.
April 8, 2025: KB5055523 and an application-specific report
Microsoft’s April 8, 2025 security update, KB5055523, moved Windows 11 24H2 to OS build 26100.3775. PFU/Ricoh then documented that ScanSnap Home may not work properly for CrowdStrike users when KB5055523 is installed. PFU directs affected administrators toward Sensor Visibility Exclusions (SVE) for the relevant ScanSnap Home modules.
This is evidence of a narrow Windows-update/application/Falcon interaction. It does not establish that KB5055523 broke Office, browsers, or every third-party application.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to confirm your Windows build and recent update
- Press Win + R, enter
winver, and record the Windows version and OS build. - Open Settings → Windows Update → Update history.
- Record recently installed cumulative updates, including whether KB5055523 is present.
- Record the affected application’s exact name and version, and the time the failure began.
- Note whether Falcon is active and whether the computer is managed by your employer or an IT provider.
Capture Event Viewer and application error details before uninstalling anything. A reproducible timestamp helps administrators correlate the failure with Falcon detections, prevention actions, Windows servicing, or application logs.
How administrators can check Falcon status
CrowdStrike’s sensor-repair documentation lists these read-only service checks:
sc.exe query csagent
sc.exe query csfalconserviceThe Falcon tray icon may also show driver and service state. A STOPPED state can be relevant to a repair case, but these commands are diagnostic—not a universal fix for frozen applications. The Falcon sensor-repair guide warns that repair procedures are not for operational sensors. Do not stop, delete, rename, or manually modify Falcon files unless your organization or CrowdStrike support directs you.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Safe troubleshooting order
- Preserve evidence. Record the build, KB, Falcon Sensor version, application version, timestamps, symptoms, and relevant logs.
- Restart once and reproduce. A one-time hang may be unrelated to the update or sensor.
- Check the application vendor. Look for a compatibility notice or a newer application/driver release.
- Contact the Falcon administrator. Ask whether the endpoint is in a prevention policy, sensor policy, or visibility-exclusion group and whether Falcon recorded a block.
- Install approved updates. Apply tested Windows, Falcon, application, and driver updates through normal change control.
- Evaluate a rollback only with authorization. If the issue began immediately after a Windows update, an administrator can assess staged removal or rollback under the organization’s recovery process.
- Use dedicated recovery guidance for blue screens. Boot loops require Microsoft/CrowdStrike recovery procedures, and may require BitLocker keys or physical/console access.
When a Falcon exclusion is justified
For the ScanSnap case, PFU’s advisory points CrowdStrike administrators to Sensor Visibility Exclusions for affected ScanSnap Home modules. An SVE is not a general “turn Falcon off” switch, but it does reduce inspection or visibility for the specified items.
- Use exclusions only when the application vendor documents them or the security team approves them.
- Scope them to the exact modules or processes; avoid broad paths, wildcards, and user-profile directories.
- Test on a non-production device first, log the change, and review an expiry or removal date.
- Remove the exclusion after the application or sensor vendor supplies a permanent fix.
Do not publish or apply a guessed ScanSnap module list. Obtain the current list from PFU/Ricoh or your CrowdStrike administrator.
July 2024 outage versus 24H2 application failures
| July 2024 CrowdStrike outage | Windows 11 24H2 application compatibility |
|---|---|
| Faulty Falcon content/configuration update | Potential interaction among a Windows update, application, driver, Falcon policy, or protection feature |
| Blue screens and reboot loops, including 0x50 or 0x7E | Application launch failures, freezes, or hangs during operations such as scanning or file access |
| Associated with Falcon channel file C-00000291 and the July 19 distribution window | Often requires identifying the exact Windows build, application, sensor version, and policy |
| Microsoft KB5042421 recovery instructions apply | Vendor-specific troubleshooting and controlled compatibility testing apply |
| Not caused by Windows 11 24H2 | May involve Windows 11 24H2, but is not a universal 24H2/Falcon failure |
Other 24H2 causes to rule out
Microsoft’s resolved-issues list includes unrelated 24H2 problems involving camera-related application hangs, Easy Anti-Cheat, App Attach, cloud-backed storage, and third-party drivers such as sprotect.sys. A failure that occurs on a Falcon-protected machine is not automatically a Falcon defect. A successful temporary exclusion test shows an interaction is possible; it does not by itself prove root cause.
When to contact IT, CrowdStrike, or the application vendor
- The computer blue-screens, loops at startup, or requests BitLocker recovery.
- You lack administrator rights or a Falcon maintenance token.
- Multiple endpoints show the same symptom.
- A security exclusion is being considered.
- Falcon services cannot be repaired or show unexpected state.
- Logs indicate a kernel or driver fault.
- The application vendor has issued a specific compatibility advisory.
Home users should not uninstall Falcon to test a theory. It is normally organization-managed, and removing it may violate policy or require authorization.
Bottom line
The correct diagnosis depends on the exact Windows build, installed KB, Falcon Sensor version, application, policy, and symptom. Treat an app-only freeze as a targeted compatibility investigation. Treat a blue screen or reboot loop as a potential July 2024 Falcon content incident or another kernel failure, and use the dedicated recovery process instead of broad exclusions or manual sensor-file changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
