20 July 2024
A small percentage of Windows, an enormous disruption
Microsoft estimated that the faulty update affected 8.5 million Windows devices: less than one per cent of Windows machines. The impact was outsized because affected organisations ran services that many other people depended on.
Microsoft described engineers, recovery guidance and collaboration with other cloud providers to bring systems back. That was recovery work, not a claim that every interrupted journey or appointment had already been repaired.
29 July 2024
Machines returned; the losses did not disappear
CrowdStrike later said roughly 99 per cent of Windows sensors were online by 29 July compared with the pre-incident baseline. It noted normal week-to-week variation of about one per cent.
That company-reported connection measure is not a census proving every business recovered or every loss was paid. The story was moving from getting computers running to explaining what failed.
6 August 2024
The mismatch that testing missed
CrowdStrike’s technical report described a template defining 21 inputs while the code supplied 20. A new content update exposed the mismatch, leading to an out-of-bounds memory read and a system crash. Validation and testing had not caught that combination.
This was a failure in CrowdStrike’s update and its handling by the Windows sensor. It should not be confused with Microsoft having released that content, or with evidence of a hostile attack.
6 August 2024
Updates would reach customers in stages
CrowdStrike’s executive summary marked broader testing and successive deployment rings as completed, alongside added customer controls. Other checks and releases still had future dates in that document; those promises need to keep their original status.
ABC’s later account of congressional testimony described the shift from simultaneous global rollout to staged rings. These are reported process changes, not an independent guarantee against every future outage.
CrowdStrike · completed and planned changes · 6 August 2024 · ABC News · congressional testimony · 25 September 2024
14 January 2026
One dismissal did not settle every claim
Reuters reported that a judge dismissed shareholders’ fraud lawsuit because the pleading did not adequately establish the required misleading statements and intent, while permitting an attempt to amend.
That was an investor case. It was not a general finding that the software worked correctly, nobody suffered loss or all passenger and airline claims had ended.
20 May 2026
Passengers lost an appeal, then sought further review
The Fifth Circuit affirmed dismissal of the passenger case on 20 May; rehearing was denied on 15 June. The orders appear in the Supreme Court petition’s appendices. The underlying dispute concerns whether federal airline law pre-empts these state-law claims against the supplier.
The passengers filed their petition on 14 September. Asking the Supreme Court to hear a case is not a grant of review or a decision awarding compensation.
Supreme Court · petition and lower-court orders in appendices · September 2026 · Supreme Court · Del Rio docket · checked 28 October 2026
19 October 2026
A response is due; a final answer is not here
The official Supreme Court docket records a request for a response, due on 18 November 2026. At this check it records neither a grant of review nor a final Supreme Court decision.
Separately, CrowdStrike’s SEC disclosure for the quarter ended 31 July described discovery in Delta’s damages case as ongoing. That is a dated company disclosure, not a claim that every later Delta filing was inspected here. Its reported dismissals of other derivative suits also do not settle Delta’s claim. Technical recovery is established; legal accountability has several tracks.
CrowdStrike · litigation disclosure for quarter ended 31 July 2026 · SEC · Supreme Court · Del Rio docket · checked 28 October 2026
The evidence
Sources for this update
- 01Microsoft · recovery · 20 July 2024
- 02CrowdStrike · root-cause report · 6 August 2024
- 03CrowdStrike · recovery account · 6 August 2024
- 04CrowdStrike · completed and planned changes · 6 August 2024
- 05ABC News · congressional testimony · 25 September 2024
- 06Reuters · shareholder lawsuit · 14 January 2026
- 07CrowdStrike · litigation disclosure for quarter ended 31 July 2026 · SEC
- 08Supreme Court · petition and lower-court orders in appendices · September 2026
- 09Supreme Court · Del Rio docket · checked 28 October 2026
Where the story stands
The systems recovered. The claims took separate paths.
The passenger petition remains a request for review, with a response due on 18 November. The inspected docket has no final Supreme Court outcome. Delta’s separate claim needs its own record. Research checked 28 October 2026.