Wireless profile export/import (encryption key import failed when xml profile imported successfully)
This is my steps. netsh wlan export profile name="SSID_NAME" netsh wlan add profile filename="Wireless Network Connection-SSID_NAME.xml" Cmd told me "Profile SSID_NAME is added on interface Wireless Network Connection" But I was still unable to connect to the wireless. System told me "A network security key is required to connect to SSID_NAME" in the notification area of the right bottom corner of the screen. Then I checked the properties of the wireless network connection. Please see the following screenshots. Screenshot 1: The properties of the wireless after import Screenshot 2: When clicking "Show characters"
December 1st, 2011 8:08am

Here is the notification message after import. Attached for makeup.
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2011 8:12am

BTW, here is the content of the XML file that was exported/imported. <?xml version="1.0"?> <WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1"> <name>SSID_NAME</name> <SSIDConfig> <SSID> <hex>457861724C414E</hex> <name>SSID_NAME</name> </SSID> </SSIDConfig> <connectionType>ESS</connectionType> <connectionMode>auto</connectionMode> <MSM> <security> <authEncryption> <authentication>WPA2PSK</authentication> <encryption>AES</encryption> <useOneX>false</useOneX> </authEncryption> <sharedKey> <keyType>passPhrase</keyType> <protected>true</protected> <keyMaterial>01000000D08C9DDF0115D1118C7A00C04FC297EB010000007707C487F39D7740A1CAF66FB111AF64000000000200000000001066000000010000200000005CB800463EE944493146A002CD346ACF2740CA34D7060C10D206DDBC3AA4CEFD000000000E8000000002000020000000106A6D123802E525EE14E0760572696230712D1F29731405E43DBA4BD7B49083100000005DC76FE99232D0D971A995ACAABED30040000000CE4EB81E9D3C9BCD6784D42C3DE1CB2860737972DA03FEE27C78D878331AE023EB63DF71474ACCD9BFB83D608D693C92A2F642F620F986F84F096D0EA81ED49A</keyMaterial> </sharedKey> </security> </MSM> </WLANProfile>
December 1st, 2011 8:16am

Is anyone know the reason and how to fix it?
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2011 5:13am

I'm sorry I have to be up this question. Thanks.
December 12th, 2011 10:36pm

Sorry, up again.
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2011 1:33am

I'm sorry, up again.
December 22nd, 2011 3:16am

Any experts?
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2011 3:16am

won't stop until being fixed
December 26th, 2011 3:13am

Good good study, day day up!
Free Windows Admin Tool Kit Click here and download it now
January 5th, 2012 1:28am

The problem is that the encrypted password was encrypted with a machine-specific key on the machine you exported the config from. You could import that xml file back into the same machine and it would work just fine. But it won't work on a different machine because the 2nd machine doesn't have the same machine-specific key and can't decrypt the password. I'm not exactly sure what netsh uses as the machine-specific key or whether its possible to clone it from one system to another. Im wrestling with the same issue.
January 9th, 2012 11:06am

I had the same issue. Here was a great explanation and solution: http://theether.net/kb/100166Grant Scheffert
Free Windows Admin Tool Kit Click here and download it now
March 15th, 2012 9:28am

It will work on different machines if you change the text in the protected tags to false and put the plain text key between the key material tags like this: <protected>false</protected> <keyMaterial>plaintextkey</keyMaterial> Be aware that anyone who opens/edits the .xml wireless profile will be able to see the key in plain text, but at least you can use the netsh command to import the key for different machines. I do this at work for my users, I just make sure to keep the .xml file on a flash drive.
September 17th, 2012 5:30pm

Thanks Grant and Mark. I will try the solution when I'm free. It looks like it should be OK. :-)
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2012 8:13am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics