How to fix Windows Update error 0x8007041D?

Error 0x8007041D is Windows error 1053: a service did not answer its start request in time, so Windows Update gave up. The update is fine; a service it needs, usually BITS, Windows Update or Cryptographic Services, starts too slowly. Restart, then test each service with net start to find the slow one.

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

What error 0x8007041D means in Windows Update

0x8007041D is not a Windows Update code of its own. The first half, 0x8007, marks an ordinary Windows error wrapped in the format that update components use. The second half, 041D, is the number 1053 written in hexadecimal. Microsoft's list of system error codes names 1053 ERROR_SERVICE_REQUEST_TIMEOUT, with one sentence: "The service did not respond to the start or control request in a timely fashion."

So the update file is rarely the problem. Windows Update depends on several services, and each one must tell the Service Control Manager that it is running. If one of them stays silent for too long, Windows stops waiting, records the timeout and reports 0x8007041D. You can print the same sentence yourself with net helpmsg 1053 in any command window.

What causes 0x8007041D, from most to least likely

By definition there is one cause: a service did not answer in time. What differs is why it was slow. Microsoft's own article on slow services gives only the workaround of a longer wait and adds that the timeout may be "a symptom of another problem". The table ties each likely reason to the fix that addresses it.

How to fix Windows Update error 0x8007041D

Fix 1 is the diagnosis, and everybody starts there: it takes five minutes and changes nothing. Its result tells you whether to go on with a clean boot (Fix 2), an update reset (Fix 3) or a longer timeout (Fix 4). Fixes 5 to 7 are the general repairs for a slow drive or damaged Windows files.

Fix 1. Restart, then find the service that times out

5 minutesNo riskAlways first: you see 0x8007041D and do not yet know which service is too slow.

Error 1053 always belongs to one service. Starting each update service by hand shows which one stays silent, and a restart alone clears a service that was stuck in a starting state.

1. Restart the PC with Start > Power > Restart, not Shut down. Try the update once more.
2. If it fails again, on Windows 11 right-click Start and select Terminal (Admin). On Windows 10, type cmd in the search box and select Run as administrator.
3. Start the update services one at a time. "The requested service has already been started" is a good answer.

   net start bits
   net start wuauserv
   net start cryptsvc
   net start trustedinstaller

4. Note the one that answers with "System error 1053 has occurred" or takes very long. That is the slow service.
5. Check its state. A line STATE with 2 START_PENDING that does not change means the service hangs while starting.

   sc.exe query bits

6. Open Settings > Windows Update and select Check for updates while the services are running.

• Read the event log too. Right-click Start, select Event Viewer, open Windows Logs > System and look for source Service Control Manager with event 7000, 7009 or 7011 at the time of the failed update. The event names the service.
• Event 7000 reads that the service "failed to start due to the following error: The service did not respond to the start or control request in a timely fashion."
• Events 7009 and 7011 report that a timeout was reached and print how many milliseconds Windows waited.

Fix 2. Start Windows with a clean boot and run the update

15 minutesLow riskA service times out in normal start-up, or many programs and third-party services load at sign-in.

A clean boot starts Windows with its own services only. If a third-party service or startup program slows the start of BITS or Windows Update, the update service answers in time and the update goes through.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

   

3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

   

5. 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.

   

6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. 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

1. After the restart, open Settings > Windows Update and select Check for updates, or Retry next to the failed update.
2. When the update is installed, switch the services and startup apps back on in groups and restart after each group. The group after which 0x8007041D returns holds the program that slows the services.
3. Update or remove that program. Leave Hide all Microsoft services ticked whenever you change services in System Configuration.

Fix 3. Reset the Windows Update components

15 minutesLow riskThe services start, but BITS or Windows Update hangs or stops while it checks or downloads.

Windows Update and BITS read their download queue and data store when they start work. A damaged or oversized store can keep them busy past the timeout. The reset gives both a clean, empty store.

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

The net stop and net start commands of the reset are a test in themselves. If net start bits or net start wuauserv answers with "System error 1053 has occurred" even with an empty store, the service is slow for another reason: go to Fix 4.

Fix 4. Give services more time to start with ServicesPipeTimeout

10 minutesRead the warningA service starts on the second try, or events 7009 or 7011 show that the wait ran out on a slow PC.

This is Microsoft's own workaround for a slow service that does not start in time. The registry value ServicesPipeTimeout sets how long the Service Control Manager waits before it logs a timeout.

1. Press Win + R, type regedit and press Enter. Select Yes in the User Account Control prompt.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
3. Look for ServicesPipeTimeout in the right pane. If it is not there, select Edit > New > DWORD (32-bit) Value and name it ServicesPipeTimeout.
4. Right-click ServicesPipeTimeout and select Modify.
5. Select Decimal, type 60000 and select OK. The value is in milliseconds, so 60000 is 60 seconds.
6. Restart the PC and try the update again.

The same in an administrator command window

reg add "HKLM\SYSTEM\CurrentControlSet\Control" /v ServicesPipeTimeout /t REG_DWORD /d 60000 /f

• Raise it in small steps. Microsoft recommends increasing the number a little at a time until the service can start, not setting a very large value.
• It is a workaround. Microsoft notes that the slow start may be a symptom of another problem. Keep looking for the cause with Fix 5 and Fix 6.
• To undo: delete the value with reg delete "HKLM\SYSTEM\CurrentControlSet\Control" /v ServicesPipeTimeout /f and restart, or import your backup.

Fix 5. Check the system drive for errors and free space

20 to 60 minutesLow riskThe PC starts slowly in general, the Windows drive is nearly full, or the disk is an older hard drive.

Every service loads its files from the Windows drive. A drive with file system errors or no free room answers slowly, which delays service starts and gives an update no space to unpack.

