How to fix Windows update error 0xC80003FA?

Ugnius Kiguolis
Published

Prefer to fix it yourself? The manual steps follow.

  • 8methods
  • 10 minutes to 2 hours
  • Easy to intermediate
Start fixing

Applies to Windows 11 and Windows 10: monthly cumulative updates and feature updates that fail with 0xc80003fa in Settings > Windows Update or in Update history

8 methods in this guide
  1. What the error means
  2. Causes, ranked
  3. The fixes
  4. 1. Rebuild the update cache
  5. 2. Check the drive
  6. 3. Free space on drive C:
  7. 4. Check the update services
  8. 5. Update troubleshooter
  9. 6. Install the update by hand
  10. 7. Repair system files
  11. 8. Repair install
  12. Still there: read the logs
  13. Prevent it
  14. FAQ
Question

Hey, could you help me with Windows update error 0xC80003FA? I was trying to install the latest updates on Windows 11 and it just keeps failing with this error code.

Windows Update error 0xc80003fa stops a monthly or feature update, and its number matches a database error: a checksum error on a page of a database file. Windows Update keeps such a file in the SoftwareDistribution folder, so rebuild that folder first and then check drive C: for errors.

Short answer

Yes, it can be fixed. 0xc80003fa most likely means Windows Update found a damaged page in its own update database, DataStore.edb. Stop the update services and rename the SoftwareDistribution folder so Windows builds a fresh database (Fix 1). If the code returns, check drive C: with chkdsk (Fix 2), then free space and install the failing update by hand. A repair install that keeps your files is the last step (Fix 8).

At a glance
Error0xc80003fa (also 0xC80003FA), shown next to a failed update in Settings > Windows Update and in Update history.
Where it appearsWhile Windows Update checks for, downloads or installs an update: monthly cumulative updates and feature updates on Windows 11 and Windows 10.
Main causeThe last part, 0x3FA, is 1018. In Microsoft's database engine (ESE) error -1018 is JET_errReadVerifyFailure: "There is a checksum error on a database page." Windows Update keeps its local data in the database file DataStore.edb.
Fastest fixStop the update services and rename SoftwareDistribution and catroot2 (Fix 1). Then check drive C: with chkdsk (Fix 2).
Also written as0xC80003FA, (0xc80003fa), c80003fa, Windows Update error 0xc80003fa, 0xc80003fa Windows 10 update.
AffectsWindows 11 and Windows 10. Windows 10 left support on 14 October 2025.
Microsoft's statusNo Microsoft page explains 0xc80003fa (searched 15 October 2026). The match with ESE error -1018 is our reading of Microsoft's ESE error list, not a Microsoft statement about Windows Update.
Related codes0x800703fa is Windows error 1018, "Illegal operation attempted on a registry key that has been marked for deletion." It has the same last part but a different meaning. 0xc80003f3 is ESE error -1011, out of memory.
Time to fix10 to 20 minutes for Fix 1. 30 minutes or more for a drive check. 1 to 2 hours for a repair install.
Where the cause is loggedWindowsUpdate.log (made with the PowerShell command Get-WindowsUpdateLog) and %systemroot%\Logs\CBS\CBS.log.

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

What Windows update error 0xc80003fa means

0xc80003fa is not on Microsoft's lists of Windows Update errors, and no Microsoft page we found explains it. The number itself gives a strong hint. Its last part, 0x3FA, is 1018 in decimal. Microsoft's list of Extensible Storage Engine (ESE) errors names -1018 JET_errReadVerifyFailure and describes it this way: "There is a checksum error on a database page". In plain words, Windows read a piece of a database file and the piece did not match its own check value, so it was damaged.

Infographic that turns 0xC80003FA into 0x3FA, which is 1018, and matches it to ESE database error -1018, a checksum error on a database page, with the DataStore.edb path and the related codes 0x800703FA and 0x8E5E03FA
The code decoded: the number matches a database checksum error, and Windows Update keeps its data in DataStore.edb.

Windows Update has such a database. Microsoft's page on Windows Update log files describes the DataStore component as "caching update data locally", and the file is C:\Windows\SoftwareDistribution\DataStore\DataStore.edb. A damaged page in that file explains why the same code returns on every check until the folder is rebuilt. We could not confirm on a Microsoft page that Windows Update reports ESE errors in this form, so read it as a well-grounded lead, not as a fact.

On Windows 10 the error usually comes with this message: "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0xc80003fa)". On Windows 11 the code stands under the name of the update that stopped.

Codes that look alike and what each one means
CodeWhat the number matchesWhere to start
0xc80003faESE error -1018, a checksum error on a database pageFix 1, then Fix 2
0x800703faWindows error 1018: "Illegal operation attempted on a registry key that has been marked for deletion."Restart the PC, then Fix 4 and Fix 1
0x8e5e03faA Windows 7 update code with the same last partWindows 7 gets no updates since January 2020
0xc80003f3ESE error -1011: "The system is out of memory."Restart, close other apps, then Fix 1

Why Windows update error 0xc80003fa happens, from most to least likely

Microsoft has not published a cause. The ranking below follows from what the number means in the ESE list: a checksum error points at a damaged database file, and a database file is damaged most often by an interrupted write or by errors on the drive. Each cause points to the fix for it.

CauseHow oftenHow to tellFix
A damaged page in the update database DataStore.edb inside SoftwareDistribution.Most likelyThe same code comes back on every Check for updates, for every update.Fix 1
File system errors on drive C: damaged the database file.OftenThe PC lost power or was shut down hard during an update, or chkdsk reports errors.Fix 2
Drive C: was nearly full when the update data was written.SometimesThe bar under drive C: in File Explorer is red.Fix 3
An update service is stopped or set to Disabled, so the rebuild cannot finish.SometimesRenaming the folder fails, or Windows Update shows Disabled in Services.Fix 4, Fix 5
One update package is broken in the download.Less oftenOnly one KB fails and the others install.Fix 6
Damaged Windows system files or update components.RarelyEverything above failed.Fix 7, Fix 8
Decision chart for error 0xC80003FA with six rows: the code on every check, a hard shutdown, a nearly full drive C:, a disabled service, one failing KB, and everything failed, each with the fix to start with
Find what you see on your PC in the left column and start with the fix on the right.
What older guides leave out

Most pages about this code list the same generic steps in random order. The code points at a damaged database, so a fresh update cache and a drive check come first, and system file repair comes late.

How to fix Windows update error 0xc80003fa

Fix 1 matches what the code means and takes about 10 minutes, so start there. Fix 2 checks the drive the database lives on. Fixes 3 to 7 are the general Windows Update repairs, each in short form. Fix 8 reinstalls Windows over itself and keeps your files.

What you see or haveStart with
The code comes back on every Check for updates, for every update.Fix 1
The PC lost power or was shut down hard during an update.Fix 2, then Fix 1
Drive C: is nearly full and its bar in File Explorer is red.Fix 3
Renaming SoftwareDistribution fails with Access is denied, or a service is Disabled.Fix 4
Only one monthly update (one KB number) fails.Fix 6
A feature update fails, or every other fix failed.Fix 8

Fix 1. Rebuild the update database: rename SoftwareDistribution and catroot2

10 minutesLow riskEveryone first, and above all when 0xc80003fa returns on every check.

The database that matches the code, DataStore.edb, sits inside the SoftwareDistribution folder. With the services stopped and the folder renamed, Windows creates a new, empty database on the next check, without the damaged page.

  1. Open Command Prompt as administrator.
  2. Stop the update services: net stop wuauserv, net stop cryptSvc, net stop bits and net stop msiserver.
  3. Rename the cache folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 Catroot2.old.
  4. Start the services again with net start and the same four names.
  5. Restart the PC and select Check for updates. The first check takes longer, because the database is built again.
  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

SoftwareDistribution.old and catroot2.old listed in Command Prompt: screenshot taken on Windows 11 26H2
Both folders end in .old. Windows creates a new SoftwareDistribution folder with a new DataStore.edb on the next check.
Administrator Command Prompt on Windows 11 after net stop bits, wuauserv, appidsvc and cryptsvc, each service reported as stopped successfully
Each net stop command must end with stopped successfully before you rename the folders.
What you lose

