Mini Kabibi Habibi

Current Path : C:/Windows/SysWOW64/en-US/
Upload File :
Current File : C:/Windows/SysWOW64/en-US/wlanapi.dll.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!>

`�K@ �;8.rdata�@@.rsrc@ <@@��J
T88��J$��8.rdata8x.rdata$zzzdbg �.rsrc$01�$�7.rsrc$02 �t��9¾�8.�M�iDu=�To�Jj�૵Jx�(�@���� �8��P�h����������������(��@��X�p�������	�����		(	8	H	X	h	x	�	�	�	�	�	�	�	�			(	8	H	X	h�$��0%���%.�(l�p(��)���)���/��00��,5��7���7"��9��X;�l?��HA���G���K��P���V\��WF�0X��MUI�����zm��k�1��H)�7Sׂ�-O����K'D0���MUIen-USMicrosoft Windows Wireless	MicrosoftWireless information collectorPAWireless Diagnostics�This data collector set collects wireless service related data on your local system. The data to be collected includes wireless debug logs, registry keys, system hardware information that can help troubleshoot wireless service related problemsPA&%1!s! - Unable to display name as textThe operation was successful.Failed for an unknown reason.'The wireless network is not compatible.7The profile for the wireless network is not compatible.0The profile is not set to connect automatically.$The wireless network is not visible.4The wireless network is blocked by the group policy.,The wireless network is blocked by the user.5The BSS type is not allowed on this wireless adapter.+The wireless network is on the failed list.,The wireless network is on the blocked list.LThe size of the SSID list exceeds the maximum size supported by the adapter.The MSM connect call failed.The MSM scan call failed.&The specific network is not available.@The profile used for the connection has changed or been deleted.2The password for the network might not be correct.8The information required from the user was not received.;Access Point profile is not allowed for old version client.<Access Point profile is not allowed by user or group policy./The profile is invalid according to the schema.$The WLAN profile 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 IHV security settings are not supported.7The IHV profile OUI did not match with the adapter OUI.!The IHV OUI settings are missing.&The IHV security settings are missing.>Both Microsoft and IHV security settings exist in the profile.*No security settings exist in the profile.The BSS type is not valid.9Automatic connection cannot be set for an ad hoc network.2Non-broadcast cannot be set for an ad hoc network.0Auto-switch cannot be set for an ad hoc network.:Auto-switch cannot be set for a manual connection profile.'1X setting is missing for IHV security..The SSID in the profile is invalid or missing.&Too many SSIDs specified in a profile.PA0The IHV connectivity settings are not supported.HThe maximum number of clients is not a valid value in Access Point mode.#The specified channel is not valid.2The operation mode is not supported by the driver.@Auto-connect or auto-switch should not be set for an AP profile.$Automatic connection is not allowed.PA@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.PAThe operation was cancelled.*The driver disconnected while associating.'Association with the network timed out. Pre-association security failed.+Failed to start security after association.Security failed.Security operation times out.&The driver disconnected while roaming.%Failed to start security for roaming.)Failed to start security for Ad hoc peer.The driver disconnected.-The driver failed to perform some operations.!The IHV service is not available.The IHV service timed out. The driver disconnect timed out.PA<An internal failure prevented the operation from completing.The UI Request timed out.^The computer is roaming too often. The security check did not complete after several attempts.+The driver failed to start as Access Point.Failed to queue UI request:802.1x authentication did not start within configured time=802.1x authentication did not complete within configured time9Dynamic key exchange did not start within configured time;Dynamic key exchange did not succeed within configured time6Message 3 of 4 way handshake has no key data (RSN/WPA)0Message 3 of 4 way handshake has no IE (RSN/WPA)3Message 3 of 4 way handshake has no Group Key (RSN);Matching security capabilities of IE in M3 failed (RSN/WPA)AMatching security capabilities of Secondary IE in M3 failed (RSN)9Required a pairwise key but AP configured only group keys:Message 1 of group key handshake has no key data (RSN/WPA)1Message 1 of group key handshake has no group key0AP reset secure bit after connection was securedL802.1x indicated there is no authenticator, but the profile requires 802.1x.Plumbing settings to NIC failed!Operation was cancelled by caller Key index specified is not validKey required, PSK presentInvalid key lengthInvalid PSK lengthNo auth/cipher specifiedToo many auth/cipher specified&Profile contains duplicate auth/cipher,Profile raw data is invalid (1x or key data)Invalid auth/cipher combination0802.1x disabled when it's required to be enabled0802.1x enabled when it's required to be disabledInvalid PMK cache modeInvalid PMK cache sizeInvalid PMK cache TTLPAInvalid PreAuth modeInvalid PreAuth throttle*PreAuth enabled when PMK cache is disabled%Capability matching failed at network!Capability matching failed at NIC%Capability matching failed at profile1Network does not support specified discovery type%Passphrase contains invalid character'Key material contains invalid character6The key type specified does not match the key material$Entered key is not in a valid formatPMixed cell suspected (AP not beaconing privacy, we have privacy enabled profile)Security downgrade detectedPSK mismatch suspected5802.1x authentication timers in profile are incorrect1Group key update interval in profile is incorrectPA;Transition network suspected, trying legacy 802.11 securitypWindows could not map all of the characters into US-ASCII. Security keys must be entered as US-ASCII characters.9Capability matching failed at profile (cipher not found).7Capability matching failed at profile (auth not found).<Forced failure because the connection method was not secure.&The FIPS 140-2 mode value is not validTThe profile requires FIPS 140-2 mode, which is not supported by the network adapter.LThe profile requires FIPS 140-2 mode, which is not supported by the network.;Message 3 of 4 way handshake contains too many RSN IE (RSN)8Message 2 of 4 way handshake has no key data (RSN Adhoc)2Message 2 of 4 way handshake has no IE (RSN Adhoc)=The authentication algorithm in the profile is not supported.5The cipher algorithm in the profile is not supported.,WCN authentication is completed as expected.Invalid Reason codePA�4VS_VERSION_INFO��
aJ
aJ?StringFileInfo�040904B0LCompanyNameMicrosoft Corporation�,FileDescriptionWindows WLAN AutoConfig Client Side API DLLh$FileVersion10.0.19041.1 (WinBuild.160101.0800)8InternalNamewlanapi.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.HOriginalFilenamewlanapi.dll.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.19041.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADD