# message_table_61_0x00000409

message_identifier: 0x8000010c
message_string:
HotPlug notification was not performed for '%1' because all user-interface dialogs have been suppressed.


message_identifier: 0x8000010b
message_string:
Client side device installation was not performed for '%1' because all user-interface dialogs have been suppressed.


message_identifier: 0xb0001db1
message_string:
Error sending device event notification window message to client %1 (hWnd=%2, Session=%3, Err=%4).


message_identifier: 0x00004e2a
message_string:
One or more of the Plug and Play service's subsystems has changed state. %n%nPlugPlay install subsystem enabled: '%1' %nPlugPlay caching subsystem enabled: '%2' %n


message_identifier: 0x00004e29
message_string:
Driver Management will reboot the system in %1 seconds to enforce a Device Installation Restriction policy setting.


message_identifier: 0x00004e28
message_string:
Driver Management has not removed Device Instance ID %1 with matching policy restriction because it is a required system device.


message_identifier: 0x00004e21
message_string:
Driver Management concluded the process to install driver %1 for Device Instance ID %4 with the following status: %9.


message_identifier: 0x00004e23
message_string:
Driver Management has concluded the process to add Service %1 for Device Instance ID %3 with the following status: %6.


message_identifier: 0x00004e22
message_string:
Driver Management concluded the process to remove driver %1 from Device Instance ID %4 with the following status: %9.


message_identifier: 0x00004e25
message_string:
Driver Management has restricted the installation of Device Instance ID %1 because of a Device Installation Restriction policy setting.


message_identifier: 0x00004e24
message_string:
Driver Management has concluded the process to remove Service %1 for Device Instance ID %3 with the following status: %6.


message_identifier: 0x00004e27
message_string:
Driver Management has removed Device Instance ID %1 because of a Device Installation Restriction policy setting.


message_identifier: 0x00004e26
message_string:
Driver Management has deferred the process to install Device Instance ID %1 until a driver has been selected because of a Device Installation Restriction policy setting.


# message_table_62_0x00000409

message_identifier: 0x00000022
message_string:
Idle power management features on processor %2 in group %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000024
message_string:
Throttle power management features on processor %2 in group %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000025
message_string:
The speed of processor %2 in group %1 is being limited by system firmware. The processor has been in this reduced performance state for %3 seconds since the last report.


message_identifier: 0x00000021
message_string:
Platform based performance and throttle power management features on processor %2 in group %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000002
message_string:
Performance power management features on processor %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000003
message_string:
Throttle power management features on processor %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000001
message_string:
Idle power management features on processor %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000006
message_string:
Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000007
message_string:
The speed of processor %1 is being limited by system firmware. The processor has been in this reduced performance state for %2 seconds since the last report.


message_identifier: 0x00000004
message_string:
Processor %1 exposes the following:%n%n%2 idle state(s)%n%3 performance state(s)%n%4 throttle state(s)


message_identifier: 0x00000005
message_string:
Some processor idle power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x00000023
message_string:
Performance power management features on processor %2 in group %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x0000001a
message_string:
Processor %2 in group %1 exposes the following:%n%n%3 idle state(s)%n%4 performance state(s)%n%5 throttle state(s)


message_identifier: 0x0000001b
message_string:
Some processor power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.


message_identifier: 0x0000001d
message_string:
The platform implements processor performance and throttle state control.%n%nMinimum performance frequency percentage: %3%n%nMinimum throttled frequency percentage: %4


# message_table_63_0x00000409

message_identifier: 0x000004b2
message_string:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer


# message_table_64_0x00000409

message_identifier: 0xc0000066
message_string:
The standard TCP/IP printer port monitor (TCPMon.dll) failed to cleanup the sockets it was using. The WSACleanup function in WS2_32.DLL returned an error. This can occur if there is a serious failure of the network subsystem, the network interface, or the local network itself.


message_identifier: 0xc00001f6
message_string:
The standard TCP/IP printer port monitor (TCPMon.dll) ran out of disk space while printing. Free up disk space on the volume where the spooler folder is located.


# message_table_65_0x00000409

message_identifier: 0x80050001
message_string:
The driver has detected that this HID keyboard has bad firmware.  It is issuing redundant report packets.


# message_table_67_0x00000409

message_identifier: 0x000003ea
message_string:
The Windows Memory Diagnostic scheduled the testing of the computer's memory to run the next time the computer starts


# message_table_68_0x00000409

message_identifier: 0xc0050002
message_string:
Not enough memory was available to allocate the ring buffer that holds incoming data for the PS/2 keyboard device. 


message_identifier: 0xc0050003
message_string:
The hardware locations for %1 could not be translated to something the memory management system understands.


message_identifier: 0xc005001a
message_string:
Exceeded the allowable number of retries (configurable via the registry) for the PS/2 keyboard device.


message_identifier: 0xc005000d
message_string:
The Start I/O procedure has detected an internal error in the driver for the PS/2 keyboard device.


message_identifier: 0xc0050029
message_string:
An error occurred while enabling the mouse to transmit information.  The device has been reset in an attempt to make the device functional.


message_identifier: 0x4005000c
message_string:
The ring buffer that stores incoming mouse data has overflowed (buffer size is configurable via the PS/2 mouse properties in device manager).


message_identifier: 0x4005000b
message_string:
The ring buffer that stores incoming keyboard data has overflowed (buffer size is configurable via the registry).


message_identifier: 0xc0050035
message_string:
Exceeded the allowable number of retries (configurable via the registry) for the PS/2 pointing device. 


message_identifier: 0xc0050034
message_string:
The Initiate I/O procedure has detected an internal state error in the driver for the PS/2 pointing device.


message_identifier: 0xc0050033
message_string:
The Start I/O procedure has detected an internal error in the driver for the PS/2 pointing device.


message_identifier: 0xc0050030
message_string:
Not enough memory was available to allocate the ring buffer that holds incoming data for the PS/2 pointing device.


message_identifier: 0x4005001f
message_string:
No PS/2 compatible mouse device was detected on the PS/2 mouse port (not a problem unless this type of mouse really is connected).


message_identifier: 0xc005000e
message_string:
The Initiate I/O procedure has detected an internal state error in the driver for the PS/2 keyboard device.


# message_table_69_0x00000409

message_identifier: 0xc0060024
message_string:
While validating that %2 was really a serial port, the contents of the divisor latch register was identical to the interrupt enable and the receive registers.
The device is assumed not to be a serial port and will be deleted.


message_identifier: 0xc0060007
message_string:
Another driver on the system, which did not report its resources, has already claimed the interrupt used by %2.


message_identifier: 0xc006000e
message_string:
While validating that %2 was really a serial port, the modem control register contained enabled bits in a must be zero bitfield.
The device is assumed not to be a serial port and will be deleted.


message_identifier: 0xc006000d
message_string:
While validating that %2 was really a serial port, the interrupt enable register contained enabled bits in a must be zero bitfield.
The device is assumed not to be a serial port and will be deleted.


message_identifier: 0xc006000f
message_string:
While validating that %2 was really a serial port, the interrupt id register contained enabled bits in a must be zero bitfield.
The device is assumed not to be a serial port and will be deleted.


message_identifier: 0xc006000a
message_string:
The hardware locations for %2 could not be translated to something the memory management system could understand.


message_identifier: 0xc0060014
message_string:
On parameter %2 which indicates a multiport card, must have a port index specified greater than 0.


message_identifier: 0xc0060015
message_string:
On parameter %2 which indicates a multiport card, the port index for the multiport card is too large.


message_identifier: 0xc0060012
message_string:
No Parameters subkey was found for user defined data.  This is odd, and it also means no user configuration can be found.


message_identifier: 0xc0060010
message_string:
While validating that %2 was really a serial port, the baud rate register could not be set consistantly.
The device is assumed not to be a serial port and will be deleted.


# message_table_70_0x00000409

message_identifier: 0xc0050010
message_string:
%2: Fan Failure on Network Controller %3 has caused the driver to shutdown the card to prevent permanent damage. Please contact Dell Support for assistance.


# message_table_72_0x00000409

message_identifier: 0xc0007233
message_string:
The attempt to Install the Active Directory Domain Services failed.  The Domain that was specified (%1) was different than the one the backup was taken from (%2).


message_identifier: 0xc0007235
message_string:
Failed to identify the requested replica partner (%1) as a valid domain controller with a machine account for (%2). This is likely due to either the machine account not being replicated to this domain controller because of replication latency or the domain controller not advertising the Active Directory Domain Services.  Please consider retrying the operation with %3 as the replica partner.


message_identifier: 0xc0007234
message_string:
The attempt to install the Active Directory Domain Services failed. The sysvol cannot be placed at the root directory. Retry the promotion with a different sysvol path.


message_identifier: 0xc0007205
message_string:
A domain controller could not be contacted for the domain %1 that contained an account for this computer. Make the computer a member of a workgroup then rejoin the domain before retrying the promotion.


message_identifier: 0x00009009
message_string:
No supported cipher suites were found when initiating an SSL connection. This indicates a configuration problem with the client application and/or the installed cryptographic modules. The SSL connection request has failed.


message_identifier: 0x0000a009
message_string:
The Security System has received an authentication attempt, and determined that the protocol %1 is the common protocol.


message_identifier: 0x00009008
message_string:
The SSL %1 specified certificate's chain could not be retrieved:%n%n   Failure Status: %2%n   Flags: %3%n%n The attached data contains the certificate.


message_identifier: 0x0000a008
message_string:
The Security System has received an authentication request that could not be decoded. The request has failed.


message_identifier: 0x0000a001
message_string:
The Security System could not establish a secured connection with the server %1. No authentication protocol was available.


message_identifier: 0x0000a000
message_string:
The Security System detected an authentication error for the server %1. The failure code from authentication protocol %2 was %3.


message_identifier: 0x0000a002
message_string:
The Security System was unable to authenticate to the server %1 because the server has completed the authentication, but the client authentication protocol %2 has not.


message_identifier: 0x0000a004
message_string:
The Security System received an authentication attempt with an unknown authentication protocol. The request has failed.


message_identifier: 0x0000a007
message_string:
The Security System has received an authentication request directly for authentication protocol %1.


message_identifier: 0x0000a006
message_string:
The Security System has received an authentication attempt, and determined that the protocol %1 preferred by the client is acceptable.


message_identifier: 0x0000800a
message_string:
The name %1 was translated to SID %2 from the trusted forest %3. The domain portion of the SID is not in the list of acceptable SID's found on the trusted domain object, thus this name to SID translation has been ignored.


message_identifier: 0x00009015
message_string:
When asking for client authentication, this server sends a list of trusted certificate authorities to the client. The client uses this list to choose a client certificate that is trusted by the server. Currently, this server trusts so many certificate authorities that the list has grown too long. This list has thus been truncated. The administrator of this machine should review the certificate authorities trusted for client authentication and remove those that do not really need to be trusted.


message_identifier: 0x00007204
message_string:
An existing, incompatible trust object was found on the parent server for domain %1.  It has been removed and replaced with an updated trust.


message_identifier: 0x00007203
message_string:
Running the Security Configuration Editor over the Domain Controller encountered a non-fatal error.  Further details can be obtained by examining the log file %1.  The return code is the data.


message_identifier: 0x40007230
message_string:
The path chosen for the system volume is not accessible. Please either manually delete the contents of the path or choose another location for the system volume.


message_identifier: 0x00008000
message_string:
The interdomain trust account for the domain %1 could not be deleted. The return code is the data.


message_identifier: 0x00008004
message_string:
The interdomain trust account for the domain %1 could not be created. The return code is the data.


message_identifier: 0x00008005
message_string:
A lookup request was made that required connectivity to a domain controller in domain %1. The LSA was unable to find a domain controller in the domain and thus failed the request. Please check connectivity and secure channel setup from this domain controller to the domain %2.


message_identifier: 0x00008008
message_string:
A lookup request was made that required a Global Catalog. The LSA was unable to either contact or authenticate to a Global Catalog and thus failed the lookup request. Please check the connectivity and authentication of this domain controller to a Global Catalog.


message_identifier: 0x00008009
message_string:
The LSA was unable to register its RPC interface over the TCP/IP interface. Please make sure that the protocol is properly installed.


message_identifier: 0x00009004
message_string:
The SSL %1 credential's private key has the following properties:%n%n   CSP name: %2%n   CSP type: %3%n   Key name: %4%n   Key Type: %5%n   Key Flags: %6%n%n The attached data contains the certificate.


message_identifier: 0x0000b000
message_string:
Logon cache was disabled. Intermittent authentication failures may result during periods of network latency or interrupts. Please contact your system administrator.


message_identifier: 0x0000b001
message_string:
A failed logon attempt has caused a logon cache entry for user %1 to be deleted. The authentication package was %2, and the error message was %3.


message_identifier: 0x0000b002
message_string:
A logon cache entry for user %1 was the oldest entry and was removed. The timestamp of this entry was %2.


message_identifier: 0x00008006
message_string:
A lookup request was made that required connectivity to the domain controller %1. The local LSA was unable to contact the LSA on the remote domain controller. Please check connectivity and secure channel setup from this domain controller to the domain controller %2.


message_identifier: 0x00008007
message_string:
A lookup request was made that required the lookup services on the remote domain controller %1. The remote domain controller failed the request thus the local LSA failed the original lookup request. Please check connectivity and secure channel setup from this domain controller to the domain controller %2.


message_identifier: 0x00007220
message_string:
Failed to disable auto logon following the successful upgrade of a domain controller.  Unable to delete registry key %1.  The return code is the data.


message_identifier: 0x00009012
message_string:
The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate.


message_identifier: 0x00009013
message_string:
The certificate received from the remote server has been revoked. This means that the certificate authority that issued the certificate has invalidated it. The SSL connection request has failed. The attached data contains the server certificate.


message_identifier: 0x00009010
message_string:
An SSL %1 handshake completed successfully. The negotiated cryptographic parameters are as follows.%n%n   Protocol: %2%n   CipherSuite: %3%n   Exchange strength: %4


message_identifier: 0x00009011
message_string:
The certificate received from the remote server has either expired or is not yet valid. The SSL connection request has failed. The attached data contains the server certificate.


message_identifier: 0x00009016
message_string:
No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.


message_identifier: 0x80007243
message_string:
The specified helper DC %1 is a Read Only DC. The helper DC should be a writable DC. Bailing out of DC promotion.


message_identifier: 0x00009001
message_string:
A fatal error occurred while opening the system %1 cryptographic module. Operations that require the SSL or TLS cryptographic protocols will not work correctly. The error code is %2.


message_identifier: 0x00009005
message_string:
The SSL %1 credential's certificate does not have a private key information property attached to it. This most often occurs when a certificate is backed up incorrectly and then later restored. This message can also indicate a certificate enrollment failure.


message_identifier: 0x00009006
message_string:
A fatal error occurred when attempting to access the SSL %1 credential private key. The error code returned from the cryptographic module is %2. The internal error state is %3.


message_identifier: 0x00001795
message_string:
The program %2, with the assigned process ID %1, could not authenticate locally by using the target name %3. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name.%n %n Try a different target name.


message_identifier: 0x00001794
message_string:
The program %2, with the assigned Process ID %1, supplied a NULL or empty target name for the pszTargetName parameter when calling the InitializeSecurityContext API to initiate an outbound NTLM security context. This is a security risk when mutual authentication is required.%n %n To help protect against a malicious attack, make your code more secure. To do this, change the program so that it specifies a target name in the pszTargetName parameter field, and then recompile the code.


message_identifier: 0x00001791
message_string:
An anonymous session connected from %1 has attempted to open an LSA policy handle on this machine. The attempt was rejected with STATUS_ACCESS_DENIED to prevent leaking security sensitive information to the anonymous caller.%n The application that made this attempt needs to be fixed. Please contact the application vendor. As a temporary workaround, this security measure can be disabled by setting the \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\TurnOffAnonymousBlock DWORD value to 1.%n This message will be logged at most once a day.


message_identifier: 0x00001793
message_string:
During a logon attempt, the user's security context accumulated too many security IDs. This is a very unusual situation. Remove the user from some global or local groups to reduce the number of security IDs to incorporate into the security context.%nUser's SID is %1%nIf this is the Administrator account, logging on in safe mode will enable Administrator to log on by automatically restricting group memberships.


message_identifier: 0x00001792
message_string:
The new top level name, %1, has been added to the forest %2. Name suffix routing for this new name is disabled because it is not within any currently routed namespace. Objects can not be resolved from this new namespace until name suffix routing is enabled for the namespace. To enable name suffix routing, open Domains and Trusts and see help under Name Suffix Routing and Forest Trusts.


message_identifier: 0x00009014
message_string:
The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is %1. The SSL connection request has failed. The attached data contains the server certificate.


message_identifier: 0x00009019
message_string:
The SSL %1 specified certificate's chain is incomplete:%n%n   Failure Status: %2%n%n This can cause trust validation failures or interoperability problems. For more information see KB 954755%n The attached data contains the certificate.


message_identifier: 0x0000900a
message_string:
An %1 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.


message_identifier: 0x0000900c
message_string:
The certificate received from the remote server has not validated correctly. The error code is %1. The SSL connection request has failed. The attached data contains the server certificate.


message_identifier: 0x0000900b
message_string:
The remote server has requested SSL client authentication, but no suitable client certificate could be found. An anonymous connection will be attempted. This SSL connection request may succeed or fail, depending on the server's policy settings.


message_identifier: 0x0000900e
message_string:
The certificate received from the remote client application is not suitable for direct mapping to a client system account, possibly because the authority that issuing the certificate is not sufficiently trusted. The error code is %1. The attached data contains the client certificate.


message_identifier: 0x0000900d
message_string:
The certificate received from the remote client application has not validated correctly. The error code is %1. The attached data contains the client certificate.


message_identifier: 0x0000900f
message_string:
The certificate received from the remote client application was not successfully mapped to a client system account. The error code is %1. This is not necessarily a fatal error, as the server application may still find the certificate acceptable.


# message_table_73_0x00000409

message_identifier: 0xc200000e
message_string:
Failed to retrieve the flags related to pagefile, hibernation file and crash dump, for disk number %1. Error code: %2


# message_table_74_0x00000409

message_identifier: 0xb0000004
message_string:
The Subscription %1 could not be activated on target machine %2 due to communication error.  Error Code is %3.  The subscription will be in retrying state until the subscription becomes active or all retries have been performed. Additional fault message:%4


message_identifier: 0xb0000006
message_string:
The Subscription %1 could not publisher events from target machine %2 to the log file of this subscription.  Error Code is %3.  All retries have been performed before reaching this point and so the subscription will remain inactive on this target until subscription is resubmitted / reset.


message_identifier: 0xb0000001
message_string:
The Subscription %1 could not be activated on target machine %2 due to communication error.  Error Code is %3.  All retries have been performed before reaching this point and so the subscription will remain inactive on this target until subscription is resubmitted / reset. Additional fault message:%4


message_identifier: 0xb0000002
message_string:
The Subscription %1 could not be activated on machine %2 due to an error. Error Code is %3. Subscription will remain inactive on this target until subscription is resubmitted / reset.


message_identifier: 0xb00001f6
message_string:
The Subscription %1 detects dropped events. Some events are dropped during transmission from target machine %2. The number of dropped events are %3.


message_identifier: 0xb00001f5
message_string:
The Subscription %1 has a lost event. An event from target machine %2 is lost and could not be delivered. Error Code is %3. Event data is:%4


# message_table_75_0x00000409

message_identifier: 0x00000448
message_string:
The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object %8. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure.


message_identifier: 0x00000449
message_string:
The processing of Group Policy failed. Windows could not determine the computer account to enforce Group Policy settings. This may be transient. Group Policy settings, including computer configuration, will not be enforced for this computer.


message_identifier: 0x00000442
message_string:
Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. This could be caused by Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately.


message_identifier: 0x00000443
message_string:
Windows could not record  the Resultant Set of Policy (RSoP) information for the Group Policy extension <%8>. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately.


