netsh wlan delete profile command does not delete registry keys for WiFi profile

Question

I typically use the command netsh wlan delete profile <ProfileName> to delete a Wi-Fi profile from the computer. But today I realized that, while the command netsh wlan delete profile does delete the WiFi network completely. i.e. it does not remove the Wi-Fi network entries from the following registry paths.

• HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles\
• HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Unmanaged
• HKLM\SOFTWARE\Microsoft\WlanSvc\ProfileSync\S**...........****\NLM\Irrelevant
• HKLM\SYSTEM\ControlSet001\Services\Dnscache\Parameters\Probe

So, my questions are as follows

1. Why does netsh wlan delete profile not remove the registry entries associated with the WiFi network?
2. Is there a command or a Windows PowerShell command which can do the work of netsh wlan delete profile and remove entries from the Windows registry too? i.e. which will remove all traces of the Wi-Fi network?
3. Apart from the above 4 listed registry keys, are there any other Windows registry keys that I have to delete to remove all traces of the Wi-Fi network?

Answer 1

Hi @ADV-8837,   

Welcome to Microsoft Q&A forum. 

Thank you for your detailed inquiry. Regarding your observation about registry retention, here are the specific technical reasons and solutions. 

1/ Reason for registry retention 

The command netsh wlan delete profile communicates exclusively with the WLAN AutoConfig Service. Its purpose is to remove the connection credentials (SSID and password). However, the registry keys you identified belong to the Network List Service. Windows retains these entries to preserve the network’s firewall categorization (Public vs. Private) and identification history. This ensures that if you reconnect later, your security settings are automatically restored. 

2/ Methods for complete removal  

There is no single native command in Windows that purges both the connection profile and the Network List registry history simultaneously. To remove all traces, you must perform a two-step process: first, use netsh to delete the profile, and second, manually delete the specific keys or utilize a PowerShell script to locate and remove the associated Profile GUIDs and Signatures from the registry. 

3/ Additional registry locations

Your paths cover the standard Network Location Awareness (NLA) artifacts. In addition to HKLM\...\Signatures\Unmanaged, also check HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Managed, which is the counterpart category used for domain-classified networks. Also check HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles, because that’s where Windows stores per-interface profile details and the effective category/authentication-related state linked by ProfileGuid.

I hope this clarifies the system behavior. Should you have any further questions, please feel free to reach out.

Answer 2

The netsh wlan delete profile command is designed to remove the Wi-Fi profile from the user's view and the network list, but it does not necessarily remove all associated registry entries. This behavior is by design, as Windows maintains certain registry keys for various reasons, such as network management and diagnostics. Therefore, the command may not remove entries from the registry paths you mentioned, as they can be used for tracking and managing network configurations.

As for a command that would remove all traces of a Wi-Fi network, there is no built-in command in Windows or PowerShell that guarantees the deletion of all registry entries associated with a Wi-Fi profile. Manual deletion of registry keys is risky and can lead to system instability if not done correctly. It is generally not recommended to modify the registry unless you are certain of the changes you are making.

Regarding other registry keys that may need to be deleted, while the three you listed are significant, there could be other keys depending on specific configurations or third-party software. However, without explicit documentation from Microsoft on all possible keys, it's challenging to provide a comprehensive list. It's best to proceed with caution and ensure you back up the registry before making any changes.

---

References:

• Understand and configure Windows Connection Manager
• Configure EAP profiles and settings in Windows