An update that sits on “Pending restart” can feel like a loop: you restart, return to Settings, and the same status is still there. Before you delete system folders or run a repair script from a forum, check whether Windows has actually completed the restart, what error code appears, and whether the pending item is a security update, a driver, or another component.
What “pending restart” can mean
Windows sometimes needs a restart to replace files or complete setup. The status can remain visible while Windows is still processing, after a restart was interrupted, or when another update is waiting behind the first one. A message that looks stuck does not reveal which part failed. The Windows Update history and any displayed error code are more useful than the wording alone.
Separate a one-time restart requirement from a repeating failure. If the device restarted once and the update status cleared, there may be nothing to repair. If the same update returns to pending after multiple normal restarts, or installation repeatedly fails, record the exact KB and error before changing system settings.
First, make one safe restart
- Save open work. Close active applications and disconnect removable drives only if Windows or the manufacturer says to do so.
- Use Start → Power → Restart. Do not hold the power button unless the system is genuinely unresponsive and you have no safer option.
- Leave the device plugged in. On a laptop, connect power and allow the update to finish. A brief black screen or several restarts may be normal during an update.
- Wait for sign-in to complete. Avoid restarting a second time while a progress screen is active.
- Check Settings → Windows Update and Update history. Look for “Successfully installed,” “Failed,” or a new KB number.
If a work or school device displays an organization-branded update screen or a message from IT, follow the managed-device process. A local repair can conflict with update rings or device-management policy. Our report on the October Remote Desktop issue is one example of why the exact Windows configuration matters before changing a security setting.
Check the easy causes before any repair
| Check | Why it helps | Low-risk action |
|---|---|---|
| Update history | Identifies the specific KB or driver and whether it failed or installed. | Write down the item and error code; do not rely on a screenshot alone. |
| Available storage | Insufficient space can interrupt update preparation or rollback. | Use Windows Storage settings to review temporary files and free space safely; do not delete folders in Windows or Program Files manually. |
| Power and network | Sleep, a weak connection, or power loss can interrupt the process. | Keep the PC on power and use a stable connection while checking for updates. |
| Device time and date | An incorrect clock can interfere with secure services and make timelines harder to interpret. | Check automatic time settings if the clock is clearly wrong. |
| Restart state | A pending update can be waiting for a full restart rather than another troubleshooting tool. | Use a normal Restart once, then wait for Windows to finish. |
Use Microsoft’s built-in troubleshooting path
Microsoft’s Windows Update troubleshooting guide is the safest starting point after a normal restart and basic checks. The available steps can vary by Windows version, so follow the instructions for your installed release rather than a screenshot from a different version.
Run the troubleshooter through Windows Settings if it is available for your device. It may identify common update-service or configuration problems, but it cannot guarantee that every failure will be repaired. Note what it reports and whether it recommends another step. Avoid running several repair tools at once; changing multiple components makes it harder to know which action helped or created a new symptom.
Microsoft may recommend restarting, checking update history, or following version-specific servicing instructions. If a repair requires administrator rights on a managed computer, stop and ask the administrator. Do not download a “Windows Update fixer” from an advertisement or give remote access to someone who contacts you unexpectedly.
What not to do when the status repeats
- Do not delete the SoftwareDistribution or WinSxS folders by hand. These are servicing locations; removing contents without supported instructions can damage the update process.
- Do not repeatedly hard-power-off during an update. If Windows is frozen for a long time, use the manufacturer’s support guidance or contact IT before interrupting it.
- Do not turn off antivirus or the firewall as a guess. A security control may not be related, and disabling it can expose the device.
- Do not install an update from an unofficial file host. Use Windows Update or Microsoft’s official download and support pages.
- Do not uninstall the latest security update simply because the restart message is annoying. Removal can create a security gap and may not address the cause.
- Do not repeat commands copied from old forum posts. A command written for another Windows release or another error code can have unintended effects.
If an update fails after restarting
Record the error code and the update’s KB number from Update history. Check whether Microsoft has a release-health notice for that update and Windows version. The release note may show a known issue, a safeguard hold, or an official workaround. A news article about another Windows build is not enough to infer that the same problem applies to your PC.
Also note whether the failure started after a driver, VPN client, storage change, or security policy update. That timing can help a technician narrow the issue; it does not prove causation. If the computer contains work files, use the organization’s support channel rather than trying to reset Windows or restore a system image on your own.
For a device that repeatedly returns to a previous version after installation, take a photo of the exact error screen only if it contains no confidential information, and record the time and update ID. A support technician may request Windows Update logs through an approved channel. Do not upload full diagnostic archives to public file-sharing services.
When a rollback is appropriate
Windows offers recovery options when an update causes a serious problem, but uninstalling an update should be a deliberate response—not the first way to clear “Pending restart.” A rollback might be considered when a documented update failure creates a major new issue and an administrator or Microsoft support recommends it. Before using recovery, back up important files and confirm you understand which update or version will be removed.
If the device remains usable and the only symptom is a status that did not clear, gather more information first. If the computer cannot boot, repeatedly crashes, or shows a recovery screen, seek help promptly. A managed work device should go to IT; an individually owned PC can be referred to the manufacturer or Microsoft Support.
A concise support report
“Windows Update still shows Pending restart after a normal restart on [date/time]. The item is [KB or driver], and Update history shows [status/error]. Windows version: [version]. Free storage: [approximate amount]. The device is [personal/managed]. I have not deleted servicing files or disabled security software. What supported next step should I use?”
Remove any serial number or account detail that is not required. This report gives support a reproducible starting point without sending a password, recovery code, or complete diagnostic log through an unapproved channel.
Bottom line
A persistent “Pending restart” message is a reason to inspect the update history, not to reset Windows immediately. Restart once through the normal menu, wait for setup to finish, check the KB and error, confirm storage and connectivity, and follow Microsoft’s version-specific troubleshooting steps. Avoid manual folder deletion, random scripts, and unnecessary rollback. If the computer is managed or the update keeps failing, let its administrator or official support channel review the evidence.
Sources
- Microsoft Support: Troubleshoot problems updating Windows
- Microsoft Support: October 13, 2026 update notes
Checked October 20, 2026. Instructions and options vary by Windows version and device-management policy.