How to fix Windows update error 0xc8000444?

Windows Update error 0xc8000444 stops an update during the download or the check, and the number matches a database error that means the disk ran out of room for the database log. Free space on drive C: first, then let Windows rebuild its update cache in the SoftwareDistribution folder.

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

What Windows update error 0xc8000444 means

0xc8000444 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, 0x444, is 1092 in decimal. Microsoft's list of Extensible Storage Engine (ESE) errors names -1092 JET_errInstanceUnavailableDueToFatalLogDiskFull: "This instance cannot be used because it encountered a log-disk-full error while performing an operation (such as a transaction rollback) that could not tolerate failure."

Windows Update has such a database. Microsoft's page on Windows Update log files describes the DataStore component as "caching update data locally" and names the file %WINDIR%\SoftwareDistribution\Datastore\Datastore.edb. The sibling code 0xc8000442 fits the same pattern: 0x442 is 1090, and ESE error -1090 says the instance "encountered a fatal error". 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.

Why Windows update error 0xc8000444 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 and from the advice Microsoft's volunteer moderators gave in the Q&A case: run the troubleshooter and clear the SoftwareDistribution folder. Each cause points to the fix for it.

How to fix Windows update error 0xc8000444

Fix 1 and Fix 2 match what the code means and take about 20 minutes together, so start there. Fix 3 checks the drive the database lives on. Fixes 4 to 6 are the general Windows Update repairs, each in short form. Fix 7 reinstalls Windows over itself and keeps your files.

Fix 1. Free space on drive C: and restart

10 minutesLow riskEveryone first, and above all when drive C: is nearly full or a feature update was downloading.

The number matches a database error that happens when the disk is too full for the database log. Windows Update keeps its database and its downloads on drive C:, so free space there removes the most likely cause.

1. Press Win + E to open File Explorer and select This PC. Look at the bar under Local Disk (C:). A red bar means the drive is nearly full.
2. Open Settings > System > Storage and select Cleanup recommendations. Clean up what you do not need.
3. Search for cleanmgr, open Disk Cleanup, choose drive C: and select Clean up system files to add old update files to the list.
4. Restart the PC with Start > Power > Restart.
5. Open Settings > Windows Update and select Check for updates or Retry.

Step by step, with Storage Sense and the system files list: 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.

Fix 2. Rebuild the update cache: rename SoftwareDistribution and catroot2

10 minutesLow riskThere is enough free space on C: and 0xc8000444 comes back 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 cache and a new database on the next check. A Microsoft Q&A moderator gave the same advice in the 0xc8000444 case.

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

Fix 3. 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 Fixes 1 and 2 did not hold.

A database that hits a fatal error, as both 0xc8000444 and 0xc8000442 suggest, can also be the victim of file system damage on the drive. chkdsk finds and repairs that damage, so a rebuilt cache stays healthy.

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 2 once more, so the cache 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)

Fix 4. Run the Windows Update troubleshooter

5 minutesNo riskYou want Windows to check the update services and settings for you before you try the manual fixes.

The troubleshooter restarts the update services and fixes common settings. A Microsoft Q&A moderator suggested it first in the 0xc8000444 case. It does not repair a broken database, so it comes after Fix 2.

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

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

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

A download from the Microsoft Update Catalog takes the Windows Update download path out of the picture. If the fault is in the download or its cache, 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

Fix 6. 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 0xc8000444. 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

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

1 to 2 hoursRead the warningEvery other fix failed, or a feature update or Insider build 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.

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

On an Insider build, the same option reinstalls the build you are on. If you no longer want preview builds, leave the Windows Insider Program in Settings > Windows Update > Windows Insider Program after the PC is working again.

If 0xc8000444 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.

• What to send to support or to Microsoft Q&A: the output of winver, the KB number or build that fails, the date from Update history, the free space on C:, and the fixes you already tried.
• One test with a third-party antivirus paused. A Microsoft Q&A moderator asked whether a third-party antivirus was installed. 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 may be damaged by a failing drive. Back up first and check the drive's health before you reinstall.

