Share via

Windows Network Profiles IP Assignment & DNS Server Assignment

Johann Schiffmacher 5 Reputation points
2026-03-09T11:35:40.1333333+00:00

Would anyone know where is Windows saving Settings > Network & Internet > Wi-Fi > {Wi-Fi Profile Name} > IP Assignment & DNS Server Assignment? Cannot find it anywhere. I will need to save different IP addresses details for different Windows Wi-Fi Profiles. Those settings here are saved & kept even if a different addresses are used with different profiles. I want to change those with a script similar to:

netsh wlan add profile filename="WiFiProfileXmlPath" interface="IfcName"

Screenshot 2026-03-09 152700

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
0 comments No comments

1 answer

Sort by: Most helpful
  1. Chen Tran 10,720 Reputation points Independent Advisor
    2026-03-09T12:31:38.3833333+00:00

    Hello Johann,

    Thank you for posting question on Microsoft Windows Forum!

    Well! The actual IP/DNS values are kept with the TCP/IP adapter configuration in the registry/NetTCPIP store. Not inside the WLAN profile XML that netsh wlan manages. The Settings UI for Wi-Fi profiles is just a modern (UWP) front-end that tells Windows which TCP/IP settings to apply to the adapter. Since Windows requires elevated privileges to change adapter TCP/IP values, there is no supported non-elevated netsh wlan equivalent to set IP assignment to Manual for a profile.

    Per-interface IP/DNS values, Windows stores, are persisted under the TCP/IP parameters in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces<Interface-GUID>. These keys reflect the adapter’s IPv4/IPv6 addresses, gateways, DNS entries, DHCP flags. On the other hand, the Wi-Fi profile XMLs that netsh wlan can add/export do not include TCP/IP static IP or DNS settings. Those are separate. The Settings app uses the newer networking APIs and UWP context to flip the adapter’s TCP/IP configuration; the classic CLI/API (netsh / NetTCPIP) touches the same HKLM keys and therefore requires elevated/network-config privileges. As a result, the IP/DNS are applied to the adapter, not stored inside the wlan profile XML.

    Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same issue too.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.