Normally, after Windows successfully installs an update, Windows Update records the package as installed and should not offer the same update again.

Sometimes, however, a Windows 11 or Windows 10 computer repeatedly downloads or installs what appears to be the same cumulative update, security update, .NET update, driver update, or KB package.

For example:

• Windows installs an update successfully.
• The computer restarts.
• Windows Update is checked again.
• The same update appears again.
• It downloads and installs again.
• After another restart, the process repeats.

This can happen because the update did not actually complete, Windows Update's local database is damaged, the component store has corruption, a prerequisite is missing, or Windows is incorrectly detecting the installed state.

This guide explains how to identify the actual cause and repair Windows Update safely.

1. First Determine Whether It Is Really the Same Update

Do not assume two updates are identical simply because their names look similar.

Microsoft may release several updates with very similar descriptions, especially:

• Cumulative Updates
• .NET Framework updates
• Microsoft Defender intelligence updates
• Servicing Stack Updates
• Driver updates

Check the KB number.

Go to:

Settings → Windows Update → Update history

Look at the update that keeps appearing.

Example:

2026-08 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KBxxxxxxx)

Write down the complete KB number.

If the KB number changes, Windows is probably installing different updates rather than repeatedly installing the same one.

2. Check Windows Update History

Open:

Settings → Windows Update → Update history

Find the problematic update.

Look for its status.

It may show:

• Successfully installed
• Failed to install
• Pending restart
• Installation error
• Retry

This distinction is important.

Scenario A – Update shows "Failed"

Windows is not actually installing the update repeatedly. It is repeatedly attempting to install an update that continues to fail.

Scenario B – Update shows "Successfully installed"

If the same KB is successfully installed but Windows continues offering it, there may be a Windows Update detection or servicing problem.

3. Restart Windows Properly

Before performing advanced troubleshooting, perform a normal Windows restart.

Use:

Start → Power → Restart

Do not simply shut down and power the computer back on.

A restart can complete pending servicing operations that Windows Update requires before recognizing an update as fully installed.

After restarting:

Settings → Windows Update → Check for updates

Check whether the same update is offered again.

4. Check for a Pending Restart

An update may have copied files successfully but still require Windows to finish servicing operations during restart.

Signs include:

• "Restart required"
• "Pending restart"
• Update reaches 100% but appears again
• Update installs again after shutdown
• Windows Update repeatedly requests a restart

Restart Windows once or twice before performing deeper repairs.

5. Run the Windows Update Troubleshooter

Windows includes automated diagnostics for Windows Update problems.

Windows 11

Go to:

Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run

Depending on your Windows 11 version, Windows may open the Get Help application and perform Windows Update diagnostics.

Allow the troubleshooter to finish.

Restart Windows afterward.

Then check:

Settings → Windows Update → Check for updates

6. Check Available Disk Space

Windows requires sufficient free storage for:

• Downloading update packages
• Extracting installation files
• Creating temporary servicing files
• Component store operations
• Rollback files

Check:

File Explorer → This PC → Local Disk (C:)

If the system drive is almost full, remove unnecessary temporary files.

You can also open:

Settings → System → Storage → Temporary files

Be cautious before deleting the Downloads category if it contains personal files.

After freeing disk space, restart the computer and try Windows Update again.

7. Repair Windows System Files with DISM

Corruption inside the Windows component store can prevent Windows from correctly completing or detecting an update.

Open:

Command Prompt as Administrator

Run:

DISM /Online /Cleanup-Image /CheckHealth

Then:

DISM /Online /Cleanup-Image /ScanHealth

Finally:

DISM /Online /Cleanup-Image /RestoreHealth

The final command may take considerable time.

Do not close Command Prompt merely because the percentage appears stuck for several minutes.

After DISM finishes successfully, restart Windows.

8. Run System File Checker

After DISM, open Command Prompt as Administrator and run:

sfc /scannow

Wait until verification reaches 100%.

Possible results include:

No integrity violations

Windows did not detect corrupted protected system files.

Corrupt files successfully repaired

Restart Windows and check for updates again.

