Additional Resources for Windows Server Update Services
Applies To: Windows Server Update Services
For more information and support, see the following resources.
Windows Server Update Services Communities
Microsoft communities are great places to exchange ideas with other users and discuss common issues. You can read and write messages by using an NNTP-based newsreader such as Microsoft Outlook Express. You can also use the Web-based newsreader provided by Microsoft to access all of the newsgroups. To access the WSUS Communities, go to the following:
- Windows Server Update Services Communities Homepage at https://go.microsoft.com/fwlink/?LinkID=45215
More Documentation
For high-level information about what's new and features of WSUS, see Microsoft Windows Server Update Services Overview at https://go.microsoft.com/fwlink/?LinkID=42213.
For step-by-step guidance for getting started, including installing WSUS, setting up a client computer, and deploying your first set of updates, see Step-by-Step Guide to Getting Started with Microsoft Windows Server Update Services 2.0
For information about planning for, installing, and then configuring WSUS components and infrastructure, see Deploying Microsoft Windows Server Update Services at https://go.microsoft.com/fwlink/?linkid=41777.
For information that helps you automate tasks or customize WSUS, see the Microsoft Windows Server Update Services Software Developer's Kit at https://go.microsoft.com/fwlink/?LinkID=43099 and Windows Update Agent Software Developer's Kit at https://go.microsoft.com/fwlink/?LinkID=43101. Note that the Windows Update Agent is the Automatic Updates service. Both SDKs contain information about the application programming interface (API), as well as sample scripts and ready-to-use tools for your WSUS deployment and implementation.
WSUS Server Error Codes
Hexadecimal Error Code |
Decimal Error Code |
Error String |
Description |
0x00000000 |
-4294967296 |
Success |
Success |
0x00000001 |
-4294967295 |
ERROR_INVALID_FUNCTION |
Invalid function. |
0x0000007B |
-4294967173 |
Error_Invalid_Name |
The filename, directory name,or volume label syntax is incorrect |
0x00000275 |
-4294966667 |
Error_cant_enable_Deny_only |
A group marked use for deny only can not be enabled |
0x0000041D |
-4294966243 |
ERROR_SERVICE_ REQUEST_TIMEOUT |
The service did not respond to the start or control request in a timely fashion. |
0x000004C3 |
-4294966077 |
Error_Session_Credential_Conflict |
Multiple connections to a server or shared resource by the same user,using more than one user name, are not allowed. |
0x000004C5 |
-4294966075 |
Error_Dup_Domainename |
The workgroup or domain name is already in use by another computer on the network. |
0x000005D5 |
-4294965803 |
NULL |
|
0x00000619 |
-4294965735 |
error_Invalid_HW_Profile |
The specified hardware profile configuration is invalid |
0x00000641 |
-4294965695 |
Error_Install_Service_failure |
The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Microsoft Windows Installer is not correctly installed. |
0x00000643 |
-4294965693 |
ERROR_INSTALL_FAILURE |
Fatal error during installation |
0x00000652 |
-4294965678 |
ERROR_INSTALL_ ALREADY_RUNNING |
Another installation is already in progress. Complete that installation before proceeding with this install. |
0x000006D9 |
-4294965543 |
EPT_S_Not_Registered |
There are no more endpoints available from the endpoint mapper. |
0x000006F6 |
-4294965514 |
RPC_X_BYTE_Count_TOO_Small |
The byte count is too small |
0x00000963 |
-4294964893 |
NERR_BADPasswordCore |
This share name or password is invalid |
0x00000BC2 |
-4294964286 |
Error_Success_Reboot_Required |
|
0x00000C0B |
-4294964213 |
NULL |
|
0x00000CC4 |
-4294964028 |
NULL |
|
0x00000D47 |
-4294963897 |
NULL |
|
0x00000E5C |
-4294963620 |
NULL |
|
0x00000E74 |
-4294963596 |
NULL |
|
0x0000109F |
-4294963041 |
NULL |
|
0x00001112 |
-4294962926 |
Error_No_Media_In_Drive |
No media in drive |
0x0000117A |
-4294962822 |
NULL |
|
0x00001190 |
-4294962800 |
Error_Shutdown_IS_Scheduled |
A system shutdown has already been scheduled |
0x00001234 |
-4294962636 |
Error_Port_Unreachable |
No Service is operating at the destination network endpoint on the remote system |
0x00001396 |
-4294962282 |
Error_Wrong_Target_Name |
Logon failure: The target account name is incorrect. |
0x000013D7 |
-4294962217 |
Error_Cluster_restype_Note_Supported |
The specified node does not support a resource of this type. This amy be due to version inconsistancies or due to the absence of the resource DLL on this node. |
0x00001449 |
-4294962103 |
Error_Invalid_Showwin_Command |
Cannot show or remove the window in the way specified |
Windows Update Client Error Codes
Hexadecimal error code |
Error String |
Description |
0x00240001 |
WU_S_SERVICE_STOP |
Service stopped. |
0x00240002 |
WU_S_SELFUPDATE |
Agent selfupdates |
0x00240003 |
WU_S_UPDATE_ERROR |
Overall operation completed but error occurred while processing one or more specified updates. |
0x00240004 |
WU_S_ MARKED_FOR_DISCONNECT |
The system needs to be rebooted to complete installtation. |
0x00240006 |
WU_S_ ALREADY_INSTALLED |
The update to be installed is already installed. |
0x00240007 |
WU_S_ ALREADY_UNINSTALLED |
The update to be uninstalled is already not installed |
0x00240008 |
WU_S_ ALREADY_DOWNLOADED |
The update to be downloaded is already downloaded. |
0x80240001 |
WU_E_ NO_SERVICE |
Service stopped. For whatever reason, WSUS agent cannot provide the service. |
0x80240002 |
WU_E_ MAX_CAPACITY_REACHED |
Maximum capacity of the service is reached. |
0x80240003 |
WU_E_ UNKNOWN_ID |
Id not found. |
0x80240004 |
WU_E_ NOT_INITIALIZED |
Object is not correctly initialized. |
0x80240005 |
WU_E_ RANGEOVERLAP |
Update handler attempted to request a byte range that overlapped a previously requested byte range. |
0x80240006 |
WU_E_ TOOMANYRANGES |
Update handler attempted to request too many ranges (more than 2^31 - 1). |
0x80240007 |
WU_E_ INVALIDINDEX |
An attempt was made to use an invalid index. |
0x80240008 |
WU_E_ ITEMNOTFOUND |
A query was made for an item with a particular key and that key was not found |
0x80240009 |
WU_E_ OPERATIONINPROGRESS |
The caller attempted to perform an operation on an interface while another operation was in progress. |
0x8024000A |
WU_E_ COULDNOTCANCEL |
The caller attempted to cancel an operation that is not cancelable. |
0x8024000B |
WU_E_ CALL_CANCELLED |
Call has been cancelled. |
0x8024000C |
WU_E_ NOOP |
No operation is needed. |
0x8024000D |
WU_E_ XML_MISSINGDATA |
The WSUS agent is attempting to parse an update's XML blob and has not found expected data. |
0x8024000E |
WU_E_ XML_INVALID |
The WSUS agent is attempting to parse an update's XML blob and has encountered data that is invalid. |
0x8024000F |
WU_E_ CYCLE_DETECTED |
Cycle detected in metadata. |
0x80240010 |
WU_E_ TOO_DEEP_RELATION |
Too deep relationship found. |
0x80240011 |
WU_E_ INVALID_RELATIONSHIP |
Relationship data wrong for an update. |
0x80240012 |
WU_E_ REG_VALUE_INVALID |
Registry value was read but is invalid. |
0x80240013 |
WU_E_ DUPLICATE_ITEM |
Attempt was made to add a duplicate item to a list. |
0x80240016 |
WU_E_ INSTALL_NOT_ALLOWED |
Attempt was made to install while another install is going on or reboot is pending |
0x80240017 |
WU_E_ NOT_APPLICABLE |
Install is not needed because no updates are applicable. |
0x80240018 |
WU_E_ NO_USERTOKEN |
Operation failed due to missing user token. |
0x80240019 |
WU_E_ EXCLUSIVE_INSTALL_CONFILCT |
Attempt was made to install an exclusive update with other updates at the same time. |
0x8024001A |
WU_E_ POLICY_NOT_SET |
Policy value is not set. |
0x8024001B |
WU_E_ SELFUPDATE_IN_PROGRESS |
Self-update in progress. |
0x8024001D |
WU_E_ INVALID_UPDATE |
An update had invalid metadata. |
0x8024001E |
WU_E_ SERVICE_STOP |
Call was aborted due to service stop or system shut down. |
0x8024001F |
WU_E_ NO_CONNECTION |
No network connection is available to finish the operation. |
0x80240020 |
WU_E_ NO_INTERACTIVE_USER |
Interactive user is missing to finish the operation. |
0x80240021 |
WU_E_ TIME_OUT |
Operation timed out. |
0x80240022 |
WU_E_ ALL_UPDATES_FAILED |
Operation failed on all specified updates. |
0x80240023 |
WU_E_ EULAS_DECLINED |
EULAs for all the updates are declined. |
0x80240024 |
WU_E_NO_UPDATE |
There are no updates. |
0x80240025 |
WU_E_ USER_ACCESS_DISABLED |
User access to Windows Update is prevented by Group Policy setting. |
0x80240026 |
WU_E_ INVALID_UPDATE_TYPE |
Invalid type of update. |
0x80240027 |
WU_E_ URL_TOO_LONG |
URL is too long. |
0x80240028 |
WU_E_ UNINSTALL_NOT_ALLOWED |
Uninstall is not allowed due to non-managed environment. |
0x80240029 |
WU_E_ INVALID_PRODUCT_LICENSE |
A product with an invalid license was found on the system. |
0x8024002A |
WU_E_ MISSING_HANDLER |
A component required for detecting applicable updates was missing. |
0x8024002B |
WU_E_ LEGACYSERVER |
The WSUS server we are talking to is a Legacy SUS Server (SUS 1.0) |
0x8024002C |
WU_E_ BIN_SOURCE_ABSENT |
A binary-delta update failed because the source was required. |
0x8024002D |
WU_E_FF_ SOURCE_ABSENT |
A full-file update failed because the source was required. |
0x8024002E |
WU_E_ WU_DISABLED |
Non-managed server access is disallowed. |
0x8024002F |
WU_E_ CALL_CANCELLED_BY_POLICY |
Call cancelled because of DisableWindowsUpdateAccess policy takes effect. |
0x80240030 |
WU_E_ INVALID_PROXY_SERVER |
Invalid format for proxy list. |
0x80240031 |
WU_E_ INVALID_FILE |
File is not of the right format. |
0x80240032 |
WU_E_ INVALID_CRITERIA |
Invalid criteria string. |
0x80240033 |
WU_E_ EULA_UNAVAILABLE |
EULA download failure. |
0x80240034 |
WU_E_ DOWNLOAD_FAILED |
Failed to download. |
0x80240035 |
WU_E_ UPDATE_NOT_PROCESSED |
INTERNAL ONLY: The update was not processed. |
0x80240036 |
WU_E_ INVALID_OPERATION |
The operation is invalid for the object's current state. |
0x80240037 |
WU_E_ NOT_SUPPORTED |
The invoked functionality is not supported. |
0x80240FFF |
WU_E_ UNEXPECTED |
Unexpected failure. |
0x80241001 |
WU_E_ MSI_WRONG_VERSION |
The Windows Installer version on the machine is less than what we expect (WSUS requires Windows Installer 3.0) |
0x80241002 |
WU_E_ MSI_NOT_CONFIGURED |
Windows Installer is not configured. |
0x80241003 |
WU_E_ MSP_DISABLED |
Windows Installer updating is disabled by policy. |
0x80241FFF |
WU_E_ MSP_UNEXPECTED |
Unexpected MSP failure. |
0x80244000 |
WU_E_PT_ SOAPCLIENT_BASE |
Used as a base to map SOAP client errors. |
0x80244001 |
WU_E_PT_ SOAPCLIENT_INITIALIZE_ERROR |
Initialization failed; most likely an MSXML installation problem. |
0x80244002 |
WU_E_PT_ SOAPCLIENT_OUTOFMEMORY |
SOAP client out of memory. |
0x80244003 |
WU_E_PT_ SOAPCLIENT_GENERATE |
SOAP client failed in generating the response. |
0x80244004 |
WU_E_PT_ SOAPCLIENT_CONNECT |
SOAP client failed connecting to server. |
0x80244005 |
WU_E_PT_ SOAPCLIENT_SEND |
SOAP client failed in sending message. Deprecated in favor of the more specific underlying WinHTTP errors, which will be returned when the client encounters an error communicating with the server. |
0x80244006 |
WU_E_PT_ SOAPCLIENT_SERVER |
SOAP server error. |
0x80244007 |
WU_E_PT_ SOAPCLIENT_SOAPFAULT |
Fault was returned by the server. |
0x80244008 |
WU_E_PT_ SOAPCLIENT_PARSEFAULT |
Failed in parsing SOAP. |
0x80244009 |
WU_E_PT_ SOAPCLIENT_READ |
Failed in reading response. |
0x8024400B |
WU_E_PT_ SOAP_VERSION |
Invalid namespace for the SOAP envelope. |
0x8024400C |
WU_E_PT_ SOAP_MUST_UNDERSTAND |
Child of header with mustUnderstand = 1 wasn't understood or obeyed/ |
0x8024400D |
WU_E_PT_ SOAP_CLIENT |
The message was malformed or incomplete. |
0x8024400E |
WU_E_PT_ SOAP_SERVER |
The message was OK but server couldn't process at the moment. Same message may succeed at a later time. |
0x8024400F |
WU_E_PT_ WMI_ERROR |
An unspecified error occurred using WMI/ |
0x80244010 |
WU_E_PT_ EXCEEDED_MAX_SERVER_TRIPS |
The maximum allowed number of round trips to the server was exceeded. |
0x80244011 |
WU_E_PT_ SUS_SERVER_NOT_SET |
WSUS server policy value is missing in the registry. |
0x80244012 |
WU_E_PT_ DOUBLE_INITIALIZATION |
Object is initialized second time. |
0x80244013 |
WU_E_PT_ INVALID_COMPUTER_NAME |
Cannot determine computer name. |
0x80244014 |
WU_E_PT_ INVALID_COMPUTER_LSID |
Cannot determine computer LSID. |
0x80244015 |
WU_E_PT_ REFRESH_CACHE_REQUIRED |
Server replied with InvalidCookie or ServerChanged. Caller should refresh its internal state then repeat the call to Protocol Talker. |
0x80244016 |
WU_E_PT_ HTTP_STATUS_BAD_REQUEST |
Http status 400 - invalid syntax. |
0x80244017 |
WU_E_PT_ HTTP_STATUS_DENIED |
Http status 401 - access denied. |
0x80244019 |
WU_E_PT_ HTTP_STATUS_NOT_FOUND |
Http status 404 - object not found. |
0x8024401A |
WU_E_PT_ HTTP_STATUS_BAD_METHOD |
Http status 405 - method is not allowed. |
0x8024401B |
WU_E_PT_ HTTP_STATUS_PROXY_AUTH_REQ |
Http status 407 - proxy authentication required. |
0x8024401C |
WU_E_PT_ HTTP_STATUS_REQUEST_TIMEOUT |
Http status 408 - server timed out waiting for request. |
0x8024401D |
WU_E_PT_ HTTP_STATUS_CONFLICT |
Http status 409 - user should resubmit with more info. |
0x8024401E |
WU_E_PT_ HTTP_STATUS_GONE |
Http status 410 - the resource is no longer available. |
0x8024401F |
WU_E_PT_ HTTP_STATUS_SERVER_ERROR |
Http status 500 - internal server error. |
0x80244020 |
WU_E_PT_ HTTP_STATUS_NOT_SUPPORTED |
Http status 501 - required not supported. |
0x80244021 |
WU_E_PT_ HTTP_STATUS_BAD_GATEWAY |
Http status 502 - error response received from gateway. |
0x80244022 |
WU_E_PT_ HTTP_STATUS_SERVICE_UNAVAIL |
Http status 503 - temporarily overloaded. |
0x80244023 |
WU_E_PT_ HTTP_STATUS_GATEWAY_TIMEOUT |
Http status 504 - timed out waiting for gateway. |
0x80244024 |
WU_E_PT_ HTTP_STATUS_VERSION_NOT_SUP |
Http status 505 - HTTP version not supported. |
0x80244025 |
WU_E_PT_ FILE_LOCATIONS_CHANGED |
Server replied with FileLocationsChange. |
0x80244026 |
WU_E_PT_REGISTRATION _NOT_SUPPORTED |
Client doesn't support registration with non-WSUS server. |
0x80244027 |
WU_E_PT_NO_ AUTH_PLUGINS_REQUESTED |
Server returned an empty AuthInfo list. |
0x80244028 |
WU_E_PT_NO_ AUTH_COOKIES_CREATED |
The client was unable to create any valid auth cookies. |
0x80244029 |
WU_E_PT_ INVALID_CONFIG_PROP |
One of the ConfigurationProperty values was wrong. |
0x8024402A |
WU_E_PT_ CONFIG_PROP_MISSING |
One of the ConfigurationProperty values was missing. |
0x8024402B |
WU_E_PT_ HTTP_STATUS_NOT_MAPPED |
Http status other than 200, but not mapped above. |
0x8024402C |
WU_E_PT_ WINHTTP_NAME_NOT_RESOLVED |
Winhttp SendRequest/ReceiveResponse failed with 0x2ee7 error. Either the proxy server or target server name can not be resolved. Corresponding to ERROR_WINHTTP_NAME_NOT_RESOLVED. Stop/Restart service or reboot the machine if you see this error frequently. |
0x8024502D |
WU_E_PT_ SAME_REDIR_ID |
During recovery Protocol Talker failed to download a wuredir.cab with a newer redirectorId from the server. |
0x8024502E |
WU_E_PT_NO_MANAGED_RECOVER |
A redirector recovery action was specified, but the server is managed. |
0x80244FFF |
WU_E_PT_UNEXPECTED |
Unexpected protocol talker failure. |
0x80245001 |
WU_E_REDIRECTOR_LOAD_XML |
The XML extracted from the wuredir.cab failed to load into the DOM. |
0x80245002 |
WU_E_REDIRECTOR_S_FALSE |
An expected XML element node, map, attribute, value, etc. could not be found. |
0x80245003 |
WU_E_REDIRECTOR_UNEXPECTED |
Unexpected redirector failure. |
0x8024C001 |
WU_E_DRV_PRUNED |
Driver was pruned. |
0x8024C002 |
WU_E_DRV_NOPROP_OR_LEGACY |
A property wasn't found. Depending on the context this may not be an error. For example, it is expected that legacy drivers will be missing properties we require. |
0x8024C003 |
WU_E_DRV_REG_MISMATCH |
The registry type we read didn't match what was expected. |
0x8024C004 |
WU_E_DRV_NO_METADATA |
The driver update didn't have a metadata blob. |
0x8024C005 |
WU_E_DRV_MISSING_ATTRIBUTE |
The driver update metadata was missing a required attribute. |
0x8024C006 |
WU_E_DRV_SYNC_FAILED |
A driver sync operation failed. |
0x8024C007 |
WU_E_DRV_NO_PRINTER_CONTENT |
No printer driver content following SyncApplicablePrinters. |
0x8024CFFF |
WU_E_DRV_UNEXPECTED |
Unexpected driver utility failure. |
0x80248000 |
WU_E_DS_SHUTDOWN |
The call failed because the SUS agent is shutting down. |
0x80248001 |
WU_E_DS_INUSE |
The call failed because the data store is in use and the operation can only be executed on an idle data store. |
0x80248002 |
WU_E_DS_INVALID |
The data store is in an invalid state. This can occur if we attempt to validate the database schema and find a mismatch between the current state and the state we expect. |
0x80248003 |
WU_E_DS_TABLEMISSING |
The data store has a missing table. |
0x80248004 |
WU_E_DS_TABLEINCORRECT |
The data store has a table whose columns are not what WSUS expects. |
0x80248005 |
WU_E_DS_INVALIDTABLENAME |
The caller tried to open a table that is not in the data store. |
0x80248006 |
WU_E_DS_BADVERSION |
The data store's version does not match what the client expects. |
0x80248007 |
WU_E_DS_NODATA |
The caller asked for data that is not in the data store. |
0x80248008 |
WU_E_DS_MISSINGDATA |
The data store is in an invalid state because data that should be present is missing. This error can occur if we encounter a column in a table that is NULL when it is not allowed to be NULL. |
0x80248009 |
WU_E_DS_MISSINGREF |
The data store is in an invalid state because data that should be present is missing. This will occur if we try to fetch a linked row from another table and the linked row does not exist. This can happen with EULAs, files, and/or localized properties referenced by an update. |
0x8024800A |
WU_E_DS_ UNKNOWNHANDLER |
The caller attempted to add an update that used an unknown update handler. |
0x8024800B |
WU_E_DS_ CANTDELETE |
The caller attempted to delete an update that is referenced by one or more services. |
0x8024800C |
WU_E_DS_ LOCKTIMEOUTEXPIRED |
The caller attempted to access an update that is still locked after the timeout has expired. |
0x8024800D |
WU_E_DS_ NOCATEGORIES |
The caller attempted to add a non-top level category update that contained no parent categories. |
0x8024800E |
WU_E_DS_ ROWEXISTS |
The caller attempted to add a row whose primary key matched an existing row. |
0x8024800F |
WU_E_DS_ STOREFILELOCKED |
We attempted to initialize the data store, but it was locked by another process. |
0x80248010 |
WU_E_DS_ CANNOTREGISTER |
The caller is attempting to register the data store with COM, but the store cannot be loaded into the current process. |
0x80248011 |
WU_E_DS_ UNABLETOSTART |
Could not create an out-of-proc data store object. |
0x80248012 |
WU_E_DS_ MISSINGFILEFORURL |
A file URL was passed in for a file that does not exist in the data store. |
0x80248013 |
WU_E_DS_ DUPLICATEUPDATEID |
The server has passed the same update to the client with two different revision ids. |
0x80248014 |
WU_E_DS_ UNKNOWNSERVICE |
The caller has requested some action on a service that is not known to the data store. |
0x80248015 |
WU_E_DS_ SERVICEEXPIRED |
The caller has requested a service whose registration has expired. |
0x80248016 |
WU_E_DS_ DECLINENOTALLOWED |
An update cannot be declined while it is deployed with a deadline by 1 or more services or if it is a mandatory update. |
0x80248017 |
WU_E_DS_ TABLESESSIONMISMATCH |
The caller attempted to close a table in a session it was not associated with. |
0x80248019 |
WU_E_DS_ NEEDWINDOWSSERVICE |
The caller attempted to remove the Windows Update Service without having another service configured that delivers updates to Windows. |
0x8024801A |
WU_E_DS_ INVALIDOPERATION |
The attempted operation was not allowed. |
0x8024801B |
WU_E_DS_ SCHEMAMISMATCH |
The schema of a table in a backup XML file cannot be reconciled with the current store schema. |
0x8024801C |
WU_E_DS_ RESETREQUIRED |
The data store required a reset and either the state of the current session was too complex to retry (it is in a caller-initiated transaction or a caller acquired a section lock) or the reset failed. In either case, the only option is to release the session and try again with a newly acquired session. Once a session returns this error, it will always return this error. |
0x8024801D |
WU_E_DS_ IMPERSONATED |
The data store cannot be called while impersonating. |
0x80248FFF |
WU_E_DS_ UNEXPECTED |
Unexpected data store failure. |
0x8024A000 |
WU_E_AU_ NOSERVICE |
AU was unable to service incoming AU calls. |
0x8024A002 |
WU_E_AU_ NONLEGACYSERVER |
The legacy AU client stopped because the WSUS server has been upgraded. |
0x8024A003 |
WU_E_AU_ LEGACYCLIENTDISABLED |
The legacy AU client stopped because it was disabled. |
0x8024A004 |
WU_E_AU_ PAUSED |
AU was unable to service incoming AU calls because it was paused. |
0x8024AFFF |
WU_E_AU_ UNEXPECTED |
Unexpected Automatic Updates failure. |
0x8024200 |
WU_E_UH_ REMOTEUNAVAILABLE |
The caller requested a remote object, but no remote process is available. |
0x80242001 |
WU_E_UH_ LOCALONLY |
The caller requested a remote object, but the specified handler is local only. |
0x80242002 |
WU_E_UH_ UNKNOWNHANDLER |
The caller requested an unknown handler object. |
0x80242003 |
WU_E_UH_ REMOTEALREADYACTIVE |
The caller requested an unknown handler object. |
0x80242004 |
WU_E_UH_ DOESNOTSUPPORTACTION |
The update does not support the current action (install or uninstall). |
0x80242005 |
WU_E_UH_ WRONGHANDLER |
The caller tried to use the wrong handler for an action. |
0x80242006 |
WU_E_UH_ INVALIDMETADATA |
The caller passed an update with invalid metadata to the handler. |
0x80242007 |
WU_E_UH_ INSTALLERHUNG |
The installer took too long and was terminated. |
0x80242008 |
WU_E_UH_ OPERATIONCANCELLED |
The install was canceled via a handler method (as opposed to, for example, an installer running with UI that was cancelled externally to WSUS). |
0x80242009 |
WU_E_UH_ BADHANDLERXML |
The XML contained in the handler specific data for the update is invalid. |
0x8024200A |
WU_E_UH_ CANREQUIREINPUT |
The update may require user input so can not be installed in this context. |
0x8024200 |
WU_E_UH_ INSTALLERFAILURE |
At least one update passed to the handler failed to install. |
0x8024200C |
WU_E_UH_ FALLBACKTOSELFCONTAINED |
Handler should fall back to self-contained from delta. |
0x8024200D |
WU_E_UH_ NEEDANOTHERDOWNLOAD |
The installer requires more data to be downloaded. |
0x8024200E |
WU_E_UH_ NOTIFYFAILURE |
The attempted operation was not allowed. |
0x80242FFF |
WU_E_UH_ UNEXPECTED |
Unexpected update handler failure. |
0x80246001 |
WU_E_DM_ URLNOTAVAILABLE |
The requested file does not have an URL. |
0x80246002 |
WU_E_DM_ INCORRECTFILEHASH |
The file digest did not match the expected value. |
0x80246003 |
WU_E_DM_ UNKNOWNALGORITHM |
The file metadata requested an unknown hash algorithm. |
0x80246004 |
WU_E_DM_ NEEDDOWNLOADREQUEST |
A download request from a download handler is required. |
0x80246005 |
WU_E_DM_ NONETWORK |
Network connection was not available. |
0x80246006 |
WU_E_DM_ WRONGBITSVERSION |
The version of BITS installed on the machine is not compatible. |
0x80246007 |
WU_E_DM_ NOTDOWNLOADED |
The update has not been downloaded. |
0x80246008 |
WU_E_DM_ FAILTOCONNECTTOBITS |
Failed to create the IBackgroundCopyManager interface to BITS. The BITS service may have been disabled. |
0x80246009 |
WU_E_DM_ BITSTRANSFERERROR |
A BITS transfer error occurred, but the exact error could not be retrieved. |
0x80246FFF |
WU_E_DM_ UNEXPECTED |
Unexpected download manager failure. |
0x8024D001 |
WU_E_SETUP_ INVALID_INFDATA |
Setup failed due to invalid data in the INF file. |
0x8024D002 |
WU_E_SETUP_ INVALID_IDENTDATA |
Setup failed due to invalid data in the wuident file. |
0x8024D003 |
WU_E_SETUP_ ALREADY_INITIALIZED |
Setup failed due to multiple initialization. |
0x8024D004 |
WU_E_SETUP_NOT_ INITIALIZED |
Setup has not been initialized correctly. |
0x8024D005 |
WU_E_SETUP_SOURCE_ VERSION_MISMATCH |
Setup failed as the version specified in the INF file doesn't match the source binary version. |
0x8024D006 |
WU_E_SETUP_TARGET_ VERSION_GREATER |
Setup failed as the target version on the system is higher than source binary version. |
0x8024DFFF |
WU_E_SETUP_ UNEXPECTED |
Unexpected setup failure. |
0x8024E001 |
WU_E_EE_UNKNOWN_ EXPRESSION |
An expression handler was passed an expression that it doesn't know about. |
0x8024E002 |
WU_E_EE_INVALID_ EXPRESSION |
An expression handler was passed an expression that is bad. |
0x8024E003 |
WU_E_EE_MISSING_ METADATA |
An expression handler was passed an expression that requires an applicability |
0x8024E004 |
WU_E_EE_INVALID_ VERSION |
Invalid version of the serialized expression data. |
0x8024E005 |
WU_E_EE_NOT_ INITIALIZED |
The Expression Evaluator has not been initialized correctly. |
0x8024E006 |
WU_E_EE_INVALID_ ATTRIBUTEDATA |
An invalid attribute data was passed to an expression evaluator. |
x8024EFFF |
WU_E_EE_UNEXPECTED |
Unexpected expression evaluator failure. |
0x80243FFF |
WU_E_AUCLIENT_ UNEXPECTED |
Unexpected UI [AU Client] failure. |
0x8024F001 |
WU_E_REPORTER_ EVENTCACHECORRUPT |
Event cache file was corrupt/malformed. |
0x8024F002 |
WU_E_REPORTER_ EVENTNAMESPACEPARSEFAILED |
Event namespace descriptor XML could not be parsed. |
0x8024F003 |
WU_E_INVALID_EVENT |
Event was reported with invalid/ malformed data. |
0x8024F004 |
WU_E_SERVER_BUSY |
Event was rejected by server because server was too busy. |
0x8024FFFF |
WU_E_REPORTER_ UNEXPECTED |
Unexpected reporter failure. |
BITS Error Codes
Hexadecimal Error Code |
Decimal Error Code |
Error String |
Description |
0x80072EE2 |
-2147012894 |
ERROR_INTERNET_ TIMEOUT |
Some network problem. Server/proxy not reachable. We have also seen this with MS Proxy 2.0 (BITS 1.5 and below) and SunOne 3.6 proxy (BITS 2.0) because these proxies don't support HTTP 1.1 very well. |
0x80070422 |
-2147023838 |
ERROR_SERVICE_ DISABLED |
In almost all cases user has probably disabled BITS service incorrectly thinking that it would improve the computer perfomance. |
0x80190194 |
-2145844844 |
BG_E_HTTP_ ERROR_404 |
The URL is not found on the server. May be an issue with server cluster. |
0x800704DD |
-2147023651 |
ERROR_NOT_ LOGGED_ON |
This error could occur if the installation is initiated with "Run As" command or from a Terminal services session (only on win2k). |
0x80072EE7 |
-2147012889 |
ERROR_INTERNET_ NAME_NOT_RESOLVED |
The server/proxy is unreachable. Probably because of the incorrect IE proxy settings of the user. If the user is able to download the URL via IE and cannot download through BITS then it is definitely a BITS problem. If the user has set autoproxy detection wpad should resolve to the machine that has the autoproxy script. |
0x80072EFD |
-2147012867 |
ERROR_INTERNET_ CANNOT_CONNECT |
The web server is not running or the web server is running on a different port or the proxy is unreachable probably because of incorrect IE proxy settings of the user. If the user is able to download the URL via IE and cannot download through BITS then it is definitely a BITS problem. If the user has set autoproxy detection wpad should resolve to the machine that has the autoproxy script. |
0x80070433 |
-2147023821 |
ERROR_SERVICE_ DEPENDENCY_DELETED |
One of the services BITS depends on could not be started. BITS depends on Rpcss on all Oses. BITS depends on SENS and WMI on win2k. If SENS is disabled BITS cannot start. BITS 1.0 and 1.2 incorrectly depend on lanmanworkstation. |
0x801901F7 |
-2145844745 |
BG_E_HTTP_ERROR_503 |
The server is overloaded. BITS will retry automatically. |
0x80200013 |
-2145386477 |
BG_E_INSUFFICIENT_ RANGE_SUPPORT |
The proxy doesn't support HTTP range requests. Or the URL is a dynamic URL. BITS supports only static URLs. |
0x80200010 |
-2145386480 |
BG_E_NETWORK_ DISCONNECTED |
Network is disconnected |
0x80072EFE |
-2147012866 |
ERROR_INTERNET_ CONNECTION_ ABORTED |
Some network problem or the server/proxy reset the socket connection. |
0x8007042C |
-2147023828 |
ERROR_SERVICE_ DEPENDENCY_FAIL |
One of the services BITS depends on could not started. BITS depends on Rpcss on all Oses. BITS depends on SENS and WMI on win2k. If SENS is disabled BITS cannot start. BITS 1.0 and 1.2 incorrectly depend on lanmanworkstation. |
0x80080005 |
-2146959355 |
CO_E_SERVER_ EXEC_FAILURE |
BITS service could not be started. |
0x80070424 |
-2147023836 |
ERROR_SERVICE_ DOES_NOT_EXIST |
BITS service is deleted. |
0x80190197 |
-2145844841 |
BG_E_HTTP_ ERROR_407 |
The proxy requires credentials to authenticate the user but the credentials are not supplied. BITS 1.2 and below supported only implicit credentials (NTLM authentication) |
0x80070020 |
-2147024864 |
ERROR_SHARING_ VIOLATION |
BITS failed to create/write to a file. |
0x80040155 |
-2147221163 |
REGDB_E_ IIDNOTREG |
BITS interfaces are unregistered or the registry settings are messed up. |
0x80190193 |
-2145844845 |
BG_E_HTTP_ ERROR_403 |
Something wrong with server |
0x80040154 |
-2147221164 |
REGDB_E_ CLASSNOTREG |
BITS interfaces are unregistered or the registry settings are invalid. |
0x8020001B |
-2145386469 |
BG_E_INVALID_ SERVER_RESPONSE |
The proxy doesn't support HTTP 1.1 correctly. |
0x8007043B |
-2147023813 |
ERROR_ SERVICE_NOT_IN_EXE |
The user has messed up with service groups and removed BITS from the netsvcs service group |
0x80190198 |
-2145844840 |
BG_E_HTTP_ ERROR_408 |
Unable to reach the server |
0x80070005 |
-2147024891 |
E_ACCESSDENIED |
Access denied. |
0x80072AFC |
-2147013892 |
WSANO_DATA |
The machine is not able to resolve the proxy/server. WSANO_DATA means that the name-resolution component recognizes the hostname, but has no IP addresses associated with it. An example is when the network is disconnected after a successful lookup, and the now-unreachable IP address is trimmed from the DNS cache. |
0x80200011 |
-2145386479 |
BG_E_MISSING_ FILE_SIZE |
The proxy doesn't support HTTP 1.1 correctly. Or the URL is a dynamic URL. BITS supports only static URLs |
0x80070057 |
2147942487 |
E_INVALIDARG |
If we see this error when BITS service is started or if there is an entry in the eventlog that says that BITS service could not be started because of this error code then it means that system-wide proxy settings configured using the proxycfg.exe tool are corrupted. 2. BITS 1.5 and below returned this error code when invalid proxy information is supplied. BITS 2.0 returns a more informative BG_E_INVALID_PROXY_INFO error. Any other API when called with incorrect parameters could give this error Workaround: 1. Ensure the APIs are correctly called and the proxy information is correctly supplied. Upgrade to BITS 2.0 |
0x801901F4 |
-2145844748 |
BG_E_HTTP_ RROR_500 |
Server error. |
0x80070070 |
-2147024784 |
ERROR_ DISK_FULL |
The disk is full. |
0x80190190 |
-2145844848 |
BG_E_HTTP_ ERROR_400 |
The download URL is invalid |
0x80190195 |
-2145844843 |
BG_E_HTTP_ ERROR_405 |
Proxy doesn't support HTTP 1.1 or more specifically rejects HTTP HEAD requests. |
0x801901A0 |
-21458448 |
BG_E_HTTP_ ERROR_416 |
HTTP error 416. |
0x8007041D |
-2147023843 |
ERROR_SERVICE_ REQUEST_ TIMEOUT |
Service is taking a lot of time to start. We have seen this in service stress conditions. |
0x8020000D |
-2145386483 |
BG_E_ DESTINATION_ LOCKED |
Some other program like chkdsk is currently running which locked the disk and so BITS is not able to write to the disk. |
0x800706BA |
-2147023174 |
RPC_S_SERVER_ UNAVAILABLE |
Probably the BITS service is stopped while the app is trying to access it. |
0x80072AF9 |
-2147013895 |
WSAHOST_ NOT_FOUND |
Machine not able to resolve proxy/server. We have also seen this problem on Windows XP RTM (BITS 1.0) with a modem connection in the lab. This error could occur if the proxy server is not resolvable without the fully qualified domain suffix. This problem has been fixed in BITS 1.2 and above |
0x8019019B |
-2145844837 |
BG_E_HTTP_ ERROR_411 |
Proxy incorrectly expecting content-length in the HTTP requests. |
0x8007043C |
-2147023812 |
ERROR_NOT_ SAFEBOOT_SERVICE |
The service is not supported in the safe boot mode. |
0x800700E7 |
-2147024665 |
ERROR_PIPE_BUSY |
SCM is under stress. |
0x800704CF. |
-2147023665 |
ERROR_NETWORK_ UNREACHABLE |
Network problems. |
0x800703EB |
-2147023893 |
ERROR_CAN_ NOT_COMPLETE |
Probably BITS service is stopped. |
0x8007041F |
-2147023841 |
ERROR_SERVICE_ DATABASE_LOCKED |
SCM is under stress. |
0x80072EE4 |
-2147012892 |
ERROR_INTERNET_ INTERNAL_ERROR |
Internal winhttp error |
0x80072EF1 |
-2147012879 |
ERROR_INTERNET_ OPERATION_ CANCELLED |
Internal winhttp error |
Internal winhttp error |
-2147012744 |
ERROR_WINHTTP_ INVALID_SERVER_ RESPONSE |
Winhttp received some error while communicating with proxy/server. Or the proxy server doesn’t support HTTP 1.1 correctly. We have seen this with MS proxy 2.0. INVALID_ SERVER_RESPONSE indicates a syntax error in the response headers, which could be caused by a flaky proxy, data corruption along the way, or the connection being broken by a graceful close. |
0x8020002E |
-2145386450 |
BG_E_CONNECTION_ CLOSED |
You should only see this error in the Windows Server 2008 builds. It was included in some Windows XP SP2 builds by mistake and later removed. Instead you should see one of the WINHTTP connection errors. Anyway the reason is that the proxy/server is not reachable |
0x8020003F |
-2145386433 |
BG_E_INVALID_ PROXY_INFO |
Invalid proxy settings. |