The December 2025 Patch Tuesday update (KB5072033) for Windows 11 (versions 24H2 and 25H2) has introduced unexpected performance issues for many users. While intended to fix 56 security vulnerabilities, the update has caused significant system sluggishness, high resource consumption, and in some cases, system freezes. This article explains the technical root of the problem and provides potential workarounds.
The primary cause of the slowdown is a change in the AppX Deployment Service (AppXSVC) behavior. Previously, this service—which handles Microsoft Store app installations and updates—was set to "Manual (Trigger Start)," meaning it only ran when needed.
With update KB5072033, Microsoft has switched this service to "Automatic." Consequently, the service now launches immediately upon system boot and stays active in the background. For many users, especially those on lower-end hardware or systems with limited RAM, this results in:
Additionally, some users have reported that the Delivery Optimization service is also spiking in memory usage (in some extreme cases up to 20GB) following this update.
Since Microsoft has not yet released a "revert" patch, users are currently using the following methods to restore speed:
1. Disable "Allow downloads from other PCs"
This helps if Delivery Optimization is the cause of your RAM drain:
2. Reset the AppX Package via PowerShell
If the Store service is stuck in a loop:
3. Uninstall the Update (Last Resort)
If the system is unusable, you can roll back the update:
The Windows 11 December 2025 update is a classic example of a security "fix" creating a usability "break." By forcing the AppX Deployment Service to run at startup, Microsoft inadvertently hindered performance for millions of users. Until a follow-up "Cumulative Update Preview" is released (likely in early January 2026), toggling off Delivery Optimization is the safest way to maintain performance.
Comments & Ask Questions
Comments and Question
There are no comments yet. Be the first to comment!