wclWiFiErrors Namespace

The base exception class for all WiFi exceptions.

The WiFi Sniffer exceptions.

Administrative rights required for this operation.

The base Network List Manager error code.

The Network List Manager is closed.

Unable to initialize COM subsystem.

Connections were not found.

The Network List Manager events handler was not set.

The Network List Manager events handler is already set.

Networks with required type were not found.

The network with given ID was not found.

Network profiles list was not found.

Unable to find the Network events handler connection point.

Unable to find the Network events handler connection points container.

The Network List Manager is opened.

Unable to enumerate connections.

Unable to enumerate available networks.

Unable to find the Network List Manager events handler connection point.

Unable to find the Network List Manager events handler connection points container.

Unable to read Connected property of the Network List Manager or Network.

Unable to get a connection's adapter ID.

Unable to read a connection's ID.

Unable to get a network's or machine's connectivity.

Unable to get a network's domain type.

Unable to get a network's categiry.

Unable to get a network's creation and connection date and time.

Unable to get a network's description.

Unable to get a network's ID.

Unable to get a network's name.

Unable to set a network's categiry.

Unable to set a network's description.

Unable to set a network's name.

Unexpected or unknown error.

The Network List Manager is not supported on this platform.

The caller does not have sufficient permissions.

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.

One or more arguments are not correct.

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 profile is not valid.

The base error code for the WiFi framework.

The configuration registry key could not be opened.

Unable to change the WiFi Adapter state.

A WiFi is already closed.

Unable to create thread.

The data supplied is of the wrong type.

This error is returned if no user custom data exists for the profile specified.

A WiFi Direct Advertiser is already running.

WiFi Direct Advertiser is already running by other WiFi Framework based application.

The base error code for WiFi Direct Advertiser.

Unable to create global mutex object.

Mobile Hotspot is already running on PC.

WiFi Direct Advertiser is not running.

Unable to set Listen State Discoverability.

The publisher is aborted due to error.

Unable to change the Legacy mode setting of the WiFi Direct Advertiser.

Unable to create start synchronization event for the WiFi Direct Advertiser.

Unable to create WiFi Direct Advertiser working thread initialization event.

Unable to start WiFi Direct Advertiser working thread.

Unable to get the WiFi Direct Advertisement object.

Unable to access Legacy mode security settings of the WiFi Direct Advertiser.

Unable to access the WiFi Direct Advertiser Legacy mode settings.

Unable to set an Autonomous Group Owner state.

Unable to set event handler for WiFi Direct Advertiser connection listening.

Unable to create legacy Soft AP with Open Authetication (Open Network).

Unable to set the WiFi Direct Advertiser's Legacy mode pass phrase.

Unable to set event handler for WiFi Direct Advertiser.

Unable to set SSID for the WiFi Direct Advertiser.

Filed to start WiFi Direct Advertiser.

The base WiFi Direct error code.

The base error code for WiFi Direct device errors.

The WiFi Direct device is connected or connecting.

Connection has been terminated by user.

Unable to create WiFi Direct device object.

Unable to get WiFi Direct device creation operation result.

Unable to create device information object.

WiFi Direct device object was not created.

Unable to create pairing synchronization mutex.

Unable to create WiFi Direct device pairing notification synchronization event.

Unablet to create WiFi Direct device's thread termination event.

Timeout during creating WiFi Direct device object. Usually it appears when device has wrong DHCP configuration or uses static IP.

WiFi Direct device does not support custom pairing.

The WiFi Direct device is disconnected or disconnecting.

No connection endpoints were found.

Extended device information not supported.

Unable to convert Host Name to IP address.

Unable to get connection parameters.

Unable to get custom pairing interface.

Unable to get connection endpoints count.

Unable to get connection endpoint pairs.

Unable to get default (first) connection endpoint pair.

Unable to get IHostName interface for the connection endpoint pair.

Unable to get device information object.

Unable to get WiFi Direct device's name.

Unable to get WiFi Direct device's pairing status.

Unable to get pairing result.

Unable to get pairing settings.

Unable to pair with remote device.

WiFi Direct device does not support pairing.

IAsyncInfor interface not supported.

Unable to set disconnection event handler.

Unable to set Group Owner Intent.

Unable to set pairing event handler.

Unable to set preffered pairing procedure.

Unable to start WiFi Direct device object creating procedure.

Unable to start pairing with remote WiFi Direct device.

Unable to start WiFi Direct device connection thread.

Unable to start unpairing operation.

Wait for notification message processing failed.

The WiFi Direct Device Watcher is already running.

The base error code for WiFi Direct Device Watcher.

Unable to create Device Information Activation Factory.

IWiFiDirectDeviceStatics2 interface is not supported.

Unable to create WiFi Direct Device activation factory.

Unable to create WiFi Direct Device Watcher thread synchronization event.

Unable to create Device Watcher object.

Unable to create WiFi Direct Device Watcher thread initialization event.

Unable to create discovering completed notification event.

Unable to start WiFi Direct Device Watcher worker thread.

Discovering terminated by user.

Unable to enumerate available devices.

Unable to get Device Selector.

Get devices enumeration result failed.

The WiFi Direct Device Watcher is not running.

IAsyncInfor interface not supported.

Unable to set device added event handler.

Unable to set discovering completed event handler.

Unable to set device watcher stopped event handler.

Unable to start paired WiFi Direct devices enumeration thread.

Unable to start WiFi Direct Device Watcher.

Unable to start working thread to read remote WiFi Direct device's paired status.

Unable to start WiFi Direct device name resolving thread.

Unable to start WiFi Direct device unpairing thread.

Unexpected or unknown error.

WiFi Direct features are not supported. For WiFi Direct features Windows 10 is required.

Your application does not have the appropriate permissions level to pair the device.

The device has already been paired.

The base error code for all WiFi Direct pairing errors.

The pairing action was canceled before completion.

Authentication failed, so the device is not paired. Either the device or the application rejected the authentication.

Either the event handler wasn't registered or a required TwclWiFiDirectPairingKinds was not supported.

The device indicated there was a hardware failure.

The remove device already has an association.

The ceremony data was incorrect.

The device is already attempting to pair or unpair.

The authentication protocol is not supported, so the device is not paired.

The device is not currently paired.

The device is not in a state where it can be paired.

There are no network profiles for this device to use.

The minimum level of protection is not supported by the device or the application.

The device rejected the connection.

The application handler rejected the pairing.

The authentication process timed out before it could complete.

The device indicated it cannot accept any more incoming connections.

An unknown or unexpected failure occurred.

The WiFi Direct radio was not available. This error occurs when the WiFi Direct radio has been turned off.

The operation cannot be serviced because the necessary resources are currently in use.

Unknown or unexpected WiFi Direct error.

The EAPHost returns this error on authentication failure.

The base error code for WiFi EAP errors.

The certificate store can not be accessed on either the authenticator or the peer.

The EAPHost returns this error if the authenticator fails the authentication after the peer sent its identity.

The EAPMethod received an EAP packet that cannot be processed.

The requested EAP method is not installed.

The EAPHost returns this error when a configured EAP method does not support a requested operation (procedure call).

The EAPHost returns this error when the client and the server are not configured with compatible EAP types.

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 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.

No smart card reader was present.

The EAPhost found a server certificate which has expired.

The server certificate being user for authentication does not have a proper EKU set.

An unknown error occurred with the server certificate being used for authentication.

The server certificate being used for authentication has been revoked.

The EAPHost could not find a root certificate in the trusted root certificate store for server certificate validation.

The EAPHost received EAP failure after the identity exchange. There is likely a problem with the authenticating user account.

The EAPhost found a user certificate which has expired.

The user certificate being used for authentication does not have a proper extended key usage (EKU) set.

The EAPHost could not find the user certificate for authentication.

An unknown error occurred with the user certificate being used for authentication.

The authenticator rejected the user certificate being used for authentication.

The user certificate being used for authentication has been revoked.

