How to fix Windows update error 0xc1900104?
Prefer to fix it yourself? The manual steps follow.
- 7methods
- 10 minutes to 2 hours
- Beginner to intermediate
Applies to Windows 11 and Windows 10 22H2 feature updates through Windows Update, the Installation Assistant or setup.exe from an ISO
7 methods in this guide
Good day. I was wondering if you could help me with Windows update error 0xc1900104. I got it yesterday when I tried to install the latest feature update on Windows 11.
Error 0xc1900104 means a Windows feature update took longer than Setup allows, so Setup stopped and kept your current Windows. Microsoft names it MOSETUP_E_PROCESS_TIMEOUT. Restart, keep the PC plugged in and awake, and run the update again before you try anything else.
0xc1900104 is a time-out: the feature update did not finish within the time Windows Setup allows. Restart the PC, plug in the charger, set sleep to Never, and run the update again (Fix 1). If it stops again, unplug extra devices, free 20 GB on drive C, and use SetupDiag to see where Setup hung. Your files and apps stay as they were.
| Error | 0xc1900104, Microsoft's MOSETUP_E_PROCESS_TIMEOUT: "The installation process did not complete within the required time limit." |
|---|---|
| Where it appears | In Settings > Windows Update after a feature update fails, as Install error - 0xc1900104, or in Update history as, for example, "Feature update to Windows 10, version 20H2 - Error 0xc1900104". |
| Main cause | Setup stalled or was interrupted for too long: sleep, power loss, a device or driver that hangs, or too little free space. |
| Fastest fix | Restart, stay on the charger with sleep set to Never, and run the update again (Fix 1). |
| Also written as | 0xC1900104, 0x1900104, install error - 0xc1900104, error 0xc1900104. |
| Affects | Feature updates of Windows 11 (24H2, 25H2, 26H2) and Windows 10. Windows 10 left support on 14 October 2025. |
| Microsoft's status | Listed among the modern Setup errors. Microsoft has no separate fix page for it and no known-issue entry we could find. |
| Where the cause is written | setupact.log and setuperr.log in C:\$Windows.~BT\Sources\Panther, read for you by Microsoft's free SetupDiag tool. |
| Time to fix | 10 minutes for Fix 1 to Fix 3, plus 1 to 2 hours for each new update attempt. |
Facts checked on 15 October 2026. Steps written for Windows 11 feature updates to 24H2, 25H2 and 26H2, and Windows 10 22H2 upgrades to Windows 11.
What error 0xc1900104 means and where you see it
Codes that start with 0xC19001 come from Windows Setup, the engine that installs a feature update such as Windows 11 version 25H2 or an upgrade from Windows 10. Microsoft's list of modern Setup errors gives 0xC1900104 the name MOSETUP_E_PROCESS_TIMEOUT and the text "The installation process did not complete within the required time limit."

So the code tells you that Setup gave up waiting, not why it was slow. Your PC keeps the Windows version it had. Windows Update usually shows: There were problems installing some updates, but we'll try again later. The line below names the update and the code.
| Code | Microsoft's name | What it means for you |
|---|---|---|
| 0xC1900104 | MOSETUP_E_PROCESS_TIMEOUT | The install ran past Setup's time limit. This page. |
| 0xC1900103 | MOSETUP_E_COMPAT_TIMEOUT | A compatibility warning was not answered in time. |
| 0xC1900107 | MOSETUP_E_CLEANUP_PENDING | An earlier attempt still needs a restart to clean up. Often seen after a time-out. |
| 0xC1900101 | MOSETUP_E_SETUP_PLATFORM | A generic rollback, usually a driver. See 0xC1900101 - 0x40021. |

Why the feature update times out with 0xc1900104
Microsoft does not publish causes for this exact code. The ranking below follows what a time-out needs: Setup was paused, stuck or very slow. It matches Microsoft's notes on hangs caused by drivers and on free space, and reports from users who hit the code.
| Cause | How often | How to tell | Fix |
|---|---|---|---|
| The PC slept, ran on battery, lost power or was restarted while Setup worked. | Most often | A laptop on battery, an install left overnight, or a lid that was closed. | Fix 1 |
| A device or its driver hangs, so the percentage stops moving. | Often | It stops at the same number each time. One user on Microsoft Q&A saw 97% for hours, then the code. | Fix 2, Fix 4 |
| Too little free space, which slows Setup or leaves it waiting. | Often | Drive C shows less than 20 GB free in File Explorer. | Fix 3 |
| Another antivirus or startup software scans or locks Setup's files. | Sometimes | A non-Microsoft security suite, VPN, tuning or backup tool starts with Windows. | Fix 5 |
| A damaged update cache or system files make the download and install crawl. | Less often | Other updates fail too, or the download stays at the same percent. | Fix 6 |
| Very slow or failing disk. | Rarely | The PC is slow in general, and chkdsk or the maker's tool reports errors. | Still broken section |

