PC Windows Keeps Installing the Same Update Again and Again
Do not reset Windows Update yet. Being offered the same update again does not always mean it failed, and a reset may not fix the real cause. First check what actually happened in update history. That one check points you to the right fix and can save you time.
Your PC restarts, the update seems to finish, and then Windows offers it again the next day. Before you try anything else, open your update history, note the KB number, and write down whether it says installed successfully or failed.
From there, follow only the route that matches. It may be a reporting glitch, a newer update with the same name, or a real failure with an error code. Each one has a different fix, and the steps below take them in that order.
Part of the Windows Update Problems: Stuck, Failed and Slow Updates Fixed Safely series, the pillar guide for this cluster.
Check update history before you change anything
Start here before you change anything. Update history is the record Windows keeps of what it tried to install, and it can tell you more than the offer on the main update page. On Windows 11, open Settings, select Windows Update, then select Update history. On Windows 10, open Settings, select Update & Security, then Windows Update, then View update history.
Find the update that keeps coming back, and match it by its KB number, the number that starts with KB. The same KB can appear more than once in the list, sometimes on different dates. Check every entry with that number, and look at the most recent one first. The name alone is not enough, because similar names can belong to different updates.
Write down the exact words beside that KB number. It will say Successfully installed or Failed to install, and those words matter, so copy them as they appear. Also write down any error code shown with the entry, such as a code starting with 0x, and the date beside each entry for that KB.
Being offered the same KB again is not, by itself, proof that the update failed. Windows can offer an update again for other reasons, and the offer alone does not tell you which one applies here. The status, date, and error code you wrote down are what count, and they decide what to do next.
Check whether a same named update is actually a new one
Some updates look repeated when they are not. The clearest example is the security intelligence update for Microsoft Defender Antivirus. Windows offers one with almost the same name nearly every day, because it carries new information about current threats.
Check the number as well as the name. Compare the KB number or version number for the update Windows is offering now with the number and date you wrote down from your history. Defender updates often share the same KB number, KB2267602, so the version number is the part that changes.
If the version number is higher, or the KB number is different, this is a new update. The same applies to other updates with a similar name and a new KB number. They are separate installs, even if the description reads the same.
Let a new update install normally and check again the next day if you want to. Do not start reset steps for it. Only follow the later routes in this article if the exact same KB number or version number keeps coming back.
If it installed successfully, treat it as a reporting glitch first
If update history shows the exact same KB number as Successfully installed, treat the new offer as a reporting glitch first. Windows may have installed the update but not yet recorded it as finished on the Windows Update page. Start with this light, low risk check instead of trying to install the same update again or changing any settings.
Look for a restart notice before you do anything else, because a waiting restart can make a finished update look unfinished. Check the Windows Update page for words like Restart required or Pending restart, and check Start, then Power, for Update and restart. Save your work and close your apps, so nothing is lost when the PC restarts.
Restart the PC once, using Restart or Update and restart, whichever you saw. When you are signed back in, open Settings, go to Windows Update, and select Check for updates once. Wait for the check to finish completely, and see whether the same KB number is offered again.
If the offer has cleared, stop here. Open update history once more and confirm the same KB still shows as Successfully installed, with no new Failed to install entry beside it. That means the restart settled the report, so do not run any further fixes for this update.
If it failed to install, let the error code choose the fix
If your history entry says Failed to install, this is a real failure, not the reporting glitch in the section above. Do not restart and check again and hope it clears. The next step depends on the code beside that entry.
Write the code down exactly as Windows shows it, including the 0x at the start and every letter and number after it. For example, it might read 0x80073712 or 0x800f0922. One digit wrong points you to the wrong fix, so copy it before you close the page.
Look that code up on this site and follow its own page if there is one. One code can mean a damaged update file, another can mean a blocked connection or too little free space. The fix written for your code matches its cause, so use that page instead of steps meant for a different code.
If no code is shown beside the Failed to install entry, do not guess at a cause. Keep the KB number and the date of the failed entry somewhere safe, then move on to the general reset in the next section. That reset is the fallback for a failed update with no code to follow.
Reset Windows Update only after those checks
Use this reset only if history shows the same KB as Failed to install, and the error code check did not send you to a code fix. If you were sent to a code page, follow that page instead. Do not do this reset as well.
Start with the built-in troubleshooter. In Windows 11, go to Settings, System, Troubleshoot, Other troubleshooters, then select Run beside Windows Update. In Windows 10, go to Settings, Update & Security, Troubleshoot, Additional troubleshooters, then select Windows Update and Run the troubleshooter. Apply any fix it suggests.
Restart the PC, go back to Windows Update, and select Check for updates. Let the one failed update try once. If it fails again or is offered again, use the cache rename below.
If the loop continues, rename the folder where Windows stores downloaded update files. Windows will make a new SoftwareDistribution folder, and the old files will be set aside. Keep the old folder for now, and follow these steps in order:
- Press the Windows key + R, type services.msc, and press Enter. Leave the Services window open.
- Right-click Windows Update in the list and select Stop. Then right-click Background Intelligent Transfer Service and select Stop.
- Open File Explorer and go to C:\Windows. Rename the SoftwareDistribution folder to SoftwareDistribution.old, and select Continue if Windows asks for permission.
- Go back to the Services window. Right-click Windows Update and select Start, then right-click Background Intelligent Transfer Service and select Start.
- Restart the PC. Then go to Windows Update, select Check for updates, and let the same update try to install once more.
Do not download an updater, cleaner, or registry tool for this fix, and do not pay for tech support to do it. All the tools used here are already in Windows. The renamed folder stays on the PC, so nothing has been deleted.
Confirm the loop has stopped, and what to do if it comes back
Restart your PC, open Windows Update, and select Check for updates once. Then open Update history and find that KB number again. The loop has stopped if history shows one Successfully installed entry for that KB and Windows does not offer the same update again.
If the same KB shows Failed to install twice after the reset in section 5, stop installing it. Take a short pause from updates (see our guide to pausing updates), and if an error code is shown, follow that code's page instead. Otherwise, wait for Microsoft to offer a revised update.
Repeated failed installs have not removed your files or programs. The update simply did not take, so your documents, photos, and apps stay as they were. You can keep using your PC as normal while you wait.
Do not put the update off for good, though, especially if it is a security update. Check again in a few days, and if a revised version appears, let it install. Then repeat the history check above to confirm it worked.
Conclusion
The repeat offer on its own told you very little. The KB number and the one word beside it in history, installed or failed, told you what kind of problem you actually had, and that is what kept a small glitch from turning into a long reset you did not need.
Keep that note of the KB, date, and any code until a later check stays clear. If the same offer comes back, you can start from that record instead of guessing, and you will know at once whether you are looking at the same loop or a new one.