New
#1
Windows Update giving me 21H1 feature update that's already installed
Yes you read the thread title correctly! Can you believe it?
When I click install I get asked to restart my computer to finish the installation then it says the windows update failed so it's reversing the changes.
This happened after the November Cumulative Update failed to install so then I did an in-place repair as the Microsoft website describes, which fixed the same problem when I had it previously in October. Now instead of it asking me to install the November Cumulative Update again that failed to install, now it wants me to install Windows 10 21H1 as a feature update all over again. But I already have 21H1 installed!
To quote the website hyperlink above.
Here are the error codes I've gotCause
This issue occurs on devices that have been scavenged automatically to remove outdated resource records. When a system is scavenged, the recently installed latest cumulative update (LCU) is marked as permanent and the older components are removed from the system. After scavenging is complete and a device is in this state, you cannot uninstall KB5003214 or KB5003690, and you cannot install future LCUs.
- 0x800F0922: 2021-11 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems (KB5007186)
- 0xC1900104: Feature update to Windows 10, version 21H1
- 0x800F0922: Feature update to Windows 10, version 21H1
- 0x8031004A: Feature update to Windows 10, version 21H1
Here's what I've already tried
- sfc and dism
- Make sure all devices are working in Device Manager with no exclamation mark
- Check if System Restore works
- Run the Windows Update Troubleshooter
- In-Place Upgrade for Windows Update
- .NET Framework Optimization Service
- Rename the Software Distribution (and catroot) folders, for short, with the instructions from the Microsoft website
There's no point in me doing an in-place repair install as I already did that in October by using an .iso file when I had a similar problem back then from my previous thread. What's the point of me doing an in-place repair if the problem (or a similar one) is only going to happen again in 2 months time?
Does anyone have any ideas?
Here's my windowsupdate.log file dated today the 15th of November