Microsoft has quietly removed the ability to permanently disable automatic app updates in the Microsoft Store on Windows 10 and 11 for many consumer users. Instead, the Store now only offers time-limited pause options of one to five weeks, after which updates resume automatically. The change was first widely noticed in mid-August 2025 and marks a significant shift in how the company balances user control against security and maintainability.

The long-standing toggle labeled “Update apps automatically” no longer functions as an indefinite off switch for a growing number of users. When someone attempts to turn updates off, the Store now presents a set of pause durations—commonly one, two, three, four, or five weeks. Once the chosen period ends, the Store re-enables updates without further notice, silently downloading and installing new versions of installed apps.

A Deliberate Push Toward Automation

Microsoft’s decision did not come with a formal announcement or a dedicated support document. Instead, it was delivered through a client-side update to the Microsoft Store app itself, which means the behavior can vary by device, Windows edition, and region. Community reports and technology outlets confirmed the new behavior on both Windows 11 and Windows 10 devices running updated Store clients, though some managed environments and devices with specific policies still retain the classic toggle.

The reasoning appears threefold. First, security. Outdated apps increase the attack surface, and automatic updates shrink the window during which known vulnerabilities linger. Microsoft has long championed automated patching as a cornerstone of Windows security, and this move extends that philosophy to the app layer. Second, reliability and compatibility. Keeping Store apps current reduces version mismatches with the operating system and ensures that bug fixes reach users promptly. Third, supportability. When freshly imaged machines ship with stale inbox apps, helpdesks and end-users encounter avoidable issues. Forcing a regular update cadence reduces fragmentation and support costs.

Those motivations are technically sound. Yet the change also strips away a control that many users have relied on, sometimes for years, and introduces practical headaches for specific scenarios.

What the Change Looks Like in Practice

In earlier versions of the Store, opening Settings and flipping “Update apps automatically” to Off would stick—app updates would cease until the user manually re-enabled them. Now, on affected devices, the UI replaces that binary choice with a pause menu. Users must pick a duration: 1 week, 2 weeks, 3 weeks, 4 weeks, or 5 weeks. After the pause expires, the Store automatically re-enables updates and begins downloading any pending updates for installed apps.

Crucially, this is not a policy enforced by Windows itself but a behavioral change in the Store client. It can be overridden by administrative policies in managed environments, but for home users without access to Group Policy, the only way to stop updates permanently is to bypass the Store entirely or rely on unsupported workarounds.

The change is not yet universal. Some users report that the old toggle still works, particularly on devices that have not received the latest Store update or where other policies are in effect. Because the rollout is client-driven, the experience can differ even between two similarly configured machines. Microsoft has not publicly acknowledged the rollout as a change of policy, leaving many to wonder whether it is a permanent shift or an experiment.

Impact Across User Groups

Home Users and Casual Consumers

Most home users will likely benefit from fewer update decisions. Their apps will stay current without any action, reducing the risk that they run outdated software with known flaws. For the average person who never touched the toggle, nothing changes. But for those who intentionally disabled updates—whether to conserve bandwidth, avoid change, or maintain a specific app version—the new behavior is a rude surprise. A temporary pause of up to five weeks may not be enough for someone on a capped data plan who only wants to update over Wi-Fi or who needs a stable environment for a school project.

Power Users and Developers

The loss of a permanent off switch is felt acutely here. Testers who maintain virtual machines with exact app versions for reproducibility now face an additional administrative task. Developers who need to debug against a specific build of a Store-distributed app may find their carefully constructed environment altered by a background update. While power users can employ workarounds—such as setting a network connection as metered or using Group Policy on Windows Pro—these are blunt instruments that also affect other system behaviors.

IT Administrators and Enterprise

Enterprise environments remain insulated from the UI change. Group Policy, Intune, WSUS, and registry-based policies still allow administrators to control Store updates with precision. For organizations that need to lock app versions for compliance or stability, the “Turn off Automatic Download and Install of updates” policy under Windows Components > Store remains authoritative. The shift will, however, increase helpdesk calls from users on unmanaged devices who suddenly find updates re-enabled after believing they had turned them off permanently. Clear internal communication will be essential.

Supported Workarounds and Their Trade-offs

Even without the permanent toggle, several legitimate methods remain to control Store updates. Each comes with caveats.

Metered Network Connection

Setting a Wi-Fi network as metered (Settings > Network & Internet > select network > Set as metered connection) reduces background data usage, including some Store update activity. It is the easiest option for home users on limited data plans. However, it is a blunt tool: it can also throttle Windows Update, live tile updates, and other services. It will not freeze apps at a specific version—once the computer connects to an unmetered network, updates may still flow.

