How to fix Windows update error 0x800f0983?

Install error 0x800f0983 means Windows could not find a matching system component while it installed an update, so the update was rolled back. Microsoft fixed an underlying cause in Windows 11 update KB5067036 in October 2025. Restart, install the newest update, and if one update still fails, install it by hand from the Microsoft Update Catalog.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2), Windows 10 22H2.

What Windows Update error 0x800f0983 means

0x800f0983 is an error of the Windows servicing stack, the part of Windows that installs updates. Your internet connection is not the cause: the update has already been downloaded. The failure comes while Windows puts the new versions of system files together, often late in the install, and then everything is rolled back.

The code belongs to the PSFX group of errors (0x800F0982 to 0x800F0989). In Microsoft's list of servicing errors, its neighbours are 0x800F0982, PSFX_E_MATCHING_COMPONENT_NOT_FOUND and 0x800F0984, PSFX_E_MATCHING_BINARY_MISSING ("Matching component directory exists but binary is missing"). Both mean Windows looked for the version of a component that the update builds on and did not find it whole. 0x800F0983 is not in that list, and we could not confirm its symbolic name on a Microsoft page.

The reader above saw it on .NET Framework updates right after a cumulative update. That fits the pattern: once the servicing stack fails on one component, every package that touches the same component store can fail with the same code, whatever the package is.

Why Windows Update error 0x800f0983 appears

Microsoft gives one cause for the whole PSFX group: damage in the servicing stack from missing files, an invalid configuration or damaged metadata. For 0x800f0983 there is a second, simpler cause: a bug in Windows Update on Windows 11, which Microsoft addressed in October 2025. The table orders the causes from the most common to the rarest.

Where CBS.log is and what to look for

You do not need the log for Fix 1 or Fix 2. Read it when the update fails a second time, because it names the component Windows could not match. Microsoft points to the same three files for every PSFX error: CBS.log, CbsPersist_*.log and CbsPersist_*.cab in C:\Windows\Logs\CBS.

1. Press Win + R, type %windir%\Logs\CBS and press Enter.
2. Copy CBS.log to the Desktop and open the copy in Notepad, so the original stays untouched.
3. Press Ctrl + F and search for 0x800f0983, then for -2146498173. Note the time of the last hit.
4. Search for , Error near that time. The line before the code usually names a component and a version.
5. If the attempt was days ago and CBS.log does not hold it, open the newest CbsPersist_ file in the same folder. A .cab file opens like a folder in File Explorer.

Write down the component name and the KB number. If the component is a language resource (its name contains a language tag such as de-DE or pt-BR), look at Fix 4 early. If it is a core Windows component, go through Fix 1 to Fix 3 in order.

How to fix Windows update error 0x800f0983

Fix 1 and Fix 2 are specific to this code and solve most cases. Fix 3 to Fix 5 repair the component store, the language packs and the update cache. Fix 6 reinstalls Windows over itself and keeps your apps and files: Microsoft names it as the reliable answer for this group of errors.

Fix 1. Restart the PC and install the newest cumulative update

5 to 20 minutesNo riskAlways first, and above all on Windows 11 24H2 or 25H2 with a build lower than 26100.7019 or 26200.7019.

Microsoft's release notes for KB5067036 say it "addressed underlying issue which can cause Windows Update to fail to install with error 0x800f0983". Cumulative updates replace each other, so the newest one carries that fix, and a pending install that waits for a restart no longer blocks it.

1. Press Win + R, type winver and press Enter. Note the OS build number.
2. Save your work and select Start > Power > Restart. Use Restart, not Shut down.
3. On Windows 11 open Settings > Windows Update. On Windows 10 open Settings > Update & Security > Windows Update.
4. Select Check for updates and install everything that is offered, newest cumulative update first.
5. If the failed update is still listed, select Retry next to it once.
6. Open Update history and check whether the update is now listed as installed. Run winver again to see the new build.

Fix 2. Install the failing update by hand from the Microsoft Update Catalog

20 to 40 minutesLow riskOne KB keeps failing in Windows Update, or the update that carries the fix is the one that fails.

Windows Update installs from small difference files and needs the matching base component on the PC. The full package from the catalog does not depend on that, and Microsoft's own instructions for KB5067036 install it with DISM, which also installs the checkpoint update it needs first.

1. Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
2. Find the KB number. Open Settings > Windows Update. A failed or pending update is listed with its KB number; earlier ones are under Update history.
3. Check the processor type. Open Settings > System > About and look at System type: an x64-based PC needs the x64 file, an ARM-based PC (for example Snapdragon) needs the arm64 file.
4. Search the catalog. Open the Microsoft Update Catalog at catalog.update.microsoft.com in your browser, type the KB number (for example KB5124010) in the search box and press Enter.
5. Pick the right row. Find the row whose title names your Windows version and your processor type (x64-based or arm64-based) and select Download on that row.
6. Download every file listed. A window lists one or more .msu links. Download all of them into one empty folder, for example C:\packages. On Windows 11 24H2 and later the list can include earlier checkpoint updates that the new one needs.
7. Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
8. Install several files with DISM. If there are several files, open an elevated Terminal or Command Prompt and run DISM with the newest file. DISM finds the other files in the same folder and installs them in the right order.

   DISM /Online /Add-Package /PackagePath:C:\packages\<newest-file>.msu

9. Restart. Restart the PC when the installation finishes, then run winver again: the OS build should have changed.

These steps were written for Windows 11 24H2 and later; Windows 10 22H2. The full page with the other versions and what each result means: Install an update from the Microsoft Update Catalog

Some Windows 11 updates come as more than one MSU file. For KB5067036, Microsoft lists the checkpoint update KB5043080 first and the KB itself second. Put all files in one folder, for example C:\packages, and let DISM find the order:

DISM /Online /Add-Package /PackagePath:C:\packages\<file name of the KB>.msu

Run the command in Command Prompt opened as administrator, and restart when DISM asks. If you double-click the MSU instead, install the files one by one in the order the KB page lists.

Fix 3. Repair the component store with DISM and SFC

20 to 40 minutesNo riskFix 2 failed, or DISM and SFC report damaged files.

0x800f0983 means Windows could not find a component in the version it expected. DISM with RestoreHealth replaces damaged or missing components in the WinSxS store with clean copies, and SFC then repairs the system files that depend on them.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

If DISM cannot download clean files through a damaged Windows Update, give it installation media of the same Windows version as the source. Mount the ISO (right-click it and select Mount), note the drive letter, and run:

dism /Get-WimInfo /WimFile:D:\sources\install.wim
DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /LimitAccess

Replace D: with your drive letter and the last 1 with the index of your edition from the first command. If the folder holds install.esd, use that name and write esd: in place of wim:.

Fix 4. Remove display languages you do not use, then update again

15 minutesLow riskCBS.log names a language component, or Language & region lists languages you no longer use, often left over from an earlier Windows version.

Each display language adds its own set of components that every cumulative update must rebuild. Users on forums report that 0x800f0983 went away after they removed unused language packs. Microsoft has not confirmed this cause, so try it only when the signs above fit.

1. On Windows 11 open Settings > Time & language > Language & region. On Windows 10 open Settings > Time & Language > Language.
2. Check which language is set as Windows display language. Keep that one.
3. Next to each other language you do not use, open the three-dot menu and select Remove (Windows 11), or select the language and then Remove (Windows 10), and confirm.
4. Restart the PC.
5. Open Windows Update and select Check for updates.

Fix 5. Reset the Windows Update components

10 minutesLow riskThe update fails at once at the same percentage on every try.

A damaged download in the SoftwareDistribution folder is used again at every retry. Renaming the folder makes Windows download the update from scratch. It does not repair the component store, so it helps only when the downloaded files were the problem.

1. Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.

   net stop wuauserv
   net stop bits
   net stop cryptsvc

3. Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.

   del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

4. Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   ren %systemroot%\System32\catroot2 catroot2.old

5. Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.

   net start cryptsvc
   net start bits
   net start wuauserv

6. Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

Fix 6. Reinstall Windows over itself and keep apps and files

1 to 2 hoursLow riskEvery fix above ended with 0x800f0983, or DISM could not repair the component store.

For the PSFX servicing errors, Microsoft writes that "the only reliable resolution is an in-place upgrade", which "reinstalls the OS while preserving your data, applications, and settings". It gives the PC a clean component store with the newest build, so the failing update is no longer needed.

On Windows 11 the built-in way is Fix problems using Windows Update:

1. Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

   

2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

• With installation media: run Microsoft's Media Creation Tool or mount the ISO, run setup.exe, select Upgrade this PC now and make sure Keep personal files and apps is listed before you select Install.
• Windows 10 22H2: the same Media Creation Tool route works. Windows 10 left support on 14 October 2025, so this is also a good moment to plan the move to Windows 11.
• Keep the PC plugged in and online until the reinstall ends.

