Windows Update -2026-11 Security Update (KB5132061) (26300.9974) - Install error - 0x800f0993

Question

Windows Update -2026-11 Security Update (KB5132061) (26300.9974) - Install error - 0x800f0993

Anthony Brun 20

I was Updating my Window an I got a Install error - 0x800f0993 for 2026-11 Security Update (KB5132061) (26300.9974) I have done the Following.

Open Command Prompt as Administrator and run:

net stop bits = The Background Intelligent Transfer Service service is not started.

net stop wuauserv

net stop cryptSvc = The following services are dependent on the Cryptographic Services service.

Stopping the Cryptographic Services service will also stop these services.

Avast Tools

Avast Antivirus

Do you want to continue this operation? (Y/N) [N]: Y

The requested pause, continue, or stop is not valid for this service.

net stop msiserver = The Windows Installer service is not started.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old = Access is denied.

ren C:\Windows\System32\catroot2 catroot2.old = Access is denied

net start bits

net start wuauserv

net start cryptSvc

net start msiserver

Restart

Update Failed Install error - 0x800f0993

Open Command Prompt as Administrator and run:

sfc /scannow = Beginning system scan. This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

DISM /Online /Cleanup-Image /RestoreHealth = Deployment Image Servicing and Management tool

Version: 10.0.26100.9549

Image Version: 10.0.26300.9818

[==========================100.0%==========================]

Error: 0x800f0915

The repair content could not be found anywhere.

Check the internet connectivity or use the "Source" option to specify the location of the files that are required to restore the image. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

0 comments

2 answers

Your answer

Answer 1

Hi, good day!

Have you tried the AI's suggested solution of manually downloading and installing the update from the Microsoft Update Catalog?

If the issue persists, open Settings > System > Recovery.

Few things to check on the PC

Unplug all external peripherals except for the Mouse, Keyboard, and LAN cable before starting
Disable or uninstall any third-party Antivirus program to prevent it from interfering with the upgrade

Under Fix problems using Windows Update, click Reinstall Now

Once completed, your system will restart.

I look forward to receiving your update and I'm willing to collaborate with you till we resolve the issue. Do keep me informed by clicking "Add comment" below.

Answer 2

Install KB5132061 manually with its required checkpoint cumulative update first; for an x64 PC, install KB5043080 and then KB5132061 in that exact order.

Install the two MSU packages manually

The KB5132061 catalog entry explicitly requires checkpoint packages to be installed before the target cumulative update ^1^.

Open Settings → System → About → System type and determine whether the PC is x64 or ARM64.
Create an empty folder named:
```
   C:\Packages
```
For an x64 PC, download these two files into that folder:
1. KB5043080 checkpoint cumulative update
2. KB5132061 cumulative update
For an ARM64 PC, use the corresponding ARM64 packages listed on the KB catalog page instead. Do not install x64 packages on ARM64.
Double-click the KB5043080 file first. If Windows reports that it is already installed, continue.
Double-click the KB5132061 file.
Restart Windows, then open Settings → Windows Update → Update history and confirm that KB5132061 is installed and the OS build is 26300.9974.

Your current build, 26300.9818, identifies the 26H2 branch. KB5132061 requires a September 22, 2026-or-later update and servicing stack version 26100.9539 or later on 26H2 ^1^. Build 26300.9818 is later than that prerequisite update, but if the manual installation still rejects the package, verify the servicing stack from an elevated Command Prompt:

DISM /Online /Get-Packages | findstr /i "ServicingStack"

The returned package identity must show version 26100.9539 or later.

If the standalone installation still fails

Since SFC found no integrity violations but DISM /RestoreHealth cannot obtain repair content, use Windows 11’s supported repair-reinstall option instead of repeating the failed cache reset or the same DISM command.

Back up important personal files.
Open Settings → System → Recovery.
Under Fix problems using Windows Update, select Reinstall now.
Keep the PC connected to power and the internet.
Allow the repair installation to complete and restart.
Return to Settings → Windows Update → Check for updates.

This reinstalls the current Windows version, repairs system files and servicing components, and preserves installed applications, files, and settings ^2^.

If Fix problems using Windows Update is absent, it can be unavailable on managed work/school PCs. In that case, an administrator or Microsoft Support will need to review C:\Windows\Logs\CBS\CBS.log and C:\Windows\Logs\DISM\dism.log.

About the earlier access-denied results

Do not repeat the SoftwareDistribution/Catroot2 rename sequence at this stage. Avast prevented Cryptographic Services from stopping, so those folders remained in use and the rename returned Access is denied. Microsoft notes that third-party security software can interfere with Windows updates and may be temporarily removed before updating, provided its installer or product information is available for reinstallation ^3^.

If either the standalone MSU installation or repair reinstall is blocked again, temporarily uninstall Avast, restart, perform the operation, and reinstall Avast afterward. Simply disabling protection might not unload the service that blocked the earlier reset.

References