No files and no installed updates. The list in Update history may look shorter afterwards, because that list is read from the old database. Delete the .old folders a week later, when updates install again.

It worked if: Windows Update checks, downloads and installs the update, and the new SoftwareDistribution folder fills up again.

If not: If ren says Access is denied, a service is still running: check the services with Fix 4. If the code returns after a clean rename, check the drive with Fix 2.

Fix 2. Check drive C: for file system errors with chkdsk

30 minutes or moreLow riskThe PC lost power or was shut down during an update, or the code came back after Fix 1.

A checksum error means data on the disk no longer matches what was written. File system damage on drive C: is a common reason, and a rebuilt database on a damaged drive can break again. chkdsk finds and repairs that damage.

  1. Open Command Prompt as administrator.
  2. Run chkdsk C: and read the result. This scan only reports.
  3. If it finds errors, run chkdsk C: /f, type Y to schedule it, and restart.
  4. After the restart, run Fix 1 once more, so the database is built on a clean drive.
  1. Open Command Prompt as administrator. Type cmd in the search box on the taskbar, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
  2. Scan the drive without changing anything. Type the command below and press Enter. Replace C: with another drive letter to check that drive. This scan only reports; it does not fix anything.
    chkdsk C:
  3. If errors were found, run the repair. Run chkdsk with /f to fix file system errors. On the Windows drive (C:) chkdsk cannot lock the drive while Windows is running, so it offers to check it at the next restart.
    chkdsk C: /f
  4. Schedule the check and restart. Type Y and press Enter, then restart the PC. chkdsk runs before Windows starts. Do not turn the PC off while it runs.
  5. Read the result after the restart. The report of a check made at startup is not shown on the desktop. Open PowerShell and run the command below to see it, or open Event Viewer (eventvwr.msc) > Windows Logs > Application and filter by the sources Chkdsk and Wininit.
    Get-WinEvent -FilterHashtable @{LogName='Application'} | Where-Object { $_.ProviderName -match 'wininit' } | Select-Object -First 1 | Format-List TimeCreated, Message

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: Check a disk for errors (chkdsk)

chkdsk report ending with Windows has scanned the file system and found no problems: screenshot taken on Windows 11 26H2
A clean chkdsk result on drive C:. If errors are listed instead, schedule the repair with chkdsk C: /f.

It worked if: chkdsk reports no problems, or it repairs them at the restart, and the update installs after Fix 1.

If not: If chkdsk keeps finding new errors after each repair, the drive may be failing. Back up your files first and read the section on hardware below.

Fix 3. Free space on drive C: and clear old update files with Disk Cleanup

10 minutesLow riskDrive C: is nearly full, or the rebuilt cache cannot download the update.

The update database and the downloads live on drive C:. A drive with almost no room makes writes fail halfway, which can leave a damaged page behind. Disk Cleanup also removes old update files Windows no longer needs.

  1. Press Win + E, select This PC and look at the bar under Local Disk (C:). A red bar means the drive is nearly full.
  2. Search for cleanmgr, open Disk Cleanup, choose drive C: and select OK.
  3. Select Clean up system files, choose C: again and check Windows Update Cleanup, Temporary files and Delivery Optimization Files.
  4. Select OK, restart, and select Check for updates.
Disk Cleanup drive selection with drive C:, the Clean up system files button and the list of files to delete on Windows 11
Clean up system files adds the old Windows Update files to the list in Disk Cleanup.

Step by step, with Storage Sense and Cleanup recommendations in Settings: Free up disk space and delete temporary files. Look at what is checked before you confirm, because some options empty the Recycle Bin and the Downloads folder.

It worked if: The bar under drive C: is no longer red, and the update downloads past the point where it stopped.

If not: If space is fine and the code stays, check the update services with Fix 4.

Fix 4. Check that the update services run and are not disabled

5 minutesLow riskFix 1 failed with Access is denied, or Windows Update shows Disabled in Services.