message_identifier: 0x00000440
message_string:
The processing of Group Policy failed. Windows attempted to query the list of Group Policy objects and exceeded the maximum limit (999).


message_identifier: 0x00000441
message_string:
Windows failed to record Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. This could be caused by RSOP being disabled or Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately.


message_identifier: 0x00000447
message_string:
Windows encountered an error while recording Resultant Set of Policy (RSoP) information, which describes the scope of Group Policy objects applied to the computer or user. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately.


message_identifier: 0x00000458
message_string:
The Group Policy Client Side Extension %8 was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.


message_identifier: 0x00001027
message_string:
Failed to determine the Group Policy properties of the installed system. Group Policy will wait for the network at startup and logon for a maximum of 120 seconds.


message_identifier: 0x00001026
message_string:
Failed to determine the Group Policy properties of the installed system. Group Policy will wait for the network at startup and logon.


message_identifier: 0x00001025
message_string:
Failed to determine the Group Policy properties of the installed system. Only a subset of Group Policy functionality will be available.


message_identifier: 0x00000450
message_string:
Windows was unable to read the Windows Management Instrumentation (WMI) filter information associated with the Group Policy object %8.This may be caused by a deleted WMI Filter defined in the domain that is still in use by Group Policy objects. Group Policy settings for this Group Policy object will not be enforced. Other Group Policy objects may still apply. Windows will attempt to retrieve this information at the next policy cycle. This speciffic problem may be resolved by identifying all GPOs that reference the WMI filter and removing the references. Contact an administrator if this event recurs for several hours.


message_identifier: 0x00000455
message_string:
The user account is in a different forest than the computer account. The processing of Group Policy from another forest is not allowed. Group Policy will be processed using Loopback Replace mode. The scope of the user policy settings will be determined by the location of the computer object in Active Directory. The settings will be aquired from the User Configuration of these policies.


message_identifier: 0x00000456
message_string:
The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account.


message_identifier: 0x0000044d
message_string:
The processing of Group Policy failed. Windows could not locate the directory object %8. Group Policy settings will not be enforced until this event is resolved. View the event details for more information on this error.


message_identifier: 0x00000468
message_string:
The Group Policy Client Side Extension %3 may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue recurs.


message_identifier: 0x00000469
message_string:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has succesfully processed. If you do not see a success message for several hours, then contact your administrator.


message_identifier: 0x00000465
message_string:
The processing of Group Policy failed because of an internal system error. Please see the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle.


message_identifier: 0x00000466
message_string:
Windows was unable to determine whether new Group Policy settings defined by a network administrator should be enforced for this user or computer because this computer's clock is not synchronized with the clock of one of the domain controllers for the domain. Because of this issue, this computer system may not be in compliance with the network administrator’s requirements, and users of this system may not be able to use some functionality on the network. Windows will periodically attempt to retry this operation, and it is possible that either this system or the domain controller will correct the time settings without intervention by an administrator, so the problem will be corrected. %n%nIf this issue persists for more than an hour, checking the local system's clock settings to ensure they are accurate and are synchronized with the clocks on the network's domain controllers is one way to resolve this problem. A network administrator may be required to resolve the issue if correcting the local time settings does not address the problem.


message_identifier: 0x00000467
message_string:
The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle.


message_identifier: 0xb00014d3
message_string:
Service configuration update to standalone was attempted due to the presence of Group Policy client extension %1 that is not part of the operating system and completed with status %3.


message_identifier: 0x000005dc
message_string:
The Group Policy settings for the computer were processed successfully. There were no changes detected since the last successful processing of Group Policy.


message_identifier: 0x000005df
message_string:
The Group Policy settings for the user were processed successfully. New settings from %6 Group Policy objects were detected and applied.


message_identifier: 0x000005de
message_string:
The Group Policy settings for the computer were processed successfully. New settings from %6 Group Policy objects were detected and applied.


message_identifier: 0x000005dd
message_string:
The Group Policy settings for the user were processed successfully. There were no changes detected since the last successful processing of Group Policy.


message_identifier: 0x00001042
message_string:
Service configuration must be updated to standalone due to the presence of a Group Policy client extension that is not part of the operating system.


message_identifier: 0x000003ef
message_string:
The processing of Group Policy failed. Windows could not determine the site associated for this computer, which is required for Group Policy processing.


message_identifier: 0x000003ee
message_string:
The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description.


message_identifier: 0xb00018aa
message_string:
Group policy bandwidth estimation failed. Group policy processing will continue. Assuming %6 link.


message_identifier: 0x000003ea
message_string:
The processing of Group Policy failed because of a system allocation failure. Please ensure the computer is not running low on resources (memory, available disk space). Group Policy processing will be attempted at the next refresh cycle.


message_identifier: 0xb00018b3
message_string:
Group Policy dependency (%1) did not start. As a result, network related features of Group Policy such as bandwidth estimation and response to network changes will not work.


message_identifier: 0x00000406
message_string:
The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.


message_identifier: 0x0000041e
message_string:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.


message_identifier: 0x0000041d
message_string:
The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following: %na) Name Resolution failure on the current domain controller. %nb) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).


message_identifier: 0x0000041f
message_string:
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: %na) Name Resolution failure on the current domain controller. %nb) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).


message_identifier: 0x0000041c
message_string:
The processing of Group Policy failed. Windows could not determine the role of this computer. Role information (Workgroup, Member Server, or Domain Controller) is required to process Group Policy.


message_identifier: 0xb00018ba
message_string:
An unfinished invocation of the Group Policy Client Side Extension %1 from a previous instance of the Group Policy Service has been detected.  This may indicate that the extension caused the Group Policy Client Service to terminate unexpectedly.


message_identifier: 0xb00014be
message_string:
Account details: %n%tAccount Name : %1%n%tAccount Domain Name : %2%n%tDC Name : %3%n%tDC Domain Name : %4


message_identifier: 0x0000043d
message_string:
Windows failed to apply the %8 settings. %8 settings might have its own log file. Please click on the "More information" link.


message_identifier: 0x00000429
message_string:
The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for the Group Policy object %8. This could be caused by RSOP being disabled  or Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Make sure the WMI service is started and the startup type is set to automatic. New Group Policy objects or settings will not process until this event has been resolved.


message_identifier: 0x00000422
message_string:
The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: %na) Name Resolution/Network Connectivity to the current domain controller. %nb) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). %nc) The Distributed File System (DFS) client has been disabled.


message_identifier: 0x0000100a
message_string:
Startup scripts are not visible. Startup scripts are visible only when startup scripts are configured to run synchronously.


message_identifier: 0x0000042c
message_string:
The processing of Group Policy was interrupted. Windows prematurely ended the discovery and enforcement of Group Policy settings because the computer was requested to shutdown or the user logged off. Group Policy processing will be attempted next refresh cycle, on the next computer reboot, or the next user logon.


message_identifier: 0x00000438
message_string:
The processing of Group Policy failed. Windows could not search the Active Directory organization unit hierarchy. View the event details for more information.


message_identifier: 0x00000437
message_string:
The processing of Group Policy failed. Windows could not obtain the list of Group Policy objects applicable for this computer or user. View the event details for more information.


message_identifier: 0x00001008
message_string:
Group Policy cannot be applied because the computer has been booted in Directory Services Restore Mode.


message_identifier: 0x00001007
message_string:
Group Policy wait for network subsystem failed at computer boot. Group Policy processing will continue.


# message_table_77_0x00000409

message_identifier: 0x0000276f
message_string:
The unattend answer file contains an invalid product key. Either remove the invalid key or provide a valid product key in the unattend answer file to proceed with Windows installation.%0


message_identifier: 0x00002779
message_string:
Unattended upgrades using setup /unattend with no answer file are not supported when running Windows PE.%0


message_identifier: 0x00002772
message_string:
Windows cannot locate the disk and partition specified in the unattend answer file's %1!s! setting. Make sure the setting references a valid partition and restart the installation.%0


message_identifier: 0x00002836
message_string:
Windows could not collect information for [%1!s!] since the specified image file [%2!s!] does not exist.%0


message_identifier: 0x000027c9
message_string:
Windows cannot resolve the metadata provided in the unattend answer file's <ImageInstall> setting.%0


message_identifier: 0x00002848
message_string:
Windows is unable to read the installation media's configuration file. Installation cannot proceed.


message_identifier: 0x00004e23
message_string:
The selected disk is read only. To install to this disk use the Disk management tool to make the disk writable.%0


message_identifier: 0x00002764
message_string:
Windows could not register Component Based Servicing (CBS) binaries. Error code: 0x%1!X!. Exit code: 0x%2!X!.%0


message_identifier: 0x00002762
message_string:
The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks.%0


message_identifier: 0x000027cb
message_string:
Multiple Windows images were selected based on the provided information. Windows Setup cannot determine which one to use.%0


message_identifier: 0x00002841
message_string:
BitLocker Drive Encryption is enabled on the selected partition. Suspend (also referred to as disable) BitLocker in the Control Panel, and then restart the installation.%0


message_identifier: 0x00002842
message_string:
This version of Windows cannot be installed to a partition encrypted by BitLocker Drive Encryption. To install to this partition, turn off (decrypt) BitLocker Drive Encryption, and then restart the installation.%0


message_identifier: 0x00002843
message_string:
This 32-bit version of Windows cannot be installed to an EFI-based computer. Installation cannot proceed. Use a 64-bit version of Windows to install to an EFI-based computer.%0


message_identifier: 0x0000283c
message_string:
iSCSI deployment is disabled since no NICs referenced in the iBFT can be resolved to actual NT-visible devices.%0


message_identifier: 0x0000284a
message_string:
Setup cannot continue due to a corrupted installation file. Contact the vendor of your Windows installation disc or your system administrator for assistance.


message_identifier: 0x000027e5
message_string:
Windows could not prepare the computer to boot into the next phase of installation. To install Windows, restart the installation.%0


message_identifier: 0x0000282b
message_string:
You are attempting to install Windows while there are others users logged onto this computer. Those users may lose any unsaved data they are working on. Make sure there are no other users logged onto this computer during installation.%0


message_identifier: 0x0000282f
message_string:
To use the product key you entered, start the installation on a computer that is running a genuine version of Windows.%0


message_identifier: 0x0000282d
message_string:
Windows cannot be installed on this computer with the current system BIOS version. Contact your computer manufacturer for a BIOS update, install the update, and then start Windows installation again.
OEM Name: %1!s!;
OEM Model: %2!s!;
BIOS Version: %3!s!;
BIOS Date: %4!s!%0


message_identifier: 0x000027a6
message_string:
Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.%0


message_identifier: 0x000027a2
message_string:
One or more compliance checks failed. In accordance with the settings in the unattend answer file, installation cannot proceed.%0


message_identifier: 0x0000275f
message_string:
This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu.%0


message_identifier: 0x00002749
message_string:
cmd.exe,"/k echo This environment should only be used to recover from a failed installation.    Type EXIT and press Enter to resume installation."%0


message_identifier: 0x000027ad
message_string:
The specified drive [%1!c!:] does not meet all requirements necessary to store temporary installation files.%0


message_identifier: 0x00002832
message_string:
The partitions on the disk selected for installation are not in the recommended order. For additional information about installing to GPT disks go to the Microsoft website (www.microsoft.com) and search for GPT.

Do you want to proceed with installation?%0


message_identifier: 0x00002828
message_string:
Windows cannot be installed to the selected partition. Installation requires at least %1!u! MB of free space. To install Windows, free additional space and restart the installation.%0


message_identifier: 0x00002829
message_string:
Windows could not process the command-line argument [/tempdrive]. The required drive path was not found or is invalid.%0


message_identifier: 0x00002824
message_string:
Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information.%0


message_identifier: 0x00002782
message_string:
The product key entered does not match any of the Windows images available for installation. Enter a different product key.%0


message_identifier: 0x00004e28
message_string:
Windows was unable to validate the partition selected for installation. Installation cannot proceed.%0


message_identifier: 0x0000283b
message_string:
Configuration of or installation to disks connected through iSCSI is only supported when Windows installation is started from Windows PE.%0


message_identifier: 0x00002730
message_string:
Windows Setup could not initialize the deployment engine. To install Windows, restart the installation.%0


message_identifier: 0x00002736
message_string:
Windows Setup encountered an internal error while loading or searching for an unattend answer file.%0


message_identifier: 0x00002839
message_string:
Windows cannot find a Microsoft Reserved partition on the disk selected for installation (disk %1!d!). There is enough space on the installation disk to create one.

Click 'OK' to create this Microsoft Reserved partition and to continue installing Windows.
Click 'Cancel' to return to the previous screen.%0


message_identifier: 0x0000272c
message_string:
Windows detected that this computer has %1!d! MB of RAM, but %2!d! MB is required for installation. Installation cannot proceed.%0


message_identifier: 0x00002833
message_string:
Windows could not process the command-line argument [/installfrom]. The required path is invalid.%0


message_identifier: 0x00002831
message_string:
Windows detected that the EFI system partition was formatted as %1!s!. Format the EFI system partition as FAT32, and restart the installation.%0


message_identifier: 0x00002830
message_string:
Windows cannot find a Microsoft Reserved partition on the disk selected for installation (disk %1!d!). Although recommended, this partition is not required to complete installation.

Do you want to proceed with installation?%0


message_identifier: 0x00002721
message_string:
The specified drive [%1!c!:] cannot be found. Windows requires a valid drive to store temporary installation files. To install Windows, select another drive and restart the installation.%0


message_identifier: 0x00002720
message_string:
The specified drive [%1!c!:] cannot be used to store temporary installation files. To install Windows, select another drive and restart the installation.%0


message_identifier: 0x00002722
message_string:
Windows Setup cannot locate a valid hard drive to store temporary installation files. To install Windows, create more free space on the hard drive or add a new hard drive.%0


message_identifier: 0x00002727
message_string:
Windows could not determine the installation type. To install Windows, restart the installation.%0


message_identifier: 0x00002726
message_string:
Windows Setup cannot load. An internal error occurred. To install Windows, restart the installation.%0


message_identifier: 0x00002729
message_string:
The version of Windows PE running on this computer is not compatible with Setup. To install Windows from Windows PE, use Server 2003 SP1 Windows PE or later.%0


message_identifier: 0x00004e21
message_string:
The selected disk is offline. To install to this disk use the Disk management tool to bring the disk online.%0


message_identifier: 0x00004e22
message_string:
The selected volume is offline. To install to this volume use the Disk management tool to bring the volume online.%0


message_identifier: 0x000027e3
message_string:
Setup does not support configuration of or installation to disks connected through a USB or IEEE 1394 port.%0


message_identifier: 0x000027e4
message_string:
The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation.%0


message_identifier: 0x000027e8
message_string:
Windows could not copy files from [%1!s!] to [%2!s!]. Make sure [%1!s!] is available, and then restart the installation.%0


message_identifier: 0x00002718
message_string:
Windows Setup could not reinitialize the deployment engine. To install Windows, restart the installation.%0


message_identifier: 0x00002813
message_string:
Windows cannot be installed on a computer using battery power. If the battery runs out of power during the installation, you might lose data. To continue the installation, plug in the computer's power adapter.%0


message_identifier: 0x000027de
message_string:
Windows needs the driver for device [%1!s!]. Click 'Load Driver' and load the required device driver.%0


message_identifier: 0x000027dd
message_string:
Turn off Serial Keys. If you are upgrading from Windows XP and currently using Serial Keys with alternative input devices, such as single switch or puff and sip devices, turn off Serial Keys and install another solution before upgrading. To turn off Serial Keys, open 'Accessibility Options'. On the 'General' tab, under Serial Key devices, clear the 'Use Serial Keys' check box. See the Microsoft Ease of Access website for where to install solutions so you can keep using your devices with this version of Windows.%0


message_identifier: 0x00004e2a
message_string:
This hard disk space is formatted with an unsupported version of the NTFS file system. Please back up any data you have on this partition. Then, restart the computer using the Windows installation disc, perform a custom installation and reformat the hard disk partition.%0


message_identifier: 0x00002790
message_string:
To ensure that all Windows features work correctly, Windows might create additional partitions for system files.%0


message_identifier: 0x00002791
message_string:
Setup cannot copy the operating system's loader files to the computer's system volume. Make sure the directories Boot\ and EFI\ and the files bootmgr and bootmgr.efi are available on the installation media, and then restart the installation.%0


message_identifier: 0x00002786
message_string:
The system registry contains invalid file paths. Installation cannot proceed. This system image was applied without guaranteeing that drive-letter assignments would match across computers.%0


message_identifier: 0x000027e0
message_string:
Windows could not determine if this disk and its parent devices have the necessary driver support.%0


message_identifier: 0x0000278b
message_string:
The version of Windows being installed does not support this computer's processor. Installation cannot proceed.%0


message_identifier: 0x00002847
message_string:
Windows is unable to surface or mount the deployed image. Installation cannot proceed. To retry installing this image, reboot the system and restart the installation.


message_identifier: 0x00002788
message_string:
The partition selected for installation (%3!u!) does not exist on disk %2!u!. Make sure the unattend answer file's %1!s! setting references a valid partition on this computer, and then restart the installation.%0


message_identifier: 0x0000279d
message_string:
This computer is not compliant with the Advanced Configuration and Power Interface (ACPI) standard. Windows must be installed onto a computer that supports ACPI. Contact your computer manufacturer for a BIOS update or install Windows on an ACPI-compliant computer.%0


message_identifier: 0x00004e24
message_string:
The selected volume is read only. To install to this volume use the Disk management tool to make the volume writable.%0


message_identifier: 0x0000271d
message_string:
The specified drive [%1!c!:] cannot be used to store temporary installation files because all partitions were selected to be deleted. To install Windows, select another drive and restart the installation.%0


message_identifier: 0x0000271e
message_string:
The specified drive [%1!c!:] cannot be used to store temporary installation files because the partition was selected to be formatted. To install Windows, select another drive and restart the installation.%0


message_identifier: 0x0000271f
message_string:
The specified drive [%1!c!:] does not have enough free disk space to store temporary installation files. To install Windows, select another drive and restart the installation.%0


message_identifier: 0x00002787
message_string:
The disk selected for installation (%2!u!) does not exist. Make sure the unattend answer file's %1!s! setting references a valid disk on this computer, and then restart the installation.%0


message_identifier: 0x0000271b
message_string:
The installation cannot continue because Windows cannot restart the computer. Close any open programs, and then restart the computer. Windows installation will continue automatically.%0


message_identifier: 0x0000271c
message_string:
The specified drive [%1!c!:] is not a fixed disk. Windows requires a local, non-removable disk to store temporary installation files. To install Windows, select another drive and restart the installation.%0


message_identifier: 0x00002789
message_string:
The partition selected for installation (disk %1!u! partition %2!u!) does not meet requirements. Make sure this partition contains enough free space and is of a supported type.%0


# message_table_78_0x00000409

message_identifier: 0xc0000416
message_string:
HKLM\SYSTEM\CurrentControlSet\Control\SessionManager\SubSystems\Windows registry contains a substring SharedSection=.
The values for this SharedSection are too big. The Default values are SharedSection=1024,3072,512
Please change the registry values for Windows to load up properly. 


# message_table_80_0x00000409

message_identifier: 0xb0000005
message_string:
The servicing request received for package %1 cannot be satisfied since the package is not applicable.


message_identifier: 0x80001118
message_string:
Servicing has required reboot to complete the operation of setting package %1(%2) into %3(%4) state


message_identifier: 0x80001137
message_string:
Windows Servicing disabled hotpatching for package %1(%2) because required files or custom actions are incompatible with hotpatching.


message_identifier: 0x80001136
message_string:
Windows Servicing disabled hotpatching for package %1(%2) because a file could not be replaced immediately.


message_identifier: 0x40001140
message_string:
Windows Servicing disabled hotpatching for package %2(%3) because update %1 is being set to state %4(%5).


