ConfigMgr and Intune error codes
Literally a list of ConfigMgr and Intune error codes, as well as how to look up what they mean
Hey all!
This is literally just a post containing a bunch Intune and ConfigMgr error codes that I hope to keep updated over time.
I’ve found it’s not always straight forward finding what an error code means, maybe beacuse it’s undocuemnted, outdated or sometimes you simply just don’t know where to look, and even if you do the results vary, for example:
Looking up the same error code 4 different ways, returns 3 different results, which is confusing.
PowerShell function
That being said, CMTrace, OneTrace and ErrLookup are extremely useful!
PowerShell Function
The PowerShell function is something thrown together purely for this post, it queries a list of error codes which are stored in Json in my GitHub repository. I doubt that it’s perfect, but it’s functional.
|
|
Error Codes
When it comes to ConfigMgr & Intune, the list of error codes are probably longer than your arm!
Here is a fairly sizeable list of those error codes!
SignedIntCode | UnsignedIntCode | HexCode | Description |
0x00000000 | Success | ||
-1 | 4294967295 | 0xFFFFFFFF | Script execution failed with error code -1 |
10 | 10 | 0x0000000A | The unit test error string |
131072512 | 131072512 | 0x07D00200 | The client is successfully assigned with Group Policy Site Assignment |
131073314 | 131073314 | 0x07D00522 | No more data |
131073589 | 131073589 | 0x07D00635 | The scan was skipped because history was valid |
-2016278002 | 2278689294 | 0x87D20A0E | Shutdown received while compressing |
-2016278003 | 2278689293 | 0x87D20A0D | Unexpected error while compressing |
-2016278004 | 2278689292 | 0x87D20A0C | Already compressed |
-2016278005 | 2278689291 | 0x87D20A0B | Failed to create file header while compressing |
-2016278006 | 2278689290 | 0x87D20A0A | Failed to create file while compressing |
-2016278007 | 2278689289 | 0x87D20A09 | Failed to create folder while compressing |
-2016278008 | 2278689288 | 0x87D20A08 | Invalid compressed header in the file |
-2016278009 | 2278689287 | 0x87D20A07 | Invalid compressed file |
-2016278010 | 2278689286 | 0x87D20A06 | Failed to compress header |
-2016278011 | 2278689285 | 0x87D20A05 | The file is no more there to compress |
-2016278012 | 2278689284 | 0x87D20A04 | Invalid destination for compression |
-2016278013 | 2278689283 | 0x87D20A03 | Invalid source for compression |
-2016278014 | 2278689282 | 0x87D20A02 | Compression destination not found |
-2016278015 | 2278689281 | 0x87D20A01 | Compression source not found |
-2016278267 | 2278689029 | 0x87D20905 | SEDO lock request timed out |
-2016278268 | 2278689028 | 0x87D20904 | SEDO lock not found |
-2016278269 | 2278689027 | 0x87D20903 | Invalid object path for SEDO |
-2016278270 | 2278689026 | 0x87D20902 | SEDO request ID not found |
-2016278271 | 2278689025 | 0x87D20901 | SEDO needs lock ID or Rel path |
-2016278518 | 2278688778 | 0x87D2080A | Certificate not found |
-2016278519 | 2278688777 | 0x87D20809 | Invalid data in the certificate |
-2016278520 | 2278688776 | 0x87D20808 | Failed to find certificate |
-2016278521 | 2278688775 | 0x87D20807 | Failed to decrypt the certificate |
-2016278522 | 2278688774 | 0x87D20806 | Failed to delete certificate store |
-2016278523 | 2278688773 | 0x87D20805 | Failed to write in the certificate store |
-2016278524 | 2278688772 | 0x87D20804 | Failed to open the certificate store |
-2016278525 | 2278688771 | 0x87D20803 | Error reading peer�s encoded certificate |
-2016278526 | 2278688770 | 0x87D20802 | Error reading certificate |
-2016278527 | 2278688769 | 0x87D20801 | Service Host Name property is either missing or invalid |
-2016278776 | 2278688520 | 0x87D20708 | The specified item to update is not found in Site Control File |
-2016278777 | 2278688519 | 0x87D20707 | Invalid FQDN found in Site Control File |
-2016278778 | 2278688518 | 0x87D20706 | Legacy type item in Site Control File |
-2016278779 | 2278688517 | 0x87D20705 | Site not found in Site Control File |
-2016278780 | 2278688516 | 0x87D20704 | Bad data in Site Control File |
-2016278781 | 2278688515 | 0x87D20703 | Item type not known in Site Control File |
-2016278782 | 2278688514 | 0x87D20702 | Item not found in Site Control File |
-2016278783 | 2278688513 | 0x87D20701 | Unknown property in Site Control File |
-2016279006 | 2278688290 | 0x87D20622 | SRS data source has been modified or deleted |
-2016279007 | 2278688289 | 0x87D20621 | SRS root folder is not present |
-2016279008 | 2278688288 | 0x87D20620 | SRS is not installed or not properly configured |
-2016279019 | 2278688277 | 0x87D20615 | SRS web service is not running |
-2016279278 | 2278688018 | 0x87D20512 | The machine is not assigned to this site |
-2016279279 | 2278688017 | 0x87D20511 | The machine is not an SMS client |
-2016279280 | 2278688016 | 0x87D20510 | Machine not found foreign key constraint |
-2016279529 | 2278687767 | 0x87D20417 | Auto Deployment Rule download failed |
-2016279530 | 2278687766 | 0x87D20416 | No rule filters specified for the Auto Deployment Rule |
-2016279531 | 2278687765 | 0x87D20415 | Auto Deployment Rule results exceeded the maximum number of updates |
-2016279532 | 2278687764 | 0x87D20414 | Cannot Configure WU/MU as an upstream server on Peer Primary |
-2016279533 | 2278687763 | 0x87D20413 | Active SUP not selected |
-2016279537 | 2278687759 | 0x87D2040F | WSUS Server component failure |
-2016279538 | 2278687758 | 0x87D2040E | WSUS Server Database connection failure |
-2016279539 | 2278687757 | 0x87D2040D | Failed to set Parent WSUS Configuration on the child sites |
-2016279540 | 2278687756 | 0x87D2040C | WSUS server not ready |
-2016279797 | 2278687499 | 0x87D2030B | Device Setting Item not found Foreign Key Constraint |
-2016280054 | 2278687242 | 0x87D2020A | SDM Type not found Foreign Key Constraint |
-2016280055 | 2278687241 | 0x87D20209 | Related SDM Package not found Foreign Key Constraint |
-2016280056 | 2278687240 | 0x87D20208 | SDM Package was not found Foreign Key Constraint |
-2016280057 | 2278687239 | 0x87D20207 | SDM Type not found Foreign Key Constraint |
-2016280058 | 2278687238 | 0x87D20206 | EULA is not found Foreign Key Constraint |
-2016280059 | 2278687237 | 0x87D20205 | Update Source was not found Foreign Key Constraint |
-2016280060 | 2278687236 | 0x87D20204 | CI Type not found Foreign Key Constraint |
-2016280061 | 2278687235 | 0x87D20203 | The category was not found Foreign Key Constraint |
-2016280062 | 2278687234 | 0x87D20202 | Configuration Item not found Foreign Key Constraint |
-2016280063 | 2278687233 | 0x87D20201 | Operation on Old Configuration Item when a newer instance exits in the Database |
-2016280319 | 2278686977 | 0x87D20101 | Collection not found foreign key constraint |
-2016280528 | 2278686768 | 0x87D20030 | Error while creating inbox |
-2016280544 | 2278686752 | 0x87D20020 | Thread is signaled to be stopped |
-2016280557 | 2278686739 | 0x87D20013 | Registry write error |
-2016280558 | 2278686738 | 0x87D20012 | Registry read error |
-2016280559 | 2278686737 | 0x87D20011 | Registry connection error |
-2016280568 | 2278686728 | 0x87D20008 | SQL send batch error |
-2016280569 | 2278686727 | 0x87D20007 | SQL queue row error |
-2016280570 | 2278686726 | 0x87D20006 | SQL table binding error |
-2016280571 | 2278686725 | 0x87D20005 | SQL deadlock error |
-2016280572 | 2278686724 | 0x87D20004 | SQL error while registering type |
-2016280573 | 2278686723 | 0x87D20003 | SQL Error |
-2016280574 | 2278686722 | 0x87D20002 | SQL connection error |
-2016280575 | 2278686721 | 0x87D20001 | Invalid data |
-2016281107 | 2278686189 | 0x87D1FDED | Unsupported setting discovery source |
-2016281108 | 2278686188 | 0x87D1FDEC | Referenced setting not found in CI |
-2016281109 | 2278686187 | 0x87D1FDEB | Data type conversion failed |
-2016281110 | 2278686186 | 0x87D1FDEA | Invalid parameter to CIM setting |
-2016281111 | 2278686185 | 0x87D1FDE9 | Not applicable for this device |
-2016281112 | 2278686184 | 0x87D1FDE8 | Remediation failed |
-2016341109 | 2278626187 | 0x87D1138B | iOS device has returned an error |
-2016341110 | 2278626186 | 0x87D1138A | iOS device has rejected the command due to incorrect format |
-2016341111 | 2278626185 | 0x87D11389 | iOS device has returned an unexpected Idle status |
-2016341112 | 2278626184 | 0x87D11388 | iOS device is currently busy |
-2016344008 | 2278623288 | 0x87D10838 | (1404): Certificate access denied |
-2016344009 | 2278623287 | 0x87D10837 | (1403): Certificate not found |
-2016344010 | 2278623286 | 0x87D10836 | DCMO(1402): The Operation failed |
-2016344011 | 2278623285 | 0x87D10835 | DCMO(1401): User chose not to accept the operation when prompted |
-2016344012 | 2278623284 | 0x87D10834 | DCMO(1400): Client error |
-2016344108 | 2278623188 | 0x87D107D4 | DCMO(1204): Device Capability is disabled, and the User is allowed to re-enable it |
-2016344109 | 2278623187 | 0x87D107D3 | DCMO(1203): Device Capability is disabled, and the User is not allowed to re-enable it |
-2016344110 | 2278623186 | 0x87D107D2 | DCMO(1202): Enable operation is performed successfully, but the Device Capability is currently detached |
-2016344111 | 2278623185 | 0x87D107D1 | DCMO(1201): Enable operation is performed successfully, and the Device Capability is currently attached |
-2016344112 | 2278623184 | 0x87D107D0 | DCMO(1200): Operation is performed successfully |
-2016344197 | 2278623099 | 0x87D1077B | Operation not implemented on the client |
-2016344198 | 2278623098 | 0x87D1077A | The package is an invalid upgrade |
-2016344199 | 2278623097 | 0x87D10779 | The target location of the package is not accessible |
-2016344200 | 2278623096 | 0x87D10778 | The installer is busy doing some other operation |
-2016344201 | 2278623095 | 0x87D10777 | This indicates that network failure aborted the operation |
-2016344202 | 2278623094 | 0x87D10776 | The package has no right to perform the operation |
-2016344203 | 2278623093 | 0x87D10775 | Install/Uninstall Unknown error |
-2016344204 | 2278623092 | 0x87D10774 | The mandatory file is in use and prevents the operation |
-2016344205 | 2278623091 | 0x87D10773 | The package cannot be installed due to missing dependency |
-2016344206 | 2278623090 | 0x87D10772 | The package cannot be installed due to a security error |
-2016344207 | 2278623089 | 0x87D10771 | Package validation failed. |
-2016344208 | 2278623088 | 0x87D10770 | Installation of the package is not supported |
-2016344209 | 2278623087 | 0x87D1076F | Insufficient free memory in the drive to perform the operation |
-2016344210 | 2278623086 | 0x87D1076E | File is corrupted |
-2016344211 | 2278623085 | 0x87D1076D | User canceled the operation |
-2016344212 | 2278623084 | 0x87D1076C | The application was successfully installed |
-2016344512 | 2278622784 | 0x87D10640 | An invalid OMA download descriptor received |
-2016344593 | 2278622703 | 0x87D105EF | A maximum number of HTTP redirections has been reached. |
-2016344594 | 2278622702 | 0x87D105EE | Non-download specific error |
-2016344595 | 2278622701 | 0x87D105ED | Internal error occurred. Most probably a programming error. |
-2016344596 | 2278622700 | 0x87D105EC | An error occurred in the transaction |
-2016344597 | 2278622699 | 0x87D105EB | General storage error |
-2016344598 | 2278622698 | 0x87D105EA | Not enough disk space for the content |
-2016344599 | 2278622697 | 0x87D105E9 | Moving content file failed |
-2016344600 | 2278622696 | 0x87D105E8 | Invalid download drive |
-2016344601 | 2278622695 | 0x87D105E7 | File not found an error |
-2016344602 | 2278622694 | 0x87D105E6 | File write failed |
-2016344603 | 2278622693 | 0x87D105E5 | Media where the download is being persisted removed |
-2016344604 | 2278622692 | 0x87D105E4 | Download Manager cannot handle this URL |
-2016344605 | 2278622691 | 0x87D105E3 | Error in the destination filename |
-2016344606 | 2278622690 | 0x87D105E2 | Destination file cannot be opened/created |
-2016344607 | 2278622689 | 0x87D105E1 | Unhandled HTTP error code |
-2016344608 | 2278622688 | 0x87D105E0 | 404: object not found |
-2016344609 | 2278622687 | 0x87D105DF | 412: partial content cannot be downloaded |
-2016344610 | 2278622686 | 0x87D105DE | Paused content is expired |
-2016344611 | 2278622685 | 0x87D105DD | Resuming progressive download failed |
-2016344711 | 2278622585 | 0x87D10579 | Connection failed. No network coverage |
-2016344713 | 2278622583 | 0x87D10577 | Unknown error related to protocol |
-2016344810 | 2278622486 | 0x87D10516 | The requested operation is invalid for this protocol |
-2016344811 | 2278622485 | 0x87D10515 | The requested protocol is not known |
-2016344813 | 2278622483 | 0x87D10513 | Unknown error related to remote content |
-2016344907 | 2278622389 | 0x87D104B5 | Content needed to resent, but this failed |
-2016344908 | 2278622388 | 0x87D104B4 | Remote server required authentication but credentials supplied if any were not accepted |
-2016344909 | 2278622387 | 0x87D104B3 | Remote content was not found at the server |
-2016344910 | 2278622386 | 0x87D104B2 | The operation requested on remote content is not permitted |
-2016344911 | 2278622385 | 0x87D104B1 | Access to remote content denied |
-2016344913 | 2278622383 | 0x87D104AF | Unknown proxy related error |
-2016345007 | 2278622289 | 0x87D10451 | Proxy authentication required or proxy refused the supplied credentials if any |
-2016345008 | 2278622288 | 0x87D10450 | Connection to the proxy timed out |
-2016345009 | 2278622287 | 0x87D1044F | Invalid proxy hostname |
-2016345010 | 2278622286 | 0x87D1044E | The proxy server closed the connection prematurely |
-2016345011 | 2278622285 | 0x87D1044D | Connection to the proxy server was refused |
-2016345061 | 2278622235 | 0x87D1041B | Detection rules not present |
-2016345063 | 2278622233 | 0x87D10419 | Unknown network error |
-2016345103 | 2278622193 | 0x87D103F1 | Remote server unavailable |
-2016345104 | 2278622192 | 0x87D103F0 | Network authentication failed |
-2016345105 | 2278622191 | 0x87D103EF | Temporary network failure |
-2016345106 | 2278622190 | 0x87D103EE | The encrypted channel could not be established |
-2016345107 | 2278622189 | 0x87D103ED | The operation was canceled before it was finished |
-2016345108 | 2278622188 | 0x87D103EC | Connection to the remote server timed out |
-2016345109 | 2278622187 | 0x87D103EB | Invalid hostname |
-2016345110 | 2278622186 | 0x87D103EA | The remote server closed the connection prematurely |
-2016345111 | 2278622185 | 0x87D103E9 | The remote server refused the connection |
-2016345112 | 2278622184 | 0x87D103E8 | Error Unknown |
-2016345595 | 2278621701 | 0x87D10205 | SyncML: The response to an atomic command was too large to fit in a single message. |
-2016345596 | 2278621700 | 0x87D10204 | SyncML: Command was inside Atomic element, and Atomic failed. This command was not rolled back successfully. |
-2016345598 | 2278621698 | 0x87D10202 | SyncML: The SyncML command was not completed successfully since the operation was already canceled before processing the command. |
-2016345599 | 2278621697 | 0x87D10201 | SyncML: The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol used in the request SyncML Message. |
-2016345600 | 2278621696 | 0x87D10200 | SyncML: An application error occurred during the synchronization session. |
-2016345601 | 2278621695 | 0x87D101FF | SyncML: A severe error occurred in the server while processing the request. |
-2016345602 | 2278621694 | 0x87D101FE | SyncML: An error occurred while processing the request. The error is related to a failure in the recipient data store. |
-2016345603 | 2278621693 | 0x87D101FD | SyncML: Reserved for future use. |
-2016345604 | 2278621692 | 0x87D101FC | SyncML: An error that necessitates a refresh of the current synchronization state of the client with the server. |
-2016345605 | 2278621691 | 0x87D101FB | SyncML: The error caused all SyncML commands within an Atomic element type to fail. |
-2016345606 | 2278621690 | 0x87D101FA | SyncML: An application error occurred while processing the request. |
-2016345607 | 2278621689 | 0x87D101F9 | SyncML: The recipient does not support or refuses to support the specified version of SyncML DTD used in the request SyncML Message. |
-2016345608 | 2278621688 | 0x87D101F8 | SyncML: The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient specified by the URI (e.g., HTTP FTP LDAP) or some other auxiliary recipient (e.g., DNS) it needed to access in attempting to complete the request. |
-2016345609 | 2278621687 | 0x87D101F7 | SyncML: The recipient is currently unable to handle the request due to a temporary overloading or maintenance. |
-2016345610 | 2278621686 | 0x87D101F6 | SyncML: The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient it accessed to fulfill the request. |
-2016345611 | 2278621685 | 0x87D101F5 | SyncML: The recipient does not support the command required to fulfill the request. |
-2016345612 | 2278621684 | 0x87D101F4 | SyncML: The recipient encountered an unexpected condition that prevented it from fulfilling the request |
-2016345684 | 2278621612 | 0x87D101AC | SyncML: Move failed |
-2016345685 | 2278621611 | 0x87D101AB | SyncML: Parent cannot be deleted since it contains children. |
-2016345686 | 2278621610 | 0x87D101AA | SyncML: Partial item not accepted. |
-2016345687 | 2278621609 | 0x87D101A9 | SyncML: The requested command failed because the sender does not have adequate access control permissions (ACL) on the recipient. |
-2016345688 | 2278621608 | 0x87D101A8 | SyncML: The chunked object was received, but the size of the received object did not match the size declared within the first chunk. |
-2016345689 | 2278621607 | 0x87D101A7 | SyncML: The requested command failed because the �Soft Deleted� item was previously �Hard Deleted� on the server. |
-2016345690 | 2278621606 | 0x87D101A6 | SyncML: The requested command failed on the server because the CGI scripting in the LocURI was incorrectly formed. |
-2016345691 | 2278621605 | 0x87D101A5 | SyncML: The requested command failed on the server because the specified search grammar was not known. |
-2016345692 | 2278621604 | 0x87D101A4 | SyncML: The recipient has no more storage space for the remaining synchronization data. |
-2016345693 | 2278621603 | 0x87D101A3 | SyncML: The client request created a conflict which was resolved by the server command winning. |
-2016345694 | 2278621602 | 0x87D101A2 | SyncML: The requested Put or Add command failed because the target already exists. |
-2016345695 | 2278621601 | 0x87D101A1 | SyncML: The request failed at this time, and the originator should retry the request later. |
-2016345696 | 2278621600 | 0x87D101A0 | SyncML: The request failed because the specified byte size in the request was too big. |
-2016345697 | 2278621599 | 0x87D1019F | SyncML: Unsupported media type or format. |
-2016345698 | 2278621598 | 0x87D1019E | SyncML: The requested command failed because the target URI is too long for what the recipient is able or willing to process. |
-2016345699 | 2278621597 | 0x87D1019D | SyncML: The recipient refuses to perform the requested command because the requested item is larger than the recipient is able or willing to process. |
-2016345700 | 2278621596 | 0x87D1019C | SyncML: The requested command failed on the recipient because it was incomplete or incorrectly formed. |
-2016345701 | 2278621595 | 0x87D1019B | SyncML: The requested command must be accompanied by byte size or length information in the Meta element type. |
-2016345702 | 2278621594 | 0x87D1019A | SyncML: The requested target is no longer on the recipient, and no forwarding URI is known. |
-2016345703 | 2278621593 | 0x87D10199 | SyncML: The requested failed because of an update conflict between the client and server versions of the data. |
-2016345704 | 2278621592 | 0x87D10198 | SyncML: An expected message was not received within the required period of time. |
-2016345705 | 2278621591 | 0x87D10197 | SyncML: The requested command failed because the originator must provide proper authentication. |
-2016345706 | 2278621590 | 0x87D10196 | SyncML: The requested command failed because an optional feature in the request was not supported. |
-2016345707 | 2278621589 | 0x87D10195 | SyncML: The requested command is not allowed on the target. |
-2016345708 | 2278621588 | 0x87D10194 | SyncML: The requested target was not found. |
-2016345709 | 2278621587 | 0x87D10193 | SyncML: The requested command failed, but the recipient understood the requested command. |
-2016345710 | 2278621586 | 0x87D10192 | SyncML: The requested command failed because proper payment is needed. |
-2016345711 | 2278621585 | 0x87D10191 | SyncML: The requested command failed because the requestor must provide proper authentication. |
-2016345712 | 2278621584 | 0x87D10190 | SyncML: The requested command could not be performed because of malformed syntax in the command. |
-2016345807 | 2278621489 | 0x87D10131 | SyncML: The requested target must be accessed through the specified proxy URI. |
-2016345808 | 2278621488 | 0x87D10130 | SyncML: The requested SyncML command was not executed on the target. |
-2016345809 | 2278621487 | 0x87D1012F | SyncML: The requested target can be found at another URI. |
-2016345810 | 2278621486 | 0x87D1012E | SyncML: The requested target has temporarily moved to a different URI. |
-2016345811 | 2278621485 | 0x87D1012D | SyncML: The requested target has a new URI. |
-2016345812 | 2278621484 | 0x87D1012C | SyncML: The requested target is one of several multiple alternatives requested target. |
-2016346011 | 2278621285 | 0x87D10065 | SyncML: The specified SyncML command is being carried out but has not yet been completed. |
-2016403452 | 2278563844 | 0x87D02004 | The software distribution policy was not found. |
-2016403454 | 2278563842 | 0x87D02002 | The software distribution policy for this program was not found. |
-2016406894 | 2278560402 | 0x87D01292 | The virtual application is in use |
-2016406895 | 2278560401 | 0x87D01291 | The virtual environment is not applicable |
-2016406896 | 2278560400 | 0x87D01290 | An error occurred when querying the App-V WMI provider |
-2016406897 | 2278560399 | 0x87D0128F | The App-V time command returned failure |
-2016406898 | 2278560398 | 0x87D0128E | I could not uninstall the App-V deployment type because of conflict. The published components in this DT are still published by other DTs. This DT will always be detected as long as other DTs are still installed. |
-2016406900 | 2278560396 | 0x87D0128C | I could not find a streaming distribution point for the App-V package |
-2016406901 | 2278560395 | 0x87D0128B | The App-V application is not installed |
-2016406902 | 2278560394 | 0x87D0128A | The App-V client has reported a launch error |
-2016406906 | 2278560390 | 0x87D01286 | The App-V package has already installed a higher version by another deployment type, so we cannot install a lower version of the package |
-2016406907 | 2278560389 | 0x87D01285 | A dependent App-V package is not installed |
-2016406911 | 2278560385 | 0x87D01281 | A supported App-V client is not installed |
-2016406912 | 2278560384 | 0x87D01280 | The virtual application is currently in use |
-2016406959 | 2278560337 | 0x87D01251 | The application deployment type handler could not be initialized. The deployment type might not be supported on this system. |
-2016406960 | 2278560336 | 0x87D01250 | The computer restart cannot be initiated because a software installation job is in progress. |
-2016407024 | 2278560272 | 0x87D01210 | Failed to get content locations. |
-2016407036 | 2278560260 | 0x87D01204 | No distribution points were found for the requested content. |
-2016407037 | 2278560259 | 0x87D01203 | The client cache is currently in use by a running program or by a download in progress. |
-2016407038 | 2278560258 | 0x87D01202 | The content download cannot be performed because the total size of the client cache is smaller than the size of the requested content. |
-2016407039 | 2278560257 | 0x87D01201 | The content download cannot be performed because there is not enough available space in the cache or the disk is full. |
-2016407040 | 2278560256 | 0x87D01200 | No content request was found with the given handle. |
-2016407286 | 2278560010 | 0x87D0110A | A fatal error occurred while preparing to execute the program, for example, when creating the program execution environment making a network connection impersonating the user determining the file association information or when attempting to launch the program. This program execution will not be retried. |
-2016407287 | 2278560009 | 0x87D01109 | Failed to verify that the given file is a valid installation package. |
-2016407288 | 2278560008 | 0x87D01108 | Failed to access all the provided program locations. This program will not retry. |
-2016407289 | 2278560007 | 0x87D01107 | Failed to access all the provided program locations. This program may retry if the maximum retry count has not been reached. |
-2016407290 | 2278560006 | 0x87D01106 | Failed to verify the executable file is valid or to construct the associated command line. |
-2016407291 | 2278560005 | 0x87D01105 | An error was encountered while getting the process information for the launched program, and the program execution will not be monitored. |
-2016407292 | 2278560004 | 0x87D01104 | The command line for this program is invalid. |
-2016407293 | 2278560003 | 0x87D01103 | A nonfatal error occurred while preparing to execute the program, for example, when creating the program execution environment making a network connection impersonating the user determining the file association information or when attempting to launch the program. This program execution will be retried if the retry count has not been exceeded. |
-2016407294 | 2278560002 | 0x87D01102 | An error occurred while creating the execution context. |
-2016407295 | 2278560001 | 0x87D01101 | A fatal error has been encountered while attempting to run the program. The program execution will not be retried. |
-2016407296 | 2278560000 | 0x87D01100 | A non-fatal error has been encountered while attempting to run the program. The program execution will be retried if the retry count has not been exceeded. |
-2016407528 | 2278559768 | 0x87D01018 | The program cannot run at this time because the client is on the internet. |
-2016407529 | 2278559767 | 0x87D01017 | The content hash string or hash version is empty or incorrect in the software distribution policy, or the hash verification failed. |
-2016407531 | 2278559765 | 0x87D01015 | Failed to notify the caller that software distribution is paused because the paused state or paused cookie does not match. |
-2016407532 | 2278559764 | 0x87D01014 | The program cannot run because it is targeted to a user that requires user input or is set to run in the user context. |
-2016407533 | 2278559763 | 0x87D01013 | This program cannot run because it depends on another program that has not run successfully before. |
-2016407534 | 2278559762 | 0x87D01012 | There is no program currently running. |
-2016407535 | 2278559761 | 0x87D01011 | The execution request was not found. |
-2016407536 | 2278559760 | 0x87D01010 | A system restart is in progress, or there is a pending execution for this program that requires a computer restart. |
-2016407543 | 2278559753 | 0x87D01009 | Failed to get data from WMI. |
-2016407544 | 2278559752 | 0x87D01008 | Failed to indicate the client cache is currently in use. |
-2016407546 | 2278559750 | 0x87D01006 | The requested program is not currently pending. |
-2016407547 | 2278559749 | 0x87D01005 | The policy for this program does not exist or is invalid. |
-2016407548 | 2278559748 | 0x87D01004 | The program is disabled. |
-2016407550 | 2278559746 | 0x87D01002 | Another execution for this program is already pending. |
-2016407551 | 2278559745 | 0x87D01001 | Another software execution is in progress, or a restart is pending. |
-2016409588 | 2278557708 | 0x87D0080C | No WDS session is available. |
-2016409589 | 2278557707 | 0x87D0080B | MCS Encountered WDS error. |
-2016409590 | 2278557706 | 0x87D0080A | Invalid MCS configuration. |
-2016409591 | 2278557705 | 0x87D00809 | The package is not multicast enabled. |
-2016409592 | 2278557704 | 0x87D00808 | The package is not multicast shared. |
-2016409593 | 2278557703 | 0x87D00807 | The invalid path is specified for Package. |
-2016409594 | 2278557702 | 0x87D00806 | MCS Server is Busy with many clients. |
-2016409595 | 2278557701 | 0x87D00805 | MCS Encryption is empty |
-2016409596 | 2278557700 | 0x87D00804 | Error performing MCS health check |
-2016409597 | 2278557699 | 0x87D00803 | Error opening MCS session |
-2016409598 | 2278557698 | 0x87D00802 | MCS protocol version mismatch |
-2016409599 | 2278557697 | 0x87D00801 | General MCS Failure |
-2016409600 | 2278557696 | 0x87D00800 | The content transfer manager job is in an unexpected state |
-2016409835 | 2278557461 | 0x87D00715 | No updates specified in the requested job |
-2016409836 | 2278557460 | 0x87D00714 | User-based install not allowed as system restart is pending |
-2016409837 | 2278557459 | 0x87D00713 | Software updates detection results have not been received yet |
-2016409838 | 2278557458 | 0x87D00712 | A system restart is required to complete the installation |
-2016409839 | 2278557457 | 0x87D00711 | Software updates deployment not active yet, i.e., start time is in future |
-2016409840 | 2278557456 | 0x87D00710 | Failed to compare process creation time |
-2016409841 | 2278557455 | 0x87D0070F | Invalid updates installer path |
-2016409842 | 2278557454 | 0x87D0070E | The empty command line specified |
-2016409843 | 2278557453 | 0x87D0070D | The software update failed when attempted |
-2016409844 | 2278557452 | 0x87D0070C | Software update execution timeout |
-2016409845 | 2278557451 | 0x87D0070B | Failed to create a process |
-2016409846 | 2278557450 | 0x87D0070A | Invalid command line |
-2016409847 | 2278557449 | 0x87D00709 | Failed to resume the monitoring of the process |
-2016409848 | 2278557448 | 0x87D00708 | Software Updates Install not required |
-2016409849 | 2278557447 | 0x87D00707 | Job Id mismatch |
-2016409850 | 2278557446 | 0x87D00706 | No active job exists |
-2016409851 | 2278557445 | 0x87D00705 | Pause state required |
-2016409852 | 2278557444 | 0x87D00704 | A hard reboot is pending |
-2016409853 | 2278557443 | 0x87D00703 | Another software updates install job is in progress. Only one job is allowed at a time. |
-2016409854 | 2278557442 | 0x87D00702 | Assignment policy not found |
-2016409855 | 2278557441 | 0x87D00701 | Software updates download not allowed at this time |
-2016409856 | 2278557440 | 0x87D00700 | Software updates installation not allowed at this time |
-2016409959 | 2278557337 | 0x87D00699 | The scan is already in progress |
-2016409960 | 2278557336 | 0x87D00698 | Software update being attempted is not actionable |
-2016409961 | 2278557335 | 0x87D00697 | The software update is already installed but just requires a reboot to complete the installation |
-2016409962 | 2278557334 | 0x87D00696 | The software update is already installed |
-2016409963 | 2278557333 | 0x87D00695 | Incomplete scan results |
-2016409964 | 2278557332 | 0x87D00694 | WSUS source already exists |
-2016409965 | 2278557331 | 0x87D00693 | Windows Updates Agent version too low |
-2016409966 | 2278557330 | 0x87D00692 | Group policy conflict |
-2016409967 | 2278557329 | 0x87D00691 | Software update source not found |
-2016409968 | 2278557328 | 0x87D00690 | The software update is not applicable |
-2016409999 | 2278557297 | 0x87D00671 | Waiting for a third-party orchestration engine to initiate the installation |
-2016410006 | 2278557290 | 0x87D0066A | None of the child software updates of a bundle are applicable |
-2016410007 | 2278557289 | 0x87D00669 | Not able to get software updates content locations at this time |
-2016410008 | 2278557288 | 0x87D00668 | Software update still detected as actionable after apply |
-2016410009 | 2278557287 | 0x87D00667 | No current or future service window exists to install software updates |
-2016410010 | 2278557286 | 0x87D00666 | Software updates cannot be installed outside the service window |
-2016410011 | 2278557285 | 0x87D00665 | No updates to process in the job |
-2016410012 | 2278557284 | 0x87D00664 | Updates handler job was canceled |
-2016410013 | 2278557283 | 0x87D00663 | Failed to report installation status of software updates |
-2016410014 | 2278557282 | 0x87D00662 | Failed to trigger the installation of software updates |
-2016410015 | 2278557281 | 0x87D00661 | Error while detecting updates status after installation success |
-2016410016 | 2278557280 | 0x87D00660 | Unable to monitor a software update�s execution |
-2016410023 | 2278557273 | 0x87D00659 | An error occurred reading policy for software update |
-2016410024 | 2278557272 | 0x87D00658 | Software updates processing was canceled |
-2016410025 | 2278557271 | 0x87D00657 | Error while detecting software updates status after scan success |
-2016410026 | 2278557270 | 0x87D00656 | Updates handler was unable to continue due to some generic internal error |
-2016410027 | 2278557269 | 0x87D00655 | Failed to install one or more software updates |
-2016410028 | 2278557268 | 0x87D00654 | Software update install failure occurred |
-2016410029 | 2278557267 | 0x87D00653 | Software update download failure occurred |
-2016410030 | 2278557266 | 0x87D00652 | Software update policy was not found |
-2016410031 | 2278557265 | 0x87D00651 | Post-install scan failed |
-2016410032 | 2278557264 | 0x87D00650 | Pre-install scan failed |
-2016410060 | 2278557236 | 0x87D00634 | Legacy scanner not supported |
-2016410061 | 2278557235 | 0x87D00633 | The offline scan is pending |
-2016410062 | 2278557234 | 0x87D00632 | The online scan is pending |
-2016410063 | 2278557233 | 0x87D00631 | Scan retry is pending |
-2016410064 | 2278557232 | 0x87D00630 | Maximum retries exhausted |
-2016410071 | 2278557225 | 0x87D00629 | Rescan of the updates is pending |
-2016410072 | 2278557224 | 0x87D00628 | Invalid content location |
-2016410073 | 2278557223 | 0x87D00627 | Process instance not found |
-2016410074 | 2278557222 | 0x87D00626 | Invalid process instance information |
-2016410104 | 2278557192 | 0x87D00608 | Invalid instance type |
-2016410105 | 2278557191 | 0x87D00607 | Content not found |
-2016410106 | 2278557190 | 0x87D00606 | Offline scan tool history not found |
-2016410107 | 2278557189 | 0x87D00605 | The scan tool has been removed |
-2016410108 | 2278557188 | 0x87D00604 | The ScanTool not found in the job queue |
-2016410109 | 2278557187 | 0x87D00603 | The ScanTool Policy has been removed, so cannot complete scan operation |
-2016410110 | 2278557186 | 0x87D00602 | Content location request timeout occurred |
-2016410111 | 2278557185 | 0x87D00601 | Scanning for updates timed out |
-2016410112 | 2278557184 | 0x87D00600 | Scan Tool Policy not found |
-2016410558 | 2278556738 | 0x87D00442 | An enforcement action (install/uninstall) was attempted for a simulated deployment. |
-2016410559 | 2278556737 | 0x87D00441 | The deployment metadata is not available on the client. |
-2016410560 | 2278556736 | 0x87D00440 | Expected policy documents are incomplete or missing. |
-2016410592 | 2278556704 | 0x87D00420 | The detection rules refer to an unsupported WMI namespace. |
-2016410621 | 2278556675 | 0x87D00403 | The detection rules contain an unsupported datatype. |
-2016410622 | 2278556674 | 0x87D00402 | The detection rules contain an invalid operator. |
-2016410623 | 2278556673 | 0x87D00401 | An incorrect XML expression was found when evaluating the detection rules. |
-2016410624 | 2278556672 | 0x87D00400 | An unexpected error occurred when evaluating the detection rules. |
-2016410832 | 2278556464 | 0x87D00330 | This application deployment type does not support being enforced with a required deployment |
-2016410838 | 2278556458 | 0x87D0032A | The uninstall command line is invalid |
-2016410839 | 2278556457 | 0x87D00329 | Application requirement evaluation or detection failed |
-2016410840 | 2278556456 | 0x87D00328 | Configuration item digest not found |
-2016410841 | 2278556455 | 0x87D00327 | The script is not signed |
-2016410842 | 2278556454 | 0x87D00326 | The application deployment metadata was not found in WMI |
-2016410843 | 2278556453 | 0x87D00325 | The application was still detected after uninstalling was completed. |
-2016410844 | 2278556452 | 0x87D00324 | The application was not detected after the installation was completed. |
-2016410845 | 2278556451 | 0x87D00323 | No user is logged on. |
-2016410846 | 2278556450 | 0x87D00322 | Rule conflict. |
-2016410847 | 2278556449 | 0x87D00321 | The script execution has timed out. |
-2016410848 | 2278556448 | 0x87D00320 | The script host has not been installed yet. |
-2016410849 | 2278556447 | 0x87D0031F | Script for discovery returned invalid data. |
-2016410850 | 2278556446 | 0x87D0031E | Unsupported configuration. The application is configured to Install for User but has been targeted to a mechanical device instead of the user. |
-2016410851 | 2278556445 | 0x87D0031D | Unsupported configuration. The application is targeted to a user but is configured to install when no user is logged in. |
-2016410858 | 2278556438 | 0x87D00316 | CI Agent job was canceled. |
-2016410859 | 2278556437 | 0x87D00315 | The CI version info data is not available. |
-2016410860 | 2278556436 | 0x87D00314 | CI Version Info timed out. |
-2016410983 | 2278556313 | 0x87D00299 | The client does not recognize this type of signature |
-2016410984 | 2278556312 | 0x87D00298 | The client�s database record could not be validated |
-2016410985 | 2278556311 | 0x87D00297 | Invalid key |
-2016410986 | 2278556310 | 0x87D00296 | The client failed to process one or more CI documents |
-2016410987 | 2278556309 | 0x87D00295 | Registration certificate is either missing or invalid |
-2016410988 | 2278556308 | 0x87D00294 | Unable to verify Policy |
-2016410989 | 2278556307 | 0x87D00293 | Client unable to Refresh Site server signing certificate |
-2016410990 | 2278556306 | 0x87D00292 | Client unable to compute message signature for InBand Auth |
-2016410991 | 2278556305 | 0x87D00291 | No task sequence policies assigned |
-2016410992 | 2278556304 | 0x87D00290 | The job contains no items |
-2016410999 | 2278556297 | 0x87D00289 | Failed to decompress CI documents |
-2016411000 | 2278556296 | 0x87D00288 | Failed to decompress configuration item |
-2016411001 | 2278556295 | 0x87D00287 | The signing certificate is missing |
-2016411002 | 2278556294 | 0x87D00286 | Invalid SMS authority |
-2016411003 | 2278556293 | 0x87D00285 | Search criteria verb is either missing or invalid |
-2016411004 | 2278556292 | 0x87D00284 | Missing subject name |
-2016411005 | 2278556291 | 0x87D00283 | Missing private key |
-2016411006 | 2278556290 | 0x87D00282 | More than one certificate was found, but �select first cert� was not set |
-2016411007 | 2278556289 | 0x87D00281 | No certificate matching criteria specified |
-2016411008 | 2278556288 | 0x87D00280 | Empty certificate store |
-2016411009 | 2278556287 | 0x87D0027F | SHA could not bind as NAP Agent might not be running |
-2016411010 | 2278556286 | 0x87D0027E | Bad HTTP status code |
-2016411011 | 2278556285 | 0x87D0027D | CI documents download failed due to hash mismatch |
-2016411012 | 2278556284 | 0x87D0027C | CI documents download timed out |
-2016411013 | 2278556283 | 0x87D0027B | General CI documents download failure |
-2016411014 | 2278556282 | 0x87D0027A | Configuration item download failed due to hash mismatch |
-2016411015 | 2278556281 | 0x87D00279 | Configuration item download timed out |
-2016411016 | 2278556280 | 0x87D00278 | General configuration item download failure |
-2016411017 | 2278556279 | 0x87D00277 | Insufficient resources to complete the operation |
-2016411018 | 2278556278 | 0x87D00276 | A system restart is required |
-2016411019 | 2278556277 | 0x87D00275 | Failed to acquire the lock |
-2016411020 | 2278556276 | 0x87D00274 | No callback completion interface specified |
-2016411021 | 2278556275 | 0x87D00273 | The component has already been requested to pause |
-2016411022 | 2278556274 | 0x87D00272 | Component is disabled |
-2016411023 | 2278556273 | 0x87D00271 | Component is paused |
-2016411024 | 2278556272 | 0x87D00270 | The component is not paused |
-2016411025 | 2278556271 | 0x87D0026F | Pause cookie did not match |
-2016411026 | 2278556270 | 0x87D0026E | Pause duration too big |
-2016411027 | 2278556269 | 0x87D0026D | Pause duration too small |
-2016411028 | 2278556268 | 0x87D0026C | Status not found |
-2016411029 | 2278556267 | 0x87D0026B | Agent type not found |
-2016411030 | 2278556266 | 0x87D0026A | Key type not found |
-2016411031 | 2278556265 | 0x87D00269 | Required management point not found |
-2016411032 | 2278556264 | 0x87D00268 | Compilation failed |
-2016411033 | 2278556263 | 0x87D00267 | Download failed |
-2016411034 | 2278556262 | 0x87D00266 | Inconsistent data |
-2016411035 | 2278556261 | 0x87D00265 | Invalid store state |
-2016411036 | 2278556260 | 0x87D00264 | Invalid operation |
-2016411037 | 2278556259 | 0x87D00263 | Invalid message received from DTS |
-2016411038 | 2278556258 | 0x87D00262 | The type of DTS message received is unknown |
-2016411039 | 2278556257 | 0x87D00261 | Failed to persist configuration item definition |
-2016411040 | 2278556256 | 0x87D00260 | Job state is not valid for the action being requested |
-2016411041 | 2278556255 | 0x87D0025F | Client disconnected |
-2016411042 | 2278556254 | 0x87D0025E | Encountered a message which was not sufficiently trusted to forward to an endpoint for processing |
-2016411043 | 2278556253 | 0x87D0025D | Encountered invalid XML document which could not be validated by its corresponding XML schema(s) |
-2016411060 | 2278556236 | 0x87D0024C | Encountered invalid XML schema document |
-2016411061 | 2278556235 | 0x87D0024B | Name already exists |
-2016411062 | 2278556234 | 0x87D0024A | The job is already connected |
-2016411063 | 2278556233 | 0x87D00249 | Property is not valid for the given configuration item type |
-2016411064 | 2278556232 | 0x87D00248 | There was an error in network communication |
-2016411065 | 2278556231 | 0x87D00247 | A component required to perform the operation was missing or not registered |
-2016411066 | 2278556230 | 0x87D00246 | There was an error evaluating the health of the client |
-2016411067 | 2278556229 | 0x87D00245 | The objector subsystem has already been initialized |
-2016411068 | 2278556228 | 0x87D00244 | The object or subsystem has not been initialized |
-2016411069 | 2278556227 | 0x87D00243 | Public key mismatch |
-2016411070 | 2278556226 | 0x87D00242 | Stored procedure failed |
-2016411071 | 2278556225 | 0x87D00241 | Failed to connect to database |
-2016411072 | 2278556224 | 0x87D00240 | Insufficient disk space |
-2016411079 | 2278556217 | 0x87D00239 | Client id not found |
-2016411080 | 2278556216 | 0x87D00238 | Public key not found |
-2016411081 | 2278556215 | 0x87D00237 | Reply mode incompatible |
-2016411082 | 2278556214 | 0x87D00236 | Low memory |
-2016411083 | 2278556213 | 0x87D00235 | Syntax error occurred while parsing |
-2016411084 | 2278556212 | 0x87D00234 | An internal endpoint cannot receive a remote message |
-2016411085 | 2278556211 | 0x87D00233 | Message not trusted |
-2016411086 | 2278556210 | 0x87D00232 | Message not signed |
-2016411087 | 2278556209 | 0x87D00231 | Transient error |
-2016411088 | 2278556208 | 0x87D00230 | Error logging on as given credentials |
-2016411095 | 2278556201 | 0x87D00229 | Failed to get credentials |
-2016411096 | 2278556200 | 0x87D00228 | Invalid endpoint |
-2016411097 | 2278556199 | 0x87D00227 | Functionality disabled |
-2016411098 | 2278556198 | 0x87D00226 | Invalid protocol |
-2016411099 | 2278556197 | 0x87D00225 | Invalid address type |
-2016411100 | 2278556196 | 0x87D00224 | Invalid message |
-2016411101 | 2278556195 | 0x87D00223 | Version mismatch |
-2016411102 | 2278556194 | 0x87D00222 | Operation canceled |
-2016411103 | 2278556193 | 0x87D00221 | Invalid user |
-2016411104 | 2278556192 | 0x87D00220 | Invalid type |
-2016411111 | 2278556185 | 0x87D00219 | Global service not set |
-2016411112 | 2278556184 | 0x87D00218 | Invalid service settings |
-2016411113 | 2278556183 | 0x87D00217 | Data is corrupt |
-2016411114 | 2278556182 | 0x87D00216 | Invalid service parameter |
-2016411115 | 2278556181 | 0x87D00215 | Item not found |
-2016411116 | 2278556180 | 0x87D00214 | Invalid name length |
-2016411117 | 2278556179 | 0x87D00213 | Timeout occurred |
-2016411118 | 2278556178 | 0x87D00212 | Context is closed |
-2016411119 | 2278556177 | 0x87D00211 | Invalid Address |
-2016411120 | 2278556176 | 0x87D00210 | Invalid Translator |
-2016411127 | 2278556169 | 0x87D00209 | Data type mismatch |
-2016411128 | 2278556168 | 0x87D00208 | Invalid command |
-2016411129 | 2278556167 | 0x87D00207 | Parsing error |
-2016411130 | 2278556166 | 0x87D00206 | Invalid file |
-2016411131 | 2278556165 | 0x87D00205 | Invalid path |
-2016411132 | 2278556164 | 0x87D00204 | Data too large |
-2016411133 | 2278556163 | 0x87D00203 | No data supplied |
-2016411134 | 2278556162 | 0x87D00202 | Service is shutting down |
-2016411135 | 2278556161 | 0x87D00201 | Incorrect name format |
-2016411136 | 2278556160 | 0x87D00200 | Name not found |
-2145058817 | 2149908479 | 0x8024FFFF | There was a reporter error not covered by another error code. |
-2145062907 | 2149904389 | 0x8024F005 | The specified callback cookie is not found. |
-2145062908 | 2149904388 | 0x8024F004 | The server rejected an event because the server was too busy. |
-2145062909 | 2149904387 | 0x8024F003 | The XML in the event namespace descriptor could not be parsed. |
-2145062910 | 2149904386 | 0x8024F002 | The XML in the event namespace descriptor could not be parsed. |
-2145062911 | 2149904385 | 0x8024F001 | The event cache file was defective. |
-2145062913 | 2149904383 | 0x8024EFFF | There was an expression evaluator error not covered by another WU_E_EE_* error code. |
-2145067001 | 2149900295 | 0x8024E007 | An expression evaluator operation could not be completed because the cluster state of the computer could not be determined. |
-2145067002 | 2149900294 | 0x8024E006 | An expression evaluator operation could not be completed because there was an invalid attribute. |
-2145067003 | 2149900293 | 0x8024E005 | The expression evaluator could not be initialized. |
-2145067004 | 2149900292 | 0x8024E004 | An expression evaluator operation could not be completed because the version of the serialized expression data is invalid. |
-2145067005 | 2149900291 | 0x8024E003 | An expression evaluator operation could not be completed because an expression contains an incorrect number of metadata nodes. |
-2145067006 | 2149900290 | 0x8024E002 | An expression evaluator operation could not be completed because an expression was invalid. |
-2145067007 | 2149900289 | 0x8024E001 | An expression evaluator operation could not be completed because an expression was unrecognized. |
-2145067009 | 2149900287 | 0x8024DFFF | Windows Update Agent could not be updated because of an error not covered by another WU_E_SETUP_* error code. |
-2145071082 | 2149896214 | 0x8024D016 | Windows Update Agent could not be updated because of an unknown error. |
-2145071083 | 2149896213 | 0x8024D015 | Windows Update Agent is successfully updated, but a reboot is required to complete the setup. |
-2145071084 | 2149896212 | 0x8024D014 | Windows Update Agent is successfully updated, but a reboot is required to complete the setup. |
-2145071085 | 2149896211 | 0x8024D013 | Windows Update Agent could not be updated because the server does not contain updated information for this version. |
-2145071086 | 2149896210 | 0x8024D012 | Windows Update Agent must be updated before a search can continue. An administrator is required to perform the operation. |
-2145071087 | 2149896209 | 0x8024D011 | Windows Update Agent must be updated before a search can continue. |
-2145071088 | 2149896208 | 0x8024D010 | Windows Update Agent could not be updated because the registry contains invalid information. |
-2145071089 | 2149896207 | 0x8024D00F | Windows Update Agent could not be updated because the setup handler failed during execution. |
-2145071090 | 2149896206 | 0x8024D00E | Windows Update Agent setup package requires a reboot to complete installation. |
-2145071091 | 2149896205 | 0x8024D00D | Windows Update Agent setup is already running. |
-2145071092 | 2149896204 | 0x8024D00C | Windows Update Agent could not be updated because a restart of the system is required. |
-2145071093 | 2149896203 | 0x8024D00B | Windows Update Agent could not be updated because the system is configured to block the update. |
-2145071094 | 2149896202 | 0x8024D00A | Windows Update Agent could not be updated because the current system configuration is not supported. |
-2145071095 | 2149896201 | 0x8024D009 | An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file. |
-2145071096 | 2149896200 | 0x8024D008 | An update to the Windows Update Agent was skipped because previous attempts to update have failed. |
-2145071097 | 2149896199 | 0x8024D007 | Windows Update Agent could not be updated because regsvr32.exe returned an error. |
-2145071098 | 2149896198 | 0x8024D006 | Windows Update Agent could not be updated because a WUA file on the target system is newer than the corresponding source file. |
-2145071099 | 2149896197 | 0x8024D005 | Windows Update Agent could not be updated because the versions specified in the INF do not match the actual source file versions. |
-2145071100 | 2149896196 | 0x8024D004 | Windows Update Agent could not be updated because setup initialization was never completed successfully. |
-2145071101 | 2149896195 | 0x8024D003 | Windows Update Agent could not be updated because of an internal error that caused set up initialization to be performed twice. |
-2145071102 | 2149896194 | 0x8024D002 | Windows Update Agent could not be updated because the wuident.cab file contains invalid information. |
-2145071103 | 2149896193 | 0x8024D001 | Windows Update Agent could not be updated because an INF file contains invalid information. |
-2145071105 | 2149896191 | 0x8024CFFF | A driver error not covered by another WU_E_DRV_* code. |
-2145075193 | 2149892103 | 0x8024C007 | Information required for the synchronization of applicable printers is missing. |
-2145075194 | 2149892102 | 0x8024C006 | Driver synchronization failed. |
-2145075195 | 2149892101 | 0x8024C005 | The driver update is missing a required attribute. |
-2145075196 | 2149892100 | 0x8024C004 | The driver update is missing metadata. |
-2145075197 | 2149892099 | 0x8024C003 | The registry type read for the driver does not match the expected type. |
-2145075198 | 2149892098 | 0x8024C002 | A property for the driver could not be found. It may not conform to the required specifications. |
-2145075199 | 2149892097 | 0x8024C001 | A driver was skipped. |
-2145079291 | 2149888005 | 0x8024B005 | Cannot cancel a non-scheduled install. |
-2145079292 | 2149888004 | 0x8024B004 | The task was stopped and needs to be rerun to complete. |
-2145079293 | 2149888003 | 0x8024B003 | The operation cannot be completed since the task is not yet started. |
-2145079294 | 2149888002 | 0x8024B002 | The operation cannot be completed since the task status is currently disabled. |
-2145079295 | 2149888001 | 0x8024B001 | The task is currently in progress. |
-2145079297 | 2149887999 | 0x8024AFFF | An Automatic Updates error is not covered by another WU_E_AU * code. |
-2145083386 | 2149883910 | 0x8024A006 | The default service registered with AU changed during the search. |
-2145083387 | 2149883909 | 0x8024A005 | No unmanaged service is registered with AU. |
-2145083388 | 2149883908 | 0x8024A004 | Automatic Updates was unable to process incoming requests because it was paused. |
-2145083389 | 2149883907 | 0x8024A003 | The old version of the Automatic Updates client was disabled. |
-2145083390 | 2149883906 | 0x8024A002 | The old version of the Automatic Updates client has stopped because the WSUS server has been upgraded. |
-2145083392 | 2149883904 | 0x8024A000 | Automatic Updates was unable to service incoming requests. |
-2145087483 | 2149879813 | 0x80249005 | A WMI error occurred when enumerating the instances for a particular class. |
-2145087484 | 2149879812 | 0x80249004 | There was an inventory error not covered by another error code. |
-2145087485 | 2149879811 | 0x80249003 | Failed to upload inventory results to the server. |
-2145087486 | 2149879810 | 0x80249002 | Failed to get the requested inventory type from the server. |
-2145087487 | 2149879809 | 0x80249001 | Parsing of the rule file failed. |
-2145087489 | 2149879807 | 0x80248FFF | A data store error is not covered by another WU_E_DS_* code. |
-2145091555 | 2149875741 | 0x8024801D | A data store operation did not complete because it was requested with an impersonated identity. |
-2145091556 | 2149875740 | 0x8024801C | The data store requires a session reset; release the session and retry with a new session. |
-2145091557 | 2149875739 | 0x8024801B | The schema of the current data store and the schema of a table in a backup XML document do not match. |
-2145091558 | 2149875738 | 0x8024801A | A request was declined because the operation is not allowed. |
-2145091559 | 2149875737 | 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. |
-2145091560 | 2149875736 | 0x80248018 | A table was not closed because it is not associated with the session. |
-2145091561 | 2149875735 | 0x80248017 | A table was not closed because it is not associated with the session. |
-2145091562 | 2149875734 | 0x80248016 | A request to hide an update was declined because it is a mandatory update or because it was deployed with a deadline. |
-2145091563 | 2149875733 | 0x80248015 | An operation did not complete because the registration of the service has expired. |
-2145091564 | 2149875732 | 0x80248014 | An operation did not complete because the service is not in the data store. |
-2145091565 | 2149875731 | 0x80248013 | The server sent the same update to the client with two different revision IDs. |
-2145091567 | 2149875729 | 0x80248011 | I could not create a datastore object in another process. |
-2145091568 | 2149875728 | 0x80248010 | The datastore is not allowed to be registered with COM in the current process. |
-2145091569 | 2149875727 | 0x8024800F | The data store could not be initialized because it was locked by another process. |
-2145091570 | 2149875726 | 0x8024800E | The row was not added because an existing row has the same primary key. |
-2145091571 | 2149875725 | 0x8024800D | The category was not added because it contains no parent categories and is not a top-level category itself. |
-2145091572 | 2149875724 | 0x8024800C | The data store section could not be locked within the allotted time. |
-2145091573 | 2149875723 | 0x8024800B | The update was not deleted because it is still referenced by one or more services. |
-2145091574 | 2149875722 | 0x8024800A | The update was not processed because its update handler could not be recognized. |
-2145091575 | 2149875721 | 0x80248009 | The datastore is missing required information or references missing license terms file localized property or linked row. |
-2145091576 | 2149875720 | 0x80248008 | The datastore is missing required information or has a NULL in a table column that requires a non-null value. |
-2145091577 | 2149875719 | 0x80248007 | The information requested is not in the data store. |
-2145091578 | 2149875718 | 0x80248006 | The current and expected versions of the datastore do not match. |
-2145091579 | 2149875717 | 0x80248005 | A table could not be opened because the table is not in the data store. |
-2145091580 | 2149875716 | 0x80248004 | The data store contains a table with unexpected columns. |
-2145091581 | 2149875715 | 0x80248003 | The datastore is missing a table. |
-2145091582 | 2149875714 | 0x80248002 | The current and expected states of the datastore do not match. |
-2145091583 | 2149875713 | 0x80248001 | An operation failed because the datastore was in use. |
-2145091584 | 2149875712 | 0x80248000 | An operation failed because Windows Update Agent is shutting down. |
-2145091585 | 2149875711 | 0x80247FFF | Search using the scan package failed. |
-2145095675 | 2149871621 | 0x80247005 | The service is not registered. |
-2145095676 | 2149871620 | 0x80247004 | The size of the event payload submitted is invalid. |
-2145095677 | 2149871619 | 0x80247003 | An invalid event payload was specified. |
-2145095678 | 2149871618 | 0x80247002 | An operation could not be completed because the scan package requires a greater version of the Windows Update Agent. |
-2145095679 | 2149871617 | 0x80247001 | An operation could not be completed because the scan package was invalid. |
-2145095681 | 2149871615 | 0x80246FFF | There was a download manager error not covered by another WU_E_DM_* error code. |
-2145099764 | 2149867532 | 0x8024600C | A download failed because the current network limits downloads by update size for the update service. |
-2145099765 | 2149867531 | 0x8024600B | A download must be restarted because the updated content changed in a new revision. |
-2145099766 | 2149867530 | 0x8024600A | A download must be restarted because the location of the source of the download has changed. |
-2145099767 | 2149867529 | 0x80246009 | A download manager operation failed because of an unspecified Background Intelligent Transfer Service (BITS) transfer error. |
-2145099768 | 2149867528 | 0x80246008 | A download manager operation failed because the download manager could not connect the Background Intelligent Transfer Service (BITS). |
-2145099769 | 2149867527 | 0x80246007 | The update has not been downloaded. |
-2145099770 | 2149867526 | 0x80246006 | A download manager operation could not be completed because the version of Background Intelligent Transfer Service (BITS) is incompatible. |
-2145099771 | 2149867525 | 0x80246005 | A download manager operation could not be completed because the network connection was unavailable. |
-2145099772 | 2149867524 | 0x80246004 | An operation could not be completed because a download request is required from the download handler. |
-2145099773 | 2149867523 | 0x80246003 | A download manager operation could not be completed because the file metadata requested an unrecognized hash algorithm. |
Credits: Anoop Nair for the list of error codes
Want to see something else added? Open an issue.