Windows Errors 8

5095 0x13E7 Australia
5096 0x13E8 Japan
5097 0x13E9 Korea
5098 0x13EA China (PRC)
5099 0x13EB Taiwan
5100 0x13EC Asia
5101 0x13ED Portugal
5102 0x13EE Finland
5103 0x13EF Arabic
5104 0x13F0 Hebrew
5153 0x1421 The UPS service is about to perform final shut down.
5170 0x1432 The Workstation must be started with the NET START command.
5175 0x1437 Remote IPC
5176 0x1438 Remote Admin
5177 0x1439 Default share
5178 0x143A User Profiles
5291 0x14AB Never
5292 0x14AC Never
5293 0x14AD Never
5295 0x14AF NET.HLP
5296 0x14B0 NET.HLP
5297 0x14B1 Deny
5300 0x14B4 The network control block (NCB) request completed successfully. The NCB is the data.
5301 0x14B5 Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS. The NCB is the data.
5302 0x14B6 The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the data.
5303 0x14B7 The command specified in the network control block (NCB) is illegal. The NCB is the data.
5304 0x14B8 The message correlator specified in the network control block (NCB) is invalid. The NCB is the data.
5305 0x14B9 A network control block (NCB) command timed-out. The session may have terminated abnormally. The NCB is the data.
5306 0x14BA An incomplete network control block (NCB) message was received. The NCB is the data.
5307 0x14BB The buffer address specified in the network control block (NCB) is illegal. The NCB is the data.
5308 0x14BC The session number specified in the network control block (NCB) is not active. The NCB is the data.
5309 0x14BD No resource was available in the network adapter. The network control block (NCB) request was refused. The NCB is the data.
5310 0x14BE The session specified in the network control block (NCB) was closed. The NCB is the data.
5311 0x14BF The network control block (NCB) command was canceled. The NCB is the data.
5312 0x14C0 The message segment specified in the network control block (NCB) is illogical. The NCB is the data.
5313 0x14C1 The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is the data.
5314 0x14C2 The network adapter name table is full. The network control block (NCB) request was refused. The NCB is the data.
5315 0x14C3 The network name has active sessions and is now de-registered. The network control block (NCB) command completed. The NCB is the data.
5316 0x14C4 A previously issued Receive Lookahead command is active for this session. The network control block (NCB) command was rejected. The NCB is the data.
5317 0x14C5 The local session table is full. The network control block (NCB) request was refused. The NCB is the data.
5318 0x14C6 A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the data.
5319 0x14C7 The name number specified in the network control block (NCB) is illegal. The NCB is the data.
5320 0x14C8 The call name specified in the network control block (NCB) cannot be found or did not answer. The NCB is the data.
5321 0x14C9 The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the data.
5322 0x14CA The name specified in the network control block (NCB) is in use on a remote adapter. The NCB is the data.
5323 0x14CB The name specified in the network control block (NCB) has been deleted. The NCB is the data.
5324 0x14CC The session specified in the network control block (NCB) ended abnormally. The NCB is the data.
5325 0x14CD The network protocol has detected two or more identical names on the network. The network control block (NCB) is the data.
5326 0x14CE An unexpected protocol packet was received. There may be an incompatible remote device. The network control block (NCB) is the data.
5333 0x14D5 The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB is the data.
5334 0x14D6 There are too many network control block (NCB) commands outstanding. The NCB request was refused. The NCB is the data.
5335 0x14D7 The adapter number specified in the network control block (NCB) is illegal. The NCB is the data.
5336 0x14D8 The network control block (NCB) command completed while a cancel was occurring. The NCB is the data.
5337 0x14D9 The name specified in the network control block (NCB) is reserved. The NCB is the data.
5338 0x14DA The network control block (NCB) command is not valid to cancel. The NCB is the data.
5351 0x14E7 There are multiple network control block (NCB) requests for the same session. The NCB request was refused. The NCB is the data.
5352 0x14E8 There has been a network adapter error. The only NetBIOS command that may be issued is an NCB RESET. The network control block (NCB) is the data.
5354 0x14EA The maximum number of applications was exceeded. The network control block (NCB) request was refused. The NCB is the data.
5356 0x14EC The requested resources are not available. The network control block (NCB) request was refused. The NCB is the data.
5364 0x14F4 A system error has occurred. The network control block (NCB) request was refused. The NCB is the data.
5365 0x14F5 A ROM checksum failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5366 0x14F6 A RAM test failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5367 0x14F7 A digital loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5368 0x14F8 An analog loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5369 0x14F9 An interface failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5370 0x14FA An unrecognized network control block (NCB) return code was received. The NCB is the data.
5380 0x1504 A network adapter malfunction has occurred. The network control block (NCB) request was refused. The NCB is the data.
5381 0x1505 The network control block (NCB) command is still pending. The NCB is the data.
5509 0x1585 Windows could not be started as configured. A previous working configuration was used instead.
5600 0x15E0 Could not share the User or Script path.
5601 0x15E1 The password for this computer is not found in the local security database.
5602 0x15E2 An internal error occurred while accessing the computer's local or network security database.
5728 0x1660 Could not load any transport.
5739 0x166B This domain has more global groups than can be replicated to a LanMan BDC. Either delete some of your global groups or remove the LanMan BDCs from the domain.
5742 0x166E Service failed to retrieve messages needed to boot remote boot clients.
5743 0x166F Service experienced a severe error and can no longer provide remote boot for 3Com 3Start remote boot clients.
5744 0x1670 Service experienced a severe system error and will shut itself down.
5760 0x1680 Service experienced error evaluating RPL configurations.
5761 0x1681 Service experienced error creating RPL profiles for all configurations.
5762 0x1682 Service experienced error accessing registry.
5763 0x1683 Service experienced error replacing possibly outdated RPLDISK.SYS.
5764 0x1684 Service experienced error adding security accounts or setting file permissions. These accounts are the RPLUSER local group and the user accounts for the individual RPL workstations.
5765 0x1685 Service failed to back up its database.
5766 0x1686 Service failed to initialize from its database. The database may be missing or corrupted. Service will attempt restoring the database from the backup.
5767 0x1687 Service failed to restore its database from the backup. Service will not start.
5768 0x1688 Service successfully restored its database from the backup.
5769 0x1689 Service failed to initialize from its restored database. Service will not start.
5771 0x168B The Remoteboot database was in NT 3.5 / NT 3.51 format and NT is attempting to convert it to NT 4.0 format. The JETCONV converter will write to the Application event log when it is finished.
5806 0x16AE Dynamic DNS updates have been manually disabled on this domain controller. USER ACTION Reconfigure this domain controller to use dynamic DNS updates or manually add the DNS records from the file 'SystemRootSystem32ConfigNetlogon.dns' to the DNS database.
5808 0x16B0 The deregistration of some DNS domain controller locator records was aborted at the time of this domain controller demotion because the DNS deregistrations took too long. USER ACTION Manually delete the DNS records listed in the file 'SystemRootSystem32ConfigNetlogon.dns' from the DNS database.
5890 0x1702 An operation was attempted that is incompatible with the current membership state of the node.
5891 0x1703 The quorum resource does not contain the quorum log.
5892 0x1704 The membership engine requested shutdown of the cluster service on this node.
5893 0x1705 The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.
5894 0x1706 A matching cluster network for the specified IP address could not be found.
5895 0x1707 The actual data type of the property did not match the expected data type of the property.
5896 0x1708 The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer.
5897 0x1709 Two or more parameter values specified for a resource's properties are in conflict.
5898 0x170A This computer cannot be made a member of a cluster.
5899 0x170B This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.
5900 0x170C A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster.
5901 0x170D The cluster configuration action has already been committed.
5902 0x170E The cluster configuration action could not be rolled back.
5903 0x170F The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node.
5904 0x1710 One or more nodes in the cluster are running a version of Windows that does not support this operation.
5905 0x1711 The name of the corresponding computer account doesn't match the Network Name for this resource.
5906 0x1712 No network adapters are available.
5907 0x1713 The cluster node has been poisoned.
5908 0x1714 The group is unable to accept the request since it is moving to another node.
5909 0x1715 The resource type cannot accept the request since is too busy performing another operation.
5910 0x1716 The call to the cluster resource DLL timed out.
5911 0x1717 The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted.
5912 0x1718 An internal cluster error occurred. A call to an invalid function was attempted.
5913 0x1719 A parameter value is out of acceptable range.
5914 0x171A A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required.
5915 0x171B An invalid cluster registry operation was attempted.
5916 0x171C An input string of characters is not properly terminated.
5917 0x171D An input string of characters is not in a valid format for the data it represents.
5918 0x171E An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress.
5919 0x171F An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress.
5920 0x1720 An internal cluster error occurred. Data was not properly initialized.
5921 0x1721 An error occurred while reading from a stream of data. An unexpected number of bytes was returned.
5922 0x1722 An error occurred while writing to a stream of data. The required number of bytes could not be written.
5923 0x1723 An error occurred while deserializing a stream of cluster data.
5924 0x1724 One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s).
5925 0x1725 A quorum of cluster nodes was not present to form a cluster.
5926 0x1726 The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address.
5927 0x1727 The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends.
5928 0x1728 Quorum resource cannot reside in the Available Storage group.
5929 0x1729 The dependencies for this resource are nested too deeply.
5930 0x172A The call into the resource DLL raised an unhandled exception.
5931 0x172B The RHS process failed to initialize.
5932 0x172C The Failover Clustering feature is not installed on this node.
5933 0x172D The resources must be online on the same node for this operation
6000 0x1770 The specified file could not be encrypted.
6001 0x1771 The specified file could not be decrypted.
6002 0x1772 The specified file is encrypted and the user does not have the ability to decrypt it.
6003 0x1773 There is no valid encryption recovery policy configured for this system.
6004 0x1774 The required encryption driver is not loaded for this system.
6005 0x1775 The file was encrypted with a different encryption driver than is currently loaded.
6006 0x1776 There are no EFS keys defined for the user.
6007 0x1777 The specified file is not encrypted.
6008 0x1778 The specified file is not in the defined EFS export format.
6009 0x1779 The specified file is read only.
6010 0x177A The directory has been disabled for encryption.
6011 0x177B The server is not trusted for remote encryption operation.
6012 0x177C Recovery policy configured for this system contains invalid recovery certificate.
6013 0x177D The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file.
6014 0x177E The disk partition does not support file encryption.
6015 0x177F This machine is disabled for file encryption.
6016 0x1780 A newer system is required to decrypt this encrypted file.
6017 0x1781 The remote server sent an invalid response for a file being opened with Client Side Encryption.
6018 0x1782 Client Side Encryption is not supported by the remote server even though it claims to support it.
6019 0x1783 File is encrypted and should be opened in Client Side Encryption mode.
6020 0x1784 A new encrypted file is being created and a $EFS needs to be provided.
6021 0x1785 The SMB client requested a CSE FSCTL on a non-CSE file.
6118 0x17E6 The list of servers for this workgroup is not currently available
6200 0x1838 The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts.
6600 0x19C8 Log service encountered an invalid log sector.
6601 0x19C9 Log service encountered a log sector with invalid block parity.
6602 0x19CA Log service encountered a remapped log sector.
6603 0x19CB Log service encountered a partial or incomplete log block.
6604 0x19CC Log service encountered an attempt access data outside the active log range.
6605 0x19CD Log service user marshalling buffers are exhausted.
6606 0x19CE Log service encountered an attempt read from a marshalling area with an invalid read context.
6607 0x19CF Log service encountered an invalid log restart area.
6608 0x19D0 Log service encountered an invalid log block version.
6609 0x19D1 Log service encountered an invalid log block.
6610 0x19D2 Log service encountered an attempt to read the log with an invalid read mode.
6611 0x19D3 Log service encountered a log stream with no restart area.
6612 0x19D4 Log service encountered a corrupted metadata file.
6613 0x19D5 Log service encountered a metadata file that could not be created by the log file system.
6614 0x19D6 Log service encountered a metadata file with inconsistent data.
6615 0x19D7 Log service encountered an attempt to erroneous allocate or dispose reservation space.
6616 0x19D8 Log service cannot delete log file or file system container.
6617 0x19D9 Log service has reached the maximum allowable containers allocated to a log file.
6618 0x19DA Log service has attempted to read or write backward past the start of the log.
6619 0x19DB Log policy could not be installed because a policy of the same type is already present.
6620 0x19DC Log policy in question was not installed at the time of the request.
6621 0x19DD The installed set of policies on the log is invalid.
6622 0x19DE A policy on the log in question prevented the operation from completing.
6623 0x19DF Log space cannot be reclaimed because the log is pinned by the archive tail.
6624 0x19E0 Log record is not a record in the log file.
6625 0x19E1 Number of reserved log records or the adjustment of the number of reserved log records is invalid.
6626 0x19E2 Reserved log space or the adjustment of the log space is invalid.
6627 0x19E3 An new or existing archive tail or base of the active log is invalid.
6628 0x19E4 Log space is exhausted.
6629 0x19E5 The log could not be set to the requested size.
6630 0x19E6 Log is multiplexed, no direct writes to the physical log is allowed.
6631 0x19E7 The operation failed because the log is a dedicated log.
6632 0x19E8 The operation requires an archive context.
6633 0x19E9 Log archival is in progress.
6634 0x19EA The operation requires a non-ephemeral log, but the log is ephemeral.
6635 0x19EB The log must have at least two containers before it can be read from or written to.
6636 0x19EC A log client has already registered on the stream.
6637 0x19ED A log client has not been registered on the stream.
6638 0x19EE A request has already been made to handle the log full condition.
6639 0x19EF Log service enountered an error when attempting to read from a log container.
6640 0x19F0 Log service enountered an error when attempting to write to a log container.
6641 0x19F1 Log service enountered an error when attempting open a log container.
6642 0x19F2 Log service enountered an invalid container state when attempting a requested action.
6643 0x19F3 Log service is not in the correct state to perform a requested action.
6644 0x19F4 Log space cannot be reclaimed because the log is pinned.
6645 0x19F5 Log metadata flush failed.
6646 0x19F6 Security on the log and its containers is inconsistent.
6647 0x19F7 Records were appended to the log or reservation changes were made, but the log could not be flushed.
6648 0x19F8 The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.
6700 0x1A2C The transaction handle associated with this operation is not valid.
6701 0x1A2D The requested operation was made in the context of a transaction that is no longer active.
6702 0x1A2E The requested operation is not valid on the Transaction object in its current state.
6703 0x1A2F The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller.
6704 0x1A30 It is too late to perform the requested operation, since the Transaction has already been aborted.
6705 0x1A31 It is too late to perform the requested operation, since the Transaction has already been committed.
6706 0x1A32 The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.
6707 0x1A33 The specified ResourceManager made no changes or updates to the resource under this transaction.
6708 0x1A34 The resource manager has attempted to prepare a transaction that it has not successfully joined.
6709 0x1A35 The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow.
6710 0x1A36 The RM tried to register a protocol that already exists.
6711 0x1A37 The attempt to propagate the Transaction failed.
6712 0x1A38 The requested propagation protocol was not registered as a CRM.
6713 0x1A39 The buffer passed in to PushTransaction or PullTransaction is not in a valid format.
6714 0x1A3A The current transaction context associated with the thread is not a valid handle to a transaction object.
6715 0x1A3B The specified Transaction object could not be opened, because it was not found.
6716 0x1A3C The specified ResourceManager object could not be opened, because it was not found.
6717 0x1A3D The specified Enlistment object could not be opened, because it was not found.
6718 0x1A3E The specified TransactionManager object could not be opened, because it was not found.
6719 0x1A3F The specified ResourceManager was unable to create an enlistment, because its associated TransactionManager is not online.
6720 0x1A40 The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.
6721 0x1A41 The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transactoin can be enlisted on as a superior.
6722 0x1A42 Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.
6723 0x1A43 The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask.
6724 0x1A44 The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.
6725 0x1A45 Implicit transaction are not supported.
6726 0x1A46 The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.
6800 0x1A90 The function attempted to use a name that is reserved for use by another transaction.
6801 0x1A91 Transaction support within the specified file system resource manager is not started or was shutdown due to an error.
6802 0x1A92 The metadata of the RM has been corrupted. The RM will not function.
6803 0x1A93 The specified directory does not contain a resource manager.
6805 0x1A95 The remote server or share does not support transacted file operations.
6806 0x1A96 The requested log size is invalid.
6807 0x1A97 The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.
6808 0x1A98 The specified file miniversion was not found for this transacted file open.
6809 0x1A99 The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.
6810 0x1A9A A miniversion may only be opened in the context of the transaction that created it.
6811 0x1A9B It is not possible to open a miniversion with modify access.
6812 0x1A9C It is not possible to create any more miniversions for this stream.
6814 0x1A9E The remote server sent mismatching version number or Fid for a file opened with transactions.
6815 0x1A9F The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint.
6816 0x1AA0 There is no transaction metadata on the file.
6817 0x1AA1 The log data is corrupt.
6818 0x1AA2 The file can't be recovered because there is a handle still open on it.
6819 0x1AA3 The transaction outcome is unavailable because the resource manager responsible for it has disconnected.
6820 0x1AA4 The request was rejected because the enlistment in question is not a superior enlistment.
6821 0x1AA5 The transactional resource manager is already consistent. Recovery is not needed.
6822 0x1AA6 The transactional resource manager has already been started.
6823 0x1AA7 The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.
6824 0x1AA8 The operation cannot be performed because another transaction is depending on the fact that this property will not change.
6825 0x1AA9 The operation would involve a single file with two transactional resource managers and is therefore not allowed.
6826 0x1AAA The $Txf directory must be empty for this operation to succeed.
6827 0x1AAB The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.
6828 0x1AAC The operation could not be completed because the transaction manager does not have a log.
6829 0x1AAD A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.
6830 0x1AAE The transactional metadata attribute on the file or directory is corrupt and unreadable.
6831 0x1AAF The encryption operation could not be completed because a transaction is active.
6832 0x1AB0 This object is not allowed to be opened in a transaction.
6833 0x1AB1 An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.
6834 0x1AB2 Memory mapping (creating a mapped section) a remote file under a transaction is not supported.
6835 0x1AB3 Transaction metadata is already present on this file and cannot be superseded.
6836 0x1AB4 A transaction scope could not be entered because the scope handler has not been initialized.
6837 0x1AB5 Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.
6838 0x1AB6 This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.
6839 0x1AB7 The request to thaw frozen transactions was ignored because transactions had not previously been frozen.
6840 0x1AB8 Transactions cannot be frozen because a freeze is already in progress.
6841 0x1AB9 The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.
6842 0x1ABA The savepoint operation failed because files are open on the transaction. This is not permitted.
6843 0x1ABB Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.
6844 0x1ABC The sparse operation could not be completed because a transaction is active on the file.
6845 0x1ABD The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument.
6846 0x1ABE I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.
6847 0x1ABF The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.
6848 0x1AC0 The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down.
6849 0x1AC1 The operation could not be completed due to bad clusters on disk.
6850 0x1AC2 The compression operation could not be completed because a transaction is active on the file.
6851 0x1AC3 The operation could not be completed because the volume is dirty. Please run chkdsk and try again.
6852 0x1AC4 The link tracking operation could not be completed because a transaction is active.
6853 0x1AC5 This operation cannot be performed in a transaction.
7001 0x1B59 The specified session name is invalid.
7002 0x1B5A The specified protocol driver is invalid.
7003 0x1B5B The specified protocol driver was not found in the system path.
7004 0x1B5C The specified terminal connection driver was not found in the system path.
7005 0x1B5D A registry key for event logging could not be created for this session.
7006 0x1B5E A service with the same name already exists on the system.
7007 0x1B5F A close operation is pending on the session.
7008 0x1B60 There are no free output buffers available.
7009 0x1B61 The MODEM.INF file was not found.
7010 0x1B62 The modem name was not found in MODEM.INF.
7011 0x1B63 The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.
7012 0x1B64 The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.
7013 0x1B65 Carrier detect has failed or carrier has been dropped due to disconnect.
7014 0x1B66 Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.


2533

0

0
This site uses cookies. Browsing further, you are consenting to use them. More details here. I agree