message_identifier: 0x80001138
message_string:
Windows Servicing failed to perform hotpatching for package %1(%2) because the hotpatch installer required a reboot.


message_identifier: 0x4000111f
message_string:
Windows Servicing completed the process of changing update %1 from package %2 (%3) into %4(%5) state


message_identifier: 0x80001122
message_string:
Windows Servicing required reboot to complete the process of changing update %1 from package %2(%3) into %4(%5) state


message_identifier: 0x80001141
message_string:
Windows Servicing disabled hotpatching for package %2(%3) because hotpatch update %1 will not be installed.


message_identifier: 0xc0001121
message_string:
Windows Servicing failed to complete the process of changing update %1 from package %2(%3) into %4(%5) state


message_identifier: 0x40001131
message_string:
Windows Servicing disabled hotpatching for package %2(%3) because update %1 is not enabled for hotpatching.


message_identifier: 0x40001133
message_string:
Windows Servicing disabled hotpatching for package %1(%2) because a reboot is required to complete a prior operation.


message_identifier: 0x40001132
message_string:
Windows Servicing disabled hotpatching for package %1(%2) because servicing is being performed offline.


message_identifier: 0x40001135
message_string:
Windows Servicing has required a reboot to complete the installation of hotpatching package %1(%2).


# message_table_81_0x00000409

message_identifier: 0x80050002
message_string:
The driver has detected that this HID mouse has bad firmware.  It is reporting absolute axes where relative axes are expected.


message_identifier: 0x80050001
message_string:
The driver has detected that this HID mouse has bad firmware.  It is reporting a bad physical minimum/maximum for one or more axes.


# message_table_82_0x00000409

message_identifier: 0x00000201
message_string:
TPM Owner Authorization information was backed up successfully to Active Directory Domain Services.


message_identifier: 0x00000202
message_string:
Failed to backup TPM Owner Authorization information to Active Directory Domain Services.%nErrorcode: %1


# message_table_83_0x00000409

message_identifier: 0xb0000005
message_string:
The Offline Files service received a STOP or SHUTDOWN control from the Service Control Manager.  The service will now stop.


message_identifier: 0xb1000bbb
message_string:
SMB BranchCache prefetch ended for file %n%1 (content handle %2) with an expected result of %3. %n%4


message_identifier: 0xb1000bbd
message_string:
A summary of the Client Side Caching counters has been generated. The counter list can be found in the event details.


message_identifier: 0xb1000bbc
message_string:
SMB BranchCache prefetch ended for file %n%1 (content handle %2) with an unexpected result of %3. %n%4


message_identifier: 0xb00007d4
message_string:
Sync info for %1%nServer copy exists, client copy replaced then deleted.%n%10\%nSee details for more information.


message_identifier: 0xb00007d3
message_string:
Sync info for %1%nServer copy exists, client copy deleted.%n%13%nSee details for more information.


message_identifier: 0xb00007db
message_string:
Rename of file %1 to file %2 was blocked. The source and/or target file name is an excluded file type.


# message_table_84_0x00000409

message_identifier: 0x00000015
message_string:
The event logging service encountered a configuration-related error (res=%1) for channel %2. The error was encountered while processing the %3 configuration property.


message_identifier: 0x00000014
message_string:
The event logging service encountered an error %1 while obtaining or processing configuration for channel %2.


message_identifier: 0x00000017
message_string:
The event logging service encountered an error (res=%1) while initializing logging resources for channel %2.


message_identifier: 0x00000016
message_string:
The event logging service encountered an error while initializing publishing resources for channel %2. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.


message_identifier: 0x00000019
message_string:
The event logging service encountered a corrupt log file for channel %1. The log was renamed with a .corrupt extension.


message_identifier: 0xb000006b
message_string:
The event logging service encountered an error %1 while going through publisher configuration. The publisher %2 is already installed with GUID %3.


message_identifier: 0xd0000001
message_string:
Events were lost because there were no free buffers. Flushing to disk could not catch up with incoming events.


message_identifier: 0x00000453
message_string:
The event logging service encountered an error while processing an incoming event from publisher %3 and trying to process the metadata for it.


message_identifier: 0x00000028
message_string:
The event logging service encountered an error when attempting to apply one or more policy settings.


message_identifier: 0x00000454
message_string:
The event logging service encountered an error while processing an incoming event published from %3.


message_identifier: 0x0000001a
message_string:
The event logging service encountered a log file for channel %1 which is an unsupported version. The log was renamed with a .UnsupportedVer extension.


message_identifier: 0x0000001c
message_string:
The event logging service encountered an error (res=%1) while parsing filter for channel %2. Will continue without filter.


message_identifier: 0x0000001b
message_string:
The event logging service encountered an error (res=%1) while opening log file for channel %2. Trying again using default log file path %3.


message_identifier: 0x0000001e
message_string:
The event logging service encountered an error (%1) while enabling publisher %3 to channel %2. This does not affect channel operation, but does affect the ability of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security and has not granted enable permissions to the Event Log service identity.


message_identifier: 0x0000001d
message_string:
The event logging service encountered a fatal error (res=%1) when applying settings to the %2 channel. The service is shutting down since this channel is vital to its operation.


message_identifier: 0x0000001f
message_string:
The event logging service encountered an error (res=%1) while opening configuration for primary channel %2. Trying again using default configuration. This problem usually occurs if registry has been corrupted or explicitly misconfigured.


message_identifier: 0x0000044e
message_string:
The audit log was cleared.%nSubject:%n%tSecurity ID:%t%1%n%tAccount Name:%t%2%n%tDomain Name:%t%3%n%tLogon ID:%t%4


# message_table_85_0x00000409

message_identifier: 0x40050015
message_string:
%2: Ethernet@WireSpeed is enabled and could not negotiate maximum link speed. Potential faulty cable or connection.


message_identifier: 0xc0050011
message_string:
%2: Cannot enter low-power mode because the driver may not be able to auto-negotiate the link down to 10Mbps.


# message_table_86_0x00000409

message_identifier: 0x0000697d
message_string:
EA Information is incorrect.
                 Actual          On Disk
PackedEaSize      0x%1            0x%4
NeedEaCount       0x%2            0x%5
UnpackedEaSize    0x%3            0x%6


message_identifier: 0x0000697e
message_string:
The EA INFORMATION attribute is not consistency with the EA DATA attribute
for file 0x%1.  EA INFORMATION equals 0x%2 while EA DATA equals 0x%3.


message_identifier: 0x00006a54
message_string:
The offset 0x%2 stored in the security descriptor entry with Id
0x%4 at offset 0x%1 is invalid.  The correct value is 0x%3.


message_identifier: 0x00006a4c
message_string:
The remaining of a security data stream page starting at offset 0x%1
for 0x%2 bytes contains non-zero.


message_identifier: 0x00006a79
message_string:
The first index entry offset, 0x%2, for index %1 in file 0x%4
points beyond the length, 0x%3, of the index.  VCN is unknown.


message_identifier: 0x00006a53
message_string:
The hash value 0x%2 of the security descriptor entry with Id
0x%4 at offset 0x%1 is invalid.  The correct value is 0x%3.


message_identifier: 0x000069af
message_string:
Attribute record of type 0x%1 is cross linked starting at
cluster 0x%2 for possibly 0x%3 clusters.


message_identifier: 0x000069ae
message_string:
Attribute record of type 0x%1 and instance tag 0x%2 is cross linked
starting at 0x%3 for possibly 0x%4 clusters.


message_identifier: 0x000069fc
message_string:
The attribute length 0x%1 for attribute of type 0x%3 and
instance tag 0x%4 is too big.  The maximum value is 0x%2.


message_identifier: 0x00006a45
message_string:
The USN Journal entry length 0x%2 at offset 0x%1 in file
0x%4 is too small.  The minimum value is 0x%3.


message_identifier: 0x00006a46
message_string:
The remaining USN page length 0x%2 is too small to fit another
USN Journal entry at offset 0x%1 in file 0x%4.
It needs at least 0x%3 bytes.


message_identifier: 0x00006a41
message_string:
The USN Journal entry length 0x%2 at offset 0x%1, in file
0x%4 is larger than the remaining length 0x%3 of a page.


message_identifier: 0x00006a49
message_string:
The USN Journal length 0x%1 in file 0x%4 is less the
largest USN encountered, 0x%2, plus eight in file 0x%3.


message_identifier: 0x00006a48
message_string:
The USN Journal entry at offset 0x%1 in file 0x%4 is not
consistence.  The entry has length of 0x%3 and a file name length of 0x%2.


message_identifier: 0x000069fb
message_string:
The attribute length 0x%1 for attribute of type 0x%3 and
instance tag 0x%4 is too small.  The minimum value is 0x%2.


message_identifier: 0x00006a4e
message_string:
The length, 0x%2, of the security data stream entry at offset
0x%1 is too small.  The minimum value is 0x%3.


message_identifier: 0x00006a6d
message_string:
Mirror security descriptor block different from that of
master security descriptor at offset 0x%1.


message_identifier: 0x00006a50
message_string:
The security data stream entry at offset 0x%1 does not fit into the
remaining length, 0x%2, of a page.  The minimum value is 0x%3.



message_identifier: 0x000069a3
message_string:
The total allocated size 0x%3 of attribute of type 0x%1 and instance
tag 0x%2 in file 0x%5 is incorrect.  The expected value is %4.


message_identifier: 0x000069e4
message_string:
The reparse point index entry in file 0x%1 points to file 0x%2
but the file has no reparse point in it.


message_identifier: 0x000069e2
message_string:
The reparse tag 0x%2 of reparse point index entry in file 0x%1
is incorrect.  The correct reparse tag in file 0x%4 is 0x%3.


message_identifier: 0x000069e3
message_string:
The parent 0x%2 in the reparse point index entry with tag 0x%4
in file 0x%1 is incorrect.  The correct value is 0x%3.


message_identifier: 0x000069e1
message_string:
The reparse point index entry in file 0x%1 points to file 0x%2
which is not a base file record segment.


message_identifier: 0x000069ce
message_string:
The VCN 0x%2 of index %1 in file 0x%4 is inconsistence with
the VCN 0x%3 stored inside the index buffer.


message_identifier: 0x000069cf
message_string:
The bytes per block, 0x%3, read from index buffer of VCN 0x%2
of index %1 in file 0x%4 is incorrect.


message_identifier: 0x0000699c
message_string:
The attributes with instance tags 0x%2 and 0x%4 have different
type codes 0x%1 and 0x%3 respectively in file 0x%5.


message_identifier: 0x0000699f
message_string:
The attribute of type 0x%1 and instance tag 0x%2 in file 0x%5
has allocated length of 0x%3 instead of 0x%4.


message_identifier: 0x000069fe
message_string:
The resident attribute name is colliding with the resident value for attribute
of type 0x%4 and instance tag 0x%5.  The attribute name offset is
0x%2, length 0x%1, and the attribute value offset is 0x%3.


message_identifier: 0x0000699d
message_string:
The attributes with same type code 0x%1 but different instance tags
0x%2 and 0x%4 have non-contiguous VCN numbers 0x%3 and 0x%5
respectively in file 0x%6.


message_identifier: 0x0000699e
message_string:
The attributes with same type code 0x%1 but different instance tags
0x%2 and 0x%4 have different names %3 and %5
respectively in file 0x%6.


message_identifier: 0x000069fd
message_string:
The resident attribute for attribute of type 0x%4 and instance
tag 0x%5 is incorrect.  The attribute has value of length 0x%1,
and offset 0x%2.  The attribute length is 0x%3.


message_identifier: 0x00006a39
message_string:
The attribute length 0x%3 of attribute of type 0x%1 and name %2 in
file 0x%5 is too small.  The minimum value is 0x%4.


message_identifier: 0x000069f1
message_string:
The standard information attribute length 0x%1 is incorrect.
The expected value is 0x%2, 0x%3, or 0x%4.


message_identifier: 0x000069ff
message_string:
The mapping pairs offset 0x%1 for attribute of type 0x%3 and instance
tag 0x%4 exceeded the attribute length 0x%2.


message_identifier: 0x000069c0
message_string:
The clusters per index buffer, 0x%2, for index root %1 in file
0x%4 is incorrect.  The expected value is 0x%3.


message_identifier: 0x000069c2
message_string:
The index allocation allocated length, 0x%2, for index %1 in file
0x%4 is not in multiple of 0x%3.


message_identifier: 0x000069c3
message_string:
The first free byte, 0x%2, and bytes available, 0x%3, for
root index %1 in file 0x%4 are not equal.


message_identifier: 0x00006a18
message_string:
The record length 0x%1 of attribute of type 0x%2 and
instance tag 0x%3 in file 0x%4 is not aligned.


message_identifier: 0x00006a19
message_string:
The record length 0x%1 is too large for attribute of type 0x%3
and instance tag 0x%4 in file 0x%5.  The maximum value is 0x%2.


message_identifier: 0x00006a12
message_string:
The bytes available, 0x%1, in the file record segment header for
file 0x%3 is incorrect.  The expected value is 0x%2.


message_identifier: 0x00006a16
message_string:
The attribute record offset 0x%1 is too large for attribute of type 0x%3
and instance tag 0x%4 in file 0x%5.  The maximum value is 0x%2.


message_identifier: 0x00006a17
message_string:
The record length of attribute of type 0x%1 and instance tag 0x%2
in file 0x%3 should not be zero.


message_identifier: 0x00006a14
message_string:
The instance tag 0x%2 of attribute of type 0x%1 in file 0x%4
is too large.  The instance tag should be less than 0x%3.


message_identifier: 0x00006a0b
message_string:
The file name in file name value in attribute of type 0x%1 and instance
tag %2 contains unicode NULL.


message_identifier: 0x000069b8
message_string:
The collation rule 0x%3 for index root %1 in file 0x%2
is incorrect.  The expected value is 0x%4.


message_identifier: 0x000069b1
message_string:
The attribute list in file 0x%1 indicates the standard information
attribute is outside the base file record segment.


message_identifier: 0x000069b5
message_string:
The index bitmap %2 is present but there is no corresponding
index allocation attribute in file 0x%1.


message_identifier: 0x00006a68
message_string:
Current leaf index entry of length 0x%3 is at depth 0x%2 which
is different from other leaf index entry which has a depth of 0x%1.


message_identifier: 0x00006985
message_string:
Corrupt EA set for file 0x%1.  The unpacked total length, 0x%2,
is larger than the total data length, 0x%3.


message_identifier: 0x00006987
message_string:
Corrupt EA set for file 0x%1.  The unpacked length, 0x%2,
is not the same as the record length, 0x%3.


message_identifier: 0x00006a09
message_string:
The attribute of type 0x%2 and instance tag 0x%3 is inconsistence.
The attribute value length is 0x%1.


message_identifier: 0x00006a08
message_string:
The file name value length 0x%1 for attribute of type 0x%3 with
instance tag 0x%4 is too small.  The minimum value is 0x%2.


message_identifier: 0x00006a01
message_string:
The attribute name is colliding with the mapping pairs for attribute
of type %4 and instance tag 0x%5.  The attribute name offset is
0x%2, length 0x%1, and the mapping pairs offset is 0x%3.


message_identifier: 0x00006a00
message_string:
The mapping pairs offset 0x%1 for attribute of type 0x%3 and instance
tag 0x%4 is too small.  The minimum value is 0x%2.


message_identifier: 0x00006a02
message_string:
The attribute of type 0x%2 and instance tag 0x%3 in file 0x%4
has bad mapping pairs at attribute offset 0x%1.


message_identifier: 0x00006a05
message_string:
The non resident attribute of type 0x%4 and instance tag 0x%5 is
inconsistent.  The valid data length is 0x%1, file size 0x%2, and
allocated length 0x%3.


message_identifier: 0x00006a04
message_string:
The highest VCN 0x%1 of attribute of type 0x%3 and instance
tag 0x%4 is incorrect.  The expected value is 0x%2.


message_identifier: 0x00006a07
message_string:
The allocated length 0x%1 is not in multiple of 0x%2 for attribute
of type 0x%3 and instance tag 0x%4.


message_identifier: 0x00006a06
message_string:
The non resident attribute of type 0x%4 is inconsistent.  The valid data
length is 0x%1, file size 0x%2, and allocated length 0x%3.


message_identifier: 0x00006a1b
message_string:
The attribute of type 0x%1 and instance tag 0x%2 should be after
attribute of type 0x%3 and instance tag 0x%4 in file 0x%5.


message_identifier: 0x00006a1a
message_string:
The first free byte, 0x%1, in file 0x%4 is incorrect.  The number of
bytes free in the file record segment is 0x%2 and the total length
is 0x%3.


message_identifier: 0x000069ee
message_string:
The attribute record length 0x%1 is too small for attribute of
type 0x%3 and instance tag 0x%4.  The minimum value is 0x%2.


message_identifier: 0x000069e9
message_string:
The index entry attribute length 0x%2 of index entry type 0x%1
is incorrect.  The correct length is 0x%3.


message_identifier: 0x0000698a
message_string:
The second MFT starting LCN in the boot sector is incorrect.
The actual value is 0x%2 while the expected value is 0x%1.


message_identifier: 0x00006a92
message_string:
The mapping pairs offset 0x%1 for attribute of type 0x%2 and instance
tag 0x%3 is not quad aligned.


message_identifier: 0x000069ba
message_string:
The index attribute of type 0x%2 for index root %1
in file 0x%4 is incorrect.  The expected value is 0x%3.


message_identifier: 0x000069ea
message_string:
The index entry data offset 0x%1 and length 0x%2 is
inconsistence with the index entry length 0x%3.


message_identifier: 0x000069bf
message_string:
The bytes per index buffer, 0x%2, for index root %1 in file
0x%4 is incorrect.  The expected value is 0x%3.


message_identifier: 0x000069de
message_string:
The parent 0x%2 in an object id index entry in file 0x%1
is incorrect.  The correct value is 0x%3.


message_identifier: 0x00006a34
message_string:
The attribute name offset 0x%3 of attribute list entry with attribute of
type 0x%1 and instance tag 0x%2 in file 0x%5 is too small.
The minimum value is 0x%4.


message_identifier: 0x00006a36
message_string:
The extent list of the attribute list is crossed linked at 0x%1
for possibly 0x%2 clusters in file 0x%3.


message_identifier: 0x00006a37
message_string:
The attribute list entry with attribute of type 0x%1 and instance tag
0x%2 should be after attribute of type 0x%3 and instance tag 0x%4.


message_identifier: 0x00006a32
message_string:
The length, 0x%3, of the attribute list entry with attribute of type
0x%1 and instance tag 0x%2 in file 0x%4 is not aligned.


message_identifier: 0x00006a33
message_string:
The attribute list entry with attribute of type 0x%1 and instance tag 0x%2
in file 0x%6 is incorrect.  The attribute list entry name length is 0x%3,
and offset 0x%4.  The attribute list length is 0x%5.


message_identifier: 0x000069d9
message_string:
Unable to locate the file name attribute of index entry %3
of index %2 with parent 0x%1 in file 0x%4.


message_identifier: 0x000069d8
message_string:
The file 0x%3 pointed to by an index entry of index %2 with
parent file 0x%1 is not a base file record segment.


message_identifier: 0x000069d4
message_string:
Unable to query the name of a file name index entry of length 0x%3
of index %2 in file 0x%4 with parent 0x%1.


message_identifier: 0x000069d7
message_string:
The file 0x%4 pointed to by index entry %3 of index %2 with
parent file 0x%1 is not a base file record segment.


message_identifier: 0x000069d1
message_string:
The USA size 0x%3 of VCN 0x%2 of index %1 in file
0x%5 is incorrect.  The expected value is 0x%4.


message_identifier: 0x00006a77
message_string:
The total allocated size 0x%1 for attribute of type 0x%3 and
instance tag 0x%4 is larger than the allocated length 0x%2.


message_identifier: 0x00006a27
message_string:
The file name attributes in file 0x%3 has different parents.
The DOS name has 0x%1 as parent.  The NTFS name has 0x%2 as parent.


message_identifier: 0x00006a7c
message_string:
The parent 0x%3 of index entry %4 of index %2
in file 0x%5 is incorrect.  The expected parent is 0x%1.


message_identifier: 0x000069dc
message_string:
The object id index entry in file 0x%1 points to file 0x%2
which is not a base file record segment.


message_identifier: 0x00006a7a
message_string:
Some clusters occupied by attribute of type 0x%1 and instance tag 0x%2
in file 0x%3 is already in use.


message_identifier: 0x00000083
message_string:
The file system structure on volume %2 cannot be corrected.%nPlease run the chkdsk utility on the volume %2.


message_identifier: 0x000069da
message_string:
Unable to locate the file name attribute of an index entry
of index %2 with parent 0x%1 in file 0x%3.


message_identifier: 0x00006a78
message_string:
Unable to locate attribute with instance tag 0x%2 and segment
reference 0x%3.  The expected attribute type is 0x%1.


message_identifier: 0x00000084
message_string:
Too many repair events have occurred in a short period of time.%nTemporarily suspending posting of further repair events.


# message_table_88_0x00000409

message_identifier: 0x00000011
message_string:
The Secure Socket Tunneling Protocol service could not open the Parameters section of the registry to read the configuration values, so SSTP cannot be initialized. The detailed error message is provided below. Correct the problem and try again. %n%n%1


message_identifier: 0x00000010
message_string:
CoId=%1:The Secure Socket Tunneling Protocol server has provided a certificate with an Enhanced Key Usage that is neither Server Authentication nor Any Purpose. This client will not accept the certificate. The connection will be canceled. Contact the server administrator to correct the issue and try again.


message_identifier: 0x00000013
message_string:
The Secure Socket Tunneling Protocol service either could not read the SHA1 certificate hash from the registry or the data is invalid. To be valid, the SHA1 certificate hash must be of type REG_BINARY and 20 bytes in length. SSTP might not be able to retrieve the value from the registry due to some other system failure. The detailed error message is provided below. SSTP connections will not be accepted on this server. Correct the problem and try again. %n%n%1


message_identifier: 0x00000012
message_string:
The Secure Socket Tunneling Protocol service either could not read the SHA256 certificate hash from the registry or the data is invalid. To be valid, the SHA256 certificate hash must be of type REG_BINARY and 32 bytes in length. SSTP might not be able to retrieve the value from the registry due to some other system failure. The detailed error message is provided below. SSTP connections will not be accepted on this server. Correct the problem and try again. %n%n%1


message_identifier: 0x00000015
message_string:
The Secure Socket Tunneling Protocol service was not able to get the hash for the certificate configured with HTTP. The detailed error message is provided below. Correct the problem and try again. %n%n%1


message_identifier: 0x00000014
message_string:
The Secure Socket Tunneling Protocol service was not able to allocate memory for setting up the configuration for accepting connections. The system might be low on memory. Correct the problem and restart the service.


message_identifier: 0x00000017
message_string:
CoId=%1:The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server. This can be due to the presence of a web proxy between the client and the server requiring authentication. Proxy authentication is not supported by this version of SSTP.


message_identifier: 0x00000016
message_string:
The Secure Socket Tunneling Protocol service could not be configured to accept incoming connections. The detailed error message is provided below. Correct the problem and restart the SSTP service. %n%n%1


message_identifier: 0x00000019
message_string:
The certificate used for Secure Socket Tunnelling Protocol (SSTP) is missing. You should configure a new certificate for SSTP or use default configuration


message_identifier: 0x00000018
message_string:
The certificates bound to the HTTPS listener for IPv4 and IPv6 do not match. For SSTP connections, certificates should be configured for 0.0.0.0:Port for IPv4, and [::]:Port for IPv6. The port is the listener port configured to be used with SSTP. The default listener port is 443.


message_identifier: 0x0000000b
message_string:
The Secure Socket Tunneling Protocol (SSTP) service could not find either a Server Authentication certificate or an Any Purpose certificate to be used for HTTPS. Check to see the availability of either a Server Authentication certificate or an Any Purpose certificate which also has a private key. SSTP sessions may not get established. Use ‘netsh.exe http add sslcert’ command to configure the certificate manually or install the appropriate certificate for SSTP use and restart RemoteAccess service.


message_identifier: 0x0000000c
message_string:
The Secure Socket Tunneling Protocol service could not configure the following certificate for use with Internet Protocol version 4 (IPv4). This might prevent SSTP connections from being established successfully. Correct the problem and try again.%n%nCertificate Name - %2%n%n%1


message_identifier: 0x0000000a
message_string:
The Secure Socket Tunneling Protocol service could not secure the default URL. This can prevent the servicing of the SSTP modules. Use 'netsh.exe http add urlacl' command to secure the ACL manually. The detailed error message is given at the end of this message. %n%nURL: %1%n%n%2


message_identifier: 0x0000000f
message_string:
The Secure Socket Tunneling Protocol service could not get the network address of the remote server. This address is required for establishing the route for redirecting the traffic over the VPN interface. The detailed error message is provided below. Correct the problem and try again. %1


message_identifier: 0x0000000d
message_string:
The Secure Socket Tunneling Protocol service could not configure the following certificate for use with Internet Protocol version 6 (IPv6). This might prevent SSTP connections from being established successfully. Correct the problem and try again.%n%nCertificate Name - %2%n%n%1


message_identifier: 0x0000000e
message_string:
The Secure Socket Tunneling Protocol service could not configure the route to the VPN server, which is required for the proper functioning of the VPN connection. The detailed error message is given below. Correct the problem and try again. %1


message_identifier: 0x00000020
message_string:
The thumbprint (cert hash) of the certificate used for Secure Socket Tunnelling Protocol (SSTP) %1 is different than the certificate bound %2 to the Web listener (HTTP.sys). Configure SSTP to use the default certificate or the certificate bound to SSL. You can configure web server applications to use the same certificate used by SSTP


message_identifier: 0x00000021
message_string:
CoId=%1: “Secure Socket Tunnelling Protocol (SSTP)” service could not configure the VPN server specific cookies. The detailed information on the error is given below.%n%n%%2


message_identifier: 0x00000002
message_string:
CoId=%1:The initial Secure Socket Tunneling Protocol (SSTP) response could not be received. There might be intermittent network connectivity issues or the server might not be accepting SSTP connections. The detailed error message is provided below. Correct the problem and try again. %n%n%2


message_identifier: 0x00000003
message_string:
CoId=%1:The HTTP response received from the server-side Secure Socket Tunneling Protocol (SSTP) either does not have the version information or the version is not supported. The HTTP version information received is logged in the data section below. The HTTP response from the SSTP server must contain the version header and the version must be 1.1.


message_identifier: 0x00000001
message_string:
CoId=%1:The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server. This can be due to network connectivity issues or certificate (trust) issues. The detailed error message is provided below. Correct the problem and try again.%n%n%2


message_identifier: 0x00000006
message_string:
CoId=%1:The SSTP-based VPN connection to the remote access server was terminated because of a security check failure. Security settings on the remote access server do not match settings on this computer. Contact the system administrator of the remote access server and relay the following information:%n%nSHA1 Certificate Hash: %2%nSHA256 Certificate Hash: %3


message_identifier: 0x00000007
message_string:
The Secure Socket Tunneling Protocol service could not open the ConfigStore that is used for storing service-specific information. This can lead to incorrect service configuration or a leak of system resources.


message_identifier: 0x00000004
message_string:
CoId=%1:The server has refused the Secure Socket Tunneling Protocol (SSTP) request. Either a failure response code or no response code was received. The data portion below contains the response code that was received from the server. This is the HTTP status code present in the response. It can be because the web proxy or the SSTP server might be rejecting the connection, the server might not be configured for SSTP or the server might not have a port available for connection.


message_identifier: 0x00000005
message_string:
CoId=%1:The Secure Socket Tunneling Protocol (SSTP) negotiation has failed. The failure code is stored in the Data section of this message. Correct the problem and try again.


message_identifier: 0x00000008
message_string:
The Secure Socket Tunneling Protocol (SSTP) service could not initialize the HTTP layer for setting up the configuration. Any configuration changes applied by the administrator might not be applied by SSTP.


message_identifier: 0x00000009
message_string:
The Secure Socket Tunneling Protocol service could not secure the URL with the new service configuration. Other applications or services can override the URL reservation. Use 'netsh.exe http add urlacl' command to secure the access control list (ACL) manually. The detailed error message is given at the end of this message. %n%nURL: %1 %n%n%2


# message_table_90_0x00000409

message_identifier: 0x00000467
message_string:
An access control list (ACL) on the following file might have prevented Windows from starting : %1


message_identifier: 0x0000046d
message_string:
The computer firmware (BIOS) is not compatible with Windows. Contact your computer manufacturer for an update to the computer BIOS.


# message_table_91_0x00000409

message_identifier: 0x4005000b
message_string:
The ring buffer that stores incoming mouse data has overflowed (buffer size is configurable via the registry).


# message_table_92_0x00000409

message_identifier: 0xc006005a
message_string:
Volume %2 is offline for shadow copy protection.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc006005e
message_string:
Volume %2 is offline for shadow copy protection.  An application attempted to write to the shadow copy meta data.  If this program was run intentionally then turn off protection mode for this volume in order to allow the application (which may be FORMAT) to run.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc006003c
message_string:
The shadow copies of volume %2 were aborted because volume %3, which contains shadow copy storage for this shadow copy, has been taken offline.


message_identifier: 0xc006001b
message_string:
The shadow copies of volume %2 were aborted during detection because a critical control file could not be opened.


message_identifier: 0xc006001c
message_string:
The shadow copy of volume %2 could not be created due to a failure in creating the necessary on disk structures.


message_identifier: 0xc0060029
message_string:
When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 did not have sufficiently large contiguous blocks.  Consider deleting unnecessary files on the shadow copy storage volume or use a different shadow copy storage volume.


message_identifier: 0xc0060027
message_string:
When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 could not be located in non-critical space.  Consider using a shadow copy storage volume that does not have any shadow copies.


message_identifier: 0xc006005c
message_string:
Volume %2 is offline for shadow copy protection.  A read or write error occurred.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060055
message_string:
Volume %2 is offline for shadow copy protection.  A read failure occurred during a shadow copy on write operation.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060024
message_string:
The shadow copies of volume %2 were aborted because the shadow copy storage could not grow due to a user imposed limit.


message_identifier: 0xc0060058
message_string:
Volume %2 is offline for shadow copy protection.  The shadow copy storage was exhausted before conditions permitted it to grow.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc006005d
message_string:
Volume %2 is offline for shadow copy protection.  The shadow copy storage was made inaccessible or removed from the system.  Please ensure that the shadow copy storage is present.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060020
message_string:
The shadow copies of volume %2 were aborted because the shadow copy storage volume was not present.


message_identifier: 0xc0060005
message_string:
The shadow copy of volume %2 could not be created due to insufficient non-paged memory pool for a bitmap structure.


message_identifier: 0xc0060004
message_string:
The shadow copy of volume %2 could not be created due to insufficient resources for worker threads.


message_identifier: 0xc0060006
message_string:
The shadow copy of volume %2 could not create a new paged heap.  The system may be low on virtual memory.


message_identifier: 0xc0060003
message_string:
The shadow copy of volume %2 could not lock down the location of the shadow copy storage on volume %3.


message_identifier: 0xc0060002
message_string:
The shadow copy of volume %2 could not be created because volume %3, which is specified as the location for shadow copy storage, is not an NTFS volume or an error was encountered while trying to determine the file system type of this volume.


message_identifier: 0xc006003b
message_string:
The shadow copies of volume %2 were aborted because the shadow copy storage volume was not present in time during a previous session.


message_identifier: 0x80060018
message_string:
There was insufficient disk space on volume %3 to grow the shadow copy storage for shadow copies of %2.  As a result of this failure all shadow copies of volume %2 are at risk of being deleted.


message_identifier: 0xc0060008
message_string:
The flush and hold writes operation on volume %2 timed out while waiting for a release writes command.


message_identifier: 0xc006003f
message_string:
An error occurred while trying to delete a snapshot of %2.  The delete will be retried at a later time.


message_identifier: 0xc0060059
message_string:
Volume %2 is offline for shadow copy protection.  The shadow copy storage could not be increased as needed.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0x40060021
message_string:
The oldest shadow copy of volume %2 was deleted to keep disk space usage for shadow copies of volume %2 below the user defined limit.


message_identifier: 0x40060041
message_string:
The reverting of volume %2 is being restarted.  This is most likely because of a system shutdown or a system crash.


message_identifier: 0x4006003a
message_string:
The oldest shadow copy of volume %2 was deleted to keep the total number of shadow copies of volume %2 below a limit.


message_identifier: 0xc006005b
message_string:
Volume %2 is offline for shadow copy protection.  An error occurred when doing a file system operation.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060030
message_string:
When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 did not have sufficiently large contiguous blocks.  A shadow copy create computation is in progress to find more contiguous blocks.


message_identifier: 0xc0060056
message_string:
Volume %2 is offline for shadow copy protection.  A read or write failure to shadow copy storage occurred.  Please ensure that the shadow copy storage is still present in the system.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0x8006003e
message_string:
The revert operation on volume %2 stopped because of the loss of a volume.  When the volume is re-introduced, the revert will continue.  You may have to reboot to trigger the revert.


message_identifier: 0x8006003d
message_string:
The revert operation on volume %2 encountered a bad sector error.  Please validate the data on this volume.


message_identifier: 0xc0060017
message_string:
There was insufficient disk space on volume %3 to create the shadow copy of volume %2.  Shadow copy storage creation failed.


message_identifier: 0xc0060010
message_string:
The shadow copies of volume %2 were aborted because volume %3, which contains shadow copy storage for this shadow copy, was force dismounted.


message_identifier: 0xc0060011
message_string:
An attempt to flush and hold writes on volume %2 was attempted while another flush and hold was already in progress.


message_identifier: 0xc0060052
message_string:
Volume %2 is offline for shadow copy protection.  A shadow copy meta data corruption was detected.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060053
message_string:
Volume %2 is offline for shadow copy protection.  A memory allocation failed.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060050
message_string:
Volume %2 is offline for shadow copy protection.  The shadow copy storage is not present.  This volume will go online and its shadow copies will become available once the shadow copy storage is introduced in the system.  Revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060051
message_string:
Volume %2 is offline for shadow copy protection.  An IO error occurred during shadow copy discovery.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0x80060026
message_string:
There was a user imposed limit that prevented disk space on volume %3 from being used to grow the shadow copy storage for shadow copies of %2.  As a result of this failure all shadow copies of volume %2 are at risk of being deleted.


message_identifier: 0xc0060057
message_string:
Volume %2 is offline for shadow copy protection.  The shadow copy storage has been exhausted.  Please try clearing the protection fault or restart the computer followed by an increase of the shadow copy storage or a removal of unneeded shadow copies.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060054
message_string:
Volume %2 is offline for shadow copy protection.  A memory mapping failed.  Consider increasing the size of the page file.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.


message_identifier: 0xc0060019
message_string:
The shadow copies of volume %2 were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.


# message_table_93_0x00000409

message_identifier: 0xc0010004
message_string:
Initial connection to Bluetooth HID device %2 failed.  The device has been removed as a personal or paired device.  You must reinstall the device.


# message_table_94_0x00000409

message_identifier: 0xc000000c
message_string:
Target provided invalid data for login redirect. Dump data contains the data returned by the target.


message_identifier: 0xc000000b
message_string:
Target returned an invalid login response packet. The login response packet is given in the dump data.


message_identifier: 0xc000000f
message_string:
CHAP challenge given by the target contains invalid characters. Dump data contains the challenge given.


message_identifier: 0xc000000e
message_string:
Target offered an unknown digest algorithm for CHAP. Dump data contains the data returned by the target.


message_identifier: 0xc000002a
message_string:
Target sent an invalid status sequence number for a connection. Dump data contains 
Expected Status Sequence number followed by the given status sequence number.


message_identifier: 0xc000002d
message_string:
Target failed to respond in time for a login request. This login request was for adding a new connection to a session.


message_identifier: 0x40000022
message_string:
A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.


message_identifier: 0xc0000039
message_string:
Initiator could not allocate required resources for processing a request resulting in I/O failure. 


message_identifier: 0xc0000019
message_string:
Data digest error was detected. Dump data contains the calculated checksum followed by the given checksum.


message_identifier: 0xc0000033
message_string:
Target failed to respond in time to a logout request sent in response to an asynchronous message from the target.


message_identifier: 0xc0000010
message_string:
An invalid key was received during CHAP negotiation. The key=value pair is given in the dump data.


message_identifier: 0xc0000011
message_string:
CHAP Response given by the target did not match the expected one. Dump data contains the CHAP response.


message_identifier: 0x40000047
message_string:
Initiator did not start a session recovery upon receiving the request. Dump data contains the error status.


message_identifier: 0xc0000034
message_string:
Initiator Service failed to respond in time to a request to configure IPSec resources for an iSCSI connection.


message_identifier: 0xc000003c
message_string:
Target sent data in SCSI Response PDU instead of Data_IN PDU. Only Sense Data can be sent in SCSI Response.


message_identifier: 0xc0000035
message_string:
Initiator Service failed to respond in time to a request to release IPSec resources allocated for an iSCSI connection.


message_identifier: 0xc0000045
message_string:
Attempt to recover an unexpected terminated session failed. Error status is given in the dump data.


message_identifier: 0xc0000044
message_string:
After receiving an async logout from the target, attempt to relogin the session failed.  Error status is given in the dump data.


message_identifier: 0xc000001b
message_string:
Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.


message_identifier: 0xc0000003
message_string:
Maximum command sequence number is not serially greater than expected command sequence number in login response.
Dump data contains Expected Command Sequence number followed by Maximum Command Sequence number.


message_identifier: 0xc0000001
message_string:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.


message_identifier: 0xc0000004
message_string:
MaxBurstLength is not serially greater than FirstBurstLength.
Dump data contains FirstBurstLength followed by MaxBurstLength.


message_identifier: 0xc0000008
message_string:
Target or discovery service did not respond in time for an iSCSI request sent by the initiator. 
iSCSI Function code is given in the dump data. For details about iSCSI Function code please refer 
to iSCSI User's Guide.


message_identifier: 0xc0000024
message_string:
Initiator CHAP secret is smaller than the minimum size (12 bytes) required by the spec. Dump data contains the given CHAP secret.


message_identifier: 0xc0000027
message_string:
Initiator sent a task management command to reset the target. The target name is given in the dump data.


message_identifier: 0xc0000046
message_string:
Error occurred when processing iSCSI logon request. The request was not retried. Error status is given in the dump data.


message_identifier: 0xc0000038
message_string:
Initiator could not map an user virtual address to kernel virtual address resulting in I/O failure. 


# message_table_95_0x00000409

message_identifier: 0xb00036e8
message_string:
Discard this round of background scan because the current connection does not allow auto switch. Interface = %2


message_identifier: 0xb00032ca
message_string:
A pre-logon connection was attempted.%n%nResult: %1%nInterface GUID: %2%nProfile Name: %3%nRequested Fields: %4%n


message_identifier: 0xb0002eed
message_string:
Wireless 802.1x authentication failed.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nIdentity: %7%nUser: %8%nDomain: %9%nReason: %10%nError: %12%nEAP Reason: %13%nEAP Root cause String: %14%nEAP Error: %15%n


message_identifier: 0xb0002eee
message_string:
Wireless 802.1x authentication was restarted.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nEap Information: Type %7, Vendor ID %8, Vendor Type %9, Author ID %10%nRestart Reason: %11%n


message_identifier: 0xb0002eeb
message_string:
Wireless 802.1x authentication started.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nEap Information: Type %7, Vendor ID %8, Vendor Type %9, Author ID %10%n