Some corrupt files could not be repaired

Run:

DISM /Online /Cleanup-Image /RestoreHealth

again, restart the computer, and then run:

sfc /scannow

again.

9. Reset the Windows Update Cache

One of the most effective fixes for repeatedly offered updates is rebuilding Windows Update's local cache.

Windows stores downloaded updates and update metadata primarily under:

C:\Windows\SoftwareDistribution

If this database or cached download becomes corrupted, Windows may repeatedly download or attempt to install an update.

Open Command Prompt as Administrator

Run:

net stop wuauserv
net stop bits
net stop cryptsvc

Now rename the Windows Update folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

Restart the services:

net start cryptsvc
net start bits
net start wuauserv

Restart the computer.

Windows will recreate the required update folders automatically.

Then open:

Settings → Windows Update → Check for updates

Microsoft documents resetting Windows Update components, including stopping BITS, Windows Update and Cryptographic Services and rebuilding update-related folders, as a troubleshooting procedure.

10. Why Resetting SoftwareDistribution Helps

The SoftwareDistribution directory contains Windows Update working data such as downloaded packages and update-detection information.

A damaged cache can cause Windows to incorrectly believe:

• An update was never installed
• The update download is incomplete
• Installation needs to restart
• The update needs to be downloaded again

Renaming the directory forces Windows Update to create fresh working data.

Important

Resetting SoftwareDistribution can affect the locally displayed Windows Update history database.

This does not necessarily mean installed Windows updates have been uninstalled.

Installed packages remain part of the Windows servicing system.

11. Why Resetting Catroot2 Helps

The folder:

C:\Windows\System32\catroot2

is used during Windows servicing and update processing, including catalog/signature-related operations.

Corruption here can contribute to update installation or validation problems.

Therefore, resetting both:

SoftwareDistribution

and:

catroot2

is commonly used when troubleshooting persistent Windows Update corruption.

12. Perform a More Complete Windows Update Reset

If the basic reset does not solve the problem, try a more complete reset.

Open Command Prompt as Administrator.

Run:

net stop bits
net stop wuauserv
net stop cryptsvc

Then:

Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

Rename the update data:

Ren %Systemroot%\SoftwareDistribution\DataStore DataStore.bak
Ren %Systemroot%\SoftwareDistribution\Download Download.bak
Ren %Systemroot%\System32\catroot2 catroot2.bak

Restart the services:

net start cryptsvc
net start bits
net start wuauserv

Restart Windows.

Then check Windows Update again.

This approach is particularly useful when the update database or Background Intelligent Transfer Service download queue has become corrupted.

13. Verify Whether the KB Is Actually Installed

Sometimes Windows Update's graphical interface is misleading.

You can check installed updates separately.

Open:

Control Panel → Programs → Programs and Features → View installed updates

Search for the KB number.

You can also use PowerShell.

Open PowerShell as Administrator and run:

Get-HotFix

To search for a particular KB:

Get-HotFix -Id KB1234567

Replace:

KB1234567

with the actual KB number.

Important

Get-HotFix does not enumerate every possible Windows servicing package, so absence from this command alone does not prove an update is missing.

For servicing packages, DISM can provide additional information.

Run:

DISM /Online /Get-Packages

You can filter the results:

DISM /Online /Get-Packages | findstr KB1234567

Replace the example KB number with the actual update number.

14. Manually Install the Problematic Update

If Windows Update repeatedly fails to process one particular KB, manually installing the package can sometimes break the loop.

Identify:

• KB number
• Windows version
• System architecture

Check architecture from:

Settings → System → About → System type

Common architectures include:

• x64
• ARM64

Download the matching package from the official Microsoft Update Catalog.

Before downloading, make sure the update matches:

• Windows edition/version
• Architecture
• Applicable build
• Required prerequisites

Install the downloaded .msu package.

Restart Windows afterward.

Then check Windows Update again.

15. Check Your Exact Windows Version and Build

Press:

Windows + R

Type:

winver

Press Enter.

Record the:

• Windows edition
• Windows version
• OS build

