By john 
Listing the Wi-Fi networks your PC has saved shows every wireless profile stored on the system, useful for managing connections or finding a network name. Windows 11 lists saved profiles with a single Command TANGKAS39 Prompt command.
The Command
netsh wlan show profilesWhat It Does
This command lists all the wireless network profiles saved on your PC by name. Each represents a network your computer has connected to and remembered, so it can reconnect automatically. The output shows the profile names grouped by type, giving you a complete inventory of saved Wi-Fi networks on the system.
When You’d Use This
This is useful for reviewing which networks your PC remembers, cleaning up old or unwanted saved networks, or finding the exact name of a network before viewing its details or password. Managing saved profiles keeps your PC from cluttering with networks you no longer use, and it is the starting point for exporting or deleting specific network configurations.
Useful Variations
To see details of a particular profile, use `netsh wlan show profile name=”NetworkName”`. To remove a saved network you no longer want, `netsh wlan delete profile name=”NetworkName”` deletes its profile. To export profiles for backup, the `netsh wlan export profile` command saves them to files you can later import.
If It Doesn’t Work
If a network you expect is not listed, your PC may not have saved it, which happens if you never connected or chose not to save it. To act on a profile, use its exact name as shown. Deleting a profile makes your PC forget that network, so you would need to re-enter its password to reconnect, meaning you should remove only networks you truly no longer need.
Good to Know
Deleting a profile means your PC forgets that network and will not reconnect automatically until you enter its password again, so remove only networks you no longer need. The saved profiles persist even when you are away from those networks, which is how Windows reconnects to familiar Wi-Fi automatically.
Putting It Together
Once you have run it once or twice, this becomes second nature. As part of diagnosing and configuring your connection, this command belongs in your toolkit for whenever the network acts up. Used alongside the other networking commands here, it helps you methodically work from confirming basic connectivity to pinpointing exactly where a problem lies. Like anything in the terminal, the real value comes from trying it on your own system and adapting the variations above to what you actually need, so it is worth experimenting with in a safe, low-stakes situation before relying on it in a script or during troubleshooting. Keeping a note of the commands you find most useful, along with the variations that fit your workflow, turns scattered one-off tricks into a personal reference you can draw on whenever a similar task comes up again.