Windows schedules defragmentation, scans and update work into a maintenance window that defaults to the middle of the night. On a machine that is switched off at night, it lands in your working hours instead.
Change **ActivationBoundary** under **Schedule\Maintenance** to a time you choose, set **WakeUp** only if you accept a nightly wake, and verify with the **Maintenance Configurator** task.
The settings live under **HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\Maintenance**. **ActivationBoundary** is the start time in 24-hour form.
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\Maintenance' |
Select-Object ActivationBoundary,WakeUp,MaintenanceRandomDelay,MaintenanceDisabledMaintenance only starts when the machine is idle, which is why a laptop in use all day never gets its work done. Late evening or early morning while plugged in is the realistic choice.
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\Maintenance" /v ActivationBoundary /t REG_SZ /d "03:00" /f**WakeUp** lets the maintenance window wake a sleeping PC. Useful on a desktop that should do its work at night, pointless on a laptop that lives in a bag.
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\Maintenance" /v WakeUp /t REG_DWORD /d 1 /f
powercfg /devicequery wake_armedThe task starts only when the session is idle for several minutes. A background process that keeps the CPU busy — a sync client, a game launcher — postpones maintenance indefinitely.
Get-ScheduledTask -TaskPath '\Microsoft\Windows\TaskScheduler\' | Select-Object TaskName,State
Get-ScheduledTaskInfo -TaskPath '\Microsoft\Windows\TaskScheduler\' -TaskName 'Regular Maintenance' | Select-Object LastRunTime,LastTaskResult,NextRunTimeStarting the configurator re-evaluates the window and starts the maintenance tasks. Watching it happen now is better than discovering it never ran.
Start-ScheduledTask -TaskPath '\Microsoft\Windows\TaskScheduler\' -TaskName 'Maintenance Configurator'
Start-Sleep -Seconds 20
Get-ScheduledTask -TaskPath '\Microsoft\Windows\TaskScheduler\' | Where-Object State -eq 'Running' | Select-Object TaskNameThe operational log names each maintenance task and its duration. If every run ends with a result code other than zero, the window is not the problem — the task is.
Get-WinEvent -LogName 'Microsoft-Windows-TaskScheduler/Operational' -MaxEvents 20 |
Where-Object Message -match 'Maintenance' | Select-Object TimeCreated,Id,@{n='M';e={($_.Message -split "`n")[0]}}The idle check failed earlier and Windows used the next opportunity. Close the app that keeps the CPU busy, and confirm the new ActivationBoundary value was written as REG_SZ.
Check MaintenanceDisabled, the power plan's wake timers, and whether the machine is on battery with the do-not-run-on-battery setting active.
The wake timer is armed by another task, not by maintenance. Use powercfg /waketimers to see which task asked for the wake.
A previous instance is still running. Let it finish or stop it, then check the task history for the step it hangs on.
No. Updates follow their own schedule. This window only controls background maintenance such as defragmentation, disk checks and scheduled scans.
On a machine with an SSD and a third-party backup, you can reduce it. Leaving it enabled costs nothing if the window fits your day.
Set ActivationBoundary back to the original value you recorded and WakeUp to 0, then restart the Maintenance Configurator task. The default window is 02:00.
Free · no account needed · tracks your progress