[SOLVED] Default gateway erased/reset/lost on reboot


Recommended Posts

Ok so as the title says , my tcpip default gateway gets reset on reboot , i have to manually set it again for my connection{static ip} to work.... Googling has not helped , i've tried everything - reseting tcpip , winsock , drivers - old and latest, meddling with the tcpip /interface registry entries , a win7 x64 clean reinstall fixed the problem for a while but it popped back suddenly and i cannot find the cause for it .

Someone please help me out . thanks

Hi,

As per the issue description and the steps you mentioned, i seems you have tried all possible steps to fix the problem. Here is what i will suggest and that should fix the issue.

On the problem machine, Expand to following location in registry editor.

HKLM__System__Current Control Set__Control__Network

In the right side pane, there is a REG_BINARY key named "Config", delete this key and reboot the machine and it should fix the problem.

Note : Its highly recommended to take the back up of the registry before you make any changes.

Thanks,

TechyAdmin

to be honest I find this a little hard to believe.. So for example your static set a lets say

192.168.1.100

255.255.255.0

192.168.1.254

And your saying the 192.168.1.100 and the mask stay but your gateway is gone? Is it all zeros? Just empty, what?

On your advanced IP setting do you have multiple IPs or multiple gateways setup? How many nics do you have in this machine? Do you have a wireless card as well as your ethernet? Are you connecting to multiple networks at the same time? 2 wired, wired and wireless?

You must have something on boot that is trying to set your IP, do you have any 3rd party software for location based IP settings running? What happens when you boot into safe mode with networking?

So your saying it keeps your IP and mask -- just the gateway is missing? That makes no sense what so ever.. Are you using IPv6?

Can you post the output of your ipconfig /all before you fix the gateway issue.

Using IP4 .. heres the output from ipconfig

Ok this is just after I reboot

lMsm8.png

this is after a few second it gets the auto configuration ip , however DHCP is disabled , I tried to disable autoconfiguration IP using this registry key ,but it doesnt seem to work

  Quote
Parameter: IPAutoconfigurationEnabled

Type: Reg_Dword

Value: 0 or 1

Key: tcpip/parameters for all NICs

Key: tcpip/parameters/interfaces/interface for that NIC

tdJvT.png

4TY2A.png

this is after I set my gateway , all normal.

@TGT: Not really ,I removed adobe pdf reader just to check . no luck

where is it getting the opendns servers for dns from if its using APIPA?

When you set to static IP vs dhcp, are you and admin account? Do you have UAC enabled?

Autoconfiguation is different than dhcp. And where exactly is the dword you setting?

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Adapter GUID>

Note The Adapter GUID subkey is a globally unique identifier (GUID) for the computer's LAN adapter.

Specifying a value of 0 for IPAutoconfigurationEnabled DWORD

So once you set this and reboot -- and you go back into the registry is it still set?? If you have that set in the correct place an ipconfig /all is showing its still enabled - then something wrong with the as far as permissions, or if missing something over writing the key, etc. etc. once you set a static it should be in the KEY. example

post-14624-12813691684902.jpg

Seems like to me your key is not being saved with the setting, or something is over writing it on reboot, etc. So look at your key after you make your static settings.. Now reboot, what is shown in the key? You can view exactly what the guid is for your interface with the

C:\Windows\system32>net config rdr

Computer name \\QUAD-W7

Full Computer name quad-w7.local.lan

User name <snipped>

Workstation active on

NetBT_Tcpip_{85B20B24-8E34-4B9F-B804-B9FE8BE17F9B} (00219B03ACA7)

Software version Windows 7 Ultimate

Workstation domain LOCAL

Logon domain quad-w7

COM Open Timeout (sec) 0

COM Send Count (byte) 16

COM Send Timeout (msec) 250

The command completed successfully.

edit: you most likely need to be running from an elevated prompt for the net config command to work.

Ok I entered that dword value into the interface key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Adapter GUID>

and apipa is now disabled. i'm on a admin account and uac is disabled .

Gateway is still erased on reboot. I thought it was the permissions too , I verified the permissions to the TCPIP key and it was proper.

and btw there's only 1 subkey - guid in interface key and all the arrowed-entries are present

So you seeing the gateway get placed into the key when you set it using the adapter config gui, and then when you reboot its gone??

Makes no sense -- you have to have something doing a config of your adapter on bootup, or importing the key settings, etc. Very Very ODD!!

You could to monitor your reg and see what is making the change.

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

So its there, just not getting read?

I would do a full reset of the your ip stack

netsh int ip reset

You will elevated prompt to do this.

edit: ah I see you stated you did this? "reseting tcpip" Is that command you ran?

Hey for grins -- take a look at your gateway reg key, does there happen to be a blank line above your gateway IP?

post-14624-12813754353209.jpg

Edited by BudMan

Holy crap! I Just noticed my defaultgateway key was a single string REG_SZ as opposed to REG_MULTI_SZ in your screenshot . omg the smallest of things , i'm gonna reboot n check it out

edit: nope , didnt work , i thought there was a breakthru here lol

  On 09/08/2010 at 17:43, lordvj said:

