How to Fix Windows Update Error 0x800705b4 Safely

Windows Update error 0x800705b4 means an update operation timed out before Windows could finish it. Restart the computer, run the built-in Windows Update troubleshooter, and, if the error remains, reset the Windows Update services and cache; these steps do not remove personal files.

What error 0x800705b4 means

Windows commonly displays the error like this:

0x800705b4 - The operation timed out.

The code appears when Windows Update starts an operation but does not receive a response within the expected time. Common causes include stuck Windows Update services, damaged files in the update cache, another update that is still pending, or interference from security software and other system processes.

A slow or unstable connection can contribute, but this error does not prove that your internet service is at fault. It can also appear when Windows has been running for a long time without a restart or when the system drive has too little free space for the update and its temporary files.

The steps below start with reversible checks. Do not delete random files from C:\Windows or use a registry cleaner; neither is needed for this error.

Check these issues before changing Windows

These steps apply to supported Windows 10 and Windows 11 installations. You need an Administrator account for the service-reset and repair commands later. A restart is required during the process. The steps do not intentionally delete personal files, but save your work first and make a current backup of files that would be difficult to replace before performing system repairs.

1. Confirm that websites and other online services load normally. If the connection is unreliable, reconnect to Wi-Fi or Ethernet and retry later.
2. Restart the computer from Start > Power > Restart. This can clear a pending update process that is holding the update service open.
3. Disconnect unnecessary USB drives, docks, printers, and other devices temporarily. Leave the keyboard, mouse, display, and network connection attached.
4. Check the free space on the Windows system drive, normally C:. Open File Explorer, select This PC, and make sure the drive is not nearly full. Windows needs working space for downloaded and unpacked update files.
5. Check the date, time, and time zone. Open Settings > Time & language > Date & time, turn on Set time automatically, and select Sync now if that option is available.

If the error returns after these checks, continue with the troubleshooter. Do not permanently disable Windows security protections. If third-party antivirus software is involved, use its documented temporary pause option and turn it back on immediately after testing.

Fix Windows Update error 0x800705b4 step by step

Start with the built-in troubleshooter. It can repair common service and configuration problems without changing the update cache.

1. Open the Windows Update troubleshooter.

Windows 11: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run
Windows 10: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter

2. Apply any recommended repair, then restart Windows if the troubleshooter requests it. Try Windows Update again. If it reports that it found and fixed a problem, the service configuration was likely involved. If it finds nothing or the same code returns, reset the update services and cache.
3. Open Command Prompt as Administrator. Select Start, type cmd, right-click Command Prompt, choose Run as administrator, and approve the User Account Control prompt.

The next steps stop update-related services and rename their downloaded cache folders. Renaming is safer than deleting because Windows creates fresh folders and the old data remains available until you remove it later.

4. Stop the services that may have locked update files.

net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver

Each service should report that it was stopped or was not started. If a service cannot be stopped, close Settings and other update-related windows, restart the PC, and run the commands again.

5. Rename the Windows Update cache folders.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

A successful command returns to the prompt without an error. If Windows says the file is in use, repeat the service-stop commands and check that Command Prompt is running as Administrator. Do not rename the System32 folder itself; rename only the catroot2 folder shown above.

6. Start the services again.

net start wuauserv
net start bits
net start cryptsvc
net start msiserver

Each service should report that it started successfully or was already running. If a service fails to start, record the message instead of repeatedly deleting folders. That result points to a service configuration or permissions problem that needs further repair.

7. Restart Windows. The first update check after a cache reset can take longer because Windows must create new cache data and download the update again. Leave the .old folders in place until the update succeeds and you no longer need the rollback data.

How to confirm Windows Update is working

After the restart, retry the update from Settings.

1. Open the Windows Update page.

Windows 11: Settings > Windows Update
Windows 10: Settings > Update & Security > Windows Update

2. Select Check for updates, install the offered update, and restart if Windows asks. Do not force the computer off while the update is applying.
3. Return to the same page and check the status. A successful installation should show that Windows is up to date or list the update as installed rather than offering the same update again.
4. Review the update history if you need confirmation.

Windows 11: Settings > Windows Update > Update history
Windows 10: Settings > Update & Security > View update history

Look for the update and an Installed successfully result. If 0x800705b4 no longer appears but a different error code does, the cache reset addressed the timeout and exposed a separate problem. Record the new code and the update's name instead of repeating the same reset commands.

What to do if the error keeps returning

If the troubleshooter and cache reset do not help, repair Windows component files before considering a reinstall. These commands require an elevated Command Prompt and can take time.

1. Open Command Prompt as Administrator.
2. Repair the Windows component store.

DISM.exe /Online /Cleanup-Image /RestoreHealth

A successful run ends with a message that the restore operation completed successfully. If DISM reports that it cannot find source files or ends with an error, note the exact code and continue only if you have an appropriate Windows installation source or reliable technical guidance.

3. Check and repair protected system files.

sfc /scannow

Useful results are that no integrity violations were found or that corrupted files were found and repaired. If SFC says some files could not be repaired, restart and run it once more after DISM. Persistent failures indicate deeper component damage.

4. Temporarily remove likely update conflicts. Disconnect nonessential hardware, pause scheduled third-party system cleaners, and check whether third-party antivirus or endpoint software has a documented Windows Update compatibility issue. Use the vendor's supported pause or uninstall process, then restore protection immediately after the test. Do not permanently disable security software.
5. If repairs keep failing, an in-place repair installation is usually safer than resetting Windows. It reinstalls Windows system components while normally preserving personal files, installed applications, and settings, provided you choose the option to keep them. Read every installer screen carefully and back up important files first. A full reset or clean installation should be a last resort because it can remove applications and, depending on the option selected, personal data.

Seek further help when DISM or SFC reports unrepaired corruption, the update service will not start, the problem affects several computers, or the same update fails with a new code after the cache reset. Include the Windows version, update identifier, exact error message, and the results of DISM and SFC when asking for assistance.

Conclusion

Try the update once more after the restart and cache reset. If it installs, keep the renamed cache folders until you have confirmed the system is stable, then remove them if you need the disk space. If the timeout returns, run DISM and SFC and keep their exact results for further troubleshooting.

Frequently Asked Questions

Will resetting the Windows Update cache delete my personal files?

No. The commands stop update services and rename temporary update folders. They do not target documents, photos, installed applications, or personal settings. Save your work before restarting, as you would for any system maintenance.

Should I delete the SoftwareDistribution folder instead of renaming it?

No. Renaming it is the safer first choice. Windows creates a new cache automatically, while the old folder remains available if you need to inspect it. Delete the old folder only after the update succeeds and only if you need the storage space.

Why did I get a different error after fixing 0x800705b4?

The timeout may have been resolved, allowing Windows to reach the next stage of installation. A new code points to a different issue, so record it and follow troubleshooting for that specific code rather than repeating the same cache reset.