message_identifier: 0xb0002eec
message_string:
Wireless 802.1x authentication succeeded.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nIdentity: %7%nUser: %8%nDomain: %9%n


message_identifier: 0xb00032d5
message_string:
The post-logon connection attempt is complete.%n%nNetwork connection attempt result: %1%nReason: %2%nInterface GUID: %3%nProfile Name: %4%n


message_identifier: 0xb0004e33
message_string:
A client has associated with the hosted network. %n%nInterface GUID: %1%nInterface description:%2%nNetwork SSID: %3%nLocal MAC address: %4%nPeer MAC address: %5%n


message_identifier: 0xb00036e9
message_string:
Discard this round of background scan because the current connection is the most preferred auto connection. Interface = %2


message_identifier: 0xb0002af9
message_string:
Wireless network association succeeded.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%n


message_identifier: 0xb0002af8
message_string:
Wireless network association started.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nAuthentication: %6%nEncryption: %7%n802.1X Enabled: %8%n


message_identifier: 0xb0002afe
message_string:
Wireless security failed.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nReason: %7%nError: %9%n


message_identifier: 0xb0002afd
message_string:
Wireless security succeeded.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%n


message_identifier: 0xb0002aff
message_string:
Wireless IHV security started.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%n


message_identifier: 0xb0002afa
message_string:
Wireless network association failed.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nFailure Reason: %6%nDot11 Status Code: %8%n


message_identifier: 0xb0002afc
message_string:
Wireless security stopped.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nSecurity Hint: %7%n


message_identifier: 0xb0002afb
message_string:
Wireless security started.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nAuthentication: %7%nEncryption: %9%n802.1x Enabled: %11%n


message_identifier: 0xb0005248
message_string:
WLAN Security Settings: BSS Type %1, Authentication %2, Encryption %3, OneX Enabled %4, Eap Information - Type %5, Vendor ID %6, Vendor Type %7, Author ID %8


message_identifier: 0xb0002b00
message_string:
Wireless IHV security succeeded.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%n


message_identifier: 0xb0002b01
message_string:
Wireless IHV security failed.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nReason: %7%nAdditional Data Length: %8%n


message_identifier: 0xb0002b02
message_string:
Wireless security started.%n%nNetwork Adapter: %1%nInterface GUID: %2%nLocal MAC Address: %3%nNetwork SSID: %4%nBSS Type: %5%nPeer MAC Address: %6%nAuthentication: %7%nEncryption: %9%nFIPS Mode: %11%n802.1x Enabled: %12%n


message_identifier: 0xb0001f4a
message_string:
WLAN AutoConfig service has failed to stop the hosted network.%n%nError Code: %2%nError Message: %3%nInterface GUID: %1%nSSID: %4%n


message_identifier: 0xb0001f49
message_string:
WLAN AutoConfig service has finished stopping the hosted network.%n%nInterface GUID: %1%nSSID: %2%n


message_identifier: 0xb0001f41
message_string:
WLAN AutoConfig service has successfully connected to a wireless network.%n%nNetwork Adapter: %2%nInterface GUID: %1%nConnection Mode: %3%nProfile Name: %4%nSSID: %5%nBSS Type: %6%nBSSID: %7%nPHY Type: %8%nAuthentication: %9%nEncryption: %10%n802.1x Enabled: %11%n


message_identifier: 0xb0001f40
message_string:
WLAN AutoConfig service started a connection to a wireless network.%n%nNetwork Adapter: %2%nInterface GUID: %1%nConnection Mode: %3%nProfile Name: %4%nSSID: %5%nBSS Type: %6%n


message_identifier: 0xb0001f43
message_string:
WLAN AutoConfig service has successfully disconnected from a wireless network.%n%nNetwork Adapter: %2%nInterface GUID: %1%nConnection Mode: %3%nProfile Name: %4%nSSID: %5%nBSS Type: %6%nReason: %7%n


message_identifier: 0xb0001f42
message_string:
WLAN AutoConfig service failed to connect to a wireless network.%n%nNetwork Adapter: %2%nInterface GUID: %1%nConnection Mode: %3%nProfile Name: %4%nSSID: %5%nBSS Type: %6%nFailure Reason:%7%n


message_identifier: 0xb0001f44
message_string:
Wireless network is blocked due to connection failure.%n%nNetwork Adapter: %1%nInterface GUID: %2%nConnection Mode: %5%nProfile Name: %4%nSSID(s): %3%nBSS Type: %6%nFailure Reason:%7%nLength of block timer (minutes): %8%n


message_identifier: 0xb0001f47
message_string:
WLAN AutoConfig service has failed to start the hosted network.%n%nError Code: %2%nError Message: %3%nInterface GUID: %1%nSSID: %4%n


message_identifier: 0xb0001f46
message_string:
WLAN AutoConfig service has finished starting the hosted network.%n%nInterface GUID: %1%nSSID: %2%n


message_identifier: 0xb0004e34
message_string:
A client has successfully authenticated with the hosted network. %n%nInterface GUID: %1%nInterface description:%2%nNetwork SSID: %3%nLocal MAC address: %4%nPeer MAC address: %5%n


message_identifier: 0xb0004e35
message_string:
A client has failed to authenticate with the hosted network. %n%nError code: %2%nError Message: %3%nInterface GUID: %1%nInterface description:%4%nNetwork SSID: %5%nLocal MAC address: %6%n


# message_table_96_0x00000409

message_identifier: 0xb000003c
message_string:
BITS stopped transferring the %2 transfer job that is associated with the %4 URL. The status code is %6.


message_identifier: 0xb000003e
message_string:
The BITS job named "%1" belonging to user %2 received inconsistent data while downloading. The URL was "%3". The transfer will continue using a different server.  If the problem occurs often, an administrator should scan the peer server for viruses or corruption in its hard drive.


message_identifier: 0x00004009
message_string:
BITS has encountered an error communicating with an Internet Gateway Device.  Please check that the device is functioning properly. BITS will not attempt to use this device until the next system reboot. Error code: %1.


message_identifier: 0x00004006
message_string:
Job "%2" owned by %3 failed to notify its associated application.  BITS will retry in %4 minutes.  The job ID was %1.


message_identifier: 0x801900cd
message_string:
HTTP status 205: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x00004002
message_string:
While canceling job "%2", BITS was unable to remove some temporary files. To recover disk space, delete the temporary files. Note: Due to space limitations, not all files are listed.  Check for additional files of the form BITxxx.TMP in the same directory.  The job ID was %1.  %3


message_identifier: 0x801900cc
message_string:
HTTP status 204: The server has fulfilled the request, but there is no new information to send back.


message_identifier: 0x00004001
message_string:
While canceling job "%2", BITS was unable to remove some temporary files. To recover disk space, delete the files listed below.  The job ID was %1.  %3


message_identifier: 0x8019019c
message_string:
HTTP status 412: The precondition given in one or more of the request header fields evaluated to false when it was tested on the server.


message_identifier: 0x8019019a
message_string:
HTTP status 410: The requested resource is not currently available at the server, and no forwarding address is known.


message_identifier: 0x8019019f
message_string:
HTTP status 415: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x8019019e
message_string:
HTTP status 414: The server cannot process the request because the request Uniform Resource Identifier (URI) is longer than the server can interpret.


message_identifier: 0x0020001a
message_string:
BITS was unable to delete some temporary files. Check the system event log for the complete list of files that could not be deleted.


message_identifier: 0x80200013
message_string:
The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.


message_identifier: 0x80200011
message_string:
The server did not return the file size. The URL might point to dynamic content. The Content-Length header is not available in the server's HTTP reply.


message_identifier: 0x80200010
message_string:
There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected.


message_identifier: 0x80200016
message_string:
The new owner has insufficient access to the local files for the job. The new owner might not have permissions to access the job files. Verify that the new owner has sufficient permissions, and then try again.


message_identifier: 0x80200015
message_string:
The drive mapping for the job is different for the current owner than for the previous owner. Use a UNC path instead.


message_identifier: 0x80200019
message_string:
The HTTP proxy bypass list cannot be longer than 32,000 characters. Try again with a shorter bypass proxy list.


message_identifier: 0x801900c8
message_string:
HTTP status 200: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x0000400d
message_string:
The Per-user job limit (%2) specified through Group Policy must be less than or equal to Per-computer job Limit (%3).  To correct the problem, modify BITS Group Policy settings and restart the BITS service.


message_identifier: 0x0000400e
message_string:
A new BITS job could not be created. The current job count for the user %1 (%2) is equal to or greater than the job limit (%3) specified through group policy.  To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error, and restart the BITS service. If this error recurs, contact your system administrator and increate the per-user and per-computer Group Policy job limits.


message_identifier: 0x0000400c
message_string:
Error %3 occurred when BITS tried to change the state of firewall rule "%1" to %2.  Restarting the BITS service may correct the problem.


message_identifier: 0x00004015
message_string:
A bandwidth profile is not configured correctly. The value of a Group Policy setting is missing or is not within the allowed range. Make sure that you configure the Group Policy settings correctly, and then try again.


message_identifier: 0x00004011
message_string:
BITS could not add file(s) to %1 job. The file count for %1 job (%2) has exceeded the per-job file limit (%3) specified through Group Policy.  To correct the problem, increase the Computer’s per-job file limit Group Policy settings and restart the BITS service.


message_identifier: 0x00004010
message_string:
A new BITS job could not be created. The current job count for this computer (%2) is equal to or greater than the per-computer job limit (%3) specified through Group Policy.  To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error and restarting the BITS service. If this error recurs, contact your system administrator and increase the per-computer Group Policy job limits.


message_identifier: 0x00004012
message_string:
BITS could not add ranges to %1 file. The range count for %1 file (%2) has exceeded the per-file range limit (%3) specified through group policy.  To correct the problem, increase the per-file range limit Group Policy setting and restart the BITS service.


message_identifier: 0x8020001b
message_string:
The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x8020001f
message_string:
The specified session could not be found on the server. Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x8020001d
message_string:
The local file was changed during the transfer. Recreate the job, and then try to transfer it again.


message_identifier: 0x80190192
message_string:
HTTP status 402: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x80190193
message_string:
HTTP status 403: The client does not have sufficient access rights to the requested server object.


message_identifier: 0x80190199
message_string:
HTTP status 409: The request could not be completed because of a conflict with the current state of the resource. The user should resubmit the request with more information.


message_identifier: 0xb000003f
message_string:
The BITS job %1 is configured to launch %3 after transfer of %2. The notification program returned error %4, BITS will continue to launch the program periodically until it succeeds.


message_identifier: 0x80190130
message_string:
HTTP status 304: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x80190131
message_string:
HTTP status 305: The requested resource must be accessed through the proxy given by the location field.


message_identifier: 0x8019012f
message_string:
HTTP status 303: The response to the request is under a different Uniform Resource Identifier (URI) and must be retrieved using a GET method on that resource.


message_identifier: 0x8019012e
message_string:
HTTP status 302: The requested resource was assigned a different Uniform Resource Identifier (URI). This change is temporary.


message_identifier: 0x8019012d
message_string:
HTTP status 301: The requested resource was assigned to a new permanent Uniform Resource Identifier (URI), and any future references to this resource should use one of the returned URIs.


message_identifier: 0xb000012e
message_string:
The BITS service has started successfully, but it was delayed long enough that there may be a problem. For more information on the delay, enable the analytic log for BITS, then stop and restart the BITS service.


message_identifier: 0x801901f9
message_string:
HTTP status 505: The server does not support the HTTP protocol version that was used in the request ErrorCode.


message_identifier: 0x801900ca
message_string:
HTTP status 202: The request was accepted for processing, but the processing has not been completed yet.


message_identifier: 0x0000426d
message_string:
The BITS service is configured to run as %1. BITS works correctly only when configured to run as the system account.


message_identifier: 0xb0000133
message_string:
It took %1 seconds to write a change file to the BITS job list. If this is excessive, the number of BITS jobs may be larger than this machine can handle quickly.


message_identifier: 0xb0000134
message_string:
The BITS service shut down successfully, but it was delayed for %1 seconds. This might cause delays when you turn off your computer. For more information on the delay, enable the analytic log for BITS, then stop and restart the BITS service.


message_identifier: 0xb0000137
message_string:
The BITS peer transfer with the %1 ID for the %2 transfer job resulted in the following error: %4.


message_identifier: 0x801900cb
message_string:
HTTP status 203: The returned metadata in the entity-header is not the definitive set available from the server of origin.


message_identifier: 0xb00100cb
message_string:
The BITS service provided job credentials in response to the %4 authentication challenge from the %1 server for the %2 transfer job that is associated with the following URL: %3.%nThe credentials for the %5 user were accepted.


message_identifier: 0xb00100cc
message_string:
The BITS service provided job credentials in response to the %4 authentication challenge from the %1 server for the %2 transfer job that is associated with the following URL: %3.%n The credentials for the %5 user were rejected.


message_identifier: 0xb000000e
message_string:
BITS was not able to listen for peer-server announcements.  The error code was %1.  BITS jobs on this machine will not be able to use peer-caching.  To fix this problem, try stopping the BITS service and restarting it.


message_identifier: 0xb000000b
message_string:
BITS was not able to listen for peer-client requests.  The error code was %1.  BITS jobs from other machines will not be able to use this machine as a peer server.  To fix this problem, try stopping the BITS service and restarting it.


message_identifier: 0x80200056
message_string:
The job is configured to use a different security token for some operations, but the token is not currently available.  The application must provide a token and then resume the job.


message_identifier: 0x801901a1
message_string:
HTTP status 417: The server could not meet the expectation given in an Expect request-header field.


message_identifier: 0x8020002b
message_string:
The requested byte range extends beyond the end of the web page.  Use byte ranges that are wholly within the page.


message_identifier: 0x80200054
message_string:
BITS timed out while downloading the job. The download did not complete within the maximum download time set for the job.


message_identifier: 0x80200053
message_string:
The application requested data from a web site, but the response was invalid.                               Using Event Viewer, check the log 'Application Logs \ Microsoft \ Windows \ Bits-client \ Operational' for more details.


message_identifier: 0xb0004007
message_string:
The BITS job list is not in a recognized format.  It may have been created by a different version of BITS.  The job list has been cleared.


message_identifier: 0xb0000012
message_string:
The peer list rejected an incoming server announcement. This event is generated if the request is not valid, not if the server is merely in a different Windows domain.


message_identifier: 0x00200055
message_string:
The configuration preferences were saved successfully, but one or more of them are overridden by Group Policy.


message_identifier: 0x80200022
message_string:
The client and server versions of Background Intelligent Transfer Service (BITS) are incompatible.


message_identifier: 0x80200023
message_string:
Execute permissions are enabled on the Internet Information Services (IIS) virtual directory associated with the remote file specified in the job. To upload files to the virtual directory, disable execute permissions on the virtual directory.


message_identifier: 0x80200020
message_string:
The job is too large for the server to accept. This job might exceed a job size limit set by the server administrator. Reduce the size of the job, and then try again.


message_identifier: 0x801901c1
message_string:
HTTP status 449: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x80200024
message_string:
The job is not making progress.  The server may be misconfigured.  Background Intelligent Transfer Service (BITS) will try again later.


message_identifier: 0xb00000ca
message_string:
While transferring %1, BITS encountered error %7 using %6 as the HTTP proxy server.  The web server or proxy server does not support an HTTP feature required by BITS.  This problem can only be corrected by the adminstrator of the web server or proxy server.  Details: {job: %1}, {owner: %2}, {jobId: %3}, {url: %4}, {xferId: %5}, {proxyServer: %6}, {hr: %7}, {urlContentLength: %8}, {urlHttpVersion: %9}, {urlRange: %10}


message_identifier: 0xb00000cc
message_string:
The BITS service provided job credentials in response to an authentication challenge from %1 for job %2, url %3. The credentials were rejected.


message_identifier: 0xb00000cb
message_string:
The BITS service provided job credentials in response to an authentication challenge from the %1 server for the %2 transfer job that is associated with the following URL: %3.%nThe credentials were accepted.


message_identifier: 0xb000004e
message_string:
BITS has encountered %1 error while reading the peer-cache information. BITS will now attempt to delete and re-create the peer-cache.


message_identifier: 0xb000004f
message_string:
BITS has successfully deleted the peer-cache. All the files cached until this point have been removed. The peer-cache will be re-created again as needed for handling the future requests.


message_identifier: 0x8020000d
message_string:
The destination file system volume is not available. Verify that another program, such as CheckDisk, is not running, which would lock the volume. When the volume is available, Background Intelligent Transfer Service (BITS) will try again.


message_identifier: 0x8020000e
message_string:
The destination volume has changed. If the disk is removable, it might have been replaced with a different disk. Reinsert the original disk and resume the job.


message_identifier: 0x8020000c
message_string:
The error occurred while the notification callback was being processed. Background Intelligent Transfer Service (BITS) will try again later.


message_identifier: 0xb00000c9
message_string:
The BITS job named "%1" was unable to contact any HTTP proxy server in its proxy list.  This may indicate a problem with the proxy servers or with the client's network configuration.  An administrator should verify whether the proxy list is correct.  BITS will periodically try to transfer the job.  The HTTP proxy list is "%6".  The proxy-bypass list is "%7".


message_identifier: 0xb00000c8
message_string:
While transferring %1, BITS encountered error %2 using %3 as the HTTP proxy server.  This may indicate a problem with the proxy server or with the client's network configuration.  If this error occurs frequently, then an administrator should investigate. Details: {Job: %4}, {owner: %5}, {jobid: %6}, {URL: %1}, {xferId: %7}, {proxyServerList: %8}, {hr: %2}.


message_identifier: 0xb0000040
message_string:
The BITS job %1 is configured to launch %3 after transfer of %2. The service failed to launch the program with error %4, BITS will continue trying to launch the program periodically until it succeeds.


message_identifier: 0x80200009
message_string:
The error occurred while the local file was being processed. Verify that the file is not in use, and retry.


message_identifier: 0x801901f6
message_string:
HTTP status 502: The server, while acting as a gateway or proxy to fulfill the request, received an invalid response from the upstream server it accessed.


message_identifier: 0x80200002
message_string:
The requested action is not allowed in the current job state. The job is read-only. The job may have been canceled or completed transferring.


# message_table_97_0x00000415

message_identifier: 0x80060005
message_string:
Sterownik filtru magazynu wirtualnego został wyłączony za pośrednictwem rejestru. Jest nieaktywny dla wszystkich dysków.


# message_table_97_0x00000407

message_identifier: 0x80060004
message_string:
Der Filtertreiber für den virtuellen Speicher ist für den %2-Datenträger am Speicherort (%3) inaktiv.


message_identifier: 0x80060005
message_string:
Der Filtertreiber für den virtuellen Speicher ist in der Registrierung deaktiviert. Er ist für alle Datenträgerlaufwerke inaktiv.


message_identifier: 0x40060003
message_string:
Der Filtertreiber für den virtuellen Speicher ist für den %2-Datenträger am Speicherort (%3) aktiv.


message_identifier: 0x80060002
message_string:
Der Filtertreiber des virtuellen Speichers für den %2-Datenträger (%3) konnte nicht initialisiert werden.


# message_table_97_0x00000405

message_identifier: 0x80060005
message_string:
Ovladač filtru virtuálního úložiště je v registru zakázán. Je neaktivní pro všechny diskové jednotky.


# message_table_97_0x00000410

message_identifier: 0x80060005
message_string:
Driver di filtro dell'archiviazione virtuale disabilitato nel Registro di sistema e non attivo per tutte le unità disco.


# message_table_97_0x00000413

message_identifier: 0x80060005
message_string:
Het stuurprogramma voor het virtuele opslagfilter is uitgeschakeld via het register. Het is niet actief voor alle schijfstations.


message_identifier: 0x80060002
message_string:
Het stuurprogramma voor het virtuele opslagfilter kan niet worden geïnitialiseerd voor schijf %2 (%3).