Errors such as 0x80070070 or 0xC190020E mean no free space at all, and download errors start with 0x8024. With 0xc1900104 the update was already downloaded and installing, so the fixes target what slowed or stopped the install.
Where Windows Setup logs show why 0xc1900104 happened
Microsoft suggests finding the code in the Setup log files, such as setuperr.log, and running its free SetupDiag tool, which reads the logs and names the reason for a failed upgrade. Read the logs before you clean the disk, because Disk Cleanup can delete them.
| File | Path | What it shows |
|---|---|---|
| Setup steps | C:\$Windows.~BT\Sources\Panther\setupact.log | Every step with its time. A long gap before the error shows where Setup waited. |
| Setup errors | C:\$Windows.~BT\Sources\Panther\setuperr.log | Only the errors, with the module that reported them. |
| After a rollback | C:\$Windows.~BT\Sources\Rollback | Present only when the new Windows had started. Holds device logs and, after a crash, setupmem.dmp. |
| SetupDiag result | SetupDiagResults.log next to SetupDiag.exe | A plain summary of the failure and the matching rule. |
$Windows.~BT is a hidden folder. In File Explorer select View > Show > Hidden items on Windows 11, or tick Hidden items on the View tab on Windows 10.
How to fix Windows update error 0xc1900104
Fix 1 to Fix 3 cost minutes and remove the most common reasons Setup runs out of time. Fix 4 finds where Setup hung, so you know which device or program to deal with. Fix 5 and Fix 6 deal with software and a damaged update cache. Fix 7, the upgrade from an ISO, comes last.
| What you see or have | Start with |
|---|---|
| A laptop on battery, the PC went to sleep, or the install ran overnight. | Fix 1 |
| A memory card, USB drives, a dock or a USB-C hub is attached. | Fix 2 |
| Drive C has less than 20 GB free. | Fix 3 |
| The install stops at the same percentage every time. | Fix 4 |
| Another antivirus, VPN, tuning or backup tool starts with Windows. | Fix 5 |
| Other updates fail too, or the download never finishes. | Fix 6 |
| Everything above is done and it still times out. | Fix 7 |
Fix 1. Restart, keep the PC plugged in and awake, and run the update again
10 minutes, plus the updateNo riskEveryone, and first of all laptops and PCs that sleep after a few minutes.
A time-out means Setup could not work for long enough. A restart finishes the cleanup of the failed attempt, which Microsoft says code 0xC1900107 waits for, and power and sleep settings stop Setup from being paused again.
- Save your work and restart the PC with Start > Power > Restart, not Shut down.
- Connect a laptop to its charger and keep it connected until the update ends.
- Open Settings > System > Power & battery on Windows 11, or Settings > System > Power & sleep on Windows 10.
- Set the sleep time when plugged in to Never. Note the old value so you can set it back.
- Open Settings > Windows Update and select Check for updates, then Download & install for the feature update.
- Keep the lid open and the PC online until Windows asks to restart, then select Restart now.
- Set sleep back to your old value when the new version is running.
A feature update can sit at one percentage for a long time and still finish. Give it at least two hours before you decide it is stuck, and never switch the PC off while the screen says it is working on updates.
It worked if: The update reaches 100%, the PC restarts a few times, and Settings > System > About shows the new version.
If not: If it fails again with 0xc1900104, unplug extra devices in Fix 2.
Fix 2. Remove memory cards and unplug every device except the mouse, keyboard and display
5 minutes, plus the updateNo riskPCs with USB drives, a memory card in the reader, a dock, a hub, printers or game controllers attached.
Microsoft says an incompatible driver can cause system hangs during an upgrade, and its first advice for driver problems is to disconnect all peripherals except mouse, keyboard and display. A hung device leaves Setup waiting until its time runs out.
- Shut down the PC.
- Take out any SD or micro SD card from the built-in reader.
- Unplug USB flash drives, external disks, printers, webcams, headsets and controllers.
- Undock a laptop and remove USB-C hubs. Connect the charger directly.
- Keep one display, the mouse and the keyboard, then start Windows.
- Run the update again from Settings > Windows Update.
- On the new version, plug the devices back in one at a time.
It worked if: The percentage keeps moving past the point where it stopped before, and the update completes.
If not: If drive C is nearly full, free space in Fix 3. If space is fine, find the hang in Fix 4.
Fix 3. Free at least 20 GB on drive C and remove old update files
10 to 20 minutesLow riskDrive C shows less than 20 GB free, or this is the second or third failed attempt.
Microsoft asks for 20 GB of free space to upgrade 64-bit Windows. With less, Setup has to wait for space or work slowly, and each failed attempt leaves temporary installation files behind that take more space.
- Open File Explorer > This PC and check the free space on drive C.
- Type disk cleanup in the search box and open Disk Cleanup. Choose drive C: and select OK.
- Select Clean up system files, choose C: again and select OK.
- Tick Windows Update Cleanup, Temporary Windows installation files, Delivery Optimization Files and Temporary files.
- Select OK, then Delete files, and restart before you try the update again.