Windows can build a new database only when Windows Update and its helper services can start. A service set to Disabled, often by a tuning tool, stops the rebuild before it begins.

  1. Press Win + R, type services.msc and press Enter.
  2. Double-click Windows Update. If Startup type is Disabled, set it to Manual and select Start.
  3. Do the same for Background Intelligent Transfer Service, Cryptographic Services and Windows Installer.
  4. If a service is already running, right-click it and select Restart.
  5. Run Fix 1 again and check for updates.
Services window with Windows Update selected and its Properties dialog, showing the Startup type list and the Start button on Windows 11
Windows Update Properties: the Startup type must not be Disabled, and Start runs the service now.

Step by step: Check and restart Windows services. Windows Update is set to Manual by default and starts when needed, so Manual is a correct setting.

It worked if: All four services start without an error, and the rename in Fix 1 works.

If not: If a service will not start and shows an error number, run the troubleshooter in Fix 5 and then repair system files with Fix 7.

Fix 5. Run the Windows Update troubleshooter

5 minutesNo riskYou want Windows to check the update services and settings for you.

The troubleshooter restarts the update services and fixes common settings. It does not repair a damaged database, so it comes after Fix 1.

  1. On Windows 11, open Settings > System > Troubleshoot > Other troubleshooters.
  2. Select Run next to Windows Update and follow the questions.
  3. On Windows 10, open Settings > Update & Security > Troubleshoot > Additional troubleshooters and run Windows Update.
  4. Restart and select Check for updates.
  1. Open Troubleshoot settings. Select Start > Settings > System > Troubleshoot.
  2. Open the list of troubleshooters. Select Other troubleshooters.
  3. Run the Windows Update troubleshooter. Under Most frequent, select Run next to Windows Update. The Get Help app opens and starts the checks.
  4. Read the result. Wait until Get Help finishes. If it found and fixed a problem, it says so and asks whether this solved the problem. Answer the question so it can offer the next step.
  5. Restart the PC. Restart when the troubleshooter finishes, even if it does not ask you to.
  6. Check for updates again. Select Start > Settings > Windows Update > Check for updates, and install the updates it finds.

These steps were written for Windows 11 (screenshots: 26H2). The full page with the other versions and what each result means: Run the Windows Update troubleshooter

Other troubleshooters list with Windows Update under Most frequent: screenshot taken on Windows 11 26H2
Windows Update is in the Most frequent group. Select Run on its row.

It worked if: The troubleshooter reports what it fixed, and the update downloads on the next check.

If not: If it finds nothing and the code stays, install the update by hand with Fix 6.

Fix 6. Install the failing update from the Microsoft Update Catalog

15 minutesLow riskOnly one monthly update (one KB number) fails with 0xc80003fa and the others install.

A standalone package from the Microsoft Update Catalog does not depend on the Windows Update download and its cache. If the fault is in that path, the standalone file still installs.

  1. Open Settings > Windows Update > Update history and note the KB number of the failed update.
  2. Press Win + R, type winver and note the version, for example 25H2, and whether the PC is x64 or Arm64.
  3. Search the KB number in the Microsoft Update Catalog and download the row for your version and processor.
  4. Run the downloaded .msu file and restart when asked.
  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

Microsoft Update Catalog search results for a KB number with rows for Windows 11 versions on x64 and arm64 and a Download button on each row
The catalog lists each update once per version and processor. Pick the row that matches winver.

It worked if: The standalone installer finishes, and after the restart the KB is listed as installed in Update history.

If not: If the standalone file also fails, repair the system files with Fix 7.

Fix 7. Repair Windows system files with DISM and SFC

20 to 40 minutesLow riskThe update cache is fresh and the drive is clean, but updates still fail.

This is not specific to 0xc80003fa. It rules out damaged system files in the update components before you choose a repair install.

  1. Open Command Prompt as administrator.
  2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
  3. Run sfc /scannow, restart and check for updates.
  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

The result line tells you what SFC did: screenshot taken on Windows 11 26H2
The last line of sfc /scannow tells you whether it found and repaired damaged files.

It worked if: SFC reports that it found no integrity violations or that it repaired them, and the update installs.