1. Open File Explorer > This PC and look at the free space of the Windows drive, usually C:.
2. If the bar is red or nearly full, free some space first: Free up disk space and delete temporary files
3. Run a disk check on the Windows drive. Windows schedules it for the next restart because the drive is in use.
4. Restart, let the check finish, then try the update.

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 6. Repair Windows system files with DISM and SFC

20 to 40 minutesLow riskAll update services start, yet the update still fails with 0x8007041D.

A damaged system file behind one of the services can make it hang while starting. DISM repairs the store of Windows files, and System File Checker replaces damaged files from that store.

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

Restart the PC after both scans, run the net start test from Fix 1 again and check for updates. Windows 11 also has its own update troubleshooter under Settings > System > Troubleshoot > Other troubleshooters. It is quick and worth one try here: Run the Windows Update troubleshooter

Fix 7. Reinstall the current version of Windows and keep your files and apps

1 to 2 hoursLow riskEvery other fix left the error in place, or DISM and SFC could not repair the files.

A repair install writes all Windows files and services again while it keeps your files, apps and settings. It also installs the newest build, which is what the failed update tried to do.

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.

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

If 0x8007041D is still there: read what Windows logged

Windows writes down which service was too slow. The Service Control Manager records every start that timed out in the System log, and the event text names the service. With that name you can search the vendor of a third-party service or ask support a precise question.

• What to send to support: the event 7000, 7009 or 7011 text, the output of sc.exe query for that service, your Windows version from Settings > System > About and what you installed just before the error.
• When it is not yours to fix: on a work or school PC, services and update settings can be held by policy. Report the event text to the administrator.
• When it is hardware: many services time out at once, the PC is slow from the start and the disk check finds bad sectors. That points to a failing drive. Back up your files first and replace the drive.

How to keep 0x8007041D from coming back

Each point follows from what the code means. The error appears only when a service is slower than the wait allows, so anything that keeps service starts quick and the drive healthy keeps the code away.

Frequently asked questions

What does error 0x8007041D mean?

It means a Windows service did not respond to its start request in time. The code is system error 1053, named ERROR_SERVICE_REQUEST_TIMEOUT, in the notation Windows Update uses: 0x8007 marks a wrapped Windows error and 041D is 1053 in hexadecimal. Microsoft's text for it is "The service did not respond to the start or control request in a timely fashion." In Windows Update the slow service is usually BITS, Windows Update or Cryptographic Services. The update itself is rarely damaged.

How do I fix 0x8007041D on Windows 11?

Restart the PC first, then run net start bits, net start wuauserv and net start cryptsvc in Terminal (Admin). The service that answers with System error 1053 is the slow one. If one times out, try a clean boot and update from there. If the services start but the update hangs, reset the Windows Update components. On Windows 11 the failed update shows Install error - 0x8007041d or Download error - 0x8007041d in Settings > Windows Update, and Retry works after the fix.

Why do I see 0x8007041D in the Microsoft Store or the Xbox app?

The code means the same thing there: a service the app needs did not start in time. The Store and the Xbox app install apps and games through Windows services, so a slow or stuck service gives the same 1053 timeout. Restart the PC, then run the net start test from Fix 1 and look in Event Viewer for event 7000 or 7009 at the time of the error to see which service it was. We could not confirm from a Microsoft page which Store or Xbox service is affected most often.

Is 0x8007041D the same error in Windows Update in other languages?

Yes. The code stays the same in every language, only the sentence around it is translated. On a Russian Windows 10, for example, the message starts with "С установкой обновлений возникли некоторые проблемы" and ends with (0x8007041d). It is the same message as the English "There were some problems installing updates, but we'll try again later". The fixes on this page apply unchanged, and the commands such as net start bits are the same in every language version.

Is it safe to change ServicesPipeTimeout?

Yes, if you back up the key and change only that value. Microsoft documents it as a workaround for services that do not start in time, with 60000 milliseconds as the example. Microsoft also recommends raising the number in small steps and looking for the real cause, because a slow service may be a symptom of another problem. A very large value would make Windows wait a long time for a service that has really hung. To undo it, delete the value and restart.

Can antivirus software cause error 0x8007041D?

It can slow service starts, like any software that hooks into Windows at start-up, but we found no Microsoft page that names it as a cause of this code. The safe test is a clean boot, which stops third-party services without weakening Windows' own protection. If the update installs in a clean boot, bring the services back in groups to find the one that slows things down. Do not uninstall or disable your protection for good; update or replace the program instead.

Does a Windows Update troubleshooter fix 0x8007041D?

Sometimes, when the timeout came from a stuck service that the troubleshooter restarts or from a damaged update store it resets. It does not show you which service was slow, and it cannot change how long Windows waits for a service. That is why it sits late in this guide. Run the net start test first: it takes five minutes and tells you whether a clean boot, an update reset or a longer timeout is the next step.

Is 0x8007041D a sign of a hardware problem?

Usually not. One service that times out once points to software: a busy start-up, a third-party service or a damaged update store. Hardware becomes likely when many services time out together, the PC is slow from the moment it starts, and a disk check finds bad sectors. An old hard drive close to failing makes every service slow to load. In that case back up your files first, then check the drive with chkdsk and the maker's tool, and plan to replace it.

What is the difference between 0x8007041D and 0x80070422?

Both are service errors in Windows Update, but they mean different things. Code 0x8007041D is error 1053: the service exists and is allowed to start but did not answer in time. Code 0x80070422 is error 1058: the service is disabled, so Windows does not try to start it at all. For 1058 you set the start type back to Manual or Automatic. For 1053 you look for what makes the service slow. Running sc.exe query on the service shows which case you have.