Windows Server 2025 memory management update leads to application instability
Microsoft has disclosed a known issue in Windows Server 2025 where recent memory management alterations cause applications using Address Windowing Extensions (AWE) to crash or terminate unexpectedly. The problem notably affects SQL Server when the Lock Pages in Memory policy is enabled, leading to access violations and memory corruption errors. As a temporary workaround, administrators can disable the LPIM policy, while a permanent fix is being developed for a future Windows update.
The instability stems from a shift in how Windows Server 2025 handles physical memory allocation for 32-bit applications. Specifically, SQL Server instances configured with the Lock Pages in Memory policy are prone to severe failures, including database integrity checks aborting and service processes crashing repeatedly.
Microsoft advises administrators to temporarily disable the LPIM policy, though this trade-off may degrade database performance. A permanent resolution is slated for a future patch. This is not the first post-release hiccup for the server OS, as earlier updates in 2026 caused installation failures and BitLocker recovery loops.
Organizations relying on Windows Server 2025 for critical database operations could face significant operational disruptions. If administrators disable LPIM to prevent crashes, they may see reduced database throughput, potentially affecting transaction speeds for enterprise applications. Conversely, ignoring the issue could lead to unexpected service outages and data integrity risks during maintenance. This trade-off may force IT teams to expedite patch testing and deployment cycles, impacting business continuity planning.