Quick Google =
Easy fix. But why do it in the GUI?
#Confirm that "Wireless-Networking is not installed (available).Install-WindowsFeature Wireless Networking
You'll have to restart, and after you do, if there are issues, you might need to change the "WLAN AutoConfig" service off "manual".
...and this is probably a bad thing to have in production..something...something not a best practice.
Install-WindowsFeature is actually a really interesting cmdlet.
You can within that cmdlet, do things like -ForceRestart and -Source. Source will let you specify a network UNC path, a repo specified by GPO, local system, VHD, or the venerable Windows Update.
So if you go so far as to establish a well known GPO with the repo, you can never ever need to have media available (doesn't come up much, but it does for things such as .NET 3.5 needing to be installed in 2012r2).
The kicker really is that it (centralized sources) will become more and more needed as server slims down and attack surfaces are reduced through simply reducing the amount of components installed.
Wonder if this will be merged into One-Get in the future.