For example:

Windows 11
Version 24H2
OS Build xxxxx.xxxx

This information is extremely useful when investigating whether a particular KB is applicable to the computer.

16. Check Whether the Update Is Actually Failing During Restart

Some updates appear to install successfully inside Windows but fail during reboot.

Watch the screen during restart.

Messages such as:

Working on updates

followed by:

Something didn't go as planned

or:

Undoing changes made to your computer

indicate that Windows is rolling back the update.

In this situation, the update appears again because Windows did not retain the installation.

The correct approach is to troubleshoot the installation failure rather than hide the update.

17. Check the Windows Update Error Code

Go to:

Settings → Windows Update → Update history

Look for the failed installation and note the error code.

Examples include:

0x80070002
0x80070003
0x80070005
0x80070020
0x80070057
0x800705b4
0x800f0922

The error code can significantly narrow the cause.

For example, Microsoft documentation associates various Windows Update failures with problems such as damaged files/configuration, insufficient storage, interfering processes, interrupted installations, connectivity issues, or driver incompatibilities.

18. Check Windows Update Services

Press:

Windows + R

Type:

services.msc

Check important services such as:

Windows Update

Service name:

wuauserv

Background Intelligent Transfer Service

Service name:

BITS

Cryptographic Services

Service name:

CryptSvc

Do not permanently disable these services if you expect Windows Update to function normally.

19. Temporarily Disable VPN or Proxy

VPN and proxy configurations can sometimes interfere with update downloads or Microsoft update endpoints.

Temporarily disconnect:

• VPN software
• Corporate VPN
• Third-party proxy
• Filtering proxy

Then try:

Settings → Windows Update → Check for updates

If the PC belongs to an organization, however, check with the system administrator before changing centrally managed proxy settings.

20. Check Internet Connectivity and DNS

Open Command Prompt and test:

ping 8.8.8.8

Then:

nslookup microsoft.com

If the first command works but DNS lookup fails, the machine may have a DNS resolution problem.

You can clear the local DNS resolver cache:

ipconfig /flushdns

Then retry Windows Update.

21. Temporarily Check Third-Party Antivirus or Endpoint Security

Some endpoint-security products can interfere with update files, servicing processes, or restarts.

Examples include:

• Antivirus
• Endpoint Detection and Response software
• Application-control software
• Security hardening software
• System optimization tools

Do not permanently disable corporate security protection merely to install an update.

For a managed computer, consult the IT administrator and verify whether the security product is blocking Windows servicing.

22. Perform a Clean Boot

A third-party background application or service may interfere with Windows Update.

A clean boot starts Windows with a minimal set of non-Microsoft startup components.

Press:

Windows + R

Type:

msconfig

Open the Services tab.

Select:

Hide all Microsoft services

Then disable appropriate third-party services for testing.

Also disable unnecessary startup applications through Task Manager.

Restart the PC and try Windows Update.

Warning

Do not randomly disable Microsoft services.

After testing, restore the normal startup configuration.

23. Check Date and Time

Incorrect system time can cause authentication and certificate-related problems.

Open:

Settings → Time & language → Date & time

Enable:

Set time automatically

and verify the correct:

• Date
• Time
• Time zone

Then synchronize the clock.

24. Check for Disk Errors

File-system problems can interfere with servicing.

Open Command Prompt as Administrator:

chkdsk C: /scan

For deeper repair, Windows may require:

chkdsk C: /f

Because the Windows partition is in use, Windows may ask to schedule the repair for the next restart.

Accept the request and restart the computer.

25. Check Reliability Monitor

Reliability Monitor can provide useful information about update failures.

Press:

Windows + R

Run:

perfmon /rel

Look around the date/time when the update failed.

Check for:

• Windows failures
• Application failures
• Driver installation failures
• Windows Update failures

This can reveal another component that is causing the update rollback.

26. Check Event Viewer

Advanced administrators can investigate Windows Update events.

Press:

Windows + R

Type:

eventvwr.msc

Navigate through:

Applications and Services Logs → Microsoft → Windows

