0X800705B4
What it means
The update process took too long and timed out — often due to a stuck background service.
Also seen as: 0x800705B4
Quick fix steps
- Restart the PC and try again — this alone frequently clears the stuck state.
- Restart the Windows Update, Background Intelligent Transfer, and Cryptographic services via Services (services.msc).
- Run the Windows Update Troubleshooter.
For the full step-by-step walkthrough, see Windows Update Stuck "Checking for Updates".
Frequently Asked Questions
Does "timeout" mean my internet is too slow?
Not necessarily — it can also mean a specific Windows Update service got stuck or unresponsive, which is why restarting the Windows Update service is often more effective than just checking your connection speed.
Should I just wait longer instead of troubleshooting?
If it happens once, waiting and retrying is reasonable. If it happens repeatedly on the same update, that points to something worth actively fixing rather than just waiting out.
Other error codes
0X80070002 — File Not Found
Windows Update can't find a file it expects, usually because the update cache is corrupted or a required file was deleted.
0X8024402F — Update Client Received Invalid Response
Windows Update can't properly connect to Microsoft's update servers — usually a network, proxy, or DNS issue rather than anything wrong with the update itself.
0X800F0922 — Update Failed to Install (SSL/Reserved Space)
Often caused by low disk space, a VPN interfering with the connection, or an .NET Framework update conflict.
0X80070003 — Path Not Found
Similar to 0x80070002 — Windows Update can't locate an expected file path, usually from a corrupted update cache.