Copy the C:\$Windows.~BT\Sources\Panther folder to your desktop first if you want to read the logs in Fix 4, because removing temporary installation files deletes them. More ways to make room: Free up disk space and delete temporary files.
It worked if: Drive C shows 20 GB or more free, and the next attempt gets further.
If not: If you have the space and it still times out, read the logs in Fix 4.
Fix 4. Find where Setup hung with SetupDiag, then update that driver
20 minutesLow riskThe install stops at the same percentage each time, or Fix 1 to Fix 3 did not help.
The code only says Setup ran out of time. Microsoft recommends SetupDiag, which reads the Setup logs and names the reason, so you can update or remove one driver or program instead of guessing.
- Download SetupDiag from Microsoft's SetupDiag page on Microsoft Learn and save it in a new folder.
- Right-click SetupDiag.exe and select Run as administrator. Wait until its window closes.
- Open
SetupDiagResults.login the same folder and read the matching rule and the lines under it. - If it names nothing, open
C:\$Windows.~BT\Sources\Panther\setupact.login Notepad and press Ctrl + End. - Scroll up to the last lines before the error and look for a long gap in the times or a driver,
.sysfile or device name. - Update the driver from the PC maker's support page, or uninstall the program the log names.
- Restart and run the update again.
- Open Device Manager. Right-click Start and select Device Manager.
- Open the device's Driver tab. Expand the category (for example Display adapters), right-click the device, select Properties and open the Driver tab. Driver Date and Driver Version show what is installed now.
- Update the driver. Select Update Driver and let Windows search automatically. To use a driver you downloaded from the device maker, select Browse my computer for drivers instead and point to the unpacked folder.
These steps were written for Windows 11 24H2 and later. The full page with the other versions and what each result means: Update, roll back or reinstall a driver
It worked if: SetupDiag or the log names a driver or program, and after you update or remove it the update finishes.
If not: If the logs name a security or startup program, or nothing at all, go to Fix 5.
Fix 5. Run the update in a clean boot without other security software
20 minutes, plus the updateLow riskA non-Microsoft antivirus, VPN, tuning, backup or remote access tool starts with Windows.
Microsoft's advice for upgrade failures caused by drivers and services from other makers is a clean boot, and it names antivirus filter drivers among them. Such software can scan or lock Setup's files and slow it past the limit.
- Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
- Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

With Hide all Microsoft services ticked, only third-party services stay in the list. Screenshot: Windows 11 26H2. - Disable the remaining services. Select Disable all, then select Apply.
- Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

The Startup tab only links to Task Manager. Screenshot: Windows 11 26H2. - Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.

