build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | 0 skipped | | format
apiVersion: soultec.ch/v1kind: Postmetadata: name: how-to-fix-fix-static-windows-network-settings-reset-after-reboot locale: en labels: author: valentina-cicmak series: how-to capability/network: 2.16 annotations: source: blog-content/posts/en/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.md route: /en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/ schema: /nerd/schema/posts.json markdown: /en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.mdspec: title: Fix Static Windows Network Settings Reset After Reboot date: 2026-06-01 author: valentina-cicmak locale: en summary: >- If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot. capabilities: [network] series: how-to hero: >- /blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/hero.webp legacySlug: how-to-fix-fix-static-windows-network-settings-reset-after-reboot migrated: 2026-08-24 draft: false sections: - body: | If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot. This is especially annoying when the IP address, gateway, or DNS server should actually be configured statically, but are missing or overwritten again after restarting. You can work around this issue by setting the network configuration directly via CMD using netsh. This stores the values directly for the network interface and helps keep them in place even after a reboot. ![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/01.webp) ### Solution If network settings in Windows keep getting reset after a reboot, the IP address, gateway, or DNS server can be set manually via Command Prompt. To do this, open CMD as administrator and configure the network settings using netsh. ![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/02.webp) A static IPv4 address including subnet mask, gateway and DNS can be set like this: ```powershell netsh interface ipv4 set address name="INTERFACE_NAME" static IP_ADDRESS SUBNET_MASK GATEWAY netsh interface ipv4 set dnsservers name="INTERFACE_NAME" static DNS_SERVER primary netsh interface ipv4 add dnsservers name="INTERFACE_NAME" address=SECONDARY_DNS_SERVER index=2 ``` INTERFACE\_NAME, IP\_ADDRESS, SUBNET\_MASK, GATEWAY, and DNS\_SERVER must be replaced with the correct values for your Windows environment. After that, the network settings should remain in place even after a reboot. Below you can find an example configuration. ```powershell netsh interface ipv4 set address name="Ethernet0" static 192.168.1.50 255.255.255.0 192.168.1.1 netsh interface ipv4 set dnsservers name="Ethernet0" static 192.168.1.10 primary netsh interface ipv4 add dnsservers name="Ethernet0" address=192.168.1.11 index=2 ``` - heading:

Next Steps