# message_table_97_0x00000c0a

message_identifier: 0x80060004
message_string:
El controlador de filtro de almacenamiento virtual está inactivo para el disco %2 en la ubicación (%3).


message_identifier: 0x80060005
message_string:
El controlador de filtro de almacenamiento virtual está deshabilitado en el Registro. Está inactivo para todas las unidades de disco.


message_identifier: 0x40060003
message_string:
El controlador de filtro de almacenamiento virtual está activo para el disco %2 en la ubicación (%3).


# message_table_97_0x0000041f

message_identifier: 0x80060005
message_string:
Sanal Depolama Filtre Sürücüsü kayıt defteri kullanılarak devre dışı bırakılmış. Tüm disk sürücüleri için devre dışı.


# message_table_97_0x00000416

message_identifier: 0x80060005
message_string:
O Driver do Filtro de Armazenamento Virtual foi desabilitado por meio do registro e está inativo para todas as unidades de disco.


# message_table_97_0x00000419

message_identifier: 0x80060005
message_string:
Драйвер фильтра виртуального хранилища отключен в реестре. Он неактивен для всех дисковых накопителей.


# message_table_97_0x00000409

message_identifier: 0x80060005
message_string:
The Virtual Storage Filter Driver is disabled through the registry. It is inactive for all disk drives.


# message_table_97_0x0000041d

message_identifier: 0x80060005
message_string:
Den virtuella lagringsfilterdrivrutinen har inaktiverats i registret. Den är inaktiv för alla diskenheter.


# message_table_97_0x0000040e

message_identifier: 0x80060005
message_string:
A virtuális tár szűrőillesztője le van tiltva a beállításjegyzékben. A program minden lemezmeghajtóhoz inaktív.


# message_table_97_0x0000040c

message_identifier: 0x80060005
message_string:
Le pilote de filtre de stockage virtuel est désactivé dans le Registre. Il est inactif pour tous les lecteurs de disques.


# message_table_97_0x00000816

message_identifier: 0x80060004
message_string:
O Controlador de Filtro de Armazenamento Virtual está inactivo para o disco %2 na localização (%3).


message_identifier: 0x80060005
message_string:
O Controlador de Filtro de Armazenamento Virtual está desactivado através do registo. Está inactivo para todas as unidades de disco.


# message_table_98_0x00000409

message_identifier: 0xc000002e
message_string:
This edition of Windows Server cannot support any of the following NPS configurations:%n  - More than 50 RADIUS clients%n  - More than two RADIUS server groups%n  - Client identification by subnet mask%n To set up your server to support any of these configurations, install a Windows Server edition without these limitations.%n


message_identifier: 0x80001133
message_string:
NPS cannot log accounting information in the primary data store (%1). Because of this, NPS is now logging accounting information in the secondary data store. Error information: %2.


message_identifier: 0x80001138
message_string:
NPS cannot log accounting information in the secondary data store (%1). NPS will continue to process connection requests without logging accounting information. Error information: %2.


message_identifier: 0xc0000021
message_string:
The RADIUS Proxy was unable to forward a RADIUS request to remote RADIUS server %1 because of a network error. The error code is %2.


message_identifier: 0x80001135
message_string:
NPS cannot log accounting information in the primary data store (%1). Due to this logging failure, NPS will discard all connection requests. Error information: %2.


message_identifier: 0x80001137
message_string:
NPS cannot log accounting information in the secondary data store (%1). Due to this logging failure, NPS will discard all connection requests. Error information: %2.


message_identifier: 0xc0001005
message_string:
The Network Policy Server was unable to connect to a domain controller in the domain where the account is located. Because of this, authentication and authorization for the RADIUS request could not be performed.


message_identifier: 0xc0001006
message_string:
The NPS server is unavailable because of low hardware resources or because it failed to receive the name of a domain controller, which can be due to a security accounts manager (SAM) database failure on the local computer or an NT directory service (NTDS) failure.


message_identifier: 0x80001134
message_string:
NPS cannot log accounting information in the primary data store (%1). NPS will continue to process connection requests without logging accounting information in this data store. Error information: %2.


message_identifier: 0xc0001003
message_string:
The RADIUS Request message that Network Policy Server received from the network access server was malformed.


message_identifier: 0xc000000a
message_string:
The name, %1, of the RADIUS client, %2, could not be resolved. The data is the error code generated by Windows Sockets.


message_identifier: 0xc000000e
message_string:
A RADIUS message was received from RADIUS client %1 with an invalid authenticator. This is typically caused by mismatched shared secrets. Verify the configuration of the shared secret for the RADIUS client in the Network Policy Server snap-in and the configuration of the network access server.


message_identifier: 0xc0000018
message_string:
The RADIUS Proxy could not resolve the name of remote RADIUS server %1 in remote RADIUS server group %2 to an IP address. The error code is %3.


message_identifier: 0xc0000019
message_string:
The address of remote RADIUS server %1 in remote RADIUS server group %2 resolves to local address %3. The address will be ignored.


message_identifier: 0xc0000014
message_string:
An attribute in the response to RADIUS client %1 exceeds the maximum RADIUS attribute length. The data is the RADIUS attribute type. For more information on the RADIUS attribute type, see RFC 2865 and http://www.isi.edu/in-notes/iana/assignments/radius-types.


message_identifier: 0xc0000016
message_string:
The Network Policy Server (NPS) could not send a response due to a network error. The data is the error code generated by Windows Sockets.


message_identifier: 0xc0000010
message_string:
A RADIUS message with the Code field set to %1, which is not valid, was received on port %2 from RADIUS client %3. Valid values of the RADIUS Code field are documented in RFC 2865.


message_identifier: 0xc0000011
message_string:
An Access-Request message was received from RADIUS client %1 without a Message-Authenticator attribute when a Message-Authenticator attribute is required. Verify the configuration of the RADIUS client in the Network Policy Server snap-in (the "Client must always send the Message-Authenticator attribute in the request" checkbox) and the configuration of the network access server.


message_identifier: 0xc0000012
message_string:
An Access-Request message was received from RADIUS client %1 with a Message-Authenticator attribute that is not valid.


message_identifier: 0xc0000013
message_string:
An Access-Request message was received from RADIUS client %1 with an Extensible Authentication Protocol (EAP) message but no Message-Authenticator attribute.


message_identifier: 0xc0001013
message_string:
The user could not be authenticated using Challenge Handshake Authentication Protocol (CHAP). A reversibly encrypted password does not exist for this user account. To ensure that reversibly encrypted passwords are enabled, check either the domain password policy or the password settings on the user account.


message_identifier: 0xc0001011
message_string:
The user could not change his or her password because the new password did not meet the password requirements for this network.


message_identifier: 0xc0001010
message_string:
Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.


message_identifier: 0xc0001017
message_string:
An error occurred during the Network Policy Server use of the Extensible Authentication Protocol (EAP). Check EAP log files for EAP errors.


message_identifier: 0xc0001016
message_string:
The client could not be authenticated  because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.


message_identifier: 0xc0001015
message_string:
An NPS extension dynamic link library (DLL) that is installed on the NPS server rejected the connection request.


message_identifier: 0xc000001d
message_string:
The RADIUS Proxy received a response from server %1 with an invalid Message-Authenticator attribute.


message_identifier: 0xc000001e
message_string:
The RADIUS Proxy received a response from server %1 with a missing Message-Authenticator attribute.


message_identifier: 0xc000001f
message_string:
The RADIUS Proxy received a response from server %1 with the Code field set to the invalid value of %2. Valid values of the Code field are documented in RFC 2865.


message_identifier: 0x00001139
message_string:
NPS can now access the secondary data store (%1) and is logging accounting information in the data store.


message_identifier: 0x00001136
message_string:
NPS can now access the primary data store (%1) and is logging accounting information in the data store.


message_identifier: 0xc0001060
message_string:
Authentication failed due to an EAP session timeout; the EAP session with the access client was incomplete.


message_identifier: 0xc0001061
message_string:
The authentication request was not processed because it contained a Remote Authentication Dial-In User Service (RADIUS) message that was not appropriate for the secure authentication transaction.


message_identifier: 0xc0001074
message_string:
The local NPS proxy server cannot forward the connection request to the remote RADIUS server because network problems caused a Windows socket error.


message_identifier: 0xc0001076
message_string:
The local NPS proxy server received a RADIUS message that is malformed from a remote RADIUS server, and the message is unreadable. This issue can also be caused if a connection request contains more than the expected number of user-name attributes, or if the user-name attribute value is not valid, such as if the value has zero length or if it contains characters that are not valid.


message_identifier: 0xc0001070
message_string:
The remote RADIUS (Remote Authentication Dial-In User Service) server did not process the authentication request.


message_identifier: 0xc0001073
message_string:
The RADIUS request could not be forwarded to the RADIUS server because the issued packet was invalid.


message_identifier: 0xc0001072
message_string:
The authentication request could not be forwarded to the remote RADIUS (Remote Authentication Dial-In User Service) server because this server is no longer configured from the local server.


message_identifier: 0xc0001040
message_string:
Remote Access Account Lockout is enabled, and the user's authentication attempts have exceeded the designated lockout count because the credentials they supplied (user name and password) are not valid. The user account will be removed from the locked out list on successful authentication or on the expiration of the configured lockout time. To manually reset a locked out account, delete the registry subkey  that corresponds to the user account name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters\AccountLockout\domain name:user name


message_identifier: 0xc0001041
message_string:
The Network Access Permission setting in the dial-in properties of the user account in Active Directory is set to Deny access to the user. To change the Network Access Permission setting to either Allow access or Control access through NPS Network Policy, obtain the properties of the user account in Active Directory Users and Computers, click the Dial-in tab, and change Network Access Permission.


message_identifier: 0xc0001042
message_string:
The user attempted to use an authentication method that is not enabled on the matching network policy.


message_identifier: 0xc0001043
message_string:
The user attempted to connect through either a phone number or calling station that does not match the Caller ID listed for the user account.


message_identifier: 0xc0001044
message_string:
The user or computer does not have permission to access the network on this day at this time. To change the day and time when the user is permitted to connect to the network, change the Day and Time Restrictions in the constraints of the matching network policy.


message_identifier: 0xc0001045
message_string:
The telephone number of the network access server does not match the value of the Called-Station-ID attribute that is configured in the constraints of the matching network policy. NPS denied the Access-Request.


message_identifier: 0xc0001046
message_string:
The network access method used by the access client to connect to the network does not match the value of the NAS-Port-Type attribute that is configured in the constraints of the matching network policy.


message_identifier: 0xc0001048
message_string:
The user's password has expired or is about to expire and the user must change it, but the change password option is not enabled for the matching network policy.


message_identifier: 0xc0001049
message_string:
The user attempted to authenticate using a certificate with an Extended Key Usage or Issuance Policy that is not allowed by the matching network policy.


message_identifier: 0x80000024
message_string:
The remote RADIUS server %1 has not responded to %2 consecutive requests. The server has been marked as unavailable.


message_identifier: 0xc0001050
message_string:
The authentication or accounting record could not be written to the configured accounting datastore. Ensure that the log file location is accessible, has available space, can be written to, and that the directory or SQL server is available.


message_identifier: 0xc0001020
message_string:
The Access-Request message contains a domain user name. NPS is joined to a workgroup and can process connection requests only for local user accounts.


message_identifier: 0xc0001026
message_string:
Authentication failed due to a user account restriction or requirement that was not followed. For example, the user account settings might require the use of a password but the user attempted to log on with a blank password.


message_identifier: 0xc0001024
message_string:
The user's authentication attempts have exceeded the maximum allowed number of failed attempts specified by the account lockout threshold setting in Account Lockout Policy in Group Policy. To unlock the account, edit the user account properties.


message_identifier: 0xc0001025
message_string:
According to Active Directory user account logon hours, the user is not permitted to access the network on this day and time. To change the account logon hours, edit the user account properties in Active Directory.


# message_table_99_0x00000409

message_identifier: 0xc0050006
message_string:
%2: ACPI BIOS does not contain an IRQ for the device in PCI slot %3, function %4. Please contact your system vendor for technical assistance.


message_identifier: 0xc0050004
message_string:
%2: ACPI BIOS is attempting to read from an illegal IO port address (%3), which lies in the %4 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.


message_identifier: 0xc0050005
message_string:
%2: ACPI BIOS is attempting to write to an illegal IO port address (%3), which lies in the %4 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.


message_identifier: 0xc0050002
message_string:
%1: ACPI Name Space Object %2 reports an _HID (%3) that is already in use. Such conflicts are not legal. Please contact your system vendor for technical assistance.


message_identifier: 0xc0050003
message_string:
%1: ACPI BIOS indicates that the machine has suffered a fatal error and needs to be shutdown as quickly as possible. Please contact your system vendor for technical assistance.


message_identifier: 0xc0050001
message_string:
%1: ACPI Name Space Object %2 reports an _ADR (%3) that is already in use. Such conflicts are not legal. Please contact your system vendor for technical assistance.


message_identifier: 0xc0050008
message_string:
%2: ACPI BIOS indicates that device on slot %4, function %5 is attached to an IRQ routing device named %3.  This device cannot be found.


message_identifier: 0xc0050009
message_string:
%2: ACPI BIOS provided an ambiguous entry in the PCI Routing Table (_PRT.)  Illegal _PRT entry is of the form 0x%3%4.


message_identifier: 0xc005000d
message_string:
%1: The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.


message_identifier: 0xc005000e
message_string:
%1: The embedded controller (EC) might not be functioning. Despite additional retries, no requests have been processed. This may cause some components such as thermal sensors or battery meters to stop returning data. This can be corrected by restarting the computer. For a more permanent fix, you should check with your computer manufacturer for an upgraded BIOS.


message_identifier: 0xc005000c
message_string:
%2: ACPI BIOS is attempting to create an illegal memory OpRegion, starting at address %3,  with a length of %4. This region lies in the Operating system's protected memory address range (%5 - %6). This could lead to system instability.  Please contact your system vendor for technical assistance.


message_identifier: 0xc005000a
message_string:
%2: ACPI BIOS is attempting to write to an illegal PCI Operation Region (%3), Please contact your system vendor for technical assistance.


message_identifier: 0x8005000f
message_string:
%1: The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.


message_identifier: 0xc005000b
message_string:
%2: ACPI BIOS is trying to reference a GPE Index (%3) when there are no GPE blocks defined by the BIOS. Please contact your system vendor for technical assistance.


# message_table_100_0x00000409

message_identifier: 0xb20007e6
message_string:
A phase 1 crypto set was deleted from IPsec settings.%n%nDeleted Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tModifying User:%t%3%n%tModifying Application:%t%4


message_identifier: 0xb20007e7
message_string:
A phase 1 crypto set was added to IPsec settings when Windows Firewall started.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tOrigin:%t%4%n%tFlags:%t%6%n%tNumSuites:%t%7%n%tTimeOutMinutes:%t%10%n%tTimeOutSessions:%t%11%n%tModifyingUser:%t%12%n%tModifyingApplication:%t%13


message_identifier: 0xb20007e4
message_string:
A phase 1 crypto set was added to IPsec settings.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tOrigin:%t%4%n%tFlags:%t%6%n%tNumSuites:%t%7%n%tTimeOutMinutes:%t%10%n%tTimeOutSessions:%t%11%n%tModifyingUser:%t%12%n%tModifyingApplication:%t%13


message_identifier: 0xb20007e5
message_string:
A phase 1 crypto set was modified in IPsec settings.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tOrigin:%t%4%n%tFlags:%t%6%n%tNumSuites:%t%7%n%tTimeOutMinutes:%t%10%n%tTimeOutSessions:%t%11%n%tModifyingUser:%t%12%n%tModifyingApplication:%t%13


message_identifier: 0xb20007e2
message_string:
A main mode rule has been deleted in the IPsec settings.%n%nDeleted Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tModifying User:%t%3%n%tModifying Application:%t%4


message_identifier: 0xb20007e3
message_string:
A main mode rule was added to the IPsec settings when Windows Firewall started.%n%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tProfiles:%t%3%n%tEndpoint1:%t%4%n%tEndpoint2:%t%5%n%tPhase1AuthSetId:%t%6%n%tPhase1CryptoSetId:%t%7%n%tFlags:%t%8%n%tActive:%t%9%n%tEmbeddedContext:%t%10%n%tOrigin:%t%11%n%tModifyingUser:%t%12%n%tModifyingApplication:%t%13


message_identifier: 0xb20007e0
message_string:
A main mode rule has been added in the IPsec settings.%n%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tProfiles:%t%3%n%tEndpoint1:%t%4%n%tEndpoint2:%t%5%n%tPhase1AuthSetId:%t%6%n%tPhase1CryptoSetId:%t%7%n%tFlags:%t%8%n%tActive:%t%9%n%tEmbeddedContext:%t%10%n%tOrigin:%t%11%n%tModifyingUser:%t%12%n%tModifyingApplication:%t%13


message_identifier: 0xb20007e1
message_string:
A main mode rule has been modified in the IPsec settings.%n%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tProfiles:%t%3%n%tEndpoint1:%t%4%n%tEndpoint2:%t%5%n%tPhase1AuthSetId:%t%6%n%tPhase1CryptoSetId:%t%7%n%tFlags:%t%8%n%tActive:%t%9%n%tEmbeddedContext:%t%10%n%tOrigin:%t%11%n%tModifyingUser:%t%12%n%tModifyingApplication:%t%13


message_identifier: 0xb20007e8
message_string:
A phase 2 crypto set was added to IPsec settings.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tOrigin:%t%4%n%tPfs:%t%6%n%tNumSuites:%t%7%n%tModifyingUser:%t%10%n%tModifyingApplication:%t%11


message_identifier: 0xb20007e9
message_string:
A phase 2 crypto set was modified in IPsec settings.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tOrigin:%t%4%n%tPfs:%t%6%n%tNumSuites:%t%7%n%tModifyingUser:%t%10%n%tModifyingApplication:%t%11


message_identifier: 0xb20007de
message_string:
A connection security rule was deleted from IPsec settings.%n%nDeleted Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tModifying User:%t%3%n%tModifying Application:%t%4


message_identifier: 0xb20007dd
message_string:
A connection security rule was modified in IPsec settings.%n%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tOrigin:%t%3%n%tActive:%t%4%n%tProtocol:%t%5%n%tEndPoint1Ports:%t%6%n%tEndPoint2Ports:%t%7%n%tLocalTunnelEndpointV4:%t%8%n%tLocalTunnelEndpointV6:%t%9%n%tRemoteTunnelEndpointV4:%t%10%n%tRemoteTunnelEndpointV6:%t%11%n%tPhase1AuthSetId:%t%12%n%tPhase2AuthSetId:%t%13%n%tPhase2CryptoSetId:%t%14%n%tAction:%t%15%n%tProfiles:%t%16%n%tLocalAddresses:%t%17%n%tRemoteAddresses:%t%18%n%tEmbeddedContext:%t%20%n%tIsDTM:%t%22%n%tApplyAuthZ:%t%23%n%tBypassTunnelIfEncrypted:%t%24%n%tNoIPSecOnOutbound:%t%25%n%tModifyingUser:%t%26%n%tModifyingApplication:%t%27


message_identifier: 0xb20007df
message_string:
A connection security rule was added to IPsec settings when Windows Firewall started.%n%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tOrigin:%t%3%n%tActive:%t%4%n%tProtocol:%t%5%n%tEndPoint1Ports:%t%6%n%tEndPoint2Ports:%t%7%n%tLocalTunnelEndpointV4:%t%8%n%tLocalTunnelEndpointV6:%t%9%n%tRemoteTunnelEndpointV4:%t%10%n%tRemoteTunnelEndpointV6:%t%11%n%tPhase1AuthSetId:%t%12%n%tPhase2AuthSetId:%t%13%n%tPhase2CryptoSetId:%t%14%n%tAction:%t%15%n%tProfiles:%t%16%n%tLocalAddresses:%t%17%n%tRemoteAddresses:%t%18%n%tEmbeddedContext:%t%20%n%tIsDTM:%t%22%n%tApplyAuthZ:%t%23%n%tBypassTunnelIfEncrypted:%t%24%n%tNoIPSecOnOutbound:%t%25%n%tModifyingUser:%t%26%n%tModifyingApplication:%t%27


