The fastest fix for KB5120418 or KB5074105 installation failures is to collect the exact error first, then use SetupDiag for upgrade logs and Microsoft Update Catalog for a clean manual install. Guessing wastes time. Microsoft says SetupDiag scans Windows Setup log files and reports why a Windows upgrade failed [source: Microsoft].
TLDR: If KB5120418 or KB5074105 keeps failing, the admin should first check the error code in Windows Update history, then run SetupDiag if the failure happened during a feature upgrade or setup phase. For a normal cumulative update failure, the admin should download the matching package from Microsoft Update Catalog and install it manually. In a small office with 40 PCs, even a 15% failure rate means 6 machines may need hands-on repair, so checking logs before retrying can save hours.
Why these updates fail
KB5120418 and KB5074105 may fail for boring but common reasons. The annoying part is that Windows Update often shows a vague message after waiting 20 or 30 minutes. That helps nobody.
- Corrupt update cache in the SoftwareDistribution folder.
- Low disk space, especially on the system drive.
- Damaged component store, often fixed with DISM.
- Driver conflicts during setup or restart.
- Wrong package for the device architecture or Windows version.
- Security software blocking file changes during installation.
Before any repair starts, the admin should write down the update name, KB number, Windows edition, build number, and error code. This keeps the process grounded.
Step 1: Confirm the actual failure code
The admin should open Settings > Windows Update > Update history. Failed entries often show codes such as 0x800f081f, 0x80070002, 0x8024200B, or 0xC1900101.
If the code starts with 0xC1900101, a driver problem is likely. If it starts with 0x800f, Windows servicing files may be broken. If the error appears during a version upgrade, SetupDiag is the better tool. If it fails as a monthly update, Update Catalog and DISM usually matter more.
Step 2: Run SetupDiag for setup-related failures
SetupDiag is best for failed Windows setup, feature updates, and upgrade attempts. It reads setup logs and produces a report that points to the likely cause.
- Download or locate SetupDiag.exe.
- Run it as an administrator.
- Wait for the scan to finish.
- Open SetupDiagResults.log.
- Check the final error, matching rule, and affected file or driver.
Common log locations include:
C:$WINDOWS.~BTSourcesPantherC:WindowsPantherC:WindowsLogsMoSetup
If SetupDiag names a driver, the admin should update, roll back, or remove that driver before trying KB5120418 or KB5074105 again. Honestly, it feels like Windows should say this upfront instead of hiding it in a log folder, but SetupDiag is still useful once the admin knows where to look.
Step 3: Repair Windows servicing files
When the error points to missing or damaged system files, the admin should run these commands in Command Prompt as administrator:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
DISM checks the Windows component store. SFC checks protected system files. After both finish, the system should restart before another install attempt.
Step 4: Reset the Windows Update cache
If the update keeps downloading and failing at the same percentage, the cache may be stuck. The admin can stop update services, rename cache folders, and start the services again.
net stop wuauserv
net stop bits
net stop cryptsvc
ren C:WindowsSoftwareDistribution SoftwareDistribution.old
ren C:WindowsSystem32catroot2 catroot2.old
net start cryptsvc
net start bits
net start wuauserv
This forces Windows to download fresh update files. Expect to waste time on the next scan, though. The first refresh may take several extra minutes.
Step 5: Use Microsoft Update Catalog for manual installation
If Windows Update still fails, the admin should search for KB5120418 or KB5074105 in Microsoft Update Catalog. The package must match the device’s Windows version, edition, and CPU type, such as x64 or ARM64. The catalog is available from Microsoft [source: Microsoft Update Catalog].
After download, the admin should close open apps and run the .msu file. If the installer says the update is not applicable, the wrong package was downloaded, the update is already installed, or the device is missing a required earlier update.
Quick checklist before retrying
- Leave at least 20 GB free on the system drive.
- Disconnect unneeded USB devices.
- Pause third-party antivirus tools if company policy allows it.
- Update storage, chipset, graphics, and network drivers.
- Restart once before starting the install.
- Check whether the KB applies to that Windows build.
When the admin should stop retrying
Repeated retries can make the problem worse. If SetupDiag reports the same driver or setup phase every time, the admin should fix that item first. If DISM fails, the machine may need an in-place repair install. If many devices fail at once, the issue may be policy, WSUS approval, VPN filtering, or a bad deployment ring.
FAQ
What is the first thing an admin should check?
The admin should check Windows Update history for the exact error code. That code decides the next step.
Should SetupDiag be used for every failed update?
No. SetupDiag is best for setup and feature update failures. For regular cumulative update problems, DISM, SFC, cache reset, and Update Catalog are often faster.
Why does Microsoft Update Catalog say the update is not applicable?
The package may not match the Windows build, CPU type, or edition. The update may also already be installed.
Can KB5120418 and KB5074105 be installed offline?
Yes, if the correct .msu or related package is downloaded first. The admin should still restart after installation.
What if the update fails on many PCs?
The admin should check group policy, WSUS, Intune rings, security tools, and network filtering before touching each machine one by one.
