One of the Windows 11’s November 2026 Patch Tuesday updates are already running into download and installation issues, triggering triggers error codes 0x800f0993, 0x800f0989, and 0x80070306.

Windows 11 KB5132061 Fails to Install With 0x800f0993 and 0x800f0989 Errors

Microsoft released KB5132061 yesterday for Windows 11 versions 26H2, 25H2, and 24H2 Enterprise and Education editions. The update bumps the OS to builds 26300.9974, 26200.9974, and 26100.9974, respectively.

According to a report by Neowin and several Windows 11 user reports on Reddit, downloading and installing KB5132061, triggers error 0x800f0993. Some have even reported error 0x800f0989 during installation only.

It should be noted that Microsoft hasn’t listed any known issues for KB5132061. This means the company has not officially acknowledged the reported installation failures yet. It is also unclear whether both errors share the same underlying cause.

In case you missed, the KB5132061 update itself brings several important fixes and security improvements. Microsoft addresses USB Audio 1.0 devices failing with Device Manager error code 10. It also fixes certain printer installation failures and Remote Desktop certificate problems.

Can you fix the KB5132061 installation failures?

Running DISM repairs and the Windows Update troubleshooter is one of the ways you can try to fix the 0x800f0993 and 0x800f0989 errors. In fact, a Reddit user claimed that running DISM and SFC scans helped fix 0x800f0993 error. The user initially encountered the error while installing the latest update. The user also deleted the SoftwareDistribution cache folder before restarting their PC and checking for updates again.

The commands used were:

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

After completing these steps, the user reported that Windows Update downloaded and installed the update without errors. They also suggested that Microsoft might have fixed something on its servers during the process. It’s not going to do any harm if you try it. As of now, Microsoft has not provided an official fix or explanation.