The following table lists the most common upgrade and installation errors and some things you can try to fix them.
|0xc1900223||This indicates that there was a problem downloading and installing the selected update. Windows Update will try again later and there is nothing you need to do at this time.|
|0xC1900208 – 0x4000C||This could indicate that an incompatible app installed on your PC is blocking the upgrade process from completing. Check to make sure that any incompatible apps are uninstalled and then try upgrading again.|
|0xC1900107||A cleanup operation from a previous installation attempt is still pending, and a system restart is required to continue the upgrade. Restart the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and clean up the temporary files and the System files|
|0x80073712||A file needed by Windows Update is likely damaged or missing. Try repairing your system files: Select the Start button and type command prompt in the search box on the taskbar. Choose Command Prompt from the list of results. In the window that appears, type DISM.exe /Online /Cleanup-image /Restorehealth and press the Enter key.|
|0xC1900200 – 0x20008||This may signify that your PC doesn’t meet the minimum requirements to download or install the upgrade to Windows 10.|
|0xC1900202 – 0x20008||This may signify that your PC doesn’t meet the minimum requirements to download or install the upgrade to Windows 10.|
|0x800F0923||This might indicate that a driver or other software on your PC isn't compatible with the upgrade to Windows 10.|
|0x80200056||This could mean that the upgrade process was interrupted because you accidentally restarted your PC or signed out of your PC. Try upgrading again and make sure your PC is plugged in and stays turned on.|
|0x800F0922||This error might mean that your PC couldn't connect to the Windows Update servers. If you're using a VPN connection to connect to a work network, disconnect from the network and turn off the VPN software (if applicable) and try upgrading again. The error could also mean there isn't enough free space in the System Reserved partition. You might be able to fix this problem by using third-party software to increase the size of the System Reserved partition.|
|We couldn't complete the updates. Undoing changes. Don't turn off your computer.||These are generic errors that might appear any time a Windows update fails. You'll need to determine the specific error code to investigate how to best resolve this problem. You can find the error code for the failed update by viewing your update history. Look for the update that wasn't installed, note the error code, and then contact Microsoft support.|
|Failure configuring Windows Updates. Reverting changes.||These are generic errors that might appear any time a Windows update fails. You'll need to determine the specific error code to investigate how to best resolve this problem. You can find the error code for the failed update by viewing your update history. Look for the update that wasn't installed, note the error code, and then contact Microsoft support.|
|The update isn't applicable to your computer.||This error might mean that your PC doesn't have the required updates installed. Check to make sure that all important updates are installed on your PC before you try upgrading.|
|0x80070070 – 0x50011||This likely indicates that your PC doesn’t have enough space available to install the upgrade. Free some space on the drive and try again.|
|0x80070070 – 0x50012||This likely indicates that your PC doesn’t have enough space available to install the upgrade. Free some space on the drive and try again.|
|0x80070070 – 0x60000||This likely indicates that your PC doesn’t have enough space available to install the upgrade. Free some space on the drive and try again.|
|0x80300024||he specified disk operation is not supported by the target disk, partition, or volume. Make sure your machine meets the minimum requirements to install Windows 10.|
|0x80070002 0x20009||The system cannot find the file specified. If you have a disk or disks where you are not installing Windows 10 on, remove those disks.|
|0xC1900101 0x20017||A driver has caused a problem. Disable or remove all 3rd party antivirus or antispyware from your system. Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display. Contact your hardware vendor to obtain updated device drivers.|
|0xC1900101 0x30017||A driver has caused a problem. Disable or remove all 3rd party antivirus or antispyware from your system. Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display. Contact your hardware vendor to obtain updated device drivers.|
|0x8007042B 0x4000D||Windows Setup terminated unexpectedly due to another process running in the background. When you start Windows by using a normal startup, several applications and services start automatically, and then run in the background. These programs include basic system processes, antivirus software, system utility applications, and other software that has been previously installed. These applications and services can cause interference when you attempt to upgrade to the latest version of Windows 10. To help you determine whether a background program is interfering with the upgrade, a "clean boot" may be needed.|
|0x800700B7 0x2000a||Windows Setup terminated unexpectedly due to another process running in the background. Uninstall any antivirus or antispyware software and update again.|
|0xC1900210||MOSETUP_E_COMPAT_SCANONLY. Setup did not find any compat issue.|
|0xC1900208||MOSETUP_E_COMPAT_INSTALLREQ_BLOCK. Setup found an actionable compat issue, such as an incompatible app.|
|0xC1900204||MOSETUP_E_COMPAT_MIGCHOICE_BLOCK. The migration choice selected is not available (ex: Enterprise to Home)|
|0xC1900200||MOSETUP_E_COMPAT_SYSREQ_BLOCK. The computer is not eligible for Windows 10.|
|0xC190020E||MOSETUP_E_INSTALLDISKSPACE_BLOCK. The computer does not have enough free space to install.|
|0x8024402F||WU_E_PT_ECP_SUCCEEDED_WITH_ERRORS. External cab file processing completed with some errors. One of the reasons we see this issue is due to the design of a software called Lightspeed Rocket for Web filtering. The IP addresses of the computers you want to get updates successfully on, should be added to the exceptions list of Lightspeed.|
|0x80242006||WU_E_UH_INVALIDMETADATA. A handler operation could not be completed because the update contains invalid metadata. Rename Software Redistribution Folder and attempt to download the updates again: Rename the following folders to *.BAK: - %systemroot%\system32\catroot2 To do this, type the following commands at a command prompt. Press ENTER after you type each command. - Ren %systemroot%\SoftwareDistribution\DataStore *.bak - Ren %systemroot%\SoftwareDistribution\Download *.bak Ren %systemroot%\system32\catroot2 *.bak|
|0x80070BC9||ERROR_FAIL_REBOOT_REQUIRED. The requested operation failed. A system reboot is required to roll back changes made. Ensure that we do not have any policies that control the start behavior for the Windows Module Installer. This service should not be hardened to any start value and should be managed by the OS.|
|0x80200053||BG_E_VALIDATION_FAILED. Ensure that there is no Firewalls that filter downloads. The Firewall filtering may lead to invalid responses being received by the Windows Update Client. If the issue still persists, run the WU reset script.|
|0x80072EE2||WININET_E_TIMEOUT. The operation timed out. This error message can be caused if the computer isn't connected to Internet. To fix this issue, following these steps: make sure these URLs are not blocked: http://.update.microsoft.com https://.update.microsoft.com http://download.windowsupdate.com Additionally , you can take a network trace and see what is timing out.
|0x80072EFD||TIME_OUT_ERRORS. The operation timed out. Make sure there are no firewall rules or proxy to block Microsoft download URLs. Take a network monitor trace to understand better.
|0x80072EFE||TIME_OUT_ERRORS. The operation timed out. Make sure there are no firewall rules or proxy to block Microsoft download URLs. Take a network monitor trace to understand better.
|0x80D02002||TIME_OUT_ERRORS. The operation timed out. Make sure there are no firewall rules or proxy to block Microsoft download URLs. Take a network monitor trace to understand better.
|0X8007000D||ERROR_INVALID_DATA. Indicates invalid data downloaded or corruption occurred. Attempt to re-download the update and initiate installation.|
|0x8024A10A||USO_E_SERVICE_SHUTTING_DOWN. Indicates that the WU Service is shutting down. This may happen due to a very long period of time of inactivity, a system hang leading to the service being idle and leading to the shutdown of the service. Ensure that the system remains active and the connections remain established to complete the upgrade.|
|0x80240020||WU_E_NO_INTERACTIVE_USER. Operation did not complete because there is no logged-on interactive user. Please login to the system to initiate the installation and allow the system to be rebooted.|
|0x80242014||WU_E_UH_POSTREBOOTSTILLPENDING. The post-reboot operation for the update is still in progress. Some Windows Updates require the system to be restarted. Reboot the system to complete the installation of the Updates.|
|0x80246017||WU_E_DM_UNAUTHORIZED_LOCAL_USER. The download failed because the local user was denied authorization to download the content. Ensure that the user attempting to download and install updates has been provided with sufficient privileges to install updates (Local Administrator).|
|0x8024000B||WU_E_CALL_CANCELLED. Operation was cancelled. This indicates that the operation was cancelled by the user/service. You may also encounter this error when we are unable to filter the results. Run the Decline Superseded PowerShell script to allow the filtering process to complete.|
|0x8024000E||WU_E_XML_INVALID. Windows Update Agent found invalid information in the update's XML data. Certain drivers contain additional metadata information in the update.xml, which could lead Orchestrator to understand it as invalid data. Ensure that you have the latest Windows Update Agent installed on the machine.|
|0x8024D009||WU_E_SETUP_SKIP_UPDATE. An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file. You may encounter this error when WSUS is not sending the Self-update to the clients. Review KB920659 for instructions to resolve the issue.|
|0x80244007||WU_E_PT_SOAPCLIENT_SOAPFAULT. SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes. This issue occurs because Windows cannot renew the cookies for Windows Update. Review KB2883975 for instructions to resolve the issue.|
Windows Update troubleshooting
The update is not applicable to your computer
The most common reasons for this error are described in the following table:
Cause: Update is superseded
Explanation: As updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you’re trying to install already has a newer version of the payload on your system, you may encounter this error message.
Resolution: Check that the package that you are installing contains newer versions of the binaries. Or, check that the package is superseded by another new package.
Cause: Update is already installed
Explanation: If the update that you’re trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message.
Resolution: Verify that the package that you are trying to install was not previously installed.
Cause: Wrong update for architecture
Explanation: Updates are published by CPU architecture. If the update that you’re trying to install does not match the architecture for your CPU, you may encounter this error message.
Resolution: Verify that the package that you’re trying to install matches the Windows version that you are using. The Windows version information can be found in the “Applies To” section of the article for each update. For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers. Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. For example, an x86-based update cannot be installed on x64-based installations of Windows.
Cause: Missing prerequisite update
Explanation: Some updates require a prerequisite update before they can be applied to a system. If you are missing a prerequisite update, you may encounter this error message. For example, KB 2919355 must be installed on Windows 8.1 and Windows Server 2012 R2 computers before many of the updates that were released after April 2014 can be installed.
Resolution: Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. For example, if you encounter the error message on Windows 8.1 or Windows Server 2012 R2, you may have to install the April 2014 update 2919355 as a prerequisite and one or more pre-requisite servicing updates (KB 2919442 and KB 3173424). Note: To determine if these prerequisite updates are installed, run the following PowerShell command: get-hotfix KB3173424,KB2919355,KB2919442 If the updates are installed, the command will return the installed date in the “InstalledOn” section of the output.
Windows Update error codes by component
Automatic Update Errors
|0x80243FFF||WU_E_AUCLIENT_UNEXPECTED. There was a user interface error not covered by another WU_E_AUCLIENT_* error code.|
|0x8024A000||WU_E_AU_NOSERVICE. Automatic Updates was unable to service incoming requests.|
|0x8024A002||WU_E_AU_NONLEGACYSERVER. The old version of the Automatic Updates client has stopped because the WSUS server has been upgraded.|
|0x8024A003||WU_E_AU_LEGACYCLIENTDISABLED. The old version of the Automatic Updates client was disabled.|
|0x8024A004||WU_E_AU_PAUSED. Automatic Updates was unable to process incoming requests because it was paused.|
|0x8024A005||WU_E_AU_NO_REGISTERED_SERVICE. No unmanaged service is registered with AU.|
|0x8024AFFF||WU_E_AU_UNEXPECTED. An Automatic Updates error not covered by another WU_E_AU* code.|
Windows Update UI errors
|0x80243001||WU_E_INSTALLATION_RESULTS_UNKNOWN_VERSION. The results of download and installation could not be read from the registry due to an unrecognized data format version.|
|0x80243002||WU_E_INSTALLATION_RESULTS_INVALID_DATA. The results of download and installation could not be read from the registry due to an invalid data format.|
|0x80243003||WU_E_INSTALLATION_RESULTS_NOT_FOUND. The results of download and installation are not available; the operation may have failed to start.|
|0x80243004||WU_E_TRAYICON_FAILURE. A failure occurred when trying to create an icon in the taskbar notification area.|
|0x80243FFD||WU_E_NON_UI_MODE. Unable to show UI when in non-UI mode; WU client UI modules may not be installed.|
|0x80243FFE||WU_E_WUCLTUI_UNSUPPORTED_VERSION. Unsupported version of WU client UI exported functions.|
|0x80243FFF||WU_E_AUCLIENT_UNEXPECTED. There was a user interface error not covered by another WU_E_AUCLIENT_* error code.|
|0x80249001||WU_E_INVENTORY_PARSEFAILED. Parsing of the rule file failed.|
|0x80249002||WU_E_INVENTORY_GET_INVENTORY_TYPE_FAILED. Failed to get the requested inventory type from the server.|
|0x80249003||WU_E_INVENTORY_RESULT_UPLOAD_FAILED. Failed to upload inventory result to the server.|
|0x80249004||WU_E_INVENTORY_UNEXPECTED. There was an inventory error not covered by another error code.|
|0x80249005||WU_E_INVENTORY_WMI_ERROR. A WMI error occurred when enumerating the instances for a particular class.|
Expression evaluator errors
|0x8024E001||WU_E_EE_UNKNOWN_EXPRESSION. An expression evaluator operation could not be completed because an expression was unrecognized.|
|0x8024E002||WU_E_EE_INVALID_EXPRESSION. An expression evaluator operation could not be completed because an expression was invalid.|
|0x8024E003||WU_E_EE_MISSING_METADATA. An expression evaluator operation could not be completed because an expression contains an incorrect number of metadata nodes.|
|0x8024E004||WU_E_EE_INVALID_VERSION. An expression evaluator operation could not be completed because the version of the serialized expression data is invalid.|
|0x8024E005||WU_E_EE_NOT_INITIALIZED. The expression evaluator could not be initialized.|
|0x8024E006||WU_E_EE_INVALID_ATTRIBUTEDATA. An expression evaluator operation could not be completed because there was an invalid attribute.|
|0x8024E007||WU_E_EE_CLUSTER_ERROR. An expression evaluator operation could not be completed because the cluster state of the computer could not be determined.|
|0x8024EFFF||WU_E_EE_UNEXPECTED. There was an expression evaluator error not covered by another WU_E_EE_* error code.|
Windows Update Error Code List
|0x80247001||An operation could not be completed because the scan package was invalid.|
|0x80247002||An operation could not be completed because the scan package requires a greater version of the Windows Update Agent.|
|0x80247FFF||Search using the scan package failed.|
|0x8024F001||The event cache file was defective.|
|0x8024F002||The XML in the event namespace descriptor could not be parsed.|
|0x8024F003||The XML in the event namespace descriptor could not be parsed.|
|0x8024F004||The server rejected an event because the server was too busy.|
|0x8024FFFF||There was a reporter error not covered by another error code.|
|0x80245001||The redirector XML document could not be loaded into the DOM class.
|0x80245002||The redirector XML document is missing some required information.
|0x80245003||The redirectorId in the downloaded redirector cab is less than in the cached cab.
|0x80245FFF||The redirector failed for reasons not covered by another WU_E_REDIRECTOR_* error code.
|0x80244000||WU_E_PT_SOAPCLIENT_* error codes map to the SOAPCLIENT_ERROR enum of the ATL Server Library.|
|0x80244001||Same as SOAPCLIENT_INITIALIZE_ERROR - initialization of the SOAP client failed possibly because of an MSXML installation failure.|
|0x80244002||Same as SOAPCLIENT_OUTOFMEMORY - SOAP client failed because it ran out of memory.|
|0x80244003||Same as SOAPCLIENT_GENERATE_ERROR - SOAP client failed to generate the request.|
|0x80244004||Same as SOAPCLIENT_CONNECT_ERROR - SOAP client failed to connect to the server.|
|0x80244005||Same as SOAPCLIENT_SEND_ERROR - SOAP client failed to send a message for reasons of WU_E_WINHTTP_* error codes.|
|0x80244006||Same as SOAPCLIENT_SERVER_ERROR - SOAP client failed because there was a server error.|
|0x80244007||Same as SOAPCLIENT_SOAPFAULT - SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes.|
|0x80244008||Same as SOAPCLIENT_PARSEFAULT_ERROR - SOAP client failed to parse a SOAP fault.
|0x80244009||Same as SOAPCLIENT_READ_ERROR - SOAP client failed while reading the response from the server.|
|0x8024400A||Same as SOAPCLIENT_PARSE_ERROR - SOAP client failed to parse the response from the server.|
|0x8024400B||Same as SOAP_E_VERSION_MISMATCH - SOAP client found an unrecognizable namespace for the SOAP envelope.|
|0x8024400C||Same as SOAP_E_MUST_UNDERSTAND - SOAP client was unable to understand a header.|
|0x8024400D||Same as SOAP_E_CLIENT - SOAP client found the message was malformed; fix before resending.|
|0x8024400E||Same as SOAP_E_SERVER - The SOAP message could not be processed due to a server error; resend later.|
|0x8024400F||There was an unspecified Windows Management Instrumentation (WMI) error.|
|0x80244010||The number of round trips to the server exceeded the maximum limit.|
|0x80244011||WUServer policy value is missing in the registry.|
|0x80244012||Initialization failed because the object was already initialized.|
|0x80244013||The computer name could not be determined.|
|0x80244015||The reply from the server indicates that the server was changed or the cookie was invalid; refresh the state of the internal cache and retry.|
|0x80244016||Same as HTTP status 400 - the server could not process the request due to invalid syntax.|
|0x80244017||Same as HTTP status 401 - the requested resource requires user authentication.|
|0x80244018||Same as HTTP status 403 - server understood the request but declined to fulfill it.|
|0x80244019||Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier).|
|0x8024401A||Same as HTTP status 405 - the HTTP method is not allowed.|
|0x8024401B||Same as HTTP status 407 - proxy authentication is required.|
|0x8024401C||Same as HTTP status 408 - the server timed out waiting for the request.|
|0x8024401D||Same as HTTP status 409 - the request was not completed due to a conflict with the current state of the resource.|
|0x8024401E||Same as HTTP status 410 - requested resource is no longer available at the server.|
|0x8024401F||Same as HTTP status 500 - an error internal to the server prevented fulfilling the request.|
|0x80244020||Same as HTTP status 500 - server does not support the functionality required to fulfill the request.|
|0x80244021||Same as HTTP status 502 - the server while acting as a gateway or a proxy received an invalid response from the upstream server it accessed in attempting to fulfill the request.|
|0x80244022||Same as HTTP status 503 - the service is temporarily overloaded.|
|0x80244023||Same as HTTP status 503 - the request was timed out waiting for a gateway.|
|0x80244024||Same as HTTP status 505 - the server does not support the HTTP protocol version used for the request.|
|0x80244025||Operation failed due to a changed file location; refresh internal state and resend.|
|0x80244026||Operation failed because Windows Update Agent does not support registration with a non-WSUS server.|
|0x80244027||The server returned an empty authentication information list.|
|0x80244028||Windows Update Agent was unable to create any valid authentication cookies.|
|0x80244029||A configuration property value was wrong.|
|0x8024402A||A configuration property value was missing.|
|0x8024402B||The HTTP request could not be completed and the reason did not correspond to any of the WU_E_PT_HTTP_* error codes.|
|0x8024402C||Same as ERROR_WINHTTP_NAME_NOT_RESOLVED - the proxy server or target server name cannot be resolved.|
|0x8024402F||External cab file processing completed with some errors.|
|0x80244030||The external cab processor initialization did not complete.|
|0x80244031||The format of a metadata file was invalid.
|0x80244032||External cab processor found invalid metadata.
|0x80244033||The file digest could not be extracted from an external cab file.
|0x80244034||An external cab file could not be decompressed.
|0x80244035||External cab processor was unable to get file locations.
|0x80244FFF||A communication error not covered by another WU_E_PT_* error code.
|0x8024502D||Windows Update Agent failed to download a redirector cabinet file with a new redirectorId value from the server during the recovery.|
|0x8024502E||A redirector recovery action did not complete because the server is managed.|
|0x80246001||A download manager operation could not be completed because the requested file does not have a URL.|
|0x80246002||A download manager operation could not be completed because the file digest was not recognized.|
|0x80246003||A download manager operation could not be completed because the file metadata requested an unrecognized hash algorithm.|
|0x80246004||An operation could not be completed because a download request is required from the download handler.|
|0x80246005||A download manager operation could not be completed because the network connection was unavailable.|
|0x80246006||A download manager operation could not be completed because the version of Background Intelligent Transfer Service (BITS) is incompatible.|
|0x80246007||The update has not been downloaded.
|0x80246008||A download manager operation failed because the download manager was unable to connect the Background Intelligent Transfer Service (BITS).|
|0x80246009||A download manager operation failed because there was an unspecified Background Intelligent Transfer Service (BITS) transfer error.|
|0x8024600A||A download must be restarted because the location of the source of the download has changed.|
|0x8024600B||A download must be restarted because the update content changed in a new revision.|
|0x80246FFF||There was a download manager error not covered by another WU_E_DM_* error code.|
|0x80242000||A request for a remote update handler could not be completed because no remote process is available.|
|0x80242001||A request for a remote update handler could not be completed because the handler is local only.|
|0x80242002||A request for an update handler could not be completed because the handler could not be recognized.|
|0x80242003||A remote update handler could not be created because one already exists.
|0x80242004||A request for the handler to install (uninstall) an update could not be completed because the update does not support install (uninstall).|
|0x80242005||An operation did not complete because the wrong handler was specified.
|0x80242006||A handler operation could not be completed because the update contains invalid metadata.|
|0x80242007||An operation could not be completed because the installer exceeded the time limit.|
|0x80242008||An operation being done by the update handler was canceled.
|0x80242009||An operation could not be completed because the handler-specific metadata is invalid.|
|0x8024200A||A request to the handler to install an update could not be completed because the update requires user input.|
|0x8024200B||The installer failed to install (uninstall) one or more updates.
|0x8024200C||The update handler should download self-contained content rather than delta-compressed content for the update.|
|0x8024200D||The update handler did not install the update because it needs to be downloaded again.|
|0x8024200E||The update handler failed to send notification of the status of the install (uninstall) operation.|
|0x8024200F||The file names contained in the update metadata and in the update package are inconsistent.|
|0x80242010||The update handler failed to fall back to the self-contained content.
|0x80242011||The update handler has exceeded the maximum number of download requests.|
|0x80242012||The update handler has received an unexpected response from CBS.|
|0x80242013||The update metadata contains an invalid CBS package identifier.
|0x80242014||The post-reboot operation for the update is still in progress.
|0x80242015||The result of the post-reboot operation for the update could not be determined.|
|0x80242016||The state of the update after its post-reboot operation has completed is unexpected.|
|0x80242017||The OS servicing stack must be updated before this update is downloaded or installed.|
|0x80242FFF||An update handler error not covered by another WU_E_UH_* code.
|0x80248000||An operation failed because Windows Update Agent is shutting down.
|0x80248001||An operation failed because the data store was in use.
|0x80248002||The current and expected states of the data store do not match.
|0x80248003||The data store is missing a table.
|0x80248004||The data store contains a table with unexpected columns.
|0x80248005||A table could not be opened because the table is not in the data store.
|0x80248006||The current and expected versions of the data store do not match.
|0x80248007||The information requested is not in the data store.
|0x80248008||The data store is missing required information or has a NULL in a table column that requires a non-null value.|
|0x80248009||The data store is missing required information or has a reference to missing license terms file localized property or linked row.|
|0x8024800A||The update was not processed because its update handler could not be recognized.
|0x8024800B||The update was not deleted because it is still referenced by one or more services.
|0x8024800C||The data store section could not be locked within the allotted time.
|0x8024800D||The category was not added because it contains no parent categories and is not a top-level category itself.|
|0x8024800E||The row was not added because an existing row has the same primary key.
|0x8024800F||The data store could not be initialized because it was locked by another process.
|0x80248010||The data store is not allowed to be registered with COM in the current process.
|0x80248011||Could not create a data store object in another process.
|0x80248013||The server sent the same update to the client with two different revision IDs.
|0x80248014||An operation did not complete because the service is not in the data store.
|0x80248015||An operation did not complete because the registration of the service has expired.
|0x80248016||A request to hide an update was declined because it is a mandatory update or because it was deployed with a deadline.|
|0x80248017||A table was not closed because it is not associated with the session.
|0x80248018||A table was not closed because it is not associated with the session.
|0x80248019||A request to remove the Windows Update service or to unregister it with Automatic Updates was declined because it is a built-in service and/or Automatic Updates cannot fall back to another service.|
|0x8024801A||A request was declined because the operation is not allowed.|
|0x8024801B||The schema of the current data store and the schema of a table in a backup XML document do not match.|
|0x8024801C||The data store requires a session reset; release the session and retry with a new session.|
|0x8024801D||A data store operation did not complete because it was requested with an impersonated identity.|
|0x80248FFF||A data store error not covered by another WU_E_DS_* code.
|0x8024C001||A driver was skipped.
|0x8024C002||A property for the driver could not be found. It may not conform with required specifications.|
|0x8024C003||The registry type read for the driver does not match the expected type.
|0x8024C004||The driver update is missing metadata.
|0x8024C005||The driver update is missing a required attribute.
|0x8024C006||Driver synchronization failed.
|0x8024C007||Information required for the synchronization of applicable printers is missing.
|0x8024CFFF||A driver error not covered by another WU_E_DRV_* code.
|0x80240001||Windows Update Agent was unable to provide the service.
|0x80240002||The maximum capacity of the service was exceeded.
|0x80240003||An ID cannot be found.
|0x80240004||The object could not be initialized.
|0x80240005||The update handler requested a byte range overlapping a previously requested range.|
|0x80240006||The requested number of byte ranges exceeds the maximum number (2^31 - 1).
|0x80240007||The index to a collection was invalid.
|0x80240008||The key for the item queried could not be found.
|0x80240009||Another conflicting operation was in progress. Some operations such as installation cannot be performed twice simultaneously.|
|0x8024000A||Cancellation of the operation was not allowed.
|0x8024000B||Operation was canceled.
|0x8024000C||No operation was required.
|0x8024000D||Windows Update Agent could not find required information in the update's XML data.|
|0x8024000E||Windows Update Agent found invalid information in the update's XML data.
|0x8024000F||Circular update relationships were detected in the metadata.
|0x80240010||Update relationships too deep to evaluate were evaluated.
|0x80240011||An invalid update relationship was detected.
|0x80240012||An invalid registry value was read.
|0x80240013||Operation tried to add a duplicate item to a list.
|0x80240016||Operation tried to install while another installation was in progress or the system was pending a mandatory restart.|
|0x80240017||Operation was not performed because there are no applicable updates.
|0x80240018||Operation failed because a required user token is missing.
|0x80240019||An exclusive update cannot be installed with other updates at the same time.
|0x8024001A||A policy value was not set.
|0x8024001B||The operation could not be performed because the Windows Update Agent is self-updating.|
|0x8024001D||An update contains invalid metadata.
|0x8024001E||Operation did not complete because the service or system was being shut down.
|0x8024001F||Operation did not complete because the network connection was unavailable.|
|0x80240020||Operation did not complete because there is no logged-on interactive user.
|0x80240021||Operation did not complete because it timed out.
|0x80240022||Operation failed for all the updates.
|0x80240023||The license terms for all updates were declined.
|0x80240024||There are no updates.
|0x80240025||Group Policy settings prevented access to Windows Update.
|0x80240026||The type of update is invalid.
|0x80240027||The URL exceeded the maximum length.
|0x80240028||The update could not be uninstalled because the request did not originate from a WSUS server.|
|0x80240029||Search may have missed some updates before there is an unlicensed application on the system.|
|0x8024002A||A component required to detect applicable updates was missing.|
|0x8024002B||An operation did not complete because it requires a newer version of server.
|0x8024002C||A delta-compressed update could not be installed because it required the source.
|0x8024002D||A full-file update could not be installed because it required the source.
|0x8024002E||Access to an unmanaged server is not allowed.
|0x8024002F||Operation did not complete because the DisableWindowsUpdateAccess policy was set.|
|0x80240030||The format of the proxy list was invalid.
|0x80240031||The file is in the wrong format.
|0x80240032||The search criteria string was invalid.
|0x80240033||License terms could not be downloaded.
|0x80240034||Update failed to download.
|0x80240035||The update was not processed.
|0x80240036||The object's current state did not allow the operation.|
|0x80240037||The functionality for the operation is not supported.
|0x80240038||The downloaded file has an unexpected content type.
|0x80240039||Agent is asked by server to resync too many times.
|0x80240040||WUA API method does not run on Server Core installation.
|0x80240041||Service is not available while sysprep is running.
|0x80240042||The update service is no longer registered with AU.
|0x80240043||There is no support for WUA UI.
|0x80240FFF||An operation failed due to reasons not covered by another error code.
|0x00240001||Windows Update Agent was stopped successfully.
|0x00240002||Windows Update Agent updated itself.
|0x00240003||Operation completed successfully but there were errors applying the updates.
|0x00240004||A callback was marked to be disconnected later because the request to disconnect the operation came while a callback was executing.|
|0x00240005||The system must be restarted to complete installation of the update.
|0x00240006||The update to be installed is already installed on the system.
|0x00240007||The update to be removed is not installed on the system.
|0x00240008||The update to be downloaded has already been downloaded.
|0x80241001||Search may have missed some updates because the Windows Installer is less than version 3.1.|
|0x80241002||Search may have missed some updates because the Windows Installer is not configured.|
|0x80241003||Search may have missed some updates because policy has disabled Windows Installer patching.|
|0x80241004||An update could not be applied because the application is installed per-user.
|0x80241FFF||Search may have missed some updates because there was a failure of the Windows Installer.|
|0x8024D001||Windows Update Agent could not be updated because an INF file contains invalid information.|
|0x8024D002||Windows Update Agent could not be updated because the wuident.cab file contains invalid information.|
|0x8024D003||Windows Update Agent could not be updated because of an internal error that caused setup initialization to be performed twice.|
|0x8024D004||Windows Update Agent could not be updated because setup initialization never completed successfully.|
|0x8024D005||Windows Update Agent could not be updated because the versions specified in the INF do not match the actual source file versions.|
|0x8024D006||Windows Update Agent could not be updated because a WUA file on the target system is newer than the corresponding source file.|
|0x8024D007||Windows Update Agent could not be updated because regsvr32.exe returned an error.|
|0x8024D009||An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file.|
|0x8024D00A||Windows Update Agent could not be updated because the current system configuration is not supported.|
|0x8024D00B||Windows Update Agent could not be updated because the system is configured to block the update.|
|0x8024D00C||Windows Update Agent could not be updated because a restart of the system is required.|
|0x8024D00D||Windows Update Agent setup is already running.
|0x8024D00E||Windows Update Agent setup package requires a reboot to complete installation.|
|0x8024D00F||Windows Update Agent could not be updated because the setup handler failed during execution.|
|0x8024D010||Windows Update Agent could not be updated because the registry contains invalid information.|
|0x8024D013||Windows Update Agent could not be updated because the server does not contain update information for this version.|
|0x8024DFFF||Windows Update Agent could not be updated because of an error not covered by another WU_E_SETUP_* error code.|