How to keep 0xc8000444 from coming back

The code points at a full disk under the update database, so the best protection is room on drive C: before big updates arrive. Feature updates and Insider builds need much more space than a monthly update.

• Turn on Storage Sense in Settings > System > Storage, so temporary files and the Recycle Bin are emptied on a schedule.
• Keep large folders, such as videos and game libraries, on another drive.
• Do not turn the PC off while it shows Working on updates. A hard shutdown during a database write is a reason for Fix 3.
• On Windows 10, remember that support ended on 14 October 2025. Plan the move to Windows 11, which needs free space of its own.

Frequently asked questions

What does error code 0xc8000444 mean?

It is a Windows Update error that Microsoft does not explain on any page we found. The number matches a database error: 0x444 is 1092, and in Microsoft's Extensible Storage Engine error list -1092 means the database instance hit a log-disk-full error during an operation that could not fail. Windows Update keeps its local update data in a database file, DataStore.edb, in the SoftwareDistribution folder. So the most likely meaning is that drive C: was too full when that database tried to write, and the fix is free space plus a fresh update cache.

What is "Download error - 0xc8000444"?

It is the same error in the form Windows 11 shows it in Settings > Windows Update, under the name of the update that stopped. The word download tells you the update never reached the install stage, so nothing on your PC was changed. Free space on C: (Fix 1), then rename the SoftwareDistribution folder with the update services stopped (Fix 2). Select Retry or Check for updates after each fix, not before, because retrying with the same full disk and the same cache gives the same result.

What is 8000444 or (0xc8000444)?

Both are the same code written differently. Windows writes it as 0xc8000444 or 0xC8000444, sometimes in brackets after a message, and some people drop the first characters when they search. The fixes on this page apply to all of these spellings. If you see 0xc8000442 instead, it is the sibling code: 0x442 is 1090, and ESE error -1090 says the database "encountered a fatal error". The same fixes apply to it, in the same order, starting with free space on C: and a rebuilt update cache.

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.

How much free space does Windows Update need?

We could not confirm one exact number on a Microsoft page for monthly updates, and it changes with every update. A monthly cumulative update needs far less than a feature update or a new Insider build, which downloads a whole new Windows version. The safe approach for this error is to make sure the bar under drive C: in File Explorer is not red, and to use Cleanup recommendations and Disk Cleanup before you retry. If the PC has a small drive, move personal files to another drive or to OneDrive first.

Does error 0xc8000444 happen on Windows 10?

Yes, the code is reported on Windows 10 and Windows 11, and the fixes are the same on both. The only difference is the menu path of the troubleshooter and the storage settings, which this page gives for both versions. 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. If this error appears while you try to upgrade to Windows 11, free space comes first, because a feature upgrade downloads a full new copy of Windows.

Why did I get 0xc8000444 on a Windows Insider build?

The case on Microsoft Q&A was exactly that: an upgrade to Windows 11 Insider Preview build 10.0.22598.200 in April 2022 stopped with 0xc8000444. Insider builds are full new versions of Windows, so they download much more data than a monthly update and need more room for it. Free space on C: and a fresh update cache are the first two steps here too. If the build still fails, the repair install in Fix 7 reinstalls the build you are on, and you can leave the Insider Program afterwards.

Is "windows error 4" the same as 0xc8000444?

No, this page is about 0xc8000444 only. Some people search for the error by its last digit, but "error 4" is a different, generic code that many programs use with other meanings. If Windows Update shows the full code 0xc8000444, the steps here apply. If it shows another number, search for that exact number, because Windows Update codes point at very different causes, from network problems to damaged system files, and the order of fixes changes with them.

What are the steps if nothing on this page worked?

Collect the information support needs: the output of winver, the KB number or build that fails, the date from Update history, the free space on C:, and the list of fixes you tried. Make WindowsUpdate.log with the PowerShell command Get-WindowsUpdateLog and look for 0xc8000444 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 break the rebuilt database again.