Quick fix: Open Terminal (Admin), reset the Windows Update components with net stop wuauserv && net stop bits && ren C:\Windows\SoftwareDistribution SoftwareDistribution.old && ren C:\Windows\System32\catroot2 catroot2.old && net start wuauserv && net start bits. Then run wuauclt /resetauthorization /detectnow. If the update still reinstalls itself in a loop, use wushowhide.diagcab from Microsoft to permanently hide it.

You install a Windows feature update (e.g., 23H2). It says “Installation complete.” You reboot. The same feature update appears in Update History as installed AND as “Available for install.” You click install again, it completes, reboots, and the loop repeats. The cause is a partially-failed install that Windows Update can’t recognize as finished.

Symptom: Windows 11 feature update keeps offering itself for install even though Update History shows it succeeded; reinstall loop.
Affects: Windows 11 with feature updates failing mid-install or after install.
Fix time: ~30 minutes.

What causes this

Feature updates install in two phases: online phase (download and stage files while Windows runs) and offline phase (reboot and apply changes). If the offline phase aborts mid-way (power loss, crash, manual cancel), Windows may roll back but mark the update as “needs install” in Windows Update’s session database while also showing it as “installed” in History. The result: Windows Update keeps offering it.

Less commonly: a cumulative update interferes with the feature update detection; or BITS download cache contains a partial file that’s now stale; or registry entries for the update version don’t match what’s on disk.

Method 1: Reset Windows Update components

The standard fix for update misbehavior.

Open Terminal (Admin).

Stop the Windows Update services:

net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver

Rename the download and cache folders (forces fresh state):

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

Restart the services:

net start wuauserv
net start bits
net start cryptsvc
net start msiserver

Trigger a fresh scan:
```
wuauclt /resetauthorization /detectnow
```
Wait 2 minutes. Open Settings → Windows Update → Check for updates.
If the feature update no longer appears in the available list, you’re done. If it’s still offered, proceed to Method 2.

This is the standard reset. Resolves most update-loop cases.

Method 2: Use wushowhide to hide the unwanted feature update

For when the update keeps appearing even after component reset.

Download wushowhide.diagcab from Microsoft’s support site (search “wushowhide diagcab”). This is the official Microsoft tool for hiding updates.
Run wushowhide.diagcab. Click Next.
Pick Hide updates. Wait for the tool to scan available updates.
From the list, tick the feature update you want hidden. Click Next.
The tool hides the update. It no longer appears in Settings → Windows Update.
To unhide later: run wushowhide.diagcab → Show hidden updates.
For feature updates that show as both Installed AND Available: hide via wushowhide. The Installed entry stays in History (correct — it’s in your build), but no more “Available” offers.
This is the Microsoft-supported way to skip a specific update permanently.

Hiding via the official tool is preferable to disabling Windows Update entirely.

Method 3: Repair via DISM and run setup.exe directly

For when the underlying system files are corrupted.

Open Terminal (Admin).
Repair the component store:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Takes 10–30 minutes. Downloads fresh component files from Windows Update.
Repair system files:
```
sfc /scannow
```
If both succeed and the loop continues: download the Windows 11 ISO matching your version from Microsoft. Mount the ISO. Run setup.exe from inside the mounted ISO.
In the installer, choose Upgrade: Install Windows and keep files, settings, and apps. This is an in-place upgrade.
The in-place upgrade overwrites system files and reinstalls Windows over itself, preserving data. After completion, Windows Update should no longer offer the version you just installed.
Reboot, check Update History — the feature update should now appear as installed without re-offering.

This is the nuclear option for stubborn loops. Use when Methods 1 and 2 don’t resolve.

How to verify the fix worked

Open Settings → Windows Update → Check for updates. The previously-looping update no longer appears.
Run winver in Run dialog. The Windows version shown should match the installed feature update (e.g., 23H2).
Run Get-WindowsUpdateLog in PowerShell. Read the log: no “available update” entries for the version you don’t want again.

If none of these work

If the loop persists despite all fixes, the issue may be license/activation state. Reset activation: Settings → System → Activation → Activation state → Troubleshoot. Reset Update Orchestrator: open services.msc → Update Orchestrator Service → restart. Schedule-based update detection runs from this service. Check for stuck downloads: Get-BitsTransfer -AllUsers | Where-Object { $_.JobState -eq ’Suspended’ } | Remove-BitsTransfer. Clears stuck BITS transfers that may be holding update state. For users on Windows Insider: switch back to stable channel via Settings → Windows Update → Windows Insider Program → Stop Insider Preview builds. Insider feature updates loop more often than stable. Last resort — defer feature updates entirely: Settings → Windows Update → Advanced options → Receive updates for other Microsoft products → Off. And from Group Policy (Windows 11 Pro): Computer Configuration → Administrative Templates → Windows Components → Windows Update → Manage updates offered → Select when Preview Builds and Feature Updates are received → Enabled, set defer to 365 days.

Bottom line: Reset Windows Update components (stop services, rename SoftwareDistribution and catroot2, restart). If looping persists, hide the update with Microsoft’s wushowhide.diagcab tool.