If not: If DISM fails or the update still stops with 0xc80003fa, do the repair install in Fix 8.

Fix 8. Reinstall Windows over itself and keep your files and apps

1 to 2 hoursRead the warningEvery other fix failed, or a feature update keeps failing with the code.

A repair install replaces Windows, the update components and their folders with a fresh copy, and keeps your files, apps and settings. It clears whatever the earlier fixes missed.

Back up first

The repair install keeps files and apps, but a failure halfway through can leave the PC in a bad state. Copy your documents to an external drive or OneDrive first. Do not choose Reset this PC with Remove everything.

  1. Back up your files: Back up your files (Windows Backup, File History, Time Machine)
  2. On Windows 11, open Settings > System > Recovery.
  3. Next to Fix problems using Windows Update, select Reinstall now.
  4. Keep the PC plugged in and online, and restart when asked.
  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.
  4. If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
  5. Choose Keep my files. Select Keep my files. Do not select Remove everything.
  6. Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
  7. Reset. Review the summary and select Reset. The PC restarts several times.

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

Settings, System, Recovery: Fix problems using Windows Update, Reinstall now: screenshot taken on Windows 11 26H2
Fix problems using Windows Update reinstalls the current version and keeps your apps, files and settings.

On Windows 10 22H2 this option is not in Settings. The library page above shows the way with the installation media that keeps files and apps.

It worked if: Windows restarts on the same version with your files and apps in place, and Check for updates works without the code.

If not: If the repair install itself fails, collect the logs below and ask Microsoft support, or use Reset this PC with Keep my files.

If 0xc80003fa is still there: the logs to read and when it is hardware

Collect the logs right after a failed attempt, while the time of the failure is fresh. Microsoft's page on Windows Update log files names these two as the ones to read when an update fails.

Where each part of the failure is written
LogWhereWhat to look for
WindowsUpdate.logOn the desktop, after you run Get-WindowsUpdateLog in PowerShell0xc80003fa and lines from the DataStore component near the time of the failure
CBS.log%systemroot%\Logs\CBSThe update installation part. Search for , error if the update got past the download.
  • What to send to support or to Microsoft Q&A: the output of winver, the KB number that fails, the date from Update history, the free space on C:, the chkdsk result and the fixes you already tried.
  • One test with a clean boot. Start Windows with only Microsoft services to rule out a program that locks update files, then undo it: How to perform a clean boot in Windows
  • One test with a third-party antivirus paused. Pause it for one attempt and turn it back on right after: Turn off Microsoft Defender protection for a moment
  • Is it hardware? If chkdsk finds new errors after each repair, or the drive is slow and makes noise, the database is being damaged by a failing drive. Back up first and check the drive's health before you reinstall.

How to keep 0xc80003fa from coming back

The code points at a damaged database page, and such pages come from interrupted writes and drive errors. So the best protection is to let updates finish and to keep drive C: healthy and not full.

  • Do not turn the PC off while it shows Working on updates. A hard shutdown during a database write is the classic way to get a checksum error.
  • On a laptop, keep the charger plugged in during big updates.
  • Turn on Storage Sense in Settings > System > Storage, so temporary files are removed on a schedule.
  • On Windows 10, remember that support ended on 14 October 2025. Plan the move to Windows 11 or enrol in Extended Security Updates.

Frequently asked questions

What does error code 0xc80003fa mean?

It is a Windows Update error that Microsoft does not explain on any page we found. The number matches a database error: 0x3FA is 1018, and in Microsoft's Extensible Storage Engine error list -1018 is JET_errReadVerifyFailure: "There is a checksum error on a database page". Windows Update keeps its local update data in a database file, DataStore.edb, in the SoftwareDistribution folder. So the most likely meaning is that a page of that file is damaged, and the fix is a fresh update database plus a drive check.

How do I fix 0xc80003fa on Windows 10?

The fixes are the same as on Windows 11, and only two menu paths differ: the troubleshooter is under Settings > Update & Security > Troubleshoot > Additional troubleshooters, and the repair install uses installation media instead of the Settings button. Start with Fix 1, the rename of SoftwareDistribution, then chkdsk in Fix 2. Windows 10 left support on 14 October 2025, so a Windows 10 PC without Extended Security Updates gets no more monthly security updates at all, and the error may also appear while the PC tries to install the last ones.

