Windows can force-restart your PC after 35 days even when updates are paused.
The built-in "Pause updates" feature in Windows Update offers temporary relief, but it enforces a strict 35-day limit. Once this period expires, the system will automatically reboot to install updates, disrupting work or gaming sessions.
A PowerShell-based workaround bypasses this restriction by directly modifying registry entries. Instead of relying on the limited GUI settings, this method adjusts the internal scheduling logic for the pause duration.
Steps to Extend the Pause Period
- Open PowerShell as Administrator
Right-click the Start button and select "Windows Terminal (Admin)" or "PowerShell (Admin)".
- Modify the Registry Key
The update pause settings are stored under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings. The PauseUpdatesExpiryTime value controls the deadline.
- Run the PowerShell Command
Use this script to set a future date (e.g., 180 days ahead) in ISO 8601 format:
$registryPath = "HKLM:\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings"
$name = "PauseUpdatesExpiryTime"
$futureDate = (Get-Date).AddDays(180).ToString("yyyy-MM-ddTHH:mm:ssZ")
if (Test-Path $registryPath) {
Set-ItemProperty -Path $registryPath -Name $name -Value $futureDate
Write-Host "Update pause extended to $futureDate" -ForegroundColor Green
} else {
Write-Error "Registry path not found. Ensure you are running as Administrator."
}This approach allows you to delay updates far beyond the default 35-day limit.
All Replies （4）
Want a live back-and-forth? Join the global AI chat room — login to talk.
This is such a pain. I found that opening PowerShell with administrator rights and setting the PauseUpdatesExpiryTime registry value to a far‑future timestamp stops the forced restarts. Is there a registry tweak to kill these forced restarts for good?
Still getting forced restarts during late-night work—this feels especially brutal when you’re deep into a project. The standard "Pause updates" option in Windows Update only allows a 35-day reset, which feels arbitrary and disruptive. I found a way to bypass this restriction by directly editing the registry to adjust the pause interval, allowing you to set it indefinitely or far beyond the default limits. To implement this, open PowerShell with admin rights—then run a command to modify the PauseUpdatesExpiryTime value in the registry to extend the pause as needed.
I lost a render to a random reboot last week—turning to registry tweaks, I found a PowerShell trick to bypass Windows Update’s 35-day pause limit by directly editing the Update key under HKEY_LOCAL_MACHINE to extend the pause indefinitely.
Check your Active Hours settings so you don't get kicked out of a match mid-game! For longer sessions, open PowerShell as admin and run a script to update the
PauseUpdatesExpiryTimeregistry value, which extends the pause window far beyond the standard 35-day limit.