Useful logs can include Windows Update and servicing-related events.

Look for errors occurring at approximately the same time as the failed installation.

Event Viewer is particularly useful when Windows Update only displays a generic error.

27. Generate the WindowsUpdate.log

On modern Windows versions, Windows Update diagnostic information can be reconstructed using PowerShell.

Open PowerShell as Administrator.

Run:

Get-WindowsUpdateLog

Windows generates a readable Windows Update log, typically on the desktop.

This is primarily intended for advanced troubleshooting.

Search the log for:

• Error
• Failed
• KB number
• Installation failure
• Download failure

28. Check CBS.log for Servicing Problems

Windows servicing operations are recorded in:

C:\Windows\Logs\CBS\CBS.log

This log is especially useful when:

• SFC reports corruption
• DISM fails
• Cumulative updates repeatedly fail
• Windows rolls back during reboot

The file can be large, so administrators should concentrate on timestamps corresponding to the failed update.

29. Driver Updates Keep Reappearing

Sometimes the repeated item is not a Windows cumulative update but a driver update.

For example:

• Intel driver
• Realtek driver
• NVIDIA/AMD graphics driver
• Printer driver
• Firmware
• Bluetooth driver

Windows Update may repeatedly offer a driver when the currently installed driver does not match the update detection criteria.

Check:

Settings → Windows Update → Update history → Driver Updates

Also check:

Device Manager → Device → Properties → Driver

Compare:

• Driver provider
• Driver version
• Driver date

For critical hardware, prefer the computer manufacturer's validated driver when appropriate.

30. .NET Framework Update Keeps Reinstalling

Repeated .NET updates may indicate:

• Component store corruption
• Failed prerequisite
• Pending restart
• Damaged Windows servicing state
• Incomplete .NET servicing

Start with:

DISM /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

Restart Windows and try the update again.

31. Microsoft Defender Updates Are Different

Microsoft Defender security intelligence updates are released very frequently.

Therefore, seeing repeated entries referring to:

Security Intelligence Update for Microsoft Defender Antivirus

does not automatically mean Windows is installing exactly the same package.

Check the definition/version number before treating this as a Windows Update loop.

New Defender definitions can arrive multiple times within a short period.

32. Do Not Immediately Hide the Update

Hiding an update may stop it from appearing, but it does not fix the underlying servicing problem.

If an important:

• Security update
• Cumulative update
• Servicing update

continually fails, investigate the reason.

Hiding should generally be considered only after confirming that the update is inappropriate or known to cause a specific compatibility problem.

33. Recommended Troubleshooting Sequence

For most computers, use this order:

Step 1: Record the KB number.

Step 2: Check Windows Update history.

Step 3: Restart Windows.

Step 4: Run Windows Update Troubleshooter.

Step 5: Verify free disk space.

Step 6: Run:

DISM /Online /Cleanup-Image /RestoreHealth

Step 7: Run:

sfc /scannow

Step 8: Reset SoftwareDistribution and catroot2.

Step 9: Restart Windows.

Step 10: Check Windows Update again.

Step 11: Manually install the KB if appropriate.

Step 12: Investigate Event Viewer, WindowsUpdate.log and CBS.log if the problem remains.

34. Technician Quick Repair Procedure

For experienced technicians, the following procedure resolves many corrupted Windows Update states.

Open Command Prompt as Administrator:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

net stop wuauserv
net stop bits
net stop cryptsvc

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

net start cryptsvc
net start bits
net start wuauserv

Restart the computer.

Then run:

Settings → Windows Update → Check for updates

This sequence repairs the Windows component store, verifies protected system files and rebuilds important Windows Update working data.

35. What If SoftwareDistribution.old Already Exists?

If you previously performed this repair, a folder such as:

C:\Windows\SoftwareDistribution.old

may already exist.

Rename the current folder using a different name, for example:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old2

Similarly:

ren C:\Windows\System32\catroot2 catroot2.old2

Restart Windows afterward.

36. What If "Access Denied" Appears?

Make sure Command Prompt was opened using:

Run as administrator

Also verify that the relevant services were stopped before renaming their folders:

net stop wuauserv
net stop bits
net stop cryptsvc

If Windows still reports that files are in use, restart the computer and retry before opening other applications.

37. What If DISM /RestoreHealth Fails?

If:

DISM /Online /Cleanup-Image /RestoreHealth

fails, note the exact error code.

DISM normally uses Windows Update as a repair source. If Windows Update itself is badly damaged, an administrator may need to provide a compatible Windows installation image as the repair source.

The source should correspond closely to the installed Windows version, edition, architecture and servicing level.

Do not blindly use an unrelated Windows ISO as a DISM source.

38. Last Resort – Repair Install Windows

If all Windows Update repairs fail, an in-place repair installation of Windows can repair the operating system while preserving applications and user data when performed correctly.

For Windows 11, obtain official installation media matching the PC, run Windows Setup from within the existing Windows installation, and select the option to preserve personal files and applications when available.

A repair installation can rebuild many Windows components that ordinary Windows Update resets cannot repair.

Before proceeding

Back up important information.

For business computers, also verify:

• BitLocker recovery information
• Application licensing
• Database backups
• Outlook/PST data where applicable
• Accounting software data
• Browser data
• Encryption keys
• Specialized application configurations

39. Windows 10 Support Consideration

Windows 10 reached the end of its standard free support lifecycle on October 14, 2025.

If a Windows 10 machine is experiencing update problems in 2026, also determine whether the device is:

• Eligible for Windows 11
• Covered by an applicable Extended Security Updates arrangement
• Using an edition with a different servicing lifecycle

Do not assume every Windows 10 PC will continue receiving the same standard Windows Update servicing it received before end of support.

40. Common Causes at a Glance

When Windows Update keeps installing the same update, the most common causes are:

1. Update actually failed and Windows is retrying.
2. Restart is still pending.
3. Windows Update cache is corrupted.
4. SoftwareDistribution database is damaged.
5. Catroot2 data is corrupted.
6. Windows component store is damaged.
7. Protected Windows system files are corrupted.
8. Insufficient free disk space.
9. A driver is blocking the update.
10. Third-party antivirus/security software is interfering.
11. A prerequisite update is missing.
12. Windows rolls back the update during restart.
13. Windows Update incorrectly detects the package as missing.
14. The apparently identical update is actually a newer revision.
15. A driver or Defender definition only appears to be the same update.

Frequently Asked Questions (FAQ)

Q1. Why does Windows Update keep installing the same update?

Usually because the previous installation did not fully complete or Windows Update incorrectly detects the update as missing. Corrupted update cache, damaged servicing components, pending restarts and system-file corruption are common causes.

Q2. Does seeing the same update name mean it is the exact same update?

No.

Always compare the KB number and, where applicable, the package or definition version.

Q3. How can I find the KB number?

Open:

Settings → Windows Update → Update history

The update description normally contains a number such as:

KB1234567

Q4. Can restarting fix a repeated Windows Update?

Yes.

Some updates remain in a pending servicing state until Windows completes one or more restart operations.

Q5. Is it safe to rename the SoftwareDistribution folder?

Generally yes when done as part of Windows Update troubleshooting after stopping the appropriate services.

Windows recreates the folder when Windows Update runs again.

Q6. Does deleting SoftwareDistribution uninstall Windows updates?

No. Clearing or rebuilding the Windows Update working cache does not normally uninstall the Windows packages already installed in the operating system.

However, locally displayed update-history information may be affected.

Q7. What is the catroot2 folder?

catroot2 is used by Windows during servicing and update processing, including update catalog and cryptographic operations.

Corruption in this area can contribute to Windows Update problems.

Q8. Should I delete catroot2?

Renaming it is generally preferable during troubleshooting:

ren C:\Windows\System32\catroot2 catroot2.old

Windows can then recreate the required folder.

Q9. What does DISM /RestoreHealth do?

The command:

DISM /Online /Cleanup-Image /RestoreHealth

checks and repairs corruption in the Windows component store used for servicing Windows.