What is the Windows 10 message "There were some problems installing updates" with this code?

It is the general message Windows 10 shows when any update fails, and the number in brackets at the end tells you which error it was. When the brackets hold 0xc80003fa, the steps on this page apply. Russian Windows shows the same text in Russian. If the brackets hold 0x800703fa instead, read the next question, because that code has a different meaning even though it ends in the same three characters.

Is 0x800703fa the same error as 0xc80003fa?

No. Both end in 3FA, which is 1018. But 0x800703fa wraps Windows system error 1018: "Illegal operation attempted on a registry key that has been marked for deletion". It means a program or service tried to use a part of the registry that was being closed, for example a user profile that was unloading. A full restart closes those handles, so restart first, not just sign out. Then check the update services (Fix 4) and rebuild the update cache (Fix 1). If it keeps coming back, we could not confirm one Microsoft fix for it.

What is 0x8e5e03fa on Windows 7?

It is an older Windows Update code from Windows 7 with the same last part, 3FA. Windows 7 has received no regular updates since 14 January 2020, so on a home PC this error usually appears when the old update client cannot reach a service that no longer serves it. Rebuilding SoftwareDistribution may clear the error, but it will not bring new security updates. The lasting fix is a supported Windows version on hardware that meets its requirements.

What is "installer encountered an error 0xc80003f3"?

It is a sibling code from the same family. 0x3F3 is 1011, and ESE error -1011 is JET_errOutOfMemory, "The system is out of memory." It often shows in the Windows Update Standalone Installer when you run an .msu file. Restart the PC to free memory, close large apps, and run the installer again. If it repeats, rebuild the update cache with Fix 1. The causes differ from 0xc80003fa, but the first steps are the same.

Is it safe to rename or delete the SoftwareDistribution folder?

Yes, when the update services are stopped first. Windows creates a new, empty SoftwareDistribution folder and a new update database the next time it checks for updates. You lose no files and no installed updates. The list in Update history may look shorter, because that list is read from the old database. Renaming to SoftwareDistribution.old instead of deleting keeps a copy in case you need it. Delete the old folder once updates install again, for example a week later, to get the space back.

What does "error 0x000003fa" mean?

It is the bare number 1018 without a prefix. Without the prefix you cannot tell which family it came from: as a Windows system error it is the registry key marked for deletion, and in Windows Update with the 0xC8 prefix it matches the database checksum error. Look at the full code the program showed. If it is 0xc80003fa, follow Fix 1 and Fix 2. If it is 0x800703fa, restart the PC first.

The update still will not install after every fix. What now?

Collect what support needs: the output of winver, the KB number that fails, the date from Update history, the free space on C:, the chkdsk result and the list of fixes you tried. Make WindowsUpdate.log with the PowerShell command Get-WindowsUpdateLog and look for 0xc80003fa near the time of the failure. Then ask on Microsoft Q&A or contact Microsoft support. If chkdsk keeps finding new errors, back up your files and check the drive itself before you reinstall Windows, because a failing drive will damage the rebuilt database again.

Sources

  1. Microsoft Learn: Extensible Storage Engine error codes (JET_errReadVerifyFailure -1018, JET_errOutOfMemory -1011) (learn.microsoft.com)
  2. Microsoft Learn: System error codes 1000-1299 (1018, 0x3FA, registry key marked for deletion) (learn.microsoft.com)
  3. Microsoft Learn: Windows Update log files (DataStore, WindowsUpdate.log, CBS.log) (learn.microsoft.com)

Did this fix work?

One click, no account. It tells the next reader which guides are worth their time.

We show the result once 20 readers have answered.
Still broken? Describe your case with the exact error text.

Questions and experiences: fix Windows update error 0xC80003FA

Still broken, or found a fix we did not cover? Ask here: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…

4,322 members already hereThey read, write, comment and vote. 0 verified · 31 joined this year
All membersJoin