Select an app, then Disable. Screenshot: Windows 11 26H2. - Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
- Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).
These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows
- In the clean boot, open Settings > Apps > Installed apps and uninstall a non-Microsoft security suite. Keep its installer and licence.
- Restart. Microsoft Defender turns on by itself when no other antivirus is installed.
- Run the update from Settings > Windows Update.
- On the new version, reinstall the security suite and undo the clean boot as the procedure describes.
Step by step for removing a program: Uninstall a program or app in Windows.
It worked if: Windows Security shows Microsoft Defender as active, and the update completes in the clean boot.
If not: If it still times out, reset the update cache and repair system files in Fix 6.
Fix 6. Reset the Windows Update components and repair system files
20 to 30 minutesLow riskOther updates fail too, or the download stays at one percentage for hours.
A damaged download in the update cache makes Setup check and fetch files again and again. Renaming the cache folders makes Windows download a clean copy, and DISM and SFC repair the files Setup copies from.
- 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.
- 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
The update services are stopped. Screenshot: Windows 11 26H2. - 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" - 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
Both folders now end in .old. Screenshot: Windows 11 26H2. - 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
BITS and Windows Update are running again. Screenshot: Windows 11 26H2. - 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
- Right-click Start and open Terminal (Admin).
- Run
DISM.exe /Online /Cleanup-image /Restorehealthand wait until it reaches 100%. - Run
sfc /scannowand wait until the verification reaches 100%. - Restart, then run the feature update again from Settings > Windows Update.
With screenshots and what each result means: Run DISM and SFC to repair Windows system files.
It worked if: The update downloads again from 0% and installs past the point where it stopped before.
If not: If it still fails, upgrade from the ISO in Fix 7.
Fix 7. Upgrade from the Windows ISO with setup.exe, keeping files and apps
1 to 2 hoursRead the warningEvery fix above is done and Windows Update still stops with 0xc1900104.
Setup from the ISO uses a full, freshly downloaded copy of Windows instead of the update cache. It is not a cure on its own: one user on Microsoft Q&A saw setup.exe stall at 89%, so run it after Fix 1 to Fix 5.
An upgrade keeps your files and apps, but a power cut or a forced shutdown can leave the PC unable to start. Copy your files to an external drive or cloud storage first: Back up your files (Windows Backup, File History, Time Machine).
- Open Microsoft's Download Windows 11 page and download the ISO, or the Media Creation Tool and choose ISO file.
- Right-click the ISO and select Mount. A new drive appears in File Explorer.
- Double-click
setup.exeon that drive and select Yes in the User Account Control prompt. - When Setup offers updates, let it download them, as Microsoft recommends for upgrades.
- Choose to keep personal files and apps, and select Install.
- Keep the PC plugged in, awake and online until it reaches the sign-in screen.

