Skip to content
NewA calmer, faster ZeroHour
Advisorymedium

Microsoft: Windows Server 2025 changes causing app crashes

BleepingComputerby Sergiu Gatlan ()2 min read3
AI summary · glm-5.3Summaries by Vani AI

Microsoft warns Windows Server 2025 memory-management changes crash AWE apps, including SQL Server with Lock Pages in Memory; disable LPIM as workaround.

Microsoft confirmed a known issue where Windows Server 2025 memory-management changes cause access violations, memory corruption, or unexpected termination in applications using Address Windowing Extensions (AWE). SQL Server running with the Lock Pages in Memory (LPIM) policy is affected, with symptoms including 0xC0000005 access violations, DBCC CHECKDB failures, crash dumps, and services stopping or restarting unexpectedly. Microsoft's temporary workaround is to disable the LPIM policy for the SQL Server service account or disable AWE in other affected apps, with a permanent fix promised in a future Windows update.

Key facts
  • Windows Server 2025 memory-management changes break apps using Address Windowing Extensions (AWE)
  • SQL Server with Lock Pages in Memory policy hit by 0xC0000005 errors and unexpected crashes
  • Workaround: disable LPIM for SQL Server service account or disable AWE; permanent fix pending
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

2 min read at bleepingcomputer.com

Microsoft warned customers last week that they may experience application crashes on some Windows Server 2025 due to recent memory management changes. [...]

BleepingComputer

By Sergiu Gatlan · bleepingcomputer.com

Read the full article at BleepingComputer

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.