Page 8 of 8
Re: HIGH % YOUR InputLag/HitReg IS NETWRK RELATED.
Posted: 06 Jan 2026, 14:00
by Syykfk
Hyote wrote: ↑27 Feb 2025, 07:19
I've been experimenting with some settings that needed to be disabled in gpedit and now I have massively reduced desync. The last two that disable cmd and regedit should be set before playing games and reenabled when needed. There is a potential for placebo as always but the reason I'm sharing these is because I notice a huge change in online games which have been nearly unplayable until now.
Computer Configuration, Administrative Templates, System:
Display highly detailed status messages - Disabled
Computer Configuration, Administrative Templates, Windows Components, Event Logging:
Enable Protected Event Logging - Disabled
Computer Configuration, Administrative Templates, Windows Components, Event Viewer:
Events.asp program - Disabled
User Config, Admin Templates, System, Scripts:
Run legacy logon scripts hidden - Enabled
Run logon scripts synchronously - Disabled
Run Windows PowerShell scripts first at user logon, logoff - Enabled
User Config, Admin Templates, System:
Prevent Access to the command prompt - Enabled ; Disable the command prompt script processing also - Yes
Prevent Access to registry editing tools - Enabled ; Disable regedit from running silently - Yes
Are these adjustments still in effect?
Are there any new adjustments or interpretations?
Re: HIGH % YOUR InputLag/HitReg IS NETWRK RELATED.
Posted: 06 Jan 2026, 16:34
by Hyote
Syykfk wrote: ↑06 Jan 2026, 14:00
Hyote wrote: ↑27 Feb 2025, 07:19
I've been experimenting with some settings that needed to be disabled in gpedit and now I have massively reduced desync. The last two that disable cmd and regedit should be set before playing games and reenabled when needed. There is a potential for placebo as always but the reason I'm sharing these is because I notice a huge change in online games which have been nearly unplayable until now.
Computer Configuration, Administrative Templates, System:
Display highly detailed status messages - Disabled
Computer Configuration, Administrative Templates, Windows Components, Event Logging:
Enable Protected Event Logging - Disabled
Computer Configuration, Administrative Templates, Windows Components, Event Viewer:
Events.asp program - Disabled
User Config, Admin Templates, System, Scripts:
Run legacy logon scripts hidden - Enabled
Run logon scripts synchronously - Disabled
Run Windows PowerShell scripts first at user logon, logoff - Enabled
User Config, Admin Templates, System:
Prevent Access to the command prompt - Enabled ; Disable the command prompt script processing also - Yes
Prevent Access to registry editing tools - Enabled ; Disable regedit from running silently - Yes
Are these adjustments still in effect?
Are there any new adjustments or interpretations?
I don't use these anymore as my scripts and Windows ISO already come with all of the above either disabled or broken.
Re: HIGH % YOUR InputLag/HitReg IS NETWRK RELATED.
Posted: 06 Jan 2026, 18:31
by Syykfk
Hyote wrote: ↑27 Feb 2025, 07:19
I don't use these anymore as my scripts and Windows ISO already come with all of the above either disabled or broken.
Thank you for your reply, and thank you for your contributions to the community.
Re: HIGH % YOUR InputLag/HitReg IS NETWRK RELATED.
Posted: 06 Jan 2026, 20:27
by Hyote
Syykfk wrote: ↑06 Jan 2026, 18:31
Hyote wrote: ↑27 Feb 2025, 07:19
I don't use these anymore as my scripts and Windows ISO already come with all of the above either disabled or broken.
Thank you for your reply, and thank you for your contributions to the community.
I wish I could meaningfully contribute with settings that aren't for specific use cases or break important features. Right now I'm working on a program that is supposed to make games utilize cores in a more efficient way but unlike other posters and Discord advertisers I'm going to make it open source and not base it on core burning or core hopping or any nonsensical tinkering.