If error 0x800f0983 is still there

If even the repair reinstall did not clear the code, the next step depends on who manages the PC. A home PC can use Reset this PC with Keep my files. A work PC or a server needs the logs.

• What to send to support: the exact code, the KB number, the OS build from winver, the time of the last failed attempt and the logs above.
• The line from CBS.log that names the component.
• Which fixes you already ran, and the last line DISM printed.

How to keep error 0x800f0983 from coming back

Frequently asked questions

What does install error 0x800f0983 mean?

It means Windows Update downloaded an update but could not install it, because the servicing stack did not find the matching version of a system component it builds from. Windows then rolls the update back and shows Install error - 0x800f0983. The code belongs to the PSFX group of servicing errors, next to 0x800F0982 and 0x800F0984. Your internet connection is not the cause. On Windows 11 24H2 and 25H2, a bug in Windows Update itself also produced this code until Microsoft fixed it in October 2025.

Did Microsoft fix error 0x800f0983?

Microsoft fixed an underlying cause. The release notes of KB5067036, the optional update of 28 October 2025 for Windows 11 24H2 and 25H2 (OS builds 26100.7019 and 26200.7019), say it addressed an underlying issue which can cause Windows Update to fail with error 0x800f0983. Microsoft also writes that these changes go into the next security update. So a PC with a build at or above those numbers has the fix. Reports from later months show the code can still appear when the component store itself is damaged, which Fix 3 and Fix 6 cover.

How do I fix 0x800f0983 on Windows 11 25H2?

Start with Fix 1: restart, check for updates and install the newest cumulative update, then check the build with winver. If the 25H2 feature update or one monthly update keeps failing, download the package from the Microsoft Update Catalog and install it with DISM (Fix 2). If DISM fails with the same code, repair the component store with DISM RestoreHealth and SFC (Fix 3). When nothing helps, Fix problems using Windows Update in Settings reinstalls 25H2 over itself and keeps your apps and files.

What is 0x800f0983 (-2146498173)?

It is the same error written twice. 0x800f0983 is the hexadecimal form, and -2146498173 is the same 32-bit value read as a signed decimal number. Configuration Manager, WSUS reports, PowerShell and some scripts show the decimal form, and CBS.log may use either. When you search a log, search for both. The fixes on this page apply whichever form you see.

Why do my .NET Framework updates fail with 0x800f0983?

Because the fault is in the servicing stack, not in .NET. .NET Framework updates for Windows 10 and Windows 11 are installed by the same servicing stack as cumulative updates, into the same component store. When a cumulative update leaves that store in a state where a component cannot be matched, the next packages fail with the same code. Fix the cumulative update first with Fix 1 or Fix 2, restart, and the .NET updates usually install with it.

Which updates fail with error 0x800f0983?

Any update the servicing stack installs can. Searches and forum threads name the October 2025 preview KB5067036, the November 2025 security update KB5068861 (build 26200.7171), later monthly updates and the Windows 11 version 25H2 feature update. The KB number matters less than the state of the PC: the next month's update usually fails the same way until the cause is gone, which is why Fix 1 to Fix 3 come before anything tied to one KB.

Will I lose files if I fix 0x800f0983?

No fix on this page deletes your files. Fix 1 to Fix 5 only touch updates, system components, languages and the update cache. Fix 6 reinstalls Windows but keeps your apps, files and settings, as long as Keep personal files and apps is selected. Back up the files you cannot lose before Fix 6 anyway, because any reinstall can be interrupted by a power loss. Only Reset this PC, in the section after the fixes, removes installed apps.

Does the Windows Update troubleshooter fix 0x800f0983?

Rarely. The troubleshooter checks the update services and clears stuck downloads. 0x800f0983 happens after the download, while Windows builds files in the component store, and the troubleshooter does not repair that store. Run it only if you want to rule out the simple cases first: Run the Windows Update troubleshooter. Then go back to Fix 1.

Is 0x800f0983 the same error in other languages?

Yes. Erro de instalação - 0x800f0983, Erreur d'installation 0x800f0983, Installationsfehler 0x800f0983, Errore di installazione - 0x800f0983, Error - instalación and Installatiefout - 0x800f0983 are the same message on Windows in Portuguese, French, German, Italian, Spanish and Dutch. The code is the same in every language, and so are the fixes. The menu names on this page are the English ones: on a translated Windows, follow the same position in Settings.