message_identifier: 0xb20007da
message_string:
Network profile changed on an interface.%n%nAdapter GUID:%t%1%nAdapter Name:%t%2%nOld Profile:%t%3%nNew Profile:%t%4


message_identifier: 0xb20007dc
message_string:
A connection security rule was added to IPsec settings.%n%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tOrigin:%t%3%n%tActive:%t%4%n%tProtocol:%t%5%n%tEndPoint1Ports:%t%6%n%tEndPoint2Ports:%t%7%n%tLocalTunnelEndpointV4:%t%8%n%tLocalTunnelEndpointV6:%t%9%n%tRemoteTunnelEndpointV4:%t%10%n%tRemoteTunnelEndpointV6:%t%11%n%tPhase1AuthSetId:%t%12%n%tPhase2AuthSetId:%t%13%n%tPhase2CryptoSetId:%t%14%n%tAction:%t%15%n%tProfiles:%t%16%n%tLocalAddresses:%t%17%n%tRemoteAddresses:%t%18%n%tEmbeddedContext:%t%20%n%tIsDTM:%t%22%n%tApplyAuthZ:%t%23%n%tBypassTunnelIfEncrypted:%t%24%n%tNoIPSecOnOutbound:%t%25%n%tModifyingUser:%t%26%n%tModifyingApplication:%t%27


message_identifier: 0xb20007db
message_string:
Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network.%n%nReason:%t%t%1%nApplication Path:%t%2%nIP Version:%t%3%nProtocol:%t%4%nPort:%t%t%5%nProcess Id:%t%6%nUser:%t%t%7


message_identifier: 0xb20007d5
message_string:
A rule has been modified in the Windows Firewall exception list.%n%nModified Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tOrigin:%t%3%n%tActive:%t%18%n%tDirection:%t%6%n%tProfiles:%t%11%n%tAction:%t%10%n%tApplication Path:%t%4%n%tService Name:%t%5%n%tProtocol:%t%7%n%tSecurity Options:%t%21%n%tEdge Traversal:%t%19%n%tModifying User:%t%22%n%tModifying Application:%t%23


message_identifier: 0xb20007d4
message_string:
A rule has been added to the Windows Firewall exception list.%n%nAdded Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tOrigin:%t%3%n%tActive:%t%18%n%tDirection:%t%6%n%tProfiles:%t%11%n%tAction:%t%10%n%tApplication Path:%t%4%n%tService Name:%t%5%n%tProtocol:%t%7%n%tSecurity Options:%t%21%n%tEdge Traversal:%t%19%n%tModifying User:%t%22%n%tModifying Application:%t%23


message_identifier: 0xb20007d7
message_string:
A rule has been listed when the Windows Firewall started.%n%nAdded Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tOrigin:%t%3%n%tActive:%t%18%n%tDirection:%t%6%n%tProfiles:%t%11%n%tAction:%t%10%n%tApplication Path:%t%4%n%tService Name:%t%5%n%tProtocol:%t%7%n%tSecurity Options:%t%21%n%tEdge Traversal:%t%19


message_identifier: 0xb20007d6
message_string:
A rule has been deleted in the Windows Firewall exception list.%n%nDeleted Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tModifying User:%t%3%n%tModifying Application:%t%4


message_identifier: 0xb20007d1
message_string:
The following per profile settings were applied by Windows Firewall %n%n%tProfile:%t%1%n%tOperational Mode:%t%2%n%tStealth Mode:%t%3%n%tBlock all Incoming Connections:%t%4%n%tUnicast response to multicast broadcast:%t%5%n%tLog dropped packets:%t%6%n%tLog successful connections:%t%7%n%tLog ignored rules:%t%8%n%tInbound Notifications:%t%9%n%tAllow Local Policy Merge:%t%12%n%tAllow Local IPsec Policy Merge:%t%13%n%tDefault Outbound Action:%t%14%n%tDefault Inbound Action:%t%15%n%tRemote Administration:%t%16%n%tMaximum Log file size:%t%17%n%tLog File path:%t%18%n%tAllow User preferred merge of Authorized Applications:%t%10%n%tAllow User preferred merge of Globally open ports:%t%11


message_identifier: 0xb20007d0
message_string:
The following settings were applied to the Windows Firewall at startup%n%n%tCurrent Profile:%t%1%n%tIPsec SA Idle time:%t%2%n%tIPsec preshared key encoding:%t%3%n%tIPsec Exempt:%t%4%n%tIPsec CRL Check:%t%5%n%tIPsec Through NAT:%t%6%n%tPolicy Version Supported:%t%7%n%tPolicy Version:%t%8%n%tBinary Version Supported:%t%9%n%tStateful FTP:%t%10%n%tGroup Policy Applied:%t%11%n%tRemote Machine Authorization List:%t%12%n%tRemote UserAuthorization List:%t%13


message_identifier: 0xb20007d3
message_string:
A Windows Firewall setting in the %1 profile has changed.%nNew Setting:%n%tType:%t%2%n%tValue:%t%5%n%tModifying User:%t%7%n%tModifying Application:%t%8


message_identifier: 0xb20007d2
message_string:
A Windows Firewall setting has changed.%n%nNew Setting:%n%tType:%t%1%n%tValue:%t%4%n%tModifying User:%t%6%n%tModifying Application:%t%7


message_identifier: 0xb20007ef
message_string:
An authentication set has been added to IPsec settings when Windows Firewall started.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tIPsec Phase:%t%3%n%tOrigin:%t%5%n%tNumSuites:%t%7%n%tModifyingUser:%t%10%n%tModifyingApplication:%t%11


message_identifier: 0xb20007ed
message_string:
An authentication set has been modified in IPsec settings.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tIPsec Phase:%t%3%n%tOrigin:%t%5%n%tNumSuites:%t%7%n%tModifyingUser:%t%10%n%tModifyingApplication:%t%11


message_identifier: 0xb20007ee
message_string:
An authentication set has been deleted from IPsec settings.%n%nDeleted Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tModifying User:%t%3%n%tModifying Application:%t%4


message_identifier: 0xb20007eb
message_string:
A phase 2 crypto set was added to IPsec settings when Windows Firewall started.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tOrigin:%t%4%n%tPfs:%t%6%n%tNumSuites:%t%7%n%tModifyingUser:%t%10%n%tModifyingApplication:%t%11


message_identifier: 0xb20007ec
message_string:
An authentication set has been added to IPsec settings.%n%n%tSet ID:%t%1%n%tSet Name:%t%2%n%tIPsec Phase:%t%3%n%tOrigin:%t%5%n%tNumSuites:%t%7%n%tModifyingUser:%t%10%n%tModifyingApplication:%t%11


message_identifier: 0xb20007ea
message_string:
A phase 2 crypto set was deleted from IPsec settings.%n%nDeleted Rule:%n%tRule ID:%t%1%n%tRule Name:%t%2%n%tModifying User:%t%3%n%tModifying Application:%t%4


message_identifier: 0xb20007f6
message_string:
Windows Firewall did not apply the following rule because the rule was not properly configured on this computer:%n%nRule Information:%n%tID:%t%1%n%tName:%t%2%n%nError Information:%n%tReason:%t%3


message_identifier: 0xb20007f5
message_string:
All crypto sets have been deleted from the IPsec configuration on this computer.%n%n%tIPsec Phase:%t%1%n%tStore Type:%t%2%n%tModifyingUser:%t%3%n%tModifyingApplication:%t%4


message_identifier: 0xb20007f4
message_string:
All authentication sets have been deleted from the IPsec configuration on this computer.%n%n%tIPsec Phase:%t%1%n%tStore Type:%t%2%n%tModifyingUser:%t%3%n%tModifyingApplication:%t%4


message_identifier: 0xb20007f3
message_string:
All main mode rules have been deleted from the IPsec configuration on this computer.%n%n%tStore Type:%t%1%n%tModifyingUser:%t%2%n%tModifyingApplication:%t%3


message_identifier: 0xb20007f2
message_string:
All connection security rules have been deleted from the IPsec configuration on this computer.%n%n%tStore Type:%t%1%n%tModifyingUser:%t%2%n%tModifyingApplication:%t%3


message_identifier: 0xb20007f1
message_string:
All rules have been deleted from the Windows Firewall configuration on this computer.%n%n%tStore Type:%t%1%n%tModifyingUser:%t%2%n%tModifyingApplication:%t%3


message_identifier: 0xb20007f0
message_string:
Windows Firewall has been reset to its default configuration.%n%n%tModifyingUser:%t%1%n%tModifyingApplication:%t%2


message_identifier: 0xd2000061
message_string:
Require authentication for inbound connections and request authentication for outbound connections


message_identifier: 0x04001900
message_string:
An attempt to programmatically disable the Windows Firewall using a call to INetFwProfile.FirewallEnabled(FALSE) interface was rejected because this API is not supported on Windows Vista. This has most likely occurred due to an application which is incompatible with Windows Vista. Please contact the application's vendor to make sure you have a Windows Vista compatible application version.%n%nError Code:%t%tE_NOTIMPL%nCaller Process Name:%t%1%nProcess Id:%t%t%2%nPublisher:%t%t%3


# message_table_101_0x00000409

message_identifier: 0xc0050003
message_string:
The raw port address could not be translated to something the memory management system understands.


# message_table_102_0x00000409

message_identifier: 0x80080011
message_string:
%1 is currently in a degraded state. One or more paths have failed, though the process is
now complete.


message_identifier: 0x80080014
message_string:
A Path Verification request to a device on %1 that is controlled by %2 has failed. This may
indicate a Path Failure.


message_identifier: 0xc008001a
message_string:
Reference counts on either %1 or an object controller by it are incorrect. Removal of this object will not be possible.


# message_table_103_0x00000409

message_identifier: 0x0000006a
message_string:
Application %1 from policy %2 was configured to upgrade application %3 from policy %4.  The removal
of application %3 from policy %4 failed with error : %%%5  The upgrade will be aborted.


message_identifier: 0x0000006b
message_string:
The execution of the setup program for application %1 from policy %2 failed.  The setup
path was %3 and the error was : %%%4


message_identifier: 0x0000006d
message_string:
Application %1 from policy %2 was configured to upgrade application %3 from policy %4.  The assignment or 
install of the upgrade application %1 from policy %2 failed with error : %%%5  The upgrade will be aborted.


message_identifier: 0x0000006e
message_string:
Application of software installation policy settings was aborted due to an error in determining the settings
to be applied. A previous event log record was logged containing details of the error.


message_identifier: 0x000000c9
message_string:
Application %1 from policy %2 is an upgrade of application %3 from policy %4 and
will force application %3 to be removed.


message_identifier: 0x00000096
message_string:
A network error occurred accessing software installation data in the active directory.  The error was : %%%1


message_identifier: 0x000000cc
message_string:
Resultant Set of Policy data for software installation policy settings could not be logged.  The error status was : %1


message_identifier: 0x000000cb
message_string:
Application %1 from policy %2 was configured to remove any unmanaged install
before being assigned.  An unmanaged install was found and will be removed.


message_identifier: 0x000000ca
message_string:
Application %1 from policy %2 is an upgrade of application %3 from policy %4 and
will cause the assignment of application %3 to be removed.


# message_table_107_0x00000409

message_identifier: 0xc000000b
message_string:
The Distinguished Name in the subject field of your smartcard logon certificate does not contain enough information to locate the appropriate domain on an unjoined machine. Please contact your system administrator.


message_identifier: 0x80000003
message_string:
A Kerberos Error Message was received:%n on logon session %1%n Client Time: %2%n Server Time: %3%n Error Code: %4 %5%n Extended Error: %6%n Client Realm: %7%n Client Name: %8%n Server Realm: %9%n Server Name: %10%n Target Name: %11%n Error Text: %12%n File: %13%n Line: %14%n Error Data is in record data.


message_identifier: 0x40000004
message_string:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server %1. The target name used was %3. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (%2) is different from the client domain (%4), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.


message_identifier: 0x40000005
message_string:
The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server %1. This indicates that the ticket used against that server is not yet valid (in relationship to that server time).  Contact your system administrator to make sure the client and server times are in sync, and that the KDC in realm %2 is in sync with the KDC in the client realm.


message_identifier: 0x80000006
message_string:
The kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size %2 bytes, provided by process id %3.%n %n The output SSPI token being too large is probably the result of the user %4 being a member of a large number of groups.%n %n It is recommended to minimize the number of groups a user belongs to. If the problem can not be corrected by reduction of the group memberships of this user, please contact your system administrator to increase the maximum token size, which in term is configured machine-wide via the following registry value: HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\MaxTokenSize.


message_identifier: 0xc0000011
message_string:
The kerberos SSPI package failed to locate the forest or domain %1 to search.  Please ensure that the forest search order policy is correctly configured, and that this forest or domain is available.


message_identifier: 0xc0000010
message_string:
The kerberos SSPI package failed to find the smartcard certificate in the certificate store. To remedy, logon as user %1 and insert the smartcard into your smartcard reader, then use the Certificates snap-in to verify that the smartcard certificate is in the user's personal certificate store.


message_identifier: 0x00010009
message_string:
An error occurred while verifying the digital certificate retrieved from the inserted smart card: %1


message_identifier: 0x8000000c
message_string:
While using your smartcard over a VPN connection, the Kerberos subsystem encountered an error. Typically, this indicates the card has been pulled from the reader during the VPN session. One possible solution is to close the VPN connection, reinsert the card, and restablish the connection.


message_identifier: 0x8000000a
message_string:
The kerberos subsystem is having problems fetching tickets from your domain controller using the UDP network protocol. This is typically due to network problems. Please contact your system administrator.


message_identifier: 0x8000000f
message_string:
The kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size %2 bytes, provided by process id %3.%n %n The application needs to be fixed to supply a token buffer of size at least %4 bytes.


message_identifier: 0x8000000d
message_string:
The smartcard PIN stored in Credential Manager is missing or invalid. The smartcard PIN is stored in memory only for the current interactive logon session, and is deleted if the card is removed from the reader or when the user logs off. To resolve this error, keep the card in the reader, open Credential Manager in Control Panel, and reenter the PIN for the credential %1.


message_identifier: 0x8000000e
message_string:
The password stored in Credential Manager is invalid. This might be caused by the user changing the password from this computer or a different computer. To resolve this error, open Credential Manager in Control Panel, and reenter the password for the credential %1.


message_identifier: 0xc0000007
message_string:
The digitally signed Privilege Attribute Certificate (PAC) that contains the authorization information for client %1 in realm %2 could not be validated.%n %n This error is usually caused by domain trust failures; please contact your system administrator.


message_identifier: 0xc0000009
message_string:
The client has failed to validate the Domain Controller certificate for %2. The following error was returned from the certificate validation process: %1.


message_identifier: 0xc0000008
message_string:
The Domain Controller rejected the client certificate of user %2, used for smartcard logon. The following error was returned from the certificate validation process: %1.


# message_table_108_0x00000409

message_identifier: 0xb000c756
message_string:
An error occurred in extracting options from the message received in the adapter %1. Status code is %2


message_identifier: 0xb000c75e
message_string:
The information refresh time has expired, hence triggering a new inform packet on the interface %1.


message_identifier: 0xb00003ee
message_string:
Router Advertisement settings have been changed on the network adapter %1. The current M - Managed Address Configuration flag is %2 and the O - Other Stateful Configuration flag is %3. User Action: If you are seeing this event frequently, then it could be due to frequent change in M and O flag settings on the router in the network. Please contact your network administrator to have it resolved.


message_identifier: 0xb000c742
message_string:
A valid reply is received for request from the adapter %1. Status code is %2. Received address is %3


# message_table_109_0x00000409

message_identifier: 0x000003ed
message_string:
Network device %1 was not successfully added to the system. The system limit of Physical Device Objects has been reached for this bus enumerator. No additional devices can be installed on the system.


message_identifier: 0x000003ee
message_string:
Network device %1 was not successfully added to the system. The system limit of child Physical Device Objects has been reached for this device. No additional child devices can be installed for this device.


# message_table_111_0x00000409

message_identifier: 0xc0050010
message_string:
%2: The client device is not able to bind to this driver because the system is running out of memory.


# message_table_112_0x00000409

message_identifier: 0xb0000005
message_string:
WHEA successfully initialized.%n   %1 error sources are active%n   Error record format version is %2.


message_identifier: 0xb0000007
message_string:
Machine Check Event reported is a memory hierarchy error.%n Trasaction Type: %1%n Memory Hierarchy Level: %5%n Request Type: %3%n Address: %6


message_identifier: 0xb0000009
message_string:
Machine Check Event reported is a TLB error.%n Transaction Type: %1%n Memory Hierarchy Level: %5%n Address: %6


message_identifier: 0x00000012
message_string:
PCI Express reported a fatal error.%n Device Identifier: Bus %1 Device %2 Function %3%n Uncorrectable Error Status: %4%n Correctable Error Status: %5%n Header Log: %6 %7 %8 %9


message_identifier: 0xd0000008
message_string:
The page is listed in the boot configuration data store as defective, and will not be used by the operating system after a reboot.


message_identifier: 0xd0000007
message_string:
The page is not listed in the boot configuration data store as defective, and will be used by the operating system after a reboot.


message_identifier: 0x0000000c
message_string:
Machine Check Event reported is a fatal Bus or Interconnect timeout error.%n Memory Hierarchy Level: %5%n Participation: %2%n Request Type: %3%n Memory/IO: %4%n Address: %6


message_identifier: 0x0000000a
message_string:
Machine Check Event reported is a fatal Bus or Interconnect error.%n Memory Hierarchy Level: %5%n Participation: %2%n Request Type: %3%n Memory/IO: %4%n Address: %6


message_identifier: 0xb0000013
message_string:
PCI Express reported a non-fatal error.%n Device Identifier: Bus %1 Device %2 Function %3%n Uncorrectable Error Status: %4%n Correctable Error Status: %5%n Header Log: %6 %7 %8 %9


message_identifier: 0xb000000d
message_string:
Machine Check Event reported is a Bus or Interconnect timeout error.%n Memory Hierarchy Level: %5%n Participation: %2%n Request Type: %3%n Memory/IO: %4%n Address: %6


message_identifier: 0xb000000b
message_string:
Machine Check Event reported is a Bus or Interconnect error.%n Memory Hierarchy Level: %5%n Participation: %2%n Request Type: %3%n Memory/IO: %4%n Address: %6


message_identifier: 0x00000006
message_string:
Machine Check Event reported is a fatal memory hierarchy error.%n Trasaction Type: %1%n Memory Hierarchy Level: %5%n Request Type: %3%n Address: %6


message_identifier: 0x00000008
message_string:
Machine Check Event reported is a fatal TLB error.%n Transaction Type: %1%n Memory Hierarchy Level: %5%n Address: %6


# message_table_118_0x00000409

message_identifier: 0x000003ec
message_string:
The metadata of element %1 is too large.  The maximum allowed size is 2048 bytes.  Reduce the size of the metadata of element %1.


message_identifier: 0x000003ea
message_string:
Element %1 failed to publish.  Ensure that both PKEY_PUBSVCS_METADATA and PKEY_PUBSVCS_TYPE are set properly on the function instance and there were no errors adding the function instance.


message_identifier: 0x000003e8
message_string:
Element %1 could not be published because the maximum number of 20 published elements has been reached. Reduce the number of published elements or remove %1 from publication.


message_identifier: 0xb0000067
message_string:
The service stopped publishing because the default computer information has been removed.  The user has elected to opt out of publishing on this computer.


message_identifier: 0x000003e9
message_string:
The metadata of element %1 would cause the total published metadata to be more than 32k, which is the maximum allowable size for all published elements. Reduce the number of published elements, remove %1 from publication, or reduce the size of the metadata of element %1.


# message_table_119_0x00000409

message_identifier: 0xb0017530
message_string:
A driver package which uses user-mode driver framework version %2 is being installed on device %1.


message_identifier: 0xb001083a
message_string:
Received a Pnp or Power operation (%3, %4) for device %2 which was completed by the lower drivers with status %9


message_identifier: 0x0000277f
message_string:
The device %2 (location %3) is offline due to a user-mode driver crash.  Windows will attempt to restart the device %5 more times.  Please contact the device manufacturer for more information about this problem.


message_identifier: 0x0000277e
message_string:
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.


message_identifier: 0xb0010836
message_string:
Forwarded a finished Pnp or Power operation (%3, %4) to the lower driver for device %2 with status %9.


message_identifier: 0x00002782
message_string:
The UMDF reflector was unable to complete startup because the %2 service was not found.  This service may be started later during boot, at which point Windows will attempt to start the device again.


message_identifier: 0x00002781
message_string:
The device %2 was unable to start due to conflict between the settings for driver %5 (%3 - %4) and the other drivers.  Windows will not be able to start this device.  Please contact the device manufacturer for assistance.


message_identifier: 0x00002780
message_string:
The device %2 (location %3) is offline due to a user-mode device crash.  Windows will no longer attempt to restart this device because the maximum restart limit has been reached.  Disconnecting the device and reconnecting it, or disabling it and re-enabling it from the device manager, will reset this limit and allow the device to be accessed again.  Please contact the device manufacturer for more information about this problem.


# message_table_120_0x00000409

message_identifier: 0x00004002
message_string:
An error occurred while TBS was processing power management event.  The power management event was %1, and the error code was %2.


message_identifier: 0x00000219
message_string:
A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer.  TBS could not be started.


message_identifier: 0x00004001
message_string:
An internal TBS error was detected.  The error code was %1.  This is usually caused by unexpected TPM or driver behavior and may be transient.


message_identifier: 0x0000021a
message_string:
A compatible TPM is not found.  TBS requires TPM version %1 or greater, but the version of the TPM on the computer is %2.


# message_table_121_0x00000409

message_identifier: 0x000003eb
message_string:
Certificate Services Client  failed to invoke the Providers in response to event %1. Error code %2.


# message_table_122_0x00000409

message_identifier: 0x0000006a
message_string:
Software Installation was unable to parse the ZAP file %2.  The following error was encountered: %1


message_identifier: 0x0000006b
message_string:
Software Installation was unable to read the MSI file %2.  The following error was encountered: %1


message_identifier: 0x0000006c
message_string:
Software Installation was unable to remove the package %2.  The following error was encountered: %1


message_identifier: 0x0000006e
message_string:
Software Installation was unable to generate the script for %2.  The following error was encountered: %1


message_identifier: 0x0000006f
message_string:
Software Installation was unable to secure a GUID for new category %2.  The following error was encountered: %1


message_identifier: 0x00000077
message_string:
Software Installation encountered an unexpected error while reading from the MSI file %2.  The error was not serious enough to justify halting the operation.  The following error was encountered: %1


message_identifier: 0x00000076
message_string:
Software Installation was unable to retrieve the list of categories from the DC.  The following error was encountered: %1


message_identifier: 0x00000068
message_string:
Software Installation was unable to obtain access to the DS.  The following error was encountered: %1


message_identifier: 0x00000069
message_string:
Software Installation was unable to add the package %2 to the DS.  The following error was encountered: %1


# message_table_124_0x00000409

message_identifier: 0x00004004
message_string:
Failed to delete shadow copy %2 on volume %1.

VSS error:  %3

User action
Retry the deletion or examine the event log for related VSS entries.


message_identifier: 0x00004002
message_string:
The disabled writers registry value includes a value that is not a
valid GUID.  This will be ignored.

Registry:  HKEY_LOCAL_MACHINE\%1\%2
Value:     %3

User Action
Modify the invalid GUID in the registry.  An example of a valid GUID is
{DFEA1968-8C43-45B1-A298-627435BDC254}.


message_identifier: 0x00004001
message_string:
The disabled writers registry value includes a GUID that is associated with
a writer that cannot be disabled.  This will be ignored and the writer will not
be disabled.

Registry:  HKEY_LOCAL_MACHINE\%1\%2
GUID:      %3

User Action
Remove the GUID from the registry value.


# message_table_125_0x00000409

message_identifier: 0x00001003
message_string:
Attempt to install control %1 failed. The policy settings for host URL %2 do not allow the control to be installed


# message_table_126_0x00000409

message_identifier: 0x000005fe
message_string:
There are too many profile copy errors. Refer to the previous events for details. Windows will not log any additional copy errors for this copy process. %n%n


message_identifier: 0x000005e5
message_string:
Windows cannot copy file %1 to location %2. This error may be caused by network problems or insufficient security rights. %n%n DETAIL - %3


# message_table_127_0x00000402

message_identifier: 0x00000011
message_string:
Създаването/промяната на задачата за проверка за оригинален софтуер не завърши успешно. %n hr = %1


# message_table_127_0x0000041f

message_identifier: 0x00000009
message_string:
Bilgisayarın yeniden başlatılmasını gerektiren iyileştirme denemesinden sonra bilgisayar yeniden başlatıldı. %n


# message_table_127_0x00000415

message_identifier: 0x00000009
message_string:
Ten komputer został ponownie uruchomiony po próbie naprawiania, która wymagała ponownego uruchomienia komputera. %n


# message_table_127_0x0000040b

message_identifier: 0x00000009
message_string:
Tietokone käynnistettiin uudelleen uudelleenkäynnistystä edellyttävän korjausyrityksen jälkeen. %n


# message_table_127_0x0000040c

message_identifier: 0x00000012
message_string:
Planification de la notification d'activation des licences modifiée. %n Type de planification : %1


message_identifier: 0x0000000b
message_string:
Les données de validation de l'authenticité ont été correctement envoyées vers la synchronisation automatique de version. %n


message_identifier: 0x0000000f
message_string:
La planification de la validation de l'authenticité a été créée/modifiée. %n Intervalle : %1 minutes


# message_table_128_0x00000409

message_identifier: 0x00000003
message_string:
Usage: 
   xwizard ProcessXMLFile [/u] [/m] <filename> 
where:
   /u = unattended (log parsing errors instead of showing them)
   /m = additionally generate Vista setup manifest file section
        (create resulting file in current directory as <filename>.man)
   filename = XML file name
examples:
   xwizard ProcessXMLFile myconfig.xml
   xwizard ProcessXMLFile /m mysetup.xml


message_identifier: 0x0000000d
message_string:
Usage: 
   xwizard RunWizard [/u] [/t<?>] [/c<?>] [/f<?>] [/p<GUID>] <GUID> [/z [<?>] ]
where:
   /u = unattended (log errors instead of showing them)
   /t = optional wizard type (duifixed, duiresize, wizard97, aerofixed, aeroresize)
   /c = context flags
   /f = user defined flags
   /p = parent host GUID identifier ({<GUID>})
   GUID = Wizard component GUID identifier ({<GUID>})
   /z = user command line (should always be last, rest of line)
examples:
   xwizard RunWizard {7071ECA0-663B-4bc1-A1FA-B97F3B917C55}
   xwizard RunWizard /taerofixed /c1 /f3 {7071ECA0-663B-4bc1-A1FA-B97F3B917C55} /z/myoption1 /myoption2


message_identifier: 0x0000000e
message_string:
Usage: 
   xwizard RunPropertySheet [/u] [/c<?>] [/f<?>] [/p<GUID>] <GUID> [/z [<?>] ]
where:
   /u = unattended (log errors instead of showing them)
   /c = context flags
   /f = user defined flags
   /p = parent host GUID identifier ({<GUID>})
   GUID = Property sheet component GUID identifier ({<GUID>})
   /z = user command line (should always be last, rest of line)
examples:
   xwizard RunPropertySheet {7071ECA0-663B-4bc1-A1FA-B97F3B917C55}
   xwizard RunPropertySheet /c1 /f3 {7071ECA0-663B-4bc1-A1FA-B97F3B917C55} /z/myoption1 /myoption2


# message_table_129_0x00000409

message_identifier: 0xb0000009
message_string:
There was a problem interacting with COM object %1.  An outdated version might be installed, or the component might not be installed at all.


message_identifier: 0xb0010011
message_string:
The Remote Assistance password provided was incorrect.  The RDP session was terminated, IP address of the connecting machine is %1


message_identifier: 0xb0000027
message_string:
There was a problem interacting with the PNRP service.  This component might not be installed correctly. The error code received was: %1


message_identifier: 0xb0000017
message_string:
Remote Assistance detected that it didn't restore the background and screen settings before shutting down.  An attempt was made to restore these settings.


message_identifier: 0xb0000014
message_string:
The Remote Assistance invitation was closed, any information concerning it given out is now invalid.


message_identifier: 0xb000000a
message_string:
A user tried to use Remote Assistance and send an invitation for help through their default e-mail client, but Remote Assistance failed to successfully send the invitation.  It is possible the e-mail client configured as the default client does not support SMAPI calls, or that the e-mail client is improperly configured.  It is also possible that the user closed the e-mail client without sending the message.


message_identifier: 0xb000000b
message_string:
A user opened a Remote Assistance invitation, but the invitation was closed due to too many bad password attempts to connect to the machine.


message_identifier: 0xb000000c
message_string:
A user tried to use Remote Assistance, group policy requires a session log to be maintained, and a session log couldn't be created.  Remote Assistance was terminated.  Check the disk to see if there are problems with the disk or if it is full.


message_identifier: 0xb000001c
message_string:
The Windows firewall has been checked and it appears that it is configured so that it will stop Remote Assistance from working.


message_identifier: 0xb000001b
message_string:
The system or GP settings do not allow a helper to share control.  This action has been blocked by the application.


message_identifier: 0xb000001a
message_string:
The system or GP settings do not allow an Remote Assistance invitation to be created.  This action has been blocked by the application.


# message_table_130_0x00000409

message_identifier: 0x8000000f
message_string:
Automatic certificate enrollment for %1 failed to contact the active directory (%2). %3 Enrollment will not be performed.


message_identifier: 0x40000001
message_string:
Automatic certificate enrollment for %1 failed to download certificates for %2 store from %3 (%4). %5


# message_table_131_0x00000409

message_identifier: 0x810000f8
message_string:
A system image cannot be saved to the current backup location. Change your backup settings and select a different backup location.


message_identifier: 0x81000038
message_string:
Windows Backup encountered a problem while determining additional locations of one of the users included in backup.


message_identifier: 0x81000032
message_string:
Windows Backup skipped backing up system image because one of the critical volumes cannot be included for backup. Check that volume is online and is formatted NTFS.


message_identifier: 0x81000033
message_string:
Windows Backup skipped backing up system image because one of the critical volumes is not having enough free space. Free up some space by deleting unnecessary files and try again.


message_identifier: 0x81000031
message_string:
Windows Backup failed while determining libraries location of one of the users included in backup.


message_identifier: 0x81000037
message_string:
Windows Backup failed while trying to read from the shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors.


message_identifier: 0x81000035
message_string:
Windows Backup encountered invalid MediaID.bin file on the drive where the backup is saved. Restore from a different backup or delete the MediaID.bin file and try to create another backup. The MediaID.bin file can be found under <backup location>\MediaId.Bin & <backup location>\<machine-name-folder>\MediaId.Bin.


message_identifier: 0x810000f5
message_string:
Backing up to the current location is not allowed by your system administrator.
Select a different backup location.


message_identifier: 0x810000f7
message_string:
Windows Backup is currently busy doing a backup, restore or deletion.  Please wait or close the other window.


message_identifier: 0x810000f1
message_string:
There is a problem with the backup catalog. Restore from a different backup or create new, full backup.


message_identifier: 0x810000f3
message_string:
The backup cannot finish because another program is accessing temporary files used by the backup process. 
Stop or close any anti-virus programs on the drive where Windows is installed and also on the backup target location. Then try the backup again.


message_identifier: 0x810000eb
message_string:
The backup catalog is corrupt or was created with a different version of Windows. Restore from a different backup or create a new, full backup.


message_identifier: 0x810000ec
message_string:
There is a problem with the backup catalog. Log on as an administrator and try to restore files again.


message_identifier: 0x810000ee
message_string:
Windows Backup has not been set up on this computer. An administrator must first create a backup before you can restore files.


message_identifier: 0x810000ef
message_string:
Your system administrator does not allow you to run backup from a remote session. Either run the backup while logged on directly to the computer, or contact your system administrator.


message_identifier: 0x8100001a
message_string:
The backup file could not be found. Make sure the drive that the backup is saved on is attached or try to restore from a different backup.


message_identifier: 0x810000e9
message_string:
Windows Backup cannot run because there are too many files already backed up. Create a new, full backup.


message_identifier: 0x810000ff
message_string:
Windows Backup had to skip all the drives included in backup. Make sure that the drives are plugged in and working correctly.


message_identifier: 0xc00000ea
message_string:
Windows cannot delete temporary files used for backup. This might be caused by antivirus software preventing access to the files. Review your antivirus software settings and try the backup again.


message_identifier: 0x81000019
message_string:
A shadow copy could not be created. Please check "VSS" and "SPP" application event logs for more information.


message_identifier: 0x81000014
message_string:
There is not enough space on the drive that Windows is installed on to prepare for backing up your files. At least 400 MB of free space is required to continue. Free up some space by deleting unnecessary files and try again.


message_identifier: 0x81000015
message_string:
Windows Backup could not create a zip file. This could be because the drive that Windows is installed on does not have enough space or it could be a temporary error. Make sure you have at least 400 MB of free space and try again.


message_identifier: 0x81000011
message_string:
The backup file is corrupted or missing. Check your hardware configuration or restore from a different backup.


message_identifier: 0x8100002a
message_string:
To save files on a network location, your permissions need to be set to Full Control for that location.


message_identifier: 0x8100002d
message_string:
Windows backup is not configured after Windows was upgraded from an earlier version. Review your backup settings.


message_identifier: 0x810000fe
message_string:
Your system administrator does not allow you to create a system image. Contact your system administrator for more information.


message_identifier: 0x810000fd
message_string:
Your system administrator does not allow you to back up your files. Contact your system administrator for more information.


message_identifier: 0x81000003
message_string:
The backup disk cannot be found. Review your backup and restore settings and check your hardware configuration.


message_identifier: 0x81000002
message_string:
The backup location cannot be accessed. Review your backup settings and check your backup location.


message_identifier: 0x81000001
message_string:
Windows Backup encountered an internal error. Please review your settings and retry the operation.


message_identifier: 0x81000006
message_string:
The backup location cannot be found or is not valid. Review your backup settings and check the backup location.


message_identifier: 0x81000005
message_string:
There is not enough space on this drive to save the backup. Free up space by deleting older backups and unnecessary data or change your backup settings.


message_identifier: 0x00001005
message_string:
There is not enough space to save the backup in the current backup location %1. Free up disk space or select a different backup location.


message_identifier: 0x00001004
message_string:
Backup did not complete successfully because a shadow copy could not be created. Free up disk space on the drive that you are backing up by deleting unnecessary files and then try again.


message_identifier: 0x00001007
message_string:
The backup did not complete because of an error writing to the backup location %1. The error is: %2.


message_identifier: 0x8100000b
message_string:
You cannot create a backup or change backup settings when your computer is running on battery power. Attach a power cord and try again.


message_identifier: 0x8100000a
message_string:
The latest backup set can not be found. Make sure it is accessible and it has not been deleted. Otherwise, create a new full backup.


# message_table_132_0x00000409

message_identifier: 0x000005ed
message_string:
Windows saved user %1 registry while an application or service was still using the registry when the user logged off. The memory used by the user registry has not been freed. The registry will be unloaded when it is no longer in use. %n%n This error may be caused by services running as a user account. Try configuring services to run in either the LocalService or NetworkService account.


message_identifier: 0x000005ee
message_string:
Windows cannot create a local profile and is logging you on with a temporary profile. This profile will be deleted when you log off. This problem may be caused by incorrect file system permissions or network problems.


message_identifier: 0x000005ef
message_string:
Windows cannot locate your roaming mandatory profile and is attempting to log you on with your local profile. This error may be caused by incorrect file system permissions or network problems. %n%n DETAIL - %1


message_identifier: 0x000005eb
message_string:
Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on.


message_identifier: 0x000005f9
message_string:
Roaming user profiles across forests are disabled. Windows did not load your roaming profile and is logging you on with a local profile. Changes to the profile will not be copied to the server when you log off.


message_identifier: 0x00000607
message_string:
A slow network connection is detected for the roaming profile %1. It will not be synchronized with the profile on this computer.


message_identifier: 0x000005f1
message_string:
Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you log off. This error may be caused by network problems or insufficient security rights. %n%n DETAIL - %1


message_identifier: 0x000005f0
message_string:
Windows cannot log you on because your roaming mandatory profile is not available. This error may be caused by incorrect file system permissions or network problems. %n%n DETAIL - %1


message_identifier: 0x000005f3
message_string:
Your roaming profile (read only) is not available. You are logged on with the locally stored profile. This error may be caused by incorrect file system permissions or network problems.  %n%n DETAIL - %1


message_identifier: 0x000005f2
message_string:
Windows cannot locate your roaming profile (read only) and is attempting to log you on with your local profile. This error may be caused by network problems or insufficient security rights. %n%n DETAIL - %1


message_identifier: 0x000005f5
message_string:
Windows has detected that Automatic Offline Caching is enabled on the Roaming Profile share - to avoid potential profile corruption, Offline Caching must be set to manual or disabled on shares where roaming user profiles are stored. %n%n


message_identifier: 0x000005f4
message_string:
Windows cannot unload your classes registry file - it is still in use by other applications or services. The file will be unloaded when it is no longer in use.  %n%n


message_identifier: 0x000005f6
message_string:
Windows could not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you log off. Windows could not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrators group must be the owner of the folder. %n%n


message_identifier: 0x000005dc
message_string:
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, and that your network is functioning correctly. %n%n DETAIL - %1


message_identifier: 0x000005de
message_string:
Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile. %n%n DETAIL - %1


message_identifier: 0x000005dd
message_string:
Windows cannot create a temporary profile directory. This problem may be caused by insufficient security rights. %n%n DETAIL - %1


message_identifier: 0x000005fa
message_string:
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  %n%n DETAIL - %n %1


message_identifier: 0x000005fd
message_string:
Windows cannot delete the profile directory %1. This error may be caused by files in this directory being used by another program. %n%n DETAIL - %2


message_identifier: 0x000005e8
message_string:
Windows cannot unload your registry file. The memory used by the registry has not been freed. This problem is often caused by services running as a user account. Try configuring services to run in either the LocalService or NetworkService account. %n%n DETAIL - %1


message_identifier: 0x000005e9
message_string:
Windows cannot copy your profile because it contains encrypted files or directories. The keys to decrypt the files or directories are also stored in the profile and are not available now. Decrypt the files and try again.


message_identifier: 0x000005e4
message_string:
Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights. %n%n DETAIL - %1 for %2


message_identifier: 0x000005e7
message_string:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.


message_identifier: 0x000005e0
message_string:
Windows Windows cannot update your roaming profile completely. Check previous events for more details. %n%n


message_identifier: 0x000005e1
message_string:
Windows cannot load the user's profile but has logged you on with the default profile for the system. %n%n DETAIL - %1


message_identifier: 0x000005e2
message_string:
Your roaming profile is not available. You are logged on with the locally stored profile. Changes to the profile will not be copied to the server. Possible causes of this error include network problems or insufficient security rights.  %n%n DETAIL - %1


message_identifier: 0x00000604
message_string:
Your roaming profile is not synchronized correctly with the server. Windows will load your previously-saved local profile instead. See the previous events for details.