It worked if: Setup completes, and Settings > System > About shows the new Windows version with your files and apps in place.
If not: If setup.exe also stalls, read the next section and send the logs to support.
If error 0xc1900104 is still there
When the update still times out on a clean, plugged-in PC with free space, the logs decide the next step. Copy the Panther folder after each failure, because the next attempt replaces it.
| What you find | What to do |
|---|---|
| SetupDiag or setupact.log names a driver | Update it from the device maker, or disable the device for the update. |
| The log shows long waits on disk operations | Check the drive with the maker's tool or chkdsk /f C:. A failing drive makes every step slow. |
| A work or school PC | Ask IT: their update policy or management tools may hold the update back. |
| Windows 10 that cannot reach Windows 11 | Check the Windows 11 requirements with PC Health Check. Windows 10 left support on 14 October 2025. |
Signs of a hardware cause are a PC that is slow in everything, blue screens outside the update, and disk tools that report bad sectors or a failing health status. Copy your files off before any new attempt.
- What to send to Microsoft support: the code, the version you update from and to, and how you started it.
- Attach
SetupDiagResults.log,setupact.logandsetuperr.log. - Name the PC model and the percentage where the install stopped.
How to keep 0xc1900104 from coming back
- Install feature updates on the charger, with sleep set to Never.
- Keep 20 GB or more free on drive C.
- Unplug memory cards, hubs and docks before a feature update.
- Install chipset and storage drivers from the PC maker before you update.
- Do not close a laptop lid or switch off the PC during an update.
- Do not keep two security suites installed at the same time.
- Do not delete the $Windows.~BT folder before you have read its logs.
- Do not stay on Windows 10 for good: it no longer gets free security fixes.
A good time for a feature update is when you can leave the PC on its charger for two hours. Starting it at the end of the day and closing the lid is the most common way to hit a time-out.
Frequently asked questions
What does error 0xc1900104 mean?
It means Windows Setup stopped a feature update because it did not finish within the time Setup allows. Microsoft lists the code as MOSETUP_E_PROCESS_TIMEOUT, "The installation process did not complete within the required time limit." The code does not say what made the install slow. Usually the PC slept or lost power, a device hung, or the disk was nearly full. Your current Windows, files and apps stay as they were. Start with Fix 1.
What does Install error - 0xc1900104 in Windows Update mean?
It is the same code as it appears in Settings > Windows Update on Windows 11, next to the feature update that failed, such as version 24H2 or 25H2. Windows downloaded the update and started to install it, but the install ran out of time. Windows Update will offer it again later. You do not have to wait: restart, plug in, set sleep to Never and select Download & install again.
The update is stuck at 97%. Should I wait or restart?
Wait at least two hours while the screen says it is working, because a feature update can pause on one number for a long time. If it then fails with 0xc1900104, Setup has already given up and restored your Windows. One user on Microsoft Q&A saw exactly that at 97% on an Asus laptop. In that case, unplug extra devices and run SetupDiag to see where it stopped. Never cut power during the restart phase of an update.
I get 0xc1900104 on Windows 10. What should I do?
On Windows 10 the code appears when an upgrade to Windows 11, or an old feature update to 22H2, times out. The fixes are the same. Windows 10 left support on 14 October 2025 and no longer gets free security fixes, so the goal is to reach Windows 11. Check the requirements with PC Health Check first. If your PC is supported, run Fix 1 to Fix 3, then use the ISO in Fix 7.
Will I lose my files because of error 0xc1900104?
No. The error appears when Setup stops and keeps your current Windows, so your files, apps and settings stay where they were. The failed attempt leaves temporary installation files that take space, which Disk Cleanup can remove in Fix 3. A backup is still wise before you retry, and it is required before Fix 7, because a power cut during a restart can stop Windows from starting.
Does resetting Windows Update components fix 0xc1900104?
Only when the update cache is damaged, which is less common for this code. The update was already downloaded, so the time-out usually comes from sleep, a device or free space. On Microsoft Q&A, a user reset the components as advised and still got the same error at 97%. That is why the reset is Fix 6 here. Try it when other updates fail too, or when the download never finishes.
Is 0xc1900104 the same as 0xc1900101?
No. 0xc1900101 is Microsoft's generic rollback code, which usually means a driver crashed or hung after Setup had restarted into the new Windows. 0xc1900104 means Setup hit its time limit. The two can share a cause, a driver that hangs, so unplugging devices helps with both. If you see 0xc1900101 with a second code, read our guide to 0xC1900101 - 0x40021.
Can I install the update manually to avoid 0xc1900104?
For a feature update, the manual way is the Windows ISO or the Installation Assistant from Microsoft's download page, not a single file from the Update Catalog. Fix 7 shows how to mount the ISO and run setup.exe, keeping files and apps. It avoids the update cache, but it runs the same Setup engine. So prepare the PC first: charger, sleep set to Never, no extra devices and 20 GB free.
Windows will not update (не обновляется). Is this page for me?
This page is about one code, 0xc1900104, shown when a Windows feature update times out during installation. If your Windows will not update and Settings > Windows Update > Update history shows this code next to a feature update, the fixes above apply. If the history shows a different code, search for that code, because each one has a different cause. If no update installs at all, start with Fix 6.
Why did turning off sleep fix error 0xc1900104?
Because Setup measures how long the install takes. When a PC sleeps, closes its lid or runs out of battery, Setup's work stops, and the time limit can pass before it resumes. Keeping the PC plugged in and awake lets Setup work without breaks. That is why Fix 1 helps most readers. Remember to set sleep back to your usual value after the update.
Sources
- Microsoft Learn: Windows 10 upgrade resolution procedures (modern setup errors list with 0xC1900104 MOSETUP_E_PROCESS_TIMEOUT, SetupDiag, free space, clean boot) (learn.microsoft.com)
- Microsoft Learn: Windows 10 upgrade error codes (result codes and extend codes) (learn.microsoft.com)
- Microsoft Q&A: Error 0xc1900104 on update to Windows 11 24H2 (user report: stuck at 97%, setup.exe at 89%) (learn.microsoft.com)
Did this fix work?
One click, no account. It tells the next reader which guides are worth their time.
Questions and experiences: fix Windows update error 0xc1900104
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.
…