Q10. What does SFC /scannow do?

sfc /scannow

checks protected Windows system files and attempts to replace corrupted files with valid copies.

Q11. Should I run DISM or SFC first?

For significant servicing problems, a useful sequence is:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM repairs the component store that SFC can use as part of system-file repair.

Q12. Why does the update install successfully but appear again?

Possible explanations include corrupted Windows Update detection metadata, incomplete servicing registration, a superseding/revised package, or an update whose installation is rolled back during restart.

Check the exact KB and OS build before assuming it installed twice.

Q13. Why does Windows download the same update after every restart?

The installation may be failing during reboot and Windows may be rolling back the changes. Windows then detects the package as required and downloads or installs it again.

Q14. Can antivirus cause Windows Update problems?

Yes, some third-party security or endpoint-management software can interfere with servicing. On business computers, coordinate troubleshooting with the administrator rather than permanently disabling protection.

Q15. Can low disk space cause repeated Windows Update failures?

Yes.

Windows needs working space for downloading, extracting, servicing and rollback operations.

Q16. Can I manually install a Windows update?

Yes.

A specific KB can often be downloaded from the official Microsoft Update Catalog, provided you select the correct package for your Windows version and architecture.

Q17. Should I hide an update that keeps reinstalling?

Not as the first solution.

If it is an important security or cumulative update, determine why Windows cannot successfully retain or detect the installation.

Q18. How can I check whether a Windows update is really installed?

Check:

Settings → Windows Update → Update history

and:

Control Panel → Programs and Features → View installed updates

For some updates you can also use:

Get-HotFix

or:

DISM /Online /Get-Packages

Q19. Is Get-HotFix a complete list of every Windows update?

No.

Get-HotFix is useful but should not be treated as a complete inventory of every Windows servicing package.

DISM and Windows Update history may provide additional information.

Q20. When should I consider a Windows repair installation?

Consider an in-place repair installation when:

• DISM repeatedly fails
• SFC cannot repair corruption
• Windows Update components have been reset without success
• Multiple cumulative updates fail
• Windows servicing is extensively damaged

Back up important information before performing operating-system repair work.

Conclusion

When Windows Update keeps installing the same update, the real problem is usually not that Windows simply "likes installing it twice." More commonly, Windows is failing to complete the update, rolling it back, working with corrupted update metadata, or incorrectly determining that the package is still required.

The most effective troubleshooting sequence is:

Check KB → Check Update History → Restart → Run Troubleshooter → DISM → SFC → Reset Windows Update Components → Restart → Retry Update → Manually Install KB if Necessary → Investigate Logs → Repair Install if Required

For many affected computers, repairing the Windows image and rebuilding the SoftwareDistribution and catroot2 data is enough to stop the repeated-update cycle.

Always record the KB number, Windows version, OS build and exact error code before performing advanced troubleshooting. These four details can dramatically reduce the time required to diagnose a persistent Windows Update problem.

Tags

#WindowsUpdate #Windows11 #Windows10 #WindowsUpdateFix #WindowsUpdateLoop #UpdateLoop #WindowsTroubleshooting #WindowsRepair #MicrosoftWindows #WindowsUpdates #CumulativeUpdate #SecurityUpdate #WindowsUpdateError #WindowsUpdateProblem #WindowsUpdateRepair #SameUpdate #RepeatedUpdate #KBUpdate #WindowsKB #SoftwareDistribution #Catroot2 #DISM #SFC #SystemFileChecker #RestoreHealth #WindowsCommands #CMD #PowerShell #WindowsAdministrator #ITSupport #TechSupport #ComputerRepair #PCRepair #WindowsTechnician #SystemAdministrator #WindowsTips #WindowsFix #UpdateError #UpdateFailed #UpdateTroubleshooting #WindowsServicing #WindowsMaintenance #MicrosoftUpdate #MicrosoftUpdateCatalog #WindowsSecurity #WindowsSupport #ComputerTroubleshooting #WindowsUpdateCache #WindowsUpdateComponents #KnowledgeBase