The authenticator rejected the user credentials for authentication.

The authenticator rejected the user credentials for authentication.

The trusted root certificate needed for user certificate validation has expired.

The authentication failed because the root certificate used for this network is not valid.

The EAPHost could not find a certificate in trusted root certificate store for user certificate validation.

The feature is not supported on this platform.

A calling function was not found in WLAN API.

Unable to get asynchronous operation result.

Unable to get found adapters count.

Unable to get operation thread result code.

The base error code for common Hosted Network errors.

The requested feature is not supported on current platform.

Get IP table failed.

Unable to access the IP settings of a Hosted Network.

The peer with specified MAC was not found.

Unable to read TCP/IP settings of a Hosted Network.

The driver for the wireless Hosted Network failed to start.

Bad parameters.

The base code for the hosted network reasons.

A state change occurred that was caused by client abort.

A cryptographic error occurred.

The wireless adapter used by the wireless Hosted Network changed.

This operation requires elevation.

The operation was denied by group policy.

User impersonation failed.

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 (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.

Service is out of resources.

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 status changed.

The wireless miniport driver stopped the Hosted Network.

A peer connected to the wireless Hosted Network.

A peer disconnected from the wireless Hosted Network.

A peer timed out.

Data persistence failed.

The properties of the wireless Hosted Network changed.

An attempt was made to write read-only data.

An identical service is available on a virtual station.

Service is shutting down.

The Wireless LAN service is not running.

An incorrect function call sequence was made.

Unknown error.

A state change occurred that was caused by explicit user action.

A virtual station is active and blocking operation.

The Hosted Network has already been started.

A Mobile Hotspot has already been opened.

Specified band is not supported.

The base error code for Mobile Hotspot operations.

The operation could not begin because Bluetooth or a required Bluetooth device is turned off.

Unable to change No Connection Timeout state.

The operation did not complete because the account does not currently support tethering operations.

The operation did not complete because the mobile operator could not be contacted to confirm tethering capabilities are provided for this account.

A Mobile Hotspot has already been closed.

Unable to create initialization event.

Unable to create Mobile Hotspot Manager activation factory object.

Unable to create Mobile Hotspot Manager.

Unable to create Network Information object.

Unable to create termination event.

Unable to get connected clients count.

Unable to get connected clients list.

Unable to get connected clients list size.

Get access point configuration failed.

Unable to get maximum client connections count.

Get Not Connection Timeout state failed.

Unable to get operation result.

Get operation status failed.

Unable to get current passphrase.

Unable to get Internet connection profile.

Unable to get current SSID.

Unable to get Mobile Hotspot state.

The operation could not begin because the mobile broadband device is turned off.

The operation did not complete because of limited network connectivity.

A Mobile Hotspot is closed.

The operation is still in progress.

Internet connection profile was not found.

IAsyncInfor interface not supported.

Unable to change band.

Unable to save new AP config.

Unable to set new passphrase.

Unable to set new SSID.

Mobile hotspot is already started.

Unable to start Mobile Hotspot.

Unable to create and start working thread.

The Mobile Hotspot is topped.

Unknown or undefined operation result.

The operation could not begin because the Wifi device is turned off.

WiFi hardware is turned off or not available.

Administrative rights required for this operation.

The base error code for WiFi interface operations.

IP address is not valid.

The TCP/IP settings for the given WLAN interface was not configured.

A WiFi interface is not connected.

Unable to access the IP settings of an WiFi interface.

Unable to read TCP/IP settings of an WiFi interface.

Unable to change IP settings for a WiFi interface.

The network interface for the given virtual adapter was not found.

One or more arguments passed into the WLAN API are invalid.

An invalid WLAN client handle used.

The data is not valid.

The resource is not in the correct state to perform the requested operation. This error is returned if the wireless Hosted Network is disabled by group policy on a domain.

Unable to apply changes in network configuration.

The base error code for Network Configuration operations.

Network Configuration API create failed.

Unable to enumerate network interfaces.

Network Configuration API initialization failed.

Interface was not found.

Network Configuration API lock create failed.

Network Configuration API lock failed.

Unable to prepare Network Configuration API.

TCP/IP protocol was not found for the given WiFi interface.

Start protocol changes thread.

Unable to switch protocol state.

A WiFi was not opened (is not active).

The WiFi hardware or driver was not found.

WLAN API can not allocate memory to execute an requested operation.

The wireless profile specified by was not found in the profile store.

The required operation is not supported by the WiFi subsystem.

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.

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.

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 base code for the 802.1x authentication reasons.

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 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.

Unknown reason.

The Media Specific Module (MSM) initiated the 802.1X authentication restart.

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 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 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.

One or more BSS ID in the BSS list used in Connect operation is invalid.

A WiFi is already opened.

The system cannot find the path specified.

The PHY with given index was not found.

The Hosted Network does not support PSD IE on this platform.

The radio associated with the interface is turned off. There are no available networks when the radio is off.

Failed to start security for ad hoc peer.

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.

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 internal operating system error occurred that resulted in a failure to start the wireless Hosted Network.

Driver disconnected while associating.

Association timed out.

An internal operating system error occurred with the wireless Hosted Network.

An internal operating system error occurred with the wireless Hosted Network.

Auto-switch cannot be set for an ad hoc network.

Auto-switch cannot be set for a manual connection 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 base code for the WiFi subsystem reasons.

The basic service set (BSS) type is not allowed on this wireless adapter.

The BSS type does not match.

The security settings conflict.

The Media Specific Module (MSM) connect call fails.

The data rate does not match.

Timed out waiting for the driver to disconnect.

Driver disconnected.

Driver failed to perform some operations.

The wireless network is blocked by group policy.

An application tried to apply an IHV profile on an adapter that does not support IHV connectivity settings.

The IHV service is not available.

The response from the IHV service timed out.

The IHV profile OUI did not match with the adapter OUI.

The IHV OUI settings are missing.

The independent hardware vendor (IHV) security settings are missing.

The IHV 802.1X security settings are missing.

The IHV security settings are missing.

An internal error prevented the operation from being completed.

Automatic connection cannot be set for an ad hoc network.

The BSS type is not valid.

The channel specified is invalid.

The PHY type is invalid.

The name of the profile is invalid.

The profile invalid according to the schema.

The type of the profile is invalid.

The wireless network is in the blocked list.

The wireless network is in the failed list.

The profile key does not match the network key.

802.1X authentication did not start within configured time.

802.1X authentication did not complete within configured time.

A MSM authentication WCN completed.

Operation was canceled by a caller.

Network does not support specified capability type.

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.

Capability matching failed at network.

Capability matching failed at NIC.

Capability matching failed at profile.

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.

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.

A security downgrade was detected.

There was a forced failure because the connection method was not secure.

Message 1 of group key handshake has no group key.

Message 1 of group key handshake has no key data.

Message 1 of group key handshake has no group management key.

Entered key format is not in a valid format.

Dynamic key exchange did not start within configured time.

Dynamic key exchange did not complete within configured time.

Message 2 of 4 way handshake has no IE (RSN Adhoc).

Message 2 of 4 way handshake has no key data (RSN Adhoc).

Message 3 of 4-way handshake has no GRP key.

Message 3 of 4-way handshake has no IE.

Message 3 of 4-way handshake has no key data.

Message 3 of 4 way handshake has no Mgmt Group Key (RSN).

Message 3 of 4 way handshake contains too many RSN IE (RSN).

A mixed cell is suspected. The AP is not signaling that it is compatible with a privacy-enabled profile.

Plumbing settings to NIC failed.

802.1X indicated that there is no authenticator, but the profile requires one.

Required a pairwise key but access point (AP) configured only group keys.

AP reset secure bit after connection was secured.

The number of authentication timers or the number of timeouts specified in the profile is invalid.

Profile contains duplicate auth/cipher pair.

Invalid auth/cipher combination.

The group key update interval specified in the profile is invalid.

Key index specified is not valid.

Invalid PMK cache mode.

Invalid PMK cache size.

Invalid PMK cache TTL.

Invalid preauth mode.

Invalid preauth throttle.

Key material contains invalid character.

Invalid key length.

The key contains characters that are not in the ASCII character set.

No auth/cipher pairs specified.

802.1X disabled when it is required to be enabled.

802.1X enabled when it is required to be disabled.

Passphrase contains invalid character.

Preauth enabled when PMK cache is disabled.

Invalid PSK length.

Key required, PSK present.

Profile raw data is invalid.

FIPS 140-2 mode value in the profile is invalid.

Too many auth/cipher pairs specified.

Profile specifies an unsupported authentication, mechanism.

Profile specifies an unsupported cipher.

The key type specified does not match the key material.

Matching security capabilities of IE in M3 failed.

A PSK mismatch is suspected.

Matching security capabilities of secondary IE in M3 failed.

A "transition network" is suspected. Legacy 802.11 security is used for the next authentication attempt.

Failed to queue the user interface request.

The MSM security settings are missing.

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 wireless network is not compatible.

Non-broadcast cannot be set for an ad hoc network.

The wireless network is not visible.

The profile specifies no auto connection.

Failed to connect because no connectable Access Point was visible.

The 802.1X authenticator went away from the network.

The EAP authentication failed.

The 802.1X identity could not be found.

The EAP type specified in the OneX profile(possibly supplied by the EAPType element) is not allowed.

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).

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.

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 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 OneX profile has an invalid length.

