Remember the good old Manage Wireless Networks GUI from Windows 7, allowing users full control over wireless connections? Reordering connections and ability to access properties of ANY wireless connection, not just the one to which computer is currenty connected to, is impossible on Windows 8+ via GUI.
After a little digging, I discovered these systems still reference the file where Manage Wireless Networks GUI is implemented. However, wlanpref.dll, where functionality is supposed to be, is crippled, invoking the GUI doesn't do anything. By replacing the file with the one from Windows 7, the GUI can be brought back.
For this quick guide, I'm going to assume the reader has access to Windows 7 installation, which bitness and installed GUI language(s) (language packs) matches the system he/she is going to patch and knows how to replace system files by taking ownership and giving self write access to the file.
At minimum, the following files need to be taken from Windows 7 install:
C:\Windows\System32\wlanpref.dll
C:\Windows\System32\en-US\wlanpref.dll.mui
IMPORTANT: The path of the second file depends on the primary GUI language of your operating system, so en-US may need to be replaced with some other language. If any language pack is installed, wlanpref.dll.mui files for these languages are also required for everything to work properly.
Once all files are acquired, they can be copied to the target system. To be able to replace them, one must take ownership of each file and give their user group (Users) write permission. I took care of this manually in file properties dialog on Security tab and restored original permissions and ownership afterwards. Some of you probably added option to shell context menu to take ownership and give yourself permissions with one click.
This doesn't restore hyperlink to the GUI in Control Panel->Network and Sharing Center, but the GUI can be invoked running the following command:
explorer.exe shell:::{1FA9085F-25A2-489B-85D4-86326EEDCD87}
For convenience, make a shortcut somewhere accessible, specifying above command as the target.
Here's the final result:
On Windows 8.1, wlanpref.dll hasn't been touched since 2014, on Windows 10, it's probably replaced with every new build, so perhaps writing a script that backups and replaces the files on will might be a good idea. I'm surprised just throwing in Windows 7's DLL worked so flawlessly in this case. Windows 7 also has hyperlink to export wireless profile in connection properties dialog, this is under control of some other component I suppose. The only thing I wasn't able to test is creating ad hoc network since my WiFi adapter doesn't support that functionality.
, they might find this guide useful: 
All newly-opened applications will use the classic theme. Not all applications work well with the classic theme. Internet Explorer has heavy graphical issues, Task Manager closes immediately, and restarting explorer.exe causes the taskbar and start menu to no longer work. 