Group Policy (Windows Pro, Enterprise, Education)

This is the recommended method for persistent, managed control. Using the Local Group Policy Editor (gpedit.msc), an administrator can enable “Turn off Automatic Download and Install of updates” under Computer Configuration > Administrative Templates > Windows Components > Store. The setting applies machine-wide and prevents the Store from automatically updating any app. After applying the policy (gpupdate /force), the Store’s automatic updates toggle becomes grayed out or reflects policy control. This is the only officially supported way to permanently disable auto-updates without side effects.

Registry Policy

For advanced users or scripts, the same policy can be applied via the registry. Running the following command from an elevated prompt sets the AutoDownload value to 2, disabling automatic downloads:

reg add HKLM\SOFTWARE\Policies\Microsoft\WindowsStore /v AutoDownload /t REG_DWORD /d 2 /f

This registry key lives under the Policies hive, which means the Store treats it as authoritative and respects it across client updates. Still, editing the registry carries risk; it should only be done by those comfortable with the process and on machines where unintended changes can be easily reverted.

Non-Store Installers

Bypassing the Store entirely sidesteps the issue. Many popular applications offer MSI or EXE installers on vendor websites, and the Windows Package Manager (winget) can install and update software outside the Store’s control. The trade-off is a loss of the Store’s sandboxing and verified delivery guarantees. In regulated or high-security environments, this may be a poor alternative.

Firewall rules that block Store endpoints can stop updates, but they are brittle and can break app functionality, Store licensing, and background tasks that rely on Store services. This approach is unsupported and can lead to subtle failures.

Security and Compliance Implications

Automatic updates are a proven security best practice. They reduce the time that known vulnerabilities remain exploitable and help ensure that users receive patches for critical bugs. From a platform perspective, forcing regular updates makes the entire Windows ecosystem safer.

However, automatic resumption of updates after a pause can create compliance challenges for regulated industries. If a certified application version must remain unchanged for audit purposes, an unexpected update can trigger a review. Security teams must also account for automatic app updates when performing forensic analysis; an app’s telemetry and behavior can change between two incidents, complicating root cause identification.

For the average user, the security upside is clear. For organizations, the existing policy controls ensure that the change does not weaken their ability to manage risk—so long as those controls are correctly configured.

Risks and Secondary Effects

The sudden, unannounced nature of the change risks eroding trust. Windows users have long expected that a toggle labeled “Update apps automatically” would obey their preference permanently. Removing that without warning feels like a bait-and-switch. On metered connections, the forced re-enablement after a pause can lead to unexpected data charges. And because the rollout is inconsistent, users may not know whether their device still respects the old toggle or has already switched to the new pause model.

Third-party tools that promise to restore the old behavior are already appearing. Most of them rely on unsupported system modifications that can destabilize the OS, introduce security vulnerabilities, or break after future updates. Users are best advised to avoid such hacks.

The Broader Trend Toward Mandatory Automation

The Microsoft Store change is not an isolated event. It mirrors the long-standing treatment of Windows Update, where Home users have no permanent deferral, only temporary pauses. Microsoft has been steadily reducing the number of levers for consumers to stop automatic patching, both in the OS and now in the Store. The underlying philosophy is that automatic updates are the default healthy state, and deviations should be temporary and managed with administrative tooling.

Other platform vendors have made similar moves. Apple’s iOS App Store updates can be paused temporarily, but the system will eventually prompt or install updates. Google’s Play Store auto-updates can be turned off, but the OS and security patches are increasingly automated. The industry trend is clear: automatic updates are table stakes for security, and granular user control is being relegated to managed environments.

Looking Ahead

This rollout is likely to continue in stages, with the new pause model eventually reaching most consumer devices. Microsoft may refine the UI further—perhaps adding granular per-app controls or longer pause windows—based on user feedback. In the meantime, the path forward depends on who you are. Casual users can simply let automatic updates run; the system will keep apps fresh without intervention. Power users who need a static environment should adopt Group Policy if on a supported edition or switch to non-Store installers for critical apps. Enterprises should audit their management policies to ensure that Store update behavior aligns with their security and compliance requirements, then communicate the expected behavior to their workforce.

The loss of the permanent toggle is a trade-off: a less controllable experience in exchange for a more consistently secure and stable app landscape. Whether that bargain is acceptable will depend on each user’s needs, but the direction Microsoft is heading is unmistakable.