0x800705b4In Windows Update, 0x800705b4 describes an operation that timed out or was interrupted. It does not identify one cause or establish that the cache must be deleted. What matters is whether downloading, preparing or installing was underway, whether one KB or all updates are affected, and whether Windows has already declared failure. This diagnosis does not cover activation, Defender or Sandbox even if they show the same number.
Windows Update error 0x800705b4
The update took too long or was interrupted. Retry after a normal restart and check connectivity before attempting advanced repairs.
Try this first
1 quick checks · ~3 min
Find your situation
See all the clues. Choose the one that matches what you observe.
Still working without a declared failure
Do not interrupt installation merely because a percentage is unchanged.
One specific KB fails
Investigate that package and its stage before repairing all of Windows.
Several updates fail
Compare download and installation to locate the shared blockage.
Managed PC
Policy and update-server conditions need review with IT.
Diagnostic signals
- ObservationDownload completed
- Makes connectivity a less sufficient explanation: review preparation or installation and its logs.
- ObservationAnother code appears
- Keep both in order; the new error may narrow the next step.
Step-by-step solutions
Record package, stage and state
Record what failed before retrying or repairing.
In Windows Update note the KB, visible stage, time and code. Check Update history to see whether others finished. Do not cancel an active operation to obtain this information.
If organization management is indicated, follow that branch. If installation is still active, follow the waiting branch; if already failed, separate one KB from a general failure.
Do not confuse delay with confirmed failure
Keep power stable and allow installation to finish. A fixed percentage does not establish a universal safe shutdown deadline. If Windows requests a restart, use its normal option; do not force it with the power button.
If it eventually fails and the desktop returns, record the result and continue by package or scope. If the PC remains stuck with Windows unusable, seek assistance with the screen, duration and observed activity; do not repeatedly cut power.
Investigate a KB that fails alone
Find that KB in Microsoft’s official update history for your Windows version. If a known problem matches version and symptom, follow its resolution or stated waiting guidance; matching only the code is insufficient.
If the attempt has failed and Windows is usable, save work, restart normally and retry once with stable power and connectivity. If it works, stop. If the same KB fails again at the same stage, preserve its logs before resetting components.
Separate downloading from installation
If downloads fail and other connections also fail, address connectivity first. If downloads finish but several installations fail, investigate update processing; changing DNS does not assess that stage.
With Windows usable, run the Windows Update troubleshooter through Get Help and review proposed changes. Record what it finds or repairs. A no-problems result does not prove installation is healthy: if failure persists, proceed to logs.
Preserve device policy
Give IT the KB, stage, time and whether other PCs in the same group fail. A WSUS server, pending approval or policy needs review by that environment’s administrator; do not infer it solely from 0x800705b4.
Do not change services, registry, corporate VPN or update server to bypass configuration. If IT confirms a shared incident, stop local repairs until it is resolved.
Advanced checks
Continue if the earlier steps did not help. Read each procedure’s precautions first.
Use logs to choose a repair
Only after a repeated failure and with authorization: open Command Prompt and use this PowerShell invocation to generate a readable log copy. It collects information; it does not repair components or delete the cache.
powershell.exe -NoProfile -Command "Get-WindowsUpdateLog"Creates a static snapshot; correlate the attempt time and KB rather than isolated old errors.
For installation, review or provide support with %systemroot%\Logs\CBS\CBS.log; for downloading, the Windows Update log distinguishes that activity. A final timeout may be a consequence: find the first failure related to the attempt or ask for interpretation.
Only if diagnosis confirms component damage does a Microsoft-guided DISM/SFC repair make sense. If it identifies policy or downloading, address that condition. Do not delete SoftwareDistribution, extend registry timeouts or reinstall Windows based solely on the code.
Still not working?
Without a new cause to test, stop retrying. Provide KB, stage, codes in order and logs from the same attempt. Repair should address that finding rather than follow an automatic command list.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
- Microsoft SupportOfficialTroubleshoot problems updating Windows
- Microsoft LearnOfficialWindows Update log files
- Microsoft LearnOfficialRepair a Windows Image
Source review: . A documentation review, not a physical hardware test.
Related problems
Windows Update error 0x80240034
The update or its download is incomplete. Check connectivity and Windows Update state before deleting downloaded files.
View solutionInternet keeps disconnecting
Connectivity works, then drops again. Record which devices and connection types fail together; that pattern is more useful than repeatedly resetting the network.
View solution