Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides troubleshooting guidance for issues that may occur while updating Microsoft 365 Apps. A reported update failure rarely indicates a final or permanent problem. Updates retry automatically and generally succeed over time without intervention. As a result, further action is generally not required. However, if devices in your environment are repeatedly failing to update and create compliance or servicing concerns, use the guidance in this article to investigate further.
General guidance for resolving update errors
Many update errors for Microsoft 365 Apps are due to temporary system or environmental conditions, such as loss of network connectivity or insufficient disk space. In these cases, the error occurs in the background with no impact to the end-user. Click-to-Run automatically retries within 24 hours. The following actions will resolve most update issues:
Restart the device
A device restart isn't required to apply updates to Microsoft 365 Apps. However, restarting the device can help clear up most transient conditions that prevent updates from installing successfully. These conditions include:- Applications holding files open
- In‑progress system operations
- Temporary access or file‑locking issues
- Incomplete shutdown or restart states
Verify network connectivity
Devices that update using the Office Content Delivery Network (CDN) require a reliable internet connection.- Confirm the device has reliable network connectivity
- Ensure the device can reach the recommended Microsoft 365 endpoints
- Check that network inspection, proxy, and/or VPN aren't blocking downloads
- If Delivery Optimization is in use, verify your configuration and try the DeliveryOptimizationTroubleshooter.
Verify disk space
Ensure devices have sufficient free disk space for updates to download and apply.- Target a minimum of 1 GB of free disk space, up to 5 GB if Microsoft 365 Apps has not been updated for several months
Verify endpoint security software
Ensure antivirus or other endpoint security software isn't aggressively scanning or blocking Office file paths.- C:\Program Files\Common Files\Microsoft Shared\ClickToRun\
- C:\Program Files\Microsoft Office\
- C:\Program Files (x86)\Microsoft Office\
- C:\ProgramData\Microsoft\ClickToRun\
- C:\ProgramData\Microsoft\Office\
Repair or reinstall
For persistent updates issues that aren't resolved using steps 1-4:- Try repairing the Office applications using the built-in repair tool.
- As a last resort, try reinstalling Microsoft 365 Apps using your preferred method.
Update errors
This section lists common update error codes for Microsoft 365 Apps. For devices managed by Cloud Update, error codes are reported in the Microsoft 365 Apps admin center as part of update status and reporting. Error codes can also appear directly in the application when an update is applied in the foreground on a device.
Note
For persistent Office installation or component issues, first address any underlying environmental causes and follow the recommendations in the table. If the issue persists, run a full Online Repair. If the device is multiple versions behind, use Update Repair to review its status and remotely initiate Online Repair on eligible devices.
Before starting a repair, ask users to save their work and close their Office apps. Office repair doesn't resolve Windows component, storage, network, or policy problems.
| Error code | Source | Error title | Description | Recommended action |
|---|---|---|---|---|
| 2 | Windows (Win32) | Required file not found | Windows couldn't find a file needed for the update. | • Check the update source and the file path shown in the logs. |
| 3 | Windows (Win32) | Required path not found | Windows couldn't find a path needed for the update. | • Check the local folder or shared update source. |
| 5 | Windows (Win32) | Access denied | Windows denied access needed for the update. | • Expected to resolve with a retry once a temporary access block clears. • If the issue persists, check permissions and security restrictions. |
| 8 | Windows (Win32) | Not enough available memory | The update operation didn't have enough memory to continue. | • Close unneeded apps or restart the device and retry. |
| 13 | Windows (Win32) | Invalid data | A Windows operation found invalid data. | • Use the update logs to identify the affected file or setting. |
| 19 | Windows (Win32) | Storage is read-only | The operation couldn't write to protected storage. | • Check the affected drive's settings and access permissions. |
| 21 | Windows (Win32) | Required device not ready | A device needed for the operation wasn't ready. | • Check its availability and retry. |
| 23 | Windows (Win32) | Stored data failed an integrity check | Windows detected an error while checking stored data. | • Check the affected files and drive before retrying. |
| 32 | Windows (Win32) | Required file is in use | Another process was using a file needed for the update. | • Expected to resolve with a retry once the file is released. • If needed, close the blocking app or restart the device. |
| 82 | Windows (Win32) | File or folder couldn't be created | Windows couldn't create a required file or folder. | • Check the location, permissions, and available storage. |
| 87 | Windows (Win32) | Invalid operation option | An operation received an option it couldn't use. | • Check the update command or settings if it keeps happening. |
| 112 | Windows (Win32) | Disk full | There wasn't enough disk space to complete the update. | • Free space on the affected drive and retry. |
| 123 | Windows (Win32) | Invalid file or folder name | A file, folder, or drive name wasn't valid. | • Check the configured update path and the name shown in the logs. |
| 193 | Windows (Win32) | Required program couldn't run | Windows couldn't run a required program because its format was invalid or incompatible. | • Check the file and its compatibility. |
| 216 | Windows (Win32) | Required program is incompatible | A required program wasn't compatible with the device's Windows version or processor type. | • Check the affected component. |
| 299 | Windows (Win32) | Memory operation wasn't completed | Windows could complete only part of a memory operation. | • Check the affected process and update logs. |
| 308 | Windows (Win32) | Required Windows component missing | Windows lacked a component needed to run a required program. | • Check the program requirements and Windows installation. |
| 433 | Windows (Win32) | Required device not found | Windows couldn't find a device needed by the operation. | • Check the relevant storage or device connection. |
| 473 | Windows (Win32) | Memory limit reached | Windows couldn't allocate enough memory for the operation. | • Reduce other workloads or restart the device and retry. |
| 487 | Windows (Win32) | Invalid memory address | A component tried to use an invalid memory address. | • Retry and check the update and application logs. |
| 786 | Windows (Win32) | Access blocked by administrator policy | An administrator's policy restricted access needed for the update. | • Review the policy with the responsible administrator. |
| 998 | Windows (Win32) | Invalid memory access | A component tried to use an invalid memory location. | • Retry and review application logs. |
| 1019 | Windows (Win32) | Registry log space unavailable | Windows couldn't allocate space for a registry log. | • Check disk space and Windows system logs. |
| 1062 | Windows (Win32) | Required service not running | A service needed for the update wasn't running. | • Identify the service in the logs and check its status. |
| 1117 | Windows (Win32) | Device read or write failed | Windows couldn't read from or write to a device. | • Check the affected device, storage, and system logs. |
| 1237 | Windows (Win32) | Operation needs another attempt | Windows couldn't complete the operation and requested a retry. | • Expected to resolve with a retry. • Investigate the update logs if the issue persists. |
| 1260 | Windows (Win32) | Program blocked by Group Policy | Group Policy blocked a program needed for the update. | • Review the policy with the administrator responsible for it. |
| 1392 | Windows (Win32) | File or folder is damaged | Windows found a file or folder that was damaged or unreadable. | • Check the affected drive and file system before retrying. |
| 1450 | Windows (Win32) | Not enough system resources | Windows didn't have enough resources to complete the update. | • Reduce other workloads or restart the device. |
| 1455 | Windows (Win32) | Windows memory limit reached | Windows couldn't reserve enough memory. | • Reduce memory use and review Windows memory settings. |
| 1722 | Windows (Win32) | Required component couldn't be contacted | Windows couldn't contact a component needed for the update. | • Check the relevant service or component. |
| 1726 | Windows (Win32) | Component request failed | A request to another component failed. | • Retry and check the component or service. |
| 1921 | Windows (Win32) | File name couldn't be resolved | Windows couldn't resolve a file name used by the update. | • Check the path and any links to the file. |
| 30015 | Click-to-Run | Windows error details missing | Office recorded a Windows error without including its details in this code. | • Check the update logs to find the actual error. |
| 30020 | Click-to-Run | Required file not found | Windows couldn't find a file needed for the update. | • Check the update source and file path. |
| 30029 | Click-to-Run | Invalid operation option | An operation received an option it couldn't use. | • Check the update command or settings if it keeps happening. |
| 30033 | Click-to-Run | Invalid update data | Office found invalid data needed for the update. | • Check the affected file or setting. |
| 30034 | Click-to-Run | Invalid update folder | An update operation used an invalid folder. | • Check the path, access permissions, and whether the folder is available. |
| 30035 | Click-to-Run | Invalid update data format | Office couldn't use the format of data or a file received by the update. | • Check the source files and update logs. |
| 30038 | Click-to-Run | Update operation not allowed | Office couldn't perform the update in its current state. | • Expected to resolve with a retry once a temporary blocking operation finishes. • Check update settings and logs if it persists. |
| 30045 | Click-to-Run | Invalid update information file | A file containing information needed for the update was invalid. | • Expected to resolve with a retry. |
| 30048 | Click-to-Run | Required update information missing | Office couldn't find required information in the update data. | • Check the update settings and files. |
| 30053 | Click-to-Run | No applicable Office products found | Office couldn't find products for the requested operation. | • Check the installed products and update configuration. |
| 30062 | Click-to-Run | Disk full | There wasn't enough disk space to complete the update. | • Free space on the affected drive and retry. |
| 30094 | Click-to-Run | Update signature couldn't be verified | Office couldn't verify the signature of update content. | • Expected to resolve with a retry if the download was incomplete. • Check the downloaded files and logs if it persists. |
| 30099 | Click-to-Run | Update coordination failed | Office couldn't create an item used to coordinate the update. | • Retry and check system resources and permissions. |
| 30116 | Click-to-Run | Service status couldn't be checked | Office couldn't check a service needed for the update. | • Check service availability and access. |
| 30117 | Click-to-Run | Office registry update failed | Office couldn't write required registry settings. | • Expected to resolve with a retry once a temporary registry-access block clears. • Check permissions and security restrictions if it persists. |
| 30143 | Click-to-Run | Required service couldn't stop | A service needed for the update couldn't be stopped. | • Restart the device and retry. |
| 30145 | Click-to-Run | Required service couldn't start | A service needed for the update didn't start. | • Check service status, permissions, and dependencies. |
| 30147 | Click-to-Run | Update files are in use | Office couldn't get exclusive access to the update files. | • Expected to resolve with a retry once the files are released. • Close blocking apps or resume a paused update if needed. |
| 30156 | Click-to-Run | Update operation canceled | The update was canceled. | • Expected to resolve with a retry after the cancellation or restart. |
| 30175 | Click-to-Run | Office update component failed | Office couldn't use a component needed for the update. | • Check the Click-to-Run logs. |
| 30177 | Click-to-Run | Update worker processes stopped | The processes doing the update stopped before finishing. | • Expected to resolve with a retry when the device is stable. |
| 30179 | Click-to-Run | Disk full | There wasn't enough disk space to complete the update. | • Free space on the affected drive and retry. |
| 30182 | Click-to-Run | Update file access failed | Office couldn't read or write update files. | • Expected to resolve with a retry once a temporary file-access block clears. • Check the path, permissions, and file locks if it persists. |
| 30183 | Click-to-Run | Update download failed | Office couldn't download update files. | • Expected to resolve with a retry after a temporary network interruption. • If the issue persists, check the update source, proxy, and network restrictions. |
| 30198 | Click-to-Run | Office configuration unavailable | Office couldn't read settings needed for the update. | • Expected to resolve with a retry if the configuration was temporarily unavailable. |
| 30204 | Click-to-Run | Target version doesn't support an installed product | The requested Office version doesn't support every installed product. | • Choose a version that supports the installed products. |
| 30211 | Click-to-Run | Update couldn't be prepared | Office couldn't prepare a required update operation. | • Retry and check the update logs. |
| 50002 | Click-to-Run | Update trigger disabled | This update attempt wasn't allowed by the current settings. | • Check which service or policy controls Office updates. |
| 50004 | Click-to-Run | Click-to-Run service stop failed | Office couldn't stop its Click-to-Run service for the update. | • Expected to resolve with a retry after a device restart. |
| 50006 | Click-to-Run | Office update files are in use | Office couldn't lock the update files. | • Expected to resolve with a retry once the files are released. • Close blocking apps or resume a paused update if needed. |
| 50013 | Click-to-Run | Update result is ambiguous | This code can represent a download blocked by network settings or an unidentified update result. | • Check the Click-to-Run version and update logs to identify the result. • If the logs confirm a network-policy block, review the metered-network policy. |
| 50014 | Click-to-Run | Download paused to save power | Office put the download on hold to save battery power. | • Connect the device to power and allow the download to retry. |
| 50015 | Click-to-Run | Update paused because of low battery | Office put update installation on hold because the battery was low. | • Connect the device to power. |
| 2147483658 | HRESULT, external dependency | Required information not yet available | Information needed for the update wasn't ready. | • Expected to resolve with a retry after the pending work finishes. |
| 2147500034 | HRESULT, external dependency | Required component function unavailable | A component didn't support a function the update requested. | • Check the component's installation and version. |
| 2147549186 | HRESULT, external dependency | Component request canceled | A request between components was canceled. | • Expected to resolve with a retry after a one-time cancellation. • Check the logs if it persists. |
| 2147549448 | HRESULT, external dependency | Update component disconnected | A component disconnected while the update was running. | • Retry and check the affected process or service. |
| 2147549457 | HRESULT, external dependency | Invalid component response | Windows received an invalid response from a component. | • Check the affected component and system logs. |
| 2147746065 | HRESULT, external dependency | Required component unavailable | A component couldn't provide a required function. | • Check the component's installation and version. |
| 2147746132 | HRESULT, external dependency | Required component not registered | Windows couldn't find registration for a required component. | • Identify the component in the logs and repair its installation. |
| 2147746291 | HRESULT, external dependency | Invalid component identifier | Windows received an invalid identifier for a component. | • Check the component's registration or settings. |
| 2147749890 | HRESULT, external dependency | Required Windows information not found | Windows couldn't find information needed for the operation. | • Check the Windows management service and its logs. |
| 2147749894 | HRESULT, external dependency | Not enough available memory | The update operation didn't have enough memory to continue. | • Close unneeded apps or restart the device and retry. |
| 2147749902 | HRESULT, external dependency | Windows information source not found | Windows couldn't find the information source Office requested. | • Check the affected component's installation. |
| 2147749939 | HRESULT, external dependency | Windows management service is stopping | The Windows management service was shutting down. | • Expected to resolve with a retry once the service has restarted. • Check the service status if the issue persists. |
| 2147749947 | HRESULT, external dependency | Windows management storage full | Windows ran out of space for management information. | • Check free disk space and management-service logs. |
| 2147942402 | Windows (HRESULT) | Required file not found | Windows couldn't find a file needed for the update. | • Check the update source and the file path shown in the logs. |
| 2147942403 | Windows (HRESULT) | Required path not found | Windows couldn't find a path needed for the update. | • Check the local folder or shared update source. |
| 2147942405 | HRESULT, external dependency | Access denied | Windows denied access needed for the update. | • Expected to resolve with a retry once a temporary access block clears. • If the issue persists, check permissions and security restrictions. |
| 2147942408 | Windows (HRESULT) | Not enough available memory | The update operation didn't have enough memory to continue. | • Close unneeded apps or restart the device and retry. |
| 2147942414 | HRESULT, external dependency | Not enough available memory | The update operation didn't have enough memory to continue. | • Close unneeded apps or restart the device and retry. |
| 2147942432 | Windows (HRESULT) | Required file is in use | Another process was using a file needed for the update. | • Expected to resolve with a retry once the file is released. • If needed, close the blocking app or restart the device. |
| 2147942487 | HRESULT, external dependency | Invalid operation option | An operation received an option it couldn't use. | • Check the update command or settings if it keeps happening. |
| 2147942512 | Windows (HRESULT) | Disk full | There wasn't enough disk space to complete the update. | • Free space on the affected drive and retry. |
| 2147943453 | Windows (HRESULT) | Service didn't respond in time | A service didn't respond within the allowed time. | • Check the service status and Windows logs. |
| 2147943458 | Windows (HRESULT) | Required service disabled | A required service couldn't start. | • Check whether it's disabled and review the settings or policy that controls it. |
| 2147943460 | Windows (HRESULT) | Required service not installed | Windows couldn't find a required service. | • Identify the service in the logs and repair the affected component. |
| 2147943468 | Windows (HRESULT) | Related service failed to start | A service needed by another required service failed to start. | • Check Windows service status and system logs. |
| 2147943515 | Windows (HRESULT) | System shutdown in progress | The device was shutting down while the update ran. | • Expected to resolve with a retry after the device restarts. |
| 2147943624 | Windows (HRESULT) | File still in use | Windows couldn't change a file while a process was still using it. | • Expected to resolve with a retry once the file is released. • If needed, close the blocking app or restart the device. |
| 2147943758 | Windows (HRESULT) | Windows data or storage is damaged | Windows found serious damage to stored data or the drive. | • Check storage health and system logs before retrying. |
| 2147943792 | Windows (HRESULT) | File or folder is damaged | Windows found a file or folder that was damaged or unreadable. | • Check the affected drive and file system before retrying. |
| 2147943850 | Windows (HRESULT) | Not enough system resources | Windows didn't have enough resources to complete the update. | • Reduce other workloads or restart the device. |
| 2147943860 | Windows (HRESULT) | Windows operation timed out | A Windows operation didn't finish within its time limit. | • Retry and check the affected component. |
| 2147944122 | Windows (HRESULT) | Required component couldn't be contacted | Windows couldn't contact a component needed for the update. | • Check the relevant service or component. |
| 2147944126 | Windows (HRESULT) | Component request failed | A request to another component failed. | • Retry and check the component or service. |
| 2147944127 | Windows (HRESULT) | Component request failed before it ran | A request to another component failed before it ran. | • Check the component or service, then retry. |
| 2147944183 | Windows (HRESULT) | Component received invalid data | A request between update components contained invalid data. | • Check the affected component and update logs. |
| 2147954402 | HRESULT, external dependency | Download connection timed out | A download request didn't finish within its time limit. | • Expected to resolve with a retry after a temporary network slowdown. • If the issue persists, check access to the update source. |
| 2147954407 | HRESULT, external dependency | Update server name couldn't be found | Windows couldn't find the download server's network address. | • Check name resolution and the update-source address. |
| 2147954429 | HRESULT, external dependency | Couldn't connect to the update server | Windows couldn't connect to the download server. | • Expected to resolve with a retry once connectivity is restored. • If the issue persists, check access to the update source. |
| 2147954430 | HRESULT, external dependency | Download connection ended unexpectedly | The connection to the download server ended unexpectedly. | • Expected to resolve with a retry after a temporary connection interruption. • If the issue persists, check network and proxy stability. |
| 2147954552 | HRESULT, external dependency | Invalid response from the update server | The server returned a response the download process couldn't use. | • Check the update source and any proxy. |
| 2147954556 | HRESULT, external dependency | Download redirection failed | The download couldn't follow a redirection to another address. | • Check that the redirected update address is reachable. |
| 2148007941 | HRESULT, external dependency | Required component couldn't start | Windows couldn't start a component needed for the update. | • Check its process, service, and permissions. |
| 2148007944 | HRESULT, external dependency | Required component is stopping | A component needed for the update was stopping. | • Expected to resolve with a retry once the component has restarted. |
| 2149122352 | HRESULT, external dependency | Download returned no new content (304) | The server reported that the content hadn't changed. | • If the download can't continue, check the update source and caching. |
| 2149122355 | HRESULT, external dependency | Download redirected to another address (307) | The server temporarily redirected the request. | • Check that the new address is reachable if the download fails. |
| 2149122448 | HRESULT, external dependency | Update server rejected the request (400) | The server received a request it couldn't accept. | • Check the update source and the request recorded in the logs. |
| 2149122451 | HRESULT, external dependency | Update download access denied (403) | The server refused access to the update files. | • Expected to resolve with a retry only if the access denial was temporary. • If the issue persists, check permissions, authentication, and network restrictions. |
| 2149122452 | HRESULT, external dependency | Update files not found on the server (404) | The server couldn't find the requested content. | • Check the update address and whether the required files are available. |
| 2149122455 | HRESULT, external dependency | Proxy requires authentication (407) | The proxy required authentication for the download. | • Check that the Office update service can authenticate through it. |
| 2149122548 | HRESULT, external dependency | Update server error (500) | The server failed while handling the download request. | • Expected to resolve with a retry after a temporary server error. • Retry later; check the update source if the issue persists. |
| 2149122550 | HRESULT, external dependency | Download server connection failed (502) | A gateway or proxy received an invalid reply from the update server. | • Expected to resolve with a retry after a temporary gateway error. • If the issue persists, check the proxy and connection path. |
| 2149122551 | HRESULT, external dependency | Update server unavailable (503) | The server couldn't handle the download request. | • Expected to resolve with a retry once the server is available. • Retry later; check the update source if the issue persists. |
| 2149580816 | HRESULT, external dependency | Background download lost its connection | The background download found no active network connection. | • Expected to resolve with a retry once connectivity is restored. • Allow the download to resume; investigate network access if the issue persists. |
| 2149580817 | HRESULT, external dependency | Server didn't provide the download size | The server didn't provide the file size needed for the download. | • Check the update source and response headers. |
| 2149580827 | HRESULT, external dependency | Invalid response to background download | The background download couldn't use the server's response. | • Check the update source and proxy behavior. |
| 2149580836 | HRESULT, external dependency | Background download isn't progressing | The background download stopped making progress. | • Expected to resolve with a retry after a temporary network interruption. • If the issue persists, check the update source, network, and proxy. |
| 2149580843 | HRESULT, external dependency | Invalid part of the file requested | The download requested data outside the available file. | • Check the update source and handling of partial downloads. |
| 2149580846 | HRESULT, external dependency | Background download connection closed early | The download connection closed before the transfer finished. | • Expected to resolve with a retry after a temporary connection interruption. • If the issue persists, check network and proxy stability. |
| 2149580884 | HRESULT, external dependency | Background download timed out | The background download didn't finish within its allowed time. | • Expected to resolve with a retry after a temporary network slowdown. • If the issue persists, check network reliability and the update source. |
| 2149580901 | HRESULT, external dependency | Background download paused for power saving | The background download paused while the device was saving power. | • It can resume when the device wakes. |
| 2149580908 | HRESULT, external dependency | Background download information is damaged | Windows found damage to saved background-download information. | • Review the background-download service logs and recovery guidance. |
| 2149580911 | HRESULT, external dependency | Background download paused by Game Mode | Windows paused the download while another app was using Game Mode. | • It can resume when that condition ends. |
| 2161119233 | HRESULT, external dependency | Delivery Optimization service unavailable | Delivery Optimization couldn't provide the download service. | • Check the service status and logs. |
| 2161123330 | HRESULT, external dependency | Delivery Optimization download isn't progressing | Delivery Optimization couldn't make download progress within the allowed time. | • Expected to resolve with a retry after a temporary network interruption. • If the issue persists, check network access and download-service logs. |
| 2161129477 | HRESULT, external dependency | Delivery Optimization lost its connection | Delivery Optimization paused the download after losing network access. | • Expected to resolve with a retry once connectivity is restored. • Allow Delivery Optimization to resume; investigate network access if the issue persists. |
| 2161135617 | HRESULT, external dependency | Downloaded data size didn't match the request | The server returned a different amount of data than requested. | • Check the update source and handling of partial downloads. |
| 2278556181 | HRESULT, external dependency | Required management item not found | Configuration Manager couldn't find a required item. | • Check that the relevant deployment and its files are available to the device. |
| -2147418110 | HRESULT, external dependency | Component request canceled | A request between components was canceled. | • Expected to resolve with a retry after a one-time cancellation. • Check the logs if it persists. |
| -2147024882 | HRESULT, external dependency | Not enough available memory | The update operation didn't have enough memory to continue. | • Close unneeded apps or restart the device and retry. |
| -2147024784 | Windows (HRESULT) | Disk full | There wasn't enough disk space to complete the update. | • Free space on the affected drive and retry. |
| -2147012894 | HRESULT, external dependency | Download connection timed out | A download request didn't finish within its time limit. | • Expected to resolve with a retry after a temporary network slowdown. • If the issue persists, check access to the update source. |
| -2147012889 | HRESULT, external dependency | Update server name couldn't be found | Windows couldn't find the download server's network address. | • Check name resolution and the update-source address. |
| -2147012867 | HRESULT, external dependency | Couldn't connect to the update server | Windows couldn't connect to the download server. | • Expected to resolve with a retry once connectivity is restored. • If the issue persists, check access to the update source. |
| -2147012866 | HRESULT, external dependency | Download connection ended unexpectedly | The connection to the download server ended unexpectedly. | • Expected to resolve with a retry after a temporary connection interruption. • If the issue persists, check network and proxy stability. |
| -2146974768 | Windows (HRESULT) | Disk full | There wasn't enough disk space to complete the update. | • Free space on the affected drive and retry. |
| -2145844845 | HRESULT, external dependency | Update download access denied (403) | The server refused access to the update files. | • Expected to resolve with a retry only if the access denial was temporary. • If the issue persists, check permissions, authentication, and network restrictions. |
| -2145844745 | HRESULT, external dependency | Update server unavailable (503) | The server couldn't handle the download request. | • Expected to resolve with a retry once the server is available. • Retry later; check the update source if the issue persists. |
| -2145386480 | HRESULT, external dependency | Background download lost its connection | The background download found no active network connection. | • Expected to resolve with a retry once connectivity is restored. • Allow the download to resume; investigate network access if the issue persists. |
| -2145386412 | HRESULT, external dependency | Background download timed out | The background download didn't finish within its allowed time. | • Expected to resolve with a retry after a temporary network slowdown. • If the issue persists, check network reliability and the update source. |
| -2145386388 | HRESULT, external dependency | Background download information is damaged | Windows found damage to saved background-download information. | • Review the background-download service logs and recovery guidance. |
| -2133843966 | HRESULT, external dependency | Delivery Optimization download isn't progressing | Delivery Optimization couldn't make download progress within the allowed time. | • Expected to resolve with a retry after a temporary network interruption. • If the issue persists, check network access and download-service logs. |
| -2133837819 | HRESULT, external dependency | Delivery Optimization lost its connection | Delivery Optimization paused the download after losing network access. | • Expected to resolve with a retry once connectivity is restored. • Allow Delivery Optimization to resume; investigate network access if the issue persists. |
| -2133831679 | HRESULT, external dependency | Downloaded data size didn't match the request | The server returned a different amount of data than requested. | • Check the update source and handling of partial downloads. |
| -2133793950 | HRESULT, external dependency | Delivery Optimization download isn't progressing | Delivery Optimization couldn't make download progress within the allowed time. | • Expected to resolve with a retry after a temporary network interruption. • If the issue persists, check network access and download-service logs. |
| -2133793949 | HRESULT, external dependency | Delivery Optimization download isn't progressing | Delivery Optimization couldn't make download progress within the allowed time. | • Expected to resolve with a retry after a temporary network interruption. • If the issue persists, check network access and download-service logs. |
Related articles
HRESULT Values
Microsoft 365 URLs and IP address ranges
Repair an Office application