body: | If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!status: corpus: 267 alsoLike: - {ref: posts/vmware-software-defined-wan, score: 0.85} - {ref: posts/how-to-install-vcenter-without-dns, score: 0.58} - {ref: solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing, score: 0.58}
{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "how-to-fix-fix-static-windows-network-settings-reset-after-reboot", "locale": "en", "labels": { "author": "valentina-cicmak", "series": "how-to", "capability/network": "2.16" }, "annotations": { "source": "blog-content/posts/en/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.md", "route": "/en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.md" } }, "spec": { "title": "Fix Static Windows Network Settings Reset After Reboot", "date": "2026-06-01", "author": "valentina-cicmak", "locale": "en", "summary": "If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot.", "capabilities": [ "network" ], "series": "how-to", "hero": "/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/hero.webp", "legacySlug": "how-to-fix-fix-static-windows-network-settings-reset-after-reboot", "migrated": "2026-08-24", "draft": false }, "sections": [ { "body": "If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot. This is especially annoying when the IP address, gateway, or DNS server should actually be configured statically, but are missing or overwritten again after restarting.\n\nYou can work around this issue by setting the network configuration directly via CMD using netsh. This stores the values directly for the network interface and helps keep them in place even after a reboot.\n\n![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/01.webp)\n\n### Solution\n\nIf network settings in Windows keep getting reset after a reboot, the IP address, gateway, or DNS server can be set manually via Command Prompt.\n\nTo do this, open CMD as administrator and configure the network settings using netsh.\n\n![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/02.webp)\n\nA static IPv4 address including subnet mask, gateway and DNS can be set like this:\n\n```powershell\nnetsh interface ipv4 set address name=\"INTERFACE_NAME\" static IP_ADDRESS SUBNET_MASK GATEWAY\n\nnetsh interface ipv4 set dnsservers name=\"INTERFACE_NAME\" static DNS_SERVER primary\n\nnetsh interface ipv4 add dnsservers name=\"INTERFACE_NAME\" address=SECONDARY_DNS_SERVER index=2\n```\n\nINTERFACE\\_NAME, IP\\_ADDRESS, SUBNET\\_MASK, GATEWAY, and DNS\\_SERVER must be replaced with the correct values for your Windows environment. After that, the network settings should remain in place even after a reboot. Below you can find an example configuration.\n\n```powershell\nnetsh interface ipv4 set address name=\"Ethernet0\" static 192.168.1.50 255.255.255.0 192.168.1.1\n\nnetsh interface ipv4 set dnsservers name=\"Ethernet0\" static 192.168.1.10 primary\n\nnetsh interface ipv4 add dnsservers name=\"Ethernet0\" address=192.168.1.11 index=2\n```" }, { "heading": "

Next Steps

",
"body": "If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!" } ], "status": { "corpus": 267, "alsoLike": [ { "ref": "posts/vmware-software-defined-wan", "score": "0.85" }, { "ref": "posts/how-to-install-vcenter-without-dns", "score": "0.58" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing", "score": "0.58" } ] }}
apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "how-to-fix-fix-static-windows-network-settings-reset-after-reboot"locale = "en"[metadata.labels]author = "valentina-cicmak"series = "how-to""capability/network" = "2.16"[metadata.annotations]source = "blog-content/posts/en/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.md"route = "/en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.md"[spec]title = "Fix Static Windows Network Settings Reset After Reboot"date = 2026-06-01author = "valentina-cicmak"locale = "en"summary = "If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot."capabilities = ["network"]series = "how-to"hero = "/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/hero.webp"legacySlug = "how-to-fix-fix-static-windows-network-settings-reset-after-reboot"migrated = 2026-08-24draft = false[[sections]]body = '''If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot. This is especially annoying when the IP address, gateway, or DNS server should actually be configured statically, but are missing or overwritten again after restarting.You can work around this issue by setting the network configuration directly via CMD using netsh. This stores the values directly for the network interface and helps keep them in place even after a reboot.![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/01.webp)### SolutionIf network settings in Windows keep getting reset after a reboot, the IP address, gateway, or DNS server can be set manually via Command Prompt.To do this, open CMD as administrator and configure the network settings using netsh.![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/02.webp)A static IPv4 address including subnet mask, gateway and DNS can be set like this:```powershellnetsh interface ipv4 set address name="INTERFACE_NAME" static IP_ADDRESS SUBNET_MASK GATEWAYnetsh interface ipv4 set dnsservers name="INTERFACE_NAME" static DNS_SERVER primarynetsh interface ipv4 add dnsservers name="INTERFACE_NAME" address=SECONDARY_DNS_SERVER index=2```INTERFACE\_NAME, IP\_ADDRESS, SUBNET\_MASK, GATEWAY, and DNS\_SERVER must be replaced with the correct values for your Windows environment. After that, the network settings should remain in place even after a reboot. Below you can find an example configuration.```powershellnetsh interface ipv4 set address name="Ethernet0" static 192.168.1.50 255.255.255.0 192.168.1.1netsh interface ipv4 set dnsservers name="Ethernet0" static 192.168.1.10 primarynetsh interface ipv4 add dnsservers name="Ethernet0" address=192.168.1.11 index=2```'''[[sections]]heading = "

Next Steps

"
body = "If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!"[status]corpus = 267[[status.alsoLike]]ref = "posts/vmware-software-defined-wan"score = "0.85"[[status.alsoLike]]ref = "posts/how-to-install-vcenter-without-dns"score = "0.58"[[status.alsoLike]]ref = "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing"score = "0.58"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>how-to-fix-fix-static-windows-network-settings-reset-after-reboot</name> <locale>en</locale> <labels> <author>valentina-cicmak</author> <series>how-to</series> <entry key="capability/network">2.16</entry> </labels> <annotations> <source>blog-content/posts/en/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.md</source> <route>/en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/how-to-fix-fix-static-windows-network-settings-reset-after-reboot.md</markdown> </annotations> </metadata> <spec> <title>Fix Static Windows Network Settings Reset After Reboot</title> <date>2026-06-01</date> <author>valentina-cicmak</author> <locale>en</locale> <summary>If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot.</summary> <capabilities> <item>network</item> </capabilities> <series>how-to</series> <hero>/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/hero.webp</hero> <legacySlug>how-to-fix-fix-static-windows-network-settings-reset-after-reboot</legacySlug> <migrated>2026-08-24</migrated> <draft>false</draft> </spec> <sections> <section> <body>If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot. This is especially annoying when the IP address, gateway, or DNS server should actually be configured statically, but are missing or overwritten again after restarting.You can work around this issue by setting the network configuration directly via CMD using netsh. This stores the values directly for the network interface and helps keep them in place even after a reboot.![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/01.webp)### SolutionIf network settings in Windows keep getting reset after a reboot, the IP address, gateway, or DNS server can be set manually via Command Prompt.To do this, open CMD as administrator and configure the network settings using netsh.![](/blog-assets/how-to-fix-fix-static-windows-network-settings-reset-after-reboot/02.webp)A static IPv4 address including subnet mask, gateway and DNS can be set like this:```powershellnetsh interface ipv4 set address name="INTERFACE_NAME" static IP_ADDRESS SUBNET_MASK GATEWAYnetsh interface ipv4 set dnsservers name="INTERFACE_NAME" static DNS_SERVER primarynetsh interface ipv4 add dnsservers name="INTERFACE_NAME" address=SECONDARY_DNS_SERVER index=2```INTERFACE\_NAME, IP\_ADDRESS, SUBNET\_MASK, GATEWAY, and DNS\_SERVER must be replaced with the correct values for your Windows environment. After that, the network settings should remain in place even after a reboot. Below you can find an example configuration.```powershellnetsh interface ipv4 set address name="Ethernet0" static 192.168.1.50 255.255.255.0 192.168.1.1netsh interface ipv4 set dnsservers name="Ethernet0" static 192.168.1.10 primarynetsh interface ipv4 add dnsservers name="Ethernet0" address=192.168.1.11 index=2``` </body> </section> <section> <heading>

Next Steps

</heading>
<body>If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!</body> </section> </sections> <status> <corpus>267</corpus> <alsoLike> <item> <ref>posts/vmware-software-defined-wan</ref> <score>0.85</score> </item> <item> <ref>posts/how-to-install-vcenter-without-dns</ref> <score>0.58</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing</ref> <score>0.58</score> </item> </alsoLike> </status></manifest>
How-To · 2026-06-01

Fix Static Windows Network Settings Reset After Reboot

If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot.

2026-06-01Date
Valentina CicmakAuthor
1Min read
Topics Network 2.16

If you ended up on this blog, you are probably dealing with the issue that your network settings keep getting lost after a reboot. This is especially annoying when the IP address, gateway, or DNS server should actually be configured statically, but are missing or overwritten again after restarting.

You can work around this issue by setting the network configuration directly via CMD using netsh. This stores the values directly for the network interface and helps keep them in place even after a reboot.

Solution

If network settings in Windows keep getting reset after a reboot, the IP address, gateway, or DNS server can be set manually via Command Prompt.

To do this, open CMD as administrator and configure the network settings using netsh.

A static IPv4 address including subnet mask, gateway and DNS can be set like this:

netsh interface ipv4 set address name="INTERFACE_NAME" static IP_ADDRESS SUBNET_MASK GATEWAY

netsh interface ipv4 set dnsservers name="INTERFACE_NAME" static DNS_SERVER primary

netsh interface ipv4 add dnsservers name="INTERFACE_NAME" address=SECONDARY_DNS_SERVER index=2

INTERFACE_NAME, IP_ADDRESS, SUBNET_MASK, GATEWAY, and DNS_SERVER must be replaced with the correct values for your Windows environment. After that, the network settings should remain in place even after a reboot. Below you can find an example configuration.

netsh interface ipv4 set address name="Ethernet0" static 192.168.1.50 255.255.255.0 192.168.1.1

netsh interface ipv4 set dnsservers name="Ethernet0" static 192.168.1.10 primary

netsh interface ipv4 add dnsservers name="Ethernet0" address=192.168.1.11 index=2

Next Steps

If you’ve read this far then chances are you are still having issues. Feel free to reach out to us. We’re happy to help out!

You might also like

post 0.85

Software-Defined WAN

post 0.58

Install vCenter without DNS

solution 0.58

Load Balancing (Avi)

Page to follow