Parameter disappears

Question

I am encountering an issue on Windows 11 where my DefaultTTL setting disappears after every reboot. After restarting the computer, the DefaultTTL setting is reset and disappears.

I have confirmed that I have administrator privileges and full control when setting the value. I have checked Group Policy and third-party software to ensure they are not overwriting my settings. I tried using a scheduled task to automatically set the DefaultTTL on startup, but the issue persists.

I suspect that this issue might be related to Windows updates overwriting my settings or internal system or policy configurations affecting my custom settings.

How can I ensure that the DefaultTTL setting remains unchanged after a reboot?

Thank you for your help!

***Moved from Windows / Windows 11 / Settings***

Answer 1

In my case, on a Windows Server 2022 system, it turned out to be the 'Host Network Service', which I'm assuming was left over from when I was messing around with Hyper-V.

The way I found which service was doing it was by clicking "Options > Enable Boot Logging" in Sysinternals ProcessMonitor. After rebooting I loaded ProcessMonitor back up and it showed it was 'svchost.exe' that was messing with the registry value, but I was able to narrow down the exact service by the PID.

The filter I used for ProcessMonitor was the following: " path - contains - 'DefaultTTL' "

Hopefully in your case it's not an essential app or service that's doing it. I was able to disable the service and the TTL value seems to stick now, I don't think the service does anything important in my case anyway.

Answer 2

Hello,

Thank you for posting in Microsoft Community forum.

According to your description, the issue may be due to system settings, Group Policy, or other configurations. We recommend that you try the following solutions:

1. Make sure you have the correct permissions on the registry key.

Press the Win + R keys, type regedit and press enter to open the registry editor.

By checking the following registry path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Right-click on the Parameters folder and select Permissions. Make sure your user account or group has full control. If not, add your user account and give full control.

2. Group Policy may override your settings. Check to see if any Group Policy settings are affecting DefaultTTL.

Press the Win + R keys, type gpedit.msc and press enter to open the Group Policy Editor. Navigate to Computer Configuration -> Administrative Templates -> Network -> TCP/IP. Check to see if you have set a policy related to DefaultTTL and make sure that there are no policies that affect your settings.

3. Check to see if there are any security software or optimization tools that might affect your registry settings. Some system optimization tools may reset registry settings.
4. Check for Windows Updates

Windows Update may reset some system settings. You can check for updates related to the DefaultTTL setting, or disable automatic updates to test if the update is causing the issue.

Turn on Update & Security in Settings. Check your update history to see if there are any relevant updates.

5. Corrupted system files may cause settings to not be saved. Use the system file checker tool to verify and repair system files. Open Command Prompt or PowerShell as an administrator.

Run the following command: sfc /scannow

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.



Regards,

Jill Zhou

Answer 3

Thank you for your response, Jill.

I do feel that it is related to the Windows updates, but I haven't found any points in the recent update information indicating that the default parameters would be reset, especially the DefaultTTL setting, which I first noticed. Perhaps this is an issue that needs to be addressed. However, I cannot confirm which version caused the problem after KB5039895. I am still trying to find the root cause of the problem.

Answer 4

Run this in powershell:
netsh int ipv4 set glob defaultcurhoplimit=65

It worked for me.

You can assign it as a startup command, to run automatically after turning on