The supplicant flags (possibly supplied in the EAPConfig element) in the OneX profile are invalid.

The supplicant mode specified in the OneX profile (possibly supplied by the supplicantMode element) is invalid.

A timer specified in the OneX profile (possibly supplied by the heldPeriod, authPeriod, or startPeriod element) is invalid.

The version of the OneX profile supplied is not supported.

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.

Authentication could only be completed through the user interface and this interface could not be displayed.

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.

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 operation mode is not supported.

The PHY type does not match.

Pre-association security failure.

The profile was changed or deleted before the connection was established.

The WLANProfile element is missing.

The wireless network profile is not compatible.

The SSID in the profile is invalid or missing.

Driver disconnected while roaming.

Failed to start security for roaming.

The MSM scan call fails.

Security ends up with failure.

The security settings are missing.

Security operation times out.

The size of the service set identifiers (SSID) list exceeds the maximum size supported by the adapter.

Failed to start security after association.

Roaming too often. Post security was not completed after 5 attempts.

Too many SSIDs were specified in the profile.

A user interaction request timed out.

The undefined reason code.

The reason for failure is unknown.

The security settings are not supported.

The security settings are not supported by the operating system.

User has canceled the operation.

The wireless network is blocked by the user.

The user is not responding.

Internal WLAN driver error.

No one supported adapter was found.

The object that you are trying to create already exists.

The version of the DLL does not match the version with which this executable was compiled.

The base error code for the WiFi Sniffer.

Indicates an issue between the application and the API.

The WiFi Sniffer is closed.

Frame comment information was not found.

The specified file was not found.

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 other instance of the WiFi Sniffer is already using the same interface for capturing.

The file type is not a valid Network Monitor 3 capture file.

The API or driver is in the wrong state for the requested operation.

Indicates an issue between the Network Monitor API and the ndisnapp object. See Working with Multi-Threaded Code.

Reference to a file, file path, handle, or data field is incorrect.

This function is not currently supported.

The WiFi Sniffer has already been opened.

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.

Unable to create interface protection mutex.

Unable to create API synchronization mutex.

Unable to load NetMon API DLL.

Unexpected WiFI Sniffer error.

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.

The API references counter is in wrong state.

Unable to start asynchronous operation.

Too many sessions to WLAN subsystem are opened.

An unexpected exception was raised during WLAN API call.

Unable to get asynchronous operation information interface.

The base error code for the WLAN subsystem.

The WiFi subsystem was not loaded.

The WiFi subsystem can not create synchronization mutex object.

Unable to load the WiFi subsystem.