Diagnostic finding
A restart is pending
This check reads three places where Windows records work it can only finish during a restart. If any of them is set, the scan says so before anything else is diagnosed.
A restart is pending
Repairs run against a machine with a pending restart frequently produce misleading results. Restart before further diagnosis.
REASONS is one or more of: a pending file rename, component servicing, Windows Update.
Windows has work it can only finish during a restart, usually after installing an update or a program. Until it restarts, some files on disk are not yet the files Windows will be using, and a scan or a repair reads a half-finished state.
What to do
- Save your work and close your programs.
- Choose Restart from the Start menu. Do not use Shut down: with Fast Startup turned on, which is the Windows default, Shut down does not fully restart Windows.
- Run the scan again. If the same message comes back after a restart, the next section shows which of the three reasons it is.
What the check reads
Each command checks one of the three reasons. Run them in PowerShell opened as administrator. They read the registry and change nothing.
Component servicing: Windows has staged a change to its own system files.
Test-Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending'Windows Update: an update has installed and is waiting for a restart.
Test-Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired'A pending file rename: a file was in use and is queued to be replaced at the next restart.
Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager' -Name PendingFileRenameOperations -ErrorAction SilentlyContinueTrue that reason is pending (first two commands)
False that reason is not pending (first two commands)
Any output a file rename is queued (third command)
No output no file rename is queued (third command)If it comes back after every restart
A pending file rename that returns every time is usually a program, often security software or an updater, queuing new work each time Windows starts. On its own that is not a fault. Component servicing or Windows Update that will not clear after two restarts usually means an update is failing to finish, which is a different problem and worth a look.
What this page is based on
Observed or documented
- The three registry locations above are the ones the diagnostic tool reads, and Windows sets them when work is waiting for a restart.
Our judgement
- Using Restart rather than Shut down is standard practice, because Fast Startup keeps part of the previous session when Windows shuts down.
- That repairs on a machine with a pending restart give misleading results is bench experience, not a measured rate.
- That a file rename which keeps returning is usually harmless is our experience. It is not true of every machine.
When this is worth a call
Call us if component servicing or Windows Update is still pending after two restarts, or if the computer will not finish restarting.
Reviewed November 4, 2026 · Applies to Windows 10 and Windows 11 · Finding system.pending_reboot, wording from Connected Geek Diagnostic Tool 0.9.28