Holy crap! I Just noticed my defaultgateway key was a single string REG_SZ as opposed to REG_MULTI_SZ in your screenshot . omg the smallest of things , i'm gonna reboot n check it out

edit: nope , didnt work , i thought there was a breakthru here lol

This might work - Doesn't solve the root problem, but is a patch to hold it together, why not have a script launch at Start up to automatically change the Gateway from ___.___.___.___ to the address you want.

Does not make any sense that it would of been a REG_SZ?? Some software must of jacked that up?? I have even looked at my XP box and its a REG_MULTI, very strange...

I had just noticed from you screenshots that the subnet mask does change as well.

255.255.0.0

&

other screenshot says:

255.255.255.0

Not sure if this was a onetime typo but just a note FYI

** EDIT **

I have seen this one time before while doing support to the clients network now that I am thinking about it. Ill ask around the office.

1) Have you changed your router or router firmware recently?

2) Which router and model + firmware do you have?

3) Do any other device experience this issue? Laptops? XBOX? Phones?

** EDIT 2 **

It was solved by the time i hit submit , ignore my stuff

Since he is setting his IP static -- does not mater what router or dhcp server he might be using, since this would never come into play at all. As to the netmask changes you saw.. Those were from APIPA which defaults to 16bit mask, that was not him setting his IP or mask.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Thanks for your linked article of off site examples of Windows Next hate, for a moment I thought you were lumping in all neowin users and reporters into that same category.
    • Man, the only Vista hate I remember was the fact you needed a pretty decent GPU to enable Aero Glass, and they also turned it off until you Activated Windows (no try before you buy). Point me to any articles we did on Vista hate? People shouldn't throw around accusations like this without at least backing themselves up.
    • Finally the tasteless sound is replaced with the good old pleasant sounding one.
    • Surface Pro 11 and Laptop 7 get big firmware updates that fix shutdowns, black screens, more by Taras Buria Microsoft has released major firmware updates for some of its ARM-powered Copilot+ PCs. The Surface Pro 11 and the Surface Laptop 7 can now download the June 2025 firmware updates. These updates address a wide range of issues, including abrupt shutdowns when playing Netflix, black screen flashes, bugs with the Slim Pen haptics in OneNote, incorrect battery indication on the taskbar, and various performance improvements. Here are the changelogs for both devices: Surface Pro 11 Surface Laptop 7 Reliability: Improves system stability and reduces the frequency of unexpected shutdowns or the occurrence of a black screen while watching Netflix. Mitigates the issue that could cause screen flashing or a blank display during power state transitions. Improves the touch experience by resolving an issue where touch functionality could be lost after the device remained in Sleep mode for an extended period. Addresses an issue with Slim Pen losing haptic or Side button functionality in Microsoft OneNote. Resolved an issue where the battery icon incorrectly displayed the device as plugged in after waking from Sleep mode, even when it was not connected to a power source. ​ Performance and usability: Resolves the issue that caused authentication failures while using Windows Hello when waking from Sleep mode. Improves camera stability by reducing unexpected crashes and addressing issues, including freezing in video calls when HDR is enabled, errors when launching the Camera app or taking photos, and problems switching between front and rear cameras in some apps. Mitigates an issue where the Settings app could crash when setting up Fingerprint recognition. Interoperability: Resolves connectivity issues that caused the device to lose wired network access or fail to detect external monitors when connected via USB-C. Reliability: Improves overall stability, reducing occurrences of unexpected crashes and error screens. Reduces the occurrence of crashes during audio streaming sessions. Minimizes display timeout events and reduces the frequency of recovery cycles. Resolves an issue that caused the screen to remain black when resuming from Sleep mode. Performance and usability: Addresses an intermittent audio disruption experienced during video playback with Bluetooth headsets. Resolves a problem that caused Teams audio to drop during transitions between Bluetooth and built-in speakers. Addresses a startup issue that prevented USB Type-A devices from being recognized on the first boot. Interoperability: Resolves an issue introduced in the April 2025 release that prevented Thunderbolt 4 monitors from functioning when connected to the host device. You can get these updates by heading to Settings > Windows Update. Like Windows updates, Surface firmware releases are cumulative, which means a single download contains every update released so far. While the latest firmware updates for the Surface Pro 11 and the Surface Laptop 7 do not contain any known issues, keep in mind that firmware is not uninstallable, so back up important data to keep it safe before updating. You can find release notes for the Surface Pro 11 here and the Surface Laptop 7 here. Note that these updates are only available for Snapdragon-based versions, not those with Intel processors.
    • Here’s some history of this nonsense for people with short memories. https://www.neowin.net/amp/windows-next-hate-is-nothing-new/
  • Recent Achievements

    • One Month Later
      Jdoe25 earned a badge
      One Month Later
    • Explorer
      Legend20 went up a rank
      Explorer
    • One Month Later
      jezzzy earned a badge
      One Month Later
    • First Post
      CSpera earned a badge
      First Post
    • One Month Later
      MIR JOHNNY BLAZE earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      617
    2. 2
      ATLien_0
      277
    3. 3
      +FloatingFatMan
      178
    4. 4
      Michael Scrip
      151
    5. 5
      Steven P.
      117
  • Tell a friend

    Love Neowin? Tell a friend!