Operation completed with success. One or more arguments passed into the method or function are invalid. Out of system memory. A message receiver has already been closed or not opened. A message receiver has already been opened. A message receiver was not opened yet. A message receiver can not synchronize threads and notify a "main" thread about new received message. A message receiver can not register for threads synchronization. A message receiver can not create a thread synchronization object. A thread synchronization object has not been created. An invalid thread used to call the method. Unable to create asynchronous message processing thread termination event. Invalid or unsupported message processing method. A message receiver has already been subscribed. A message receiver has not been subscribed. The message broadcaster can not initialize the hardware monitoring thread. The message broadcaster can not start the hardware monitoring thread. The message broadcaster can not create the hardware monitoring object. The message broadcaster can not register for hardware changes notifications. The message broadcaster can not create a mutex synchronization object. The message broadcaster was not created. There is the error with the references counter. The messaging subsystem is already running. Invalid or unknown synchronization method. A timeout appeared during wait operation. Wait operation failed. A message receiver with given ID was not found. Unable to create synchronization mutex for WinRT control. Unable to load WinRT core DLL. Unable to load WinRT string DLL. WinRT initialization failed. Unable to create string. Unable to active instance of the required class. Unable to create interface of the required class. Failed to read asynchronous operation status. An asynchronous operation cancelled. An asynchronous operation completed with error. Unable to detach raw buffer. An asynchronous operation timed out. Unable create WinSUB subsystem synchronization mutex. WinUSB subsystem is not available on your system. WinUSB subsystem was not loaded. Unknown or unexpected WinUSB error. A WinUSB device is already opened. A WinUSB device is closed. A WinUSB device is not opened. Unable to open specified WinUSB device. Initialize WinUSB device failed. Control transfer failed. Read data from pipe (endpoint) failed. The power events monitor is already opened. The power events monitor is already closed. The power state monitoring feature is supported on Windows 8 and above. Unable to get system power status. Unable to create Power Events Window initialization event. Unable to create and start Power Event Window thread. Unable to create Power Events Window. Unable to load Configuration Manager API. The LAF ID was not found. Unable to access the LAF key information. The LAF key was not found. Unable to load encryption DLL. Encryption functions not found. Unable to acquire encryption context. Unable to build hash. Unable to crypt the hash. Unable to get crypted hash. An application file does not contain the identity resource. Unable to read the identity. The identity has invalid format. The identity is empty. The identity has invalid format. Request to unlock limited feature failed. Unable to get unlock request status. The LAF is locked. The LAF unavailable because was not found. Unknown or undefined LAF status. The LAF manager has already been opened. The LAF manager was not opened. The LAF manager is closed. Create LAF manager initialization event failed. Create LAF manager termination event failed. Unable to start the LAF manager working thread. The LAF feature is not supported on this platform. Unable to access the LAF list. Unable to load the Wi-Fi subsystem. The Wi-Fi subsystem was not loaded. The Wi-Fi subsystem can not create synchronization mutex object. A Wi-Fi is already opened. A Wi-Fi is already closed. A Wi-Fi was not opened (is not active). A calling function was not found in WLAN API. The caller does not have sufficient permissions. An invalid WLAN client handle used. WLAN API can not allocate memory to execute an requested operation. The required operation is not supported by the Wi-Fi subsystem. An unexpected exception was raised during WLAN API call. One or more arguments passed into the WLAN API are invalid. The Wi-Fi hardware or driver was not found. Too many sessions to WLAN subsystem are opened. The resource is not in the correct state to perform the requested operation. This error is returned if an interface is in the invalid state. For example if an interface is not connected to a Wi-Fi network or if the wireless Hosted Network is disabled by a group policy on a domain. The radio associated with the interface is turned off. There are no available networks when the radio is off. Internal WLAN driver error. The PHY with given index was not found. The configuration data for the wireless Hosted Network is unconfigured. This error is returned if the application queries the Hosted Network Profile or Hosted Network Connection Settings before a SSID is configured in the wireless Hosted Network. The wireless profile specified by was not found in the profile store. The WLAN profile already exists. Typically, this return value is used when Overwrite is False; however, if Overwrite is True and Flags specifies a different profile type than the one used by the existing profile, then the existing profile will not be overwritten and WCL_E_WIFI_ALREADY_EXISTS will be returned. The profile is not valid. The interface does not support one or more of the capabilities specified in the profile. For example, if a profile specifies the use of WPA2 when the NIC only supports WPA, then this error code is returned. Also, if a profile specifies the use of FIPS mode when the NIC does not support FIPS mode, then this error code is returned. This error is returned if no user custom data exists for the profile specified. Unable to create thread. Unable to get operation thread result code. Unable to start asynchronous operation. Unable to get asynchronous operation information interface. Unable to get asynchronous operation result. Unable to get found adapters count. Unable to change the Wi-Fi Adapter state. The feature is not supported on this platform. One or more BSS ID in the BSS list used in Connect operation is invalid. The system cannot find the path specified. The data is not valid. One or more arguments are not correct. The configuration registry key could not be opened. The data supplied is of the wrong type. The error indicates that the Wi-Fi access disabled in the system settings. The error indicates that the Wi-Fi access disabled for the classic applications in system settings and used did not grant access during access request. The EAPHost received EAP failure after the identity exchange. There is likely a problem with the authenticating user account. The certificate store can not be accessed on either the authenticator or the peer. The requested EAP method is not installed. The EAPHost is not able to communicate with the EAP quarantine enforcement client (QEC) on a client with Network Access Protection (NAP) enabled. The EAPHost returns this error if the authenticator fails the authentication after the peer sent its identity. The EAPHost returns this error on authentication failure. The EAPHost returns this error when the client and the server are not configured with compatible EAP types. The EAPMethod received an EAP packet that cannot be processed. The EAPHost received a packet that cannot be processed. The EAPHost configuration schema validation failed. The EAP method does not support single signon for the provided configuration. The EAPHost returns this error when a configured EAP method does not support a requested operation (procedure call). The EAPHost could not find the user certificate for authentication. The user certificate being used for authentication does not have a proper extended key usage (EKU) set. The EAPhost found a user certificate which has expired. The user certificate being used for authentication has been revoked. An unknown error occurred with the user certificate being used for authentication. The authenticator rejected the user certificate being used for authentication. The authenticator rejected the user credentials for authentication. The authenticator rejected the user credentials for authentication. No smart card reader was present. The server certificate being user for authentication does not have a proper EKU set. The EAPhost found a server certificate which has expired. The server certificate being used for authentication has been revoked. An unknown error occurred with the server certificate being used for authentication. The EAPHost could not find a certificate in trusted root certificate store for user certificate validation. The authentication failed because the root certificate used for this network is not valid. The trusted root certificate needed for user certificate validation has expired. The EAPHost could not find a root certificate in the trusted root certificate store for server certificate velidation. The reason for failure is unknown. The wireless network is not compatible. The wireless network profile is not compatible. The profile specifies no auto connection. The wireless network is not visible. The wireless network is blocked by group policy. The wireless network is blocked by the user. The basic service set (BSS) type is not allowed on this wireless adapter. The wireless network is in the failed list. The wireless network is in the blocked list. The size of the service set identifiers (SSID) list exceeds the maximum size supported by the adapter. The Media Specific Module (MSM) connect call fails. The MSM scan call fails. The specified network is not available. This reason code is also used when there is a mismatch between capabilities specified in an XML profile and interface and/or network capabilities. For example, if a profile specifies the use of WPA2 when the NIC only supports WPA, then this error code is returned. Also, if a profile specifies the use of FIPS mode when the NIC does not support FIPS mode, then this error code is returned. The profile was changed or deleted before the connection was established. The profile key does not match the network key. The user is not responding. An application tried to apply a wireless Hosted Network profile to a physical wireless network adapter using the WlanSetProfile function, rather than to a virtual device. An application tried to apply a wireless Hosted Network profile to a physical wireless network adapter using the SetProfile method, rather than to a virtual device. The profile invalid according to the schema. The WLANProfile element is missing. The name of the profile is invalid. The type of the profile is invalid. The PHY type is invalid. The MSM security settings are missing. The independent hardware vendor (IHV) security settings are missing. The IHV profile OUI did not match with the adapter OUI. The IHV OUI settings are missing. The IHV security settings are missing. An application tried to apply an IHV profile on an adapter that does not support IHV connectivity settings. The security settings conflict. The security settings are missing. The BSS type is not valid. Automatic connection cannot be set for an ad hoc network. Non-broadcast cannot be set for an ad hoc network. Auto-switch cannot be set for an ad hoc network. Auto-switch cannot be set for a manual connection profile. The IHV 802.1X security settings are missing. The SSID in the profile is invalid or missing. Too many SSIDs were specified in the profile. An application tried to apply a wireless Hosted Network profile to a physical network adapter NIC using the SetProfile method, and specified an unacceptable value for the maximum number of clients allowed. The channel specified is invalid. The operation mode is not supported. An internal operating system error occurred with the wireless Hosted Network. An internal operating system error occurred with the wireless Hosted Network. The security settings are not supported by the operating system. The security settings are not supported. The BSS type does not match. The PHY type does not match. The data rate does not match. User has canceled the operation. Driver disconnected while associating. Association timed out. Pre-association security failure. Failed to start security after association. Security ends up with failure. Security operation times out. Driver disconnected while roaming. Failed to start security for roaming. Failed to start security for ad hoc peer. Driver disconnected. Driver failed to perform some operations. The IHV service is not available. The response from the IHV service timed out. Timed out waiting for the driver to disconnect. An internal error prevented the operation from being completed. A user interaction request timed out. Roaming too often. Post security was not completed after 5 attempts. An internal operating system error occurred that resulted in a failure to start the wireless Hosted Network. Failed to connect because no connectable Access Point was visible. Key index specified is not valid. Key required, PSK present. Invalid key length. Invalid PSK length. No auth/cipher pairs specified. Too many auth/cipher pairs specified. Profile contains duplicate auth/cipher pair. Profile raw data is invalid. Invalid auth/cipher combination. 802.1X disabled when it is required to be enabled. 802.1X enabled when it is required to be disabled. Invalid PMK cache mode. Invalid PMK cache size. Invalid PMK cache TTL. Invalid preauth mode. Invalid preauth throttle. Preauth enabled when PMK cache is disabled. Capability matching failed at network. Capability matching failed at NIC. Capability matching failed at profile. Network does not support specified capability type. Passphrase contains invalid character. Key material contains invalid character. The key type specified does not match the key material. A mixed cell is suspected. The AP is not signaling that it is compatible with a privacy-enabled profile. The number of authentication timers or the number of timeouts specified in the profile is invalid. The group key update interval specified in the profile is invalid. A "transition network" is suspected. Legacy 802.11 security is used for the next authentication attempt. The key contains characters that are not in the ASCII character set. Capability matching failed because the network does not support the authentication method in the profile. Capability matching failed because the network does not support the cipher algorithm in the profile. FIPS 140-2 mode value in the profile is invalid. Profile requires FIPS 140-2 mode, which is not supported by network interface card (NIC). Profile requires FIPS 140-2 mode, which is not supported by network. Profile specifies an unsupported authentication, mechanism. Profile specifies an unsupported cipher. Failed to queue the user interface request. The wireless LAN requires Management Frame Protection (MFP) and the network interface does not suppport MFP. For more informarion, see the IEEE 802.11w amendment to the 802.11 standard. 802.1X authentication did not start within configured time. 802.1X authentication did not complete within configured time. Dynamic key exchange did not start within configured time. Dynamic key exchange did not complete within configured time. Message 3 of 4-way handshake has no key data. Message 3 of 4-way handshake has no IE. Message 3 of 4-way handshake has no GRP key. Matching security capabilities of IE in M3 failed. Matching security capabilities of secondary IE in M3 failed. Required a pairwise key but access point (AP) configured only group keys. Message 1 of group key handshake has no key data. Message 1 of group key handshake has no group key. AP reset secure bit after connection was secured. 802.1X indicated that there is no authenticator, but the profile requires one. Plumbing settings to NIC failed. Operation was canceled by a caller. Entered key format is not in a valid format. A security downgrade was detected. A PSK mismatch is suspected. There was a forced failure because the connection method was not secure. Message 3 of 4 way handshake contains too many RSN IE (RSN). Message 2 of 4 way handshake has no key data (RSN Adhoc). Message 2 of 4 way handshake has no IE (RSN Adhoc). A MSM authentication WCN completed. Message 3 of 4 way handshake has no Mgmt Group Key (RSN). Message 1 of group key handshake has no group management key. No user is available for 802.1X authentication. This error can occur when machine authentication is disabled and no user is logged on to the machine. The 802.1X identity could not be found. Authentication could only be completed through the user interface and this interface could not be displayed. The EAP authentication failed. The 802.1X authenticator went away from the network. The version of the OneX profile supplied is not supported. The OneX profile has an invalid length. The EAP type specified in the OneX profile(possibly supplied by the EAPType element) is not allowed. The EAP Type specified in the OneX profile (possibly supplied by the EAPType element) is invalid, or one of the EAP flags (possibly supplied in the EAPConfig element) is invalid. The supplicant flags (possibly supplied in the EAPConfig element) in the OneX profile are invalid. A timer specified in the OneX profile (possibly supplied by the heldPeriod, authPeriod, or startPeriod element) is invalid. The supplicant mode specified in the OneX profile (possibly supplied by the supplicantMode element) is invalid. The authentication mode specified in the OneX profile (possibly supplied by the authMode element) is invalid. The connection properties specified in the OneX profile (possibly supplied by the EAPConfig element) are invalid. User input was canceled. This value can be returned if an EAP method requested user input, but the user hit the Cancel button or dismissed the user input dialog. The saved user credentials are not valid. This value can be returned if a profile was saved with bad credentials (an incorrect password, for example), since the credentials are not tested until the profile is actually used to establish a connection. The saved user credentials have expired. This value can be returned if a profile was saved with credentials and the credentials subsequently expired (password expirarion after some period of time, for example). User interface is not permitted. On Windows 7 and on Windows Server 2008 R2 with the Wireless LAN Service installed, this value can be returned if an EAP method requested user input and the profile is configured with user credentials saved by another user and not the currently logged in user. The undefined reason code. The EAPHost component (the peer) requested the 802.1x module to restart 802.1X authentication. This results from a EapHostPeerProcessReceivedPacket function call that returns an EapHostPeerResponseAction enumeration value of EapHostPeerResponseStartAuthentication in the pEapOutput parameter. The Media Specific Module (MSM) initiated the 802.1X authentication restart. The 802.1X authentication restart was the result of a state timeout. The timer expiring is the heldWhile timer of the 802.1X supplicant state machine defined in IEEE 802.1X - 2004 standard for Port-Based Network Access Control. The heldWhile timer is used by the supplicant state machine to define periods of time during which it will not attempt to acquire an authenticator. The 802.1X authentication restart was the result of an state timeout. The timer expiring is the authWhile timer of the 802.1X supplicant port access entity defined in IEEE 802.1X - 2004 standard for Port-Based Network Access Control. The authWhile timer is used by the supplicant port access entity to determine how long to wait for a request from the authenticator before timing it out. The 802.1X authentication restart was the result of a configuration change to the current profile. The 802.1X authentication restart was the result of a change of user. This could occur if the current user logs off and new user logs on to the local computer. The 802.1X authentication restart was the result of receiving a notification from the EAP quarantine enforcement client (QEC) due to a network health change. If an EAPHost supplicant is participating in network access protection (NAP), the supplicant will respond to changes in the state of its network health. If that state changes, the supplicant must then initiate a re-authentication session. The 802.1X authentication restart was caused by a new authentication attempt with alternate user credentials. EAP methods like MSCHAPv2 prefer to use logged-on user credentials for 802.1X authentication. If these user credentials do not work, then a dialog will be displayed to the user that asks permission to use alternate credentials for 802.1X authentication. Unknown reason. Unknown error. Bad parameters. Service is shutting down. Service is out of resources. This operation requires elevation. An attempt was made to write read-only data. Data persistence failed. A cryptographic error occurred. User impersonation failed. An incorrect function call sequence was made. A wireless interface has become available. A wireless interface has become unavailable. This reason code is returned by the wireless Hosted Network functions any time the network state of the wireless Hosted Network is hnUnavailable. For example if the wireless Hosted Network is disabled by group policy on a domain, then the network state of the wireless Hosted Network is hnUnavailable. The wireless miniport driver stopped the Hosted Network. The wireless miniport driver status changed. An incompatible connection started. An incompatible connection refers to one of the following cases: An ad hoc wireless connection is started on the primary station adapter; Network monitoring is started on the primary station adapter by an application (Network Monitor, for example); A wireless connection is started in FIPS safe mode on the primary station adapter. FIPS safe mode is specified in the profile of the wireless connection; Windows will stop the wireless Hosted Network on the software-based wireless access point (AP) adapter when an incompatible connection starts on the primary station adapter. The network state of the wireless Hosted Network state would become hnUnavailable. An incompatible connection stopped. An incompatible connection previously started on the primary station adapter (see WCL_E_WIFI_HN_RES_INCOMPATIBLE_CONNECTION_STARTED), but the incompatible connection has stopped. If the wireless Hosted Network was previously stopped as a result of an incompatible connection being started, Windows will not automatically restart the wireless Hosted Network. A state change occurred that was caused by explicit user action. A state change occurred that was caused by client abort. The driver for the wireless Hosted Network failed to start. A peer connected to the wireless Hosted Network. A peer disconnected from the wireless Hosted Network. A peer timed out. The operation was denied by group policy. The Wireless LAN service is not running. The wireless adapter used by the wireless Hosted Network changed. The properties of the wireless Hosted Network changed. A virtual station is active and blocking operation. An identical service is available on a virtual station. Unable to access the IP settings of a Hosted Network. Unable to read TCP/IP settings of a Hosted Network. The requested feature is not supported on current platform. Get IP table failed. The peer with specified MAC was not found. The Hosted Network has already been started. The Hosted Network does not support PSD IE on this platform. The error indicates that the Wi-Fi access disabled in the system settings. The error indicates that the Wi-Fi access disabled for the classic applications in system settings and used did not grant access during access request. The Network List Manager is closed. The Network List Manager is opened. Unable to initialize COM subsystem. The Network List Manager is not supported on this platform. The Network List Manager events handler is already set. The Network List Manager events handler was not set. Unable to find the Network List Manager events handler connection points container. Unable to find the Network List Manager events handler connection point. Unable to find the Network events handler connection points container. Unable to find the Network events handler connection point. The network with given ID was not found. Unable to get a network's or machine's connectivity. Unable to read Connected property of the Network List Manager or Network. Unable to get a network's domain type. Unable to get a network's categiry. Unable to get a network's description. Unable to get a network's name. Unable to get a network's ID. Unable to get a network's creation and connection date and time. Unable to get a connection's adapter ID. Unable to read a connection's ID. Unable to set a network's categiry. Unable to set a network's description. Unable to set a network's name. Unable to enumerate available networks. Networks with required type were not found. Connections were not found. Unable to enumerate connections. Network profiles list was not found. Administrative rights required for this operation. Unexpected or unknown error. Unable to get list of the network adapters. A network adapter with the specified ID was not found. Unable to create API synchronization mutex. Unable to load NetMon API DLL. The API references counter is in wrong state. The Wi-Fi Sniffer has already been opened. The Wi-Fi Sniffer is closed. Unable to create interface protection mutex. The other instance of the Wi-Fi Sniffer is already using the same interface for capturing. Indicates an issue between the Network Monitor API and the ndisnapp object. See Working with Multi-Threaded Code. The object that you are trying to create already exists. Frame comment information was not found. The specified file was not found. The API or driver is in the wrong state for the requested operation. Reference to a file, file path, handle, or data field is incorrect. This function is not currently supported. The upper limit of a resource has been reached. This may indicate that a handle limit has been reached. Sometimes this is an indication that handles are being leaked. These resources can be read with the NmGetApiConfiguration function and set with the NmApiInitialize function. The field is a container, so the content is not available. The version of the DLL does not match the version with which this executable was compiled. The file size of the capture specified by the capture function exceeds the current limit, 500 MB. The file size of the capture specified by the capture function is too small to contain any useful frame information. The frame size overlaps with the next frame. The offset in the frame table points past the bounds of the file. The file that you are saving to does not have enough space to hold the frame. This can occur when there is not enough disk space or if the file is over the 500 MB size limit. The file type is not a valid Network Monitor 3 capture file. The file type is not supported. The PCAP data link type is not supported. The data is big-endian, but only little-endian data is supported. The file is not a supported PCAP version. Indicates an issue between the application and the API. Unexpected Wi-Fi Sniffer error. No one supported adapter was found. The Wi-Fi Direct radio was not available. This error occurs when the Wi-Fi Direct radio has been turned off. The operation cannot be serviced because the necessary resources are currently in use. Unknown or unexpected Wi-Fi Direct error. Wi-Fi Direct features are not supported. For Wi-Fi Direct features Windows 10 is required. The device is not in a state where it can be paired. The device is not currently paired. The device has already been paired. The device rejected the connection. The device indicated it cannot accept any more incoming connections. The device indicated there was a hardware failure. The authentication process timed out before it could complete. The authentication protocol is not supported, so the device is not paired. Authentication failed, so the device is not paired. Either the device or the application rejected the authentication. There are no network profiles for this device to use. The minimum level of protection is not supported by the device or the application. Your application does not have the appropriate permissions level to pair the device. The ceremony data was incorrect. The pairing action was canceled before completion. The device is already attempting to pair or unpair. Either the event handler wasn't registered or a required wclWiFiDirectPairingKinds was not supported. The application handler rejected the pairing. The remove device already has an association. An unexpected failure occurred. An unknown failure occurred. The Wi-Fi Direct device is connected or connecting. The Wi-Fi Direct device is disconnected or disconnecting. Unablet to create Wi-Fi Direct device's thread termination event. Unable to start Wi-Fi Direct device connection thread. Unable to create device information object. IAsyncInfor interface not supported. Unable to get device information object. Extended device information not supported. Wi-Fi Direct device does not support pairing. Wi-Fi Direct device does not support custom pairing. Unable to create Wi-Fi Direct device pairing notification synchronization event. Connection has been terminated by user. Wait for notification message processing failed. Unable to create pairing synchronization mutex. Unable to set Group Owner Intent. Unable to get connection parameters. Unable to set preffered pairing procedure. Unable to get custom pairing interface. Unable to set pairing event handler. Unable to get pairing settings. Unable to start pairing with remote Wi-Fi Direct device. Unable to get pairing result. Unable to pair with remote device. Unable to create Wi-Fi Direct device object. Unable to get Wi-Fi Direct device creation operation result. Wi-Fi Direct device object was not created. Unable to set disconnection event handler. Unable to get Wi-Fi Direct device's pairing status. Unable to start unpairing operation. Timeout during creating Wi-Fi Direct device object. Usually it appears when device has wrong DHCP configuration or uses static IP. Unable to start Wi-Fi Direct device object creating procedure. Unable to get device ID. The Wi-Fi Direct device or driver is busy. The publisher is aborted due to error. Unable to get the Wi-Fi Direct Advertisement object. Unable to set an Autonomous Group Owner state. Unable to set Listen State Discoverability. Unable to access the Wi-Fi Direct Advertiser Legacy mode settings. Unable to change the Legacy mode setting of the Wi-Fi Direct Advertiser. Unable to set SSID for the Wi-Fi Direct Advertiser. Unable to access Legacy mode security settings of the Wi-Fi Direct Advertiser. Unable to set the Wi-Fi Direct Advertiser's Legacy mode pass phrase. Unable to create start synchronization event for the Wi-Fi Direct Advertiser. Unable to set event handler for Wi-Fi Direct Advertiser. Filed to start Wi-Fi Direct Advertiser. Unable to set event handler for Wi-Fi Direct Advertiser connection listening. A Wi-Fi Direct Advertiser is already running. Unable to create Wi-Fi Direct Advertiser working thread initialization event. Unable to start Wi-Fi Direct Advertiser working thread. Wi-Fi Direct Advertiser is not running. Unable to create legacy Soft AP with Open Authetication (Open Network). Wi-Fi Direct Advertiser is already running by other Wi-Fi Framework based application. Unable to create global mutex object. Mobile Hotspot is already running on PC. This error returned when your run x32 application on x64 platform and Autonomous Group Owner enabled in WiFiDirectAdvertiser and the Advertiser runs not in Legacy mode. The Wi-Fi Direct Device Watcher is already running. Unable to create Wi-Fi Direct Device Watcher thread synchronization event. Unable to start Wi-Fi Direct Device Watcher worker thread. The Wi-Fi Direct Device Watcher is not running. Unable to create Wi-Fi Direct Device activation factory. IWiFiDirectDeviceStatics2 interface is not supported. Unable to get Device Selector. Unable to create Device Information Activation Factory. Unable to create Device Watcher object. Unable to set device added event handler. Unable to set discovering completed event handler. Unable to start Wi-Fi Direct Device Watcher. Unable to create discovering completed notification event. Discovering terminated by user. Unexpected or unknown error. Unable to create Wi-Fi Direct Device Watcher thread initialization event. Unable to set device watcher stopped event handler. Unable to start working thread to read remote Wi-Fi Direct device's paired status. Unable to start Wi-Fi Direct device unpairing thread. Unable to start Wi-Fi Direct device name resolving thread. Unable to start paired Wi-Fi Direct devices enumeration thread. Unable to enumerate available devices. IAsyncInfor interface not supported. Get devices enumeration result failed. A Wi-Fi interface is not connected. Unable to access the IP settings of an Wi-Fi interface. Unable to read TCP/IP settings of an Wi-Fi interface. Unable to change IP settings for a Wi-Fi interface. IP address is not valid. Administrative rights required for this operation. The TCP/IP settings for the given WLAN interface was not configured. The network interface for the given virtual adapter was not found. The feature is not supported by the Wi-Fi interface. Unable to open the Wi-Fi interface parameters registry key. The interface does not have any configurable parameters. A parameter with the specified name was not found. Read parameter raw value failed. Unable to find a paratemer value. Unable to read a paratemer value. Invalid parameter value. Update parameter value failed. The Wi-Fi interface was not found. Unable to disable the Wi-Fi interface. Unable to enable the Wi-Fi interface. Unable to prepare Network Configuration API. Network Configuration API create failed. Network Configuration API lock create failed. Network Configuration API lock failed. Network Configuration API initialization failed. Unable to enumerate network interfaces. Interface was not found. TCP/IP protocol was not found for the given Wi-Fi interface. Unable to switch protocol state. Unable to apply changes in network configuration. Start protocol changes thread. A Mobile Hotspot has already been opened. A Mobile Hotspot is closed. A Mobile Hotspot has already been closed. Unable to create initialization event. Unable to create termination event. Unable to create and start working thread. Unable to create Network Information object. Unable to get Internet connection profile. Internet connection profile was not found. Unable to create Mobile Hotspot Manager activation factory object. Unable to create Mobile Hotspot Manager. Unable to get Mobile Hotspot state. Mobile hotspot is already started. Unable to start Mobile Hotspot. IAsyncInfor interface not supported. Unable to get operation result. Get operation status failed. The operation could not begin because the mobile broadband device is turned off. The operation could not begin because the Wi-Fi device is turned off. The operation did not complete because the mobile operator could not be contacted to confirm tethering capabilities are provided for this account. The operation did not complete because the account does not currently support tethering operations. The operation is still in progress. The operation could not begin because Bluetooth or a required Bluetooth device is turned off. The operation did not complete because of limited network connectivity. Unknown or undefined operation result. The Mobile Hotspot is topped. Wi-Fi hardware is turned off or not available. Get access point configuration failed. Unable to get current SSID. Unable to set new SSID. Unable to save new AP config. Unable to get current passphrase. Unable to set new passphrase. Unable to get maximum client connections count. Unable to get connected clients count. Unable to get connected clients list. Unable to get connected clients list size. Specified band is not supported. Unable to change band. Unable to change No Connection Timeout state. Get Not Connection Timeout state failed. A connection is active. A connection is not active. Unable to create communication termination event object. Unable to create connection complete event object. Unable to create communication thread. The connection has been terminated by unknown reason. The connection has been terminated by user. Unable to create a communication thread initialization event. The connection has been closed. Unexpected error. A server was not able to create or init client connection instance. A server was not able to find a specific client connection class. An OBEX client is not connected to an OBEX server. An OBEX client is already connected to an OBEX server. An OBEX operation is in progress. The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent). The request has been fulfilled, resulting in the creation of a new resource. The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs. The server is a transforming proxy that received a WCL_E_SUCCESS from its origin, but is returning a modified version of the origin's response. The server successfully processed the request and is not returning any content. The server successfully processed the request, but is not returning any content. Unlike a WCL_E_OBEX_NO_CONTENT error, this error requires that the requester reset the object. The server is delivering only part of the resource due to a range header sent by the client. The range header is used by OBEX clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. Indicates multiple options for the resource from which the client may choose. This and all future requests should be directed to the given URI. The response to the request can be found under another URI using the GET method. The response to the request can be found under another URI using the GET method. Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy. The requested resource is available only through a proxy, the address for which is provided in the response. The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). Similar to WCL_E_OBEX_FORBIDDEN, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. Reserved for future use. The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort. The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible. A request method is not supported for the requested resource. The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. The client must first authenticate itself with the proxy. The server timed out waiting for the request. Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates. Indicates that the resource requested is no longer available and will not be available again. The request did not specify the length of its content, which is required by the requested resource. The server does not meet one of the preconditions that the requester put on the request. The request is larger than the server is willing or able to process. The URI provided was too long for the server to process. The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. A generic error, given when an unexpected condition was encountered and no more specific message is suitable. The server either does not recognize the request method, or it lacks the ability to fulfill the request. The server was acting as a gateway or proxy and received an invalid response from the upstream server. The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. Also this error indicates that wrong Connect ID or Target used. The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. The server does not support the HTTP protocol version used in the request. Indicates that the client requests that something be placed into a database but the database is full (cannot take more data). Returned when the client wishes to access a database, database table, or database record that has been locked. The current operation has been terminated because a remote device is disconnected. The current operation has been terminated by a user. The operation can not be executed at this time. This error appears if for example an application calls Terminate for Connect, Disconnect or SetPath operations. The error code indicates that the OBEX session has been disconnected by a remote side. Unexpected or unknown OBEX result code. Unable to create synchronization Mutex used to generate connection ID. The maximum connection ID has been reached. Invalid data processor state. Unable to parse directory listing. Wrong directory listing format. COM initialization failed. XML parser is not available. A Bluetooth Manager is closed. A Bluetooth Manager is opened. Unable to opend the Bluetooth Manager. An other instance of the Bluetooth Manager is already opened. A Bluetooth driver is not available or not loaded. A Bluetooth hardware is not available. A Bluetooth API (driver) was not loaded. Unable to initialize a Bluetooth API (driver) subsystem. A Bluetooth API (driver) was not found in this system. A Bluetooth driver was not initialized. A Bluetooth driver has been found but it does not support all the features that WCL requires for correct work. You should update your Bluetooth driver for the latest available version. A Bluetooth Radio object is opened. A Bluetooth Radio object is closed. The Bluetooth Radio object has been removed (destroyed). Unable to initialize a Bluetooth Radio instance mutex. The same Bluetooth Radio instance has already been initialized. The Bluetooth Radio object become unavailable. Unable to change Radio connectable state. Unable to change Radio discoverable state. Unable to change Radio name. The requested feature is not supported by a Bluetooth driver. Unexpected or unknown Bluetooth error. Error other than time-out at L2CAP or Bluetooth radio level. Usualy this error appears if you try to connect to device that is paired on PC side but PC is not paired or has been unpaired on the device side. Unpairing device on PC side usually solves the error. The operation fails for an undefined reason. The request can not be processed since a same request is being processed. The limit of connection number is reached. An object with the specified attribute exists. The specified object is accessed by other process. It can not be removed or modified. Discovering is already running. Discovering is not running. Discovering has been terminated. Operation has been cancelled by user. Operation time out. Connection has been terminated by a user. Asynchronous processing is pending. Connection failure. A specified remote Bluetooth device was not found. Pairing operationis executing. Unable to start pairing with a remote Bluetooth device. A device has already been paired. The specified remote device is not paired. Access denied. Authentication (pairng) with a remote Bluetooth device is failed. Operation has been rejected. Unable to get a read buffer size. Unable to get a write buffer size. Unable to set a read buffer size. Unable to set a write buffer size. A client is already connected to a Bluetooth device. A client is not connected to a Bluetooth device. The L2CAP channel disconnected by remote peer. Wrong device type used in connection. The port/channel number requested is in use. The Bluetooth port/channel or device address not valid. No service record with the specified search pattern is found on the remote device. Unable to create a Bluetooth socket. Unable to set client authentication and/or encription states. Unable to create socket event. Unable to select socket events. Unable to aquire the connections mutex object. Unable to create system event object for overlapped IO. Unable to create disconnect notification event. Unable to create connect notification connection event. Unable to aquire the SDP mutex object. The RFCOMM multiplexor (session) disconnected by remote peer. The RFCOMM received DM response. For incoming connections, the error indicates that the connection is rejected if authentication cannot be established. For outgoing connection the error indicates that the service does not use RFCOMM. The RFCOMM channel disconnected by remote peer. Unable to resolve connected remote device address. Unable to add new SDP record. Unable to set server authentication and/or encription states. Local service is still active. Unable to create Bluetooth server. Unable to enumerate local running services. Unable to stop local predefined server. Unable to update local server database. Unable to setup the communication port. Unable to open the client COM port for the Bluetooth connection. Unable to open the server COM port for the Bluetooth connection. Sending data to a remote device was failed. Abnormal data received. Unable to create Toshiba notifications window. Unable to register Toshiba notification message. Unable to create synchronization event. SDP transaction processing failure. Unable start SDP connection thread. Unable to start connection thread. Unable to start listening thread. Inquiry processing failure. Remote name acquisition processing failure. Unable to destroy COM port. Unable to connect COM port. Unable to disconnect COM port. Unable to turn Bluetooth ON or OFF. Can not assign PSM. Unable to read local Radio information. Unable to disconnect from SDP server. Unable to register COM port notifications. Unable to change local radio information. Unablet o get connected state of the device. Unable to connect to a remote device. Unable to start connection to a remote device. PSM error. SDP record parsing error. Unable to read RSSI value. Unable to change pairing mode. Error working with SDP records. Unable to start Toshiba main thread. Unable to create BlueSoleil initialization event. Unable to start BlueSoleil initialization thread. The virtual COM port was not found. Probably it was not created by this Bluetooth radio object. A virtual COM port was already created for this Bluetooth device and service. Unable create Bluetooth Device Statics interface. Unable start Win RT asyncronous operation. Unable set Win RT asynchronous operation event handler. Unable create Bluetooth Device interface. Unable get Win RT async operation result. Failed to get Bluetooth Device ID. Failed to read Bluetooth Device properties. Unable to start RSSI measurement thread. This is Microsoft specific error indicates that the pairing with remote classic Bluetooth enabled device was not started and need to be re-initiated. Incompatible OS. This feature required to run x64 application on x64 platform and/or x86 application on x86 platform. Unable to get Bluetooth radios list. Unable to get number of available Bluetooth radios. Access to Bluetooth Radio driver instance has been failed. Unable to change Bluetooth Radio state. Bluetooth features are unsupported by the hardware. A Bluetooth Radio object is closing. The operation can not be executed. Unable to start asynchronous name reading of a remote Bluetooth LE device. Invalid pairing method specified. No system resources. Unable to create registry changes monitoring thread termination event. Unable to create registry changes monitoring thread initialization event. Failed to start registry changes monitoring thread. Unable to registry authentication callback. Unable to open or create authentication agent registry key. Create registry changes notification event failed. Unable to set registry changes notification indication. Unable to disable Bluetooth Authentication Agent. Device has been paired by other application. Drivers for the Bluetooth device has already been installed. Disoonnect operation failed because device is not connected. Device has not been installed. Unable to enumerate connections. Wait for Bluetooth communication events failed. The operation requires administrative rights. The discovering Timeout value is too high. You can not use Timeout greater than 61 seconds. The discovering Timeout is too low. You can not use Timeout less than 2 seconds. Unable to read remote device's address type. Unable read device's address type because device's type is unknown. Unable to start Win RT classic working thread. Create Device Watcher Factory failed. Create device's filter for Device Watcher failed. Create Bluetooth devices watcher failed. Create discovering completion event failed. Set Bluetooth device watcher Added event handler failed. Set Bluetooth device watcher Updated event handler failed. Set Bluetooth device watcher Removed event handler failed. Set Bluetooth device watcher Discovering Completed event handler failed. Start discovering failed. Unable to create write completion event object. Discovering has been canceled (aborted) by the system. Unable to create asynchronous operation termination indication event. Unable to set Win RT object's event handler. Unable to register Wii Remote client connect notification message. Unable to register Wii Remote client disconnect notification message. Unable to register Wii Remote client data notification message. Unable to create data received notification event. Unable to create pairing timeout event. Bluetooth hardware failed. A Classic Bluetooth Radio is not available. The pairing is handled by the OS. The Bluetooth radio instance was not found. Unable to open a Bluetooth Radio driver. Invalid Bluetooth Radio driver instance name. Invalid Bluetooth Radio driver instance path. An application does not have enough rights to open Bluetooth Radio driver. Bluetooth Radio driver not found or not working. The Bluetooth Radio driver is already in use by other application. Invalid parameters specified in Bluetooth Radio driver open request. Invalid Bluetooth Radio driver name. Too many opened Bluetooth Radio driver instances. A Bluetooth driver is busy. The attribute handle given was not valid on this server. Attribute reading is not permited. Attribute writing is not permitted. Invalid request format. The attribute requires authentication before it can be read or written. Attribute server does not support the request received from the client. Offset specified was past the end of the attribute. The attribute requires authorization before it can be read or written. Prepare queue is full. Too many prepare writes have been queued. No attribute found within the given attribute handle range. The attribute cannot be read or written using the Read Blob Request. The Encryption Key Size used for encrypting this link is insufficient. The attribute value length is invalid for the operation. The attribute requires encryption before it can be read or written. The attribute type is not a supported grouping attribute as defined by a higher layer specification. Insufficient Resources to complete the request. SMP failed. Task cancel. Connect failed. Response timed out. CCC improperly configured. Requested procedure is already in progress. Out of range. The access to the Bluetooth LE attribute failed. This is Microsoft specific error code and usually indicates that the driver or low-level API can not access to the internal GATT attribute object. At least one subscription active. The error appears if you try to read services, characteristics or descriptors with goReadFromDevice flag and there is at least one subscription active. The GATT connection is already subscribed for this attribute changes notifications. The GATT connection has not been subscribed for this attribute changes notifications. The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. A remote device closes the connection. A buffer is specified, but the buffer count size is smaller than what is required, in bytes. The current data in the cache appears to be inconsistent, and is leading to internal errors. The target server did not provide an appropriate network response. The characteristic value is not readable as dictated by the characteristic properties. Unable to create Bluetooth LE Advertisement Watcher. Unable to change Bluetooth LE Advertisement Watcher scanning mode. Unable start Bluetooth LE Advertisement Watcher. Unable to start Win RT LE working thread. Unable to set Win RT object's event handler. Unable create Bluetooth LE Device Statics interface. Unable create Bluetooth LE Device interface. Unable start Win RT asyncronous operation. Unable set Win RT asynchronous operation event handler. Unable get Win RT async operation result. Unable create IBluetoothLEDevice2 interface. Unable to get IDeviceInformation interface. Unable to get IDeviceInformation2 interface. Unable to get IDeviceInformationPairing interface. Unable to get IDeviceInformationPairing2 interface. Unable to get IDeviceInformationCustomPairing interface. Bluetooth Beacons monitoring is running. Bluetooth Beacons monitoring is not running. The Bluetooth LE advertising is already running. The Bluetooth LE advertising is not running. Unable create initialization event for the Bluetooth LE advertising thread. Unable create termination event for the Bluetooth LE advertising thread. Unable start Bluetooth LE Advertising thread. An application executes Write Without Response with value size longer than maximum PDU size (MTU). Ap application must use Write With Response instead. To do that an application must set IsWritableWithoutResponse characteristic's property to false and then call the WriteCharacteristicValue method to force Write With Response. Unable to get Bluetooth LE Advertiser object. Unable to start subscribing thread. No subscribed clients found. Unable to create connection completion event. Unable to start LE devices discovering thread. The URL passsed to the Eddytone URL Beacon is empty or too short. The length of the URL must be at least 8 characters. Invalid Eddystone URL Beacon URL scheme. An URL must start with "http://" or "https://". The Eddystone URL Beacon URL is too long. Failed to start asynchronous pairing with Bluetooth LE device. Error during executing asynchronous pairing with Bluetooth LE device. The OS does not support automatic connection to BLE device and manual pairing is required. The device object is not in a state where it can be paired. The device object is not currently paired. The device object rejected the connection. The device object indicated it cannot accept any more incoming connections. The device object indicated there was a hardware failure. The authentication process timed out before it could complete. The authentication protocol is not supported, so the device is not paired. Authentication failed, so the device is not paired. Either the device object or the application rejected the authentication. There are no network profiles for this device object to use. The minimum level of protection is not supported by the device object or the application. Your application does not have the appropriate permissions level to pair the device object. The ceremony data was incorrect. The pairing action was canceled before completion. The device object is already attempting to pair or unpair. Either the event handler was not registered or a required pairing method was not supported. The application handler rejected the pairing. The remove device already has an association. An unknown failure occurred. Failed to change protection level. The characteristic value is not writable as dictated by the characteristic properties. Attemp to connect to not previously discovered Bluetooth LE GATT device. Device object was not found by the system. A device has already been paired. Bluetooth LE features are unsupported by the hardware. Bluetooth LE features requires Bluetooth 4.0 or newest Bluetooth hardware with HCI version 6 and above. Unable to create LE devices discovering thread termination event. A specified remote Bluetooth LE device was not found. Failed to get Bluetooth LE Device ID. Failed to read Bluetooth LE Device properties. The requisted feature is not supported bu a Bluetooth LE driver. Unable to read RSSI value. Unable to start BLE RSSI measurement thread. Application error code defined by a higher layer specification. Pairing or authentication procedure is disallowed because too little time has elapsed since last pairing request or security request. Out of Band data is not available for authentication. Unable to get information ablout Bluetooth LE service that owns an attribute. Unable to read Bluetooth LE GATT service handle. Unable to read Bluetooth LE GATT characteristic handle. Unable to read Bluetooth LE GATT descriptor handle. Unable to read Bluetooth LE GATT descriptor UUID. Unable to read Bluetooth LE GATT characteristics presentation formats list. Unable to read Bluetooth LE GATT characteristics presentation formats list size (length). Unable to read Bluetooth LE GATT characteristics presentation format. Unable to read Bluetooth LE GATT characteristics presentation format type. Unable to read Bluetooth LE GATT characteristics presentation format exponent. Unable to read Bluetooth LE GATT characteristics presentation format unit. Unable to read Bluetooth LE GATT characteristics presentation format namespace. Unable to read Bluetooth LE GATT characteristics presentation format description. Unable to get Bluetooth LE GATT descriptor value size. Unable to get access to Bluetooth LE GATT descriptor value raw data. Unable to get access to Bluetooth LE GATT descriptor value data. Unable to read Bluetooth LE GATT characteristic UUID. Unable to read Bluetooth LE GATT characteristic properties. Unable to get Bluetooth LE GATT descriptor value data buffer. Unable to get Bluetooth LE GATT characteristic value data buffer. Unable to get Bluetooth LE GATT characteristic value size. Unable to get access to Bluetooth LE GATT characteristic value raw data. Unable to get access to Bluetooth LE GATT characteristic value data. Unable to read Bluetooth LE GATT descriptors list size (length). Unable to read Bluetooth LE GATT service UUID. Unable to read Bluetooth LE GATT characteristics list size (length). Unable to read Bluetooth LE GATT services list size (length). Unable to start reading device's connected status thread. LL initiated a connection but the connection has failed to be established. Controller did not receive any packets from remote end. Unable to get Bluetooth LE device connected status. Unable to start Bluetooth LE device paired status reading thread. Connection was terminated because the Message Integrity Check (MIC) failed on a received packet. Unable to get Bluetooth LE device's paired status. GATT protocol error. Usually this error indicates that a client sent wrong data to a server. Or sometime it may indicates that server requires subscribing to a characteristic before it can accept any write requests. The characteristic has already been added to the local GATT service. The characteristic has already been removed from the local GATT service. The service has already been added to the GATT server. The service has already been removed from the GATT server. The GATT server is running (advertising). The GATT server is not running. Failed to create GATT server thread initialization event. Failed to create GATT server thread termination event. Failed to create GATT server communication thread. Failed to get GATT local service interface. Unable to create local GATT characteristic parameters object. Failed to set local GATT characteristic read protection level. Failed to set local GATT characteristic write protection level. Unable to set properties of a local GATT characteristic. Local GATT characteristic was not created by unknown reason. Unable to create local GATT characteristic. Failed to set local GATT service advertisement parameters. Bluetooth hardware does not support peripheral mode. Unbale to publish local GATT service. Unable to create local GATT sevrice. Local GATT service was not created by unknown reason. The GATT server is not initialized. The GATT server has lready been initialized. Unable to set GATT local characteristic write request event handler. Unable to set GATT local characteristic read request event handler. Unable to set GATT local characteristic subscribed clients changed event handler. Unable to start unsubscribing thread. One or more connection parameter values are not valid. Characteristic is not notifiable or indicatable. Directed advertising completed without a connection being created. Unable to create GATT Server protection mutex. Other instance of the GATT server is already running. Only one instance of the GATT server is allowed. A client is not connected to a Bluetooth device. Unexpected or unknown error. Unable to set Bluetooth LE scan parameters. A characteristic does not support the Write Without Response operation Unable to create scan parameters changing event. Unable to set Bluetooth LE advertising parameters. The error code indicates that the remote device terminated the connection because of an unacceptable connection interval. Get connection PHY value failed. Unable to open process token. Unable to find one or more required privilege. Unable to change one or more privilege. Unable to allocate and initialize SID. Unable to take registry key ownership. Unable to set ACL. Unable to change registry access rights. The characteristi has invalid configuration. This error means that the characteristic has both IsNotifiable and IsIndicatable properties are set to True. Set one of the property to False. Unable to create asynchronous operation termination indication event. Discovering has been terminated. Discovering has been canceled (aborted) by the system. Local device terminated the connection. Bluetooth LE advertisement initialization failed. Bluetooth LE advertisement type is not supported. Bluetooth LE advertisement has invalid format. A Bluetooth LE Radio is not available. Unable to get the current connection parameters. Invalid or unknown preffered connection parameters type. Unable to set the current connection parameters. The extended advertisement properties are not supported. Set the UseExtendedAdvertisement property of the wclBluetoothLeAdvertiser component to False and try to restart the advertisement. Set extended advertisement properties failed. Unable to set client disconnect event handler for the GATT server. The client is not subscribed to any GATT server characteristic. Unable to read maximum notification size. Unable to get maximum PDU size. Unknown or unexpected error appeared during pairing procedure. Unable to set disconnect event handler for the GATT client. Unable to set local GATT characteristic user-friendly description. Unable to get GATT local characteristic presentation formats list. Unable to create GATT local characteristic presentation format statics. Unable to create GATT local characteristic presentation format. Unable to add GATT local characteristic presentation format. Read characteristic's user description descriptor failed. The descriptor with given UUID can not be used as custom descriptor in GATT server. Create custom descriptor failed. Unable to add custom descriptor. Set descriptor's value failed. Failed to set local GATT descriptor read protection level. Failed to set local GATT descriptor write protection level. Unable to get result of descriptor creation operation. Unable to get result code of description creation operation. Unable to get Bluetooth LE connection PHY data. Get transmit PHY information failed. Get receive PHY information failed. There is no advertisements that can be advertised. Too many advertisements. Unable to send response to a connected GATT client. The write operation was requested as Write Without Response. The response was already sent. A Bluetooth hardware driver rejected the specified scan parameters. Use the default to start a Beacon Watcher. Changing Bluetooth LE advertisement PHY is not supported on this platform. The specified primary PHY is not supported by the BluetoothLeAdvertiser. The specified secondary PHY is not supported by the BluetoothLeAdvertiser. A reliable write operation is active. Complete the reliable write operation before calling this method. Incorrect write operation selected during writing a characteristic value. A reliable write operation was started for other characteristic. A reliable write operation was not started. A reliable write operation has already been started. The reliable write operation is not supported. A device does not support the Long Write operation. Can not ceate HID devices list. A Wii Remote controller has not been installed. Unable to create overlapped read event. Unable to create overlapped write event. Unable to connect to the Wii Remote controller. Unable to create HID API access mutex. HID subsystem is not available on this platform. Not all required HID features are supported by the system. Read data from the Wii Remote failed. Write data to the Wii Remote failed. Write data to the Wii Remote has timed out. Unable to create read memory event object. Unable to create write memory event object. The Wii Remote controller has not been initialized yet. Wrong IR sensor level has been specified. Unknown IR sensor level has been specified. Wrong IR sensor mode has been specified. Unknown IR sensor mode has been specified. The extension has not been detected (or partially inserted) during initialization. Unknown or unsupported extension has been attached. The requisted feature is not supported. Probably because Balance Board is connected. Accelerometer is already enabled. Accelerometer is disabled. Invalid Wii Remote configuration. Command contained invalid parameter. Device is in wrong state to receive command. Device has run out of memory. Feature is not implemented. Command was not recognized. Command or Procedure failed due to timeout. Connection handle passed is to command is not a valid handle. Command would cause either underflow or overflow error. User attribute was accessed through API which is not supported. No valid license key found. Command maximum length exceeded. Bonding procedure can not be started because device has no space left for bond. Module was reset due to script stack overflow. Controller is at limit of connections it can support. Operation was rejected because the controller is busy and unable to process the request. A command can not be executed because other command is still running. Set handflow failed. Invalid response data size. Unable to set input and output queue size. Unable to set communication timeouts. Unable to set required baud rate. Set DTR control failed. Set line control failed. Set the special characters failed. BLED112 does not support pairing. The pairing done during connection procedure. The BLE sniffer is already active. The BLE sniffer is not active. Unable to create the thread initialization event. Unable to create the thread termination event. Unable to start BLE sniffer working thread. The CC2540 device was not found. Unable to read BLE sniffer device ident. Set BLE sniffer device power failed. Get BLE sniffer device power failed. Set capturing channel failed. Unable to start packet capturing. The device's registry key was not found or not enough privilegies. Unable to read a device's friendly name. The device's parameters registry key was not found or not enough privilegies. Unable to read a device's port name. The given Device Class Guid was not found. Monitoring is running. Monitoring is not running. Unable to get read buffer size. Unable to get write buffer size. Unable to set read buffer size. Unable to set write buffer size. Unable to initialize the overlapped IO operation. Write data to the serial port was failed. Timeout appeared during write operation. That doe snot mean real error. That just means that some bytes were sent but time out appeared before all bytes are sent. You can retry to send remaining bytes or terminate connection. A serial device has been removed. Unable to read COM port configuration. Unable to write COM port configuration. Unable to read COM port timeouts. Unable to write COM port timeouts. Unable create overlapped operation event. Unable to open the specified COM port. COM features read failed. Unable to set COM potr events mask. The PurgeComm operation was failed. The EscapeCommFunction has been failed. The SetCommBreak method failed. The ClearCommBreak method failed. The TransmitCommChar method failed. The FlushBuffers method failed. The GetCommStatus method failed. Read operation failed. Unable create communication restart event. Write operation was timed out on wait. Probably device is disconnected or not available. Configuration Manager DLL was not found. Required Configuration Manager functions (API) are not available. Unable to locate specified device's node. No one device's interface was found for specified device's instance ID. Unable to switch (disable or enable) specified USB (serial) devices. No USB devices found on this system. The COM Database API access Mutex creation failed. The COM Database API is not available. The COM Database API was not loaded. The COM database is opened. The COM database is closed. The routine could not open the database. Unknown or undefined error. The method could not access the COM database. Write to the COM port database failed. The COM port database handle is not valid. The COM port database i sfull and cannot arbitrate any more port numbers. The specified port number is not in the COM port database. COM initialization failed. Create device enumerator failed. Audio features is not supported on this platform. The Audio component is already closed. The Audio component is already opened. Unable to register audio device changes event handler. The specified audio endpoint not found. Unable to get audio endpoint channels number. Unable to get hardware supported features of the specified audio endpoint. The Audio Switcher is not opened. Unable to enumerate audio endpoints. Get audio endpoints count failed. Create Audio configurator failed. Unable to change default Audio Device. The specified device not found. Invalid device selected. Connect and Disconnect features are supported for Bluetooth Audio Devices only. The device is already connected. The device is disconnected. Unable to create device topology object. Unable to get device topology connectors number. Unable to connect to device. Unable to disconnect from device. No device connectors found. Unable to get default Audio Device. Get Audio Device ID failed. Default audio device not found. Unable to get audio stream peak value. Unable to create Audio meter instance. Unable to create Audio volume instance. Unable to get audio volume level. Unable to set audio volume level. Unable to get audio endpoint mute status. Unable to set audio endpoint mute status. This Bluetooth audio feature is not supported on this platform. Bluetooth Audio Watcher already started. Bluetooth Audio Watcher already stopped. Unable to create Bluetooth Audio Watcher initialization event. Create Bluetooth Audio Watcher termination event failed. Unable to start Bluetooth Audio Watcher working thread. Unable to get Bluetooth Audio Device selector. Create device watcher failed. Set Device Added event handler failed. Set Device Removed event handler failed. Unable to start Bluetooth Audio device watcher. The audio receiver is closed. The audio receiver is opened closed. Unable to create Bluetooth Audio Receiver initialization event. Create Bluetooth Audio Receiver termination event failed. Unable to start Bluetooth Audio Receiver working thread. Unable to create Audio Connection Listener for the specified Bluetooth Audio device. Unable to add Audio Connect Listener event handler. Enable incoming Bluetooth Audio connection failed. A Bluetooth audio device is already connected. Start Bluetooth Audio connection failed. Start Bluetooth Audio connection timedout. Start Bluetooth Audio connection denied by system. Unknow error occured during starting Bluetooth Audio connection.