Win 10 Reg Hack

MagikMark · Post by **MagikMark** » Sun Dec 05, 2021 2:07 am

Hi Philipi

Experimenting the Reg Hack for Windows 10 Pro. Tried changing ICW from 10 to 44.
Nothing happened.

I created reg file as advised then ran "Get-NetTCPSetting" to check TCP parameters.
No changes, ICW still 10 for all templates

Run reg editor changes are reflected there

Did I missed something?

MagikMark · Post by **MagikMark** » Sun Dec 05, 2021 2:20 am

Funny thing is, Upon testing my internet. Everything seems to be snappier

MagikMark · Post by **MagikMark** » Sun Dec 05, 2021 4:37 am

My bad. I have Windows 10 Enterprise

st1cky · Post by **st1cky** » Sun Dec 05, 2021 1:46 pm

Hey did you tested, what i posted sometime ago?

Bypass-Windows-10-Restrictions-(Templates-CongestionProvider)-etc

Post by **Philip** » Sun Dec 05, 2021 5:00 pm

Hi guys.
Not sure which Reg Hack..

MagikMark · Post by **MagikMark** » Sun Dec 05, 2021 5:29 pm

Philipi

The one found here:

https://www.speedguide.net/articles/win ... weaks-7507

MagikMark · Post by **MagikMark** » Sun Dec 05, 2021 5:41 pm

Sticky

What I have tested is the ICW. Windows 10 Enteprise became snappier. Made changes in the registry. However, executing "Get-NetTCPSetting" Did not reflect the changes. I wonder why

These hacks looks very promising. Maybe Philip could integrate it in TCP Optimizer

Post by **Philip** » Sun Dec 05, 2021 6:07 pm

Hm interesting... You should also be able to change it with: Set-NetTCPSetting -SettingName Internet -InitialCongestionWindow 40
However, In Windows 10 Pro Admin PowerShell I am getting an error that the property is read-only.

This also returns an error under current Windows 10 pro builds: netsh int tcp set supplemental template=internet icw=40

I will test some more with the Registry entry. Remember that those registry entries are in hex... 44 decimal would be 2C hex, and you have to reboot.
I can confirm that the Set-NetTCPSetting does not allow changes, and that the Get-NetTCPSetting does not reflect the registry change for ICW.

MagikMark · Post by **MagikMark** » Sun Dec 05, 2021 11:14 pm

Is this correct:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a03-9b1a-11d4-9123-0050047759bc}\26]
"00000000"=hex:00,00,00,00,2C,00,00,00,00,00,00,00,05,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,ff,00,00,00,00,00,00,00
"04000000"=hex:00,00,00,00,2C,00,00,00,00,00,00,00,05,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,ff,00,00,00,00,00,00,00

Post by **Philip** » Mon Dec 06, 2021 8:13 am

Yeah, seems correct.
Mine is currently set at: "00 00 00 00 24 ..." ( decimal 36 = hex 24 )

I am still not sure if auto-tuning is overriding it, since it is not reflected in PowerShell Get-NetTcpSetting after reboot, but it doesn't hurt, and it would be a good initial window.

MagikMark · Post by **MagikMark** » Mon Dec 06, 2021 4:02 pm

Philip

I get snappier experience if I use this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a03-9b1a-11d4-9123-0050047759bc}\26]
"00000000"=hex:00,00,00,00,44,00,00,00,00,00,00,00,05,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,ff,00,00,00,00,00,00,00
"04000000"=hex:00,00,00,00,44,00,00,00,00,00,00,00,05,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,ff,00,00,00,00,00,00,00

Why is that?

MagikMark · Post by **MagikMark** » Mon Dec 06, 2021 6:01 pm

Phiip

I would like to experiment with other variables. What would be an ideal value for the ff:

delayedacktimeout
enablecnwdrestart
delayedackfrequency

Post by **Philip** » Wed Dec 08, 2021 7:51 pm

enablecwndrestart - Controls whether the congestion window is restarted.. You'd have to experiment with this.
delayedackfrequency - Delayed ACK frequency has to do with the Nagle algorithm, look up the info in the Windows 10 Tweaks article: https://www.speedguide.net/articles/win ... weaks-5077
delayedacktimeout - Delayed ACK timeout has to do with the max time for sending delayed ACKs, it should be between 10-300ms, default is 40ms. Changing it would only be useful when using telnet/ssh or games that send very small amounts of data at a time.

MagikMark · Post by **MagikMark** » Sat Dec 18, 2021 4:05 pm

Philip

Do you see any benefits on using this with other templates as described here:

https://www.speedguide.net/forums/showt ... vider)-etc

Post by **Philip** » Sun Dec 19, 2021 9:35 am

Hi Mark,

It would be beneficial only if that other template (let's say "InternetCustom"?) would let you change the values you want to modify, as seen in PowerShell, vs. those same values being read-olnly in the default "internet" template.

There used to be such cases in Windows 8 I believe, where some values would be only writeable in the custom template.

MagikMark · Post by **MagikMark** » Sun Mar 06, 2022 5:48 pm

Philip,

I've been getting this advice that by adding these parameters will improve LAN networking:

HKEY_LOCAL_MACHINES\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
IRPStackSize 32
SizReqBuf 17424

HKEY_LOCAL_MACHINES\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
TCP1323Opts 1
MaxFreeTcbs 65536
GlobalMaxTcpWindowSize 65535

HKEY_LOCAL_MACHINES\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
TcpAckFrequency 1
TcpNoDelay 1

Are those even relevant in /Windows 10/11? What are your thoughts on these?

Thanks

Post by **Philip** » Mon Mar 07, 2022 8:37 am

Most of them are Windows 2k/XP entries, some are still relevant but they are not documented by Microsoft, not sure about a couple. Even if they're not in the Registry they are at their default states. Sometimes Registry entries could be overridden by other settings, at worst they're not going to make any difference. I would read on each setting to make sure you know what they do though...
I wouldn't bother with Tcp1323Opts and GlobalMaxTcpWindowSize at all. Some that may still be relevant are set by the Optimizer btw.

IRPStackSize - specifies the number of stack locations in I/O request packets (IRPs). Each stack uses 36 bytes of memory for each receive buffer. Default 15, range between 11-50, there was an issue with some OSes when set over 32.
SizReqBuf - Increases the memory buffer used by the LanManServer service, it helps increase performance significantly in higher-latency network environments. REG_DWORD value, with a range of from 512 to 65536. It uses non-paged memory, but it shouldn't be an issue to increase it even further with today's PCs.

Tcp1323Opts - RFC 1323 Options, allows for TCP buffers over 65535, enabled by default by all modern OSes including Windows, so not necessary. This is now controlled using other means, (PowerShell cmdlets, netsh, etc.)
MaxFreeTcbs - Determines the number of TCP control blocks (TCBs) the system creates to support active connections (each connection requires a TCB). Windows 2k entry, not sire it is still relevant. The default number used to be dependent on available system RAM.
GlobalMaxTcpWindowSize - old setting overwritten by TCP Auto Tuning in Windows 8/10/11

TcpAckFrequency - how often to send ACK packets. Relevant to gaming, set by the TCP Optimizer.
TcpNoDelay - specifies whether to disable the delay of sending successive small packets on the network. Also set buy the TCP Optimizer.

MagikMark · Post by **MagikMark** » Mon Mar 07, 2022 7:09 pm

I'm using Windows 11 Pro. Just to clarify the following are still relevant and not set in the TCP Optimizer:

IRPStackSize 32
SizReqBuf 65535

Would you recommend those values? I have 24GB of RAM

Post by **Philip** » Tue Mar 08, 2022 8:58 am

Sure, you can do that. I am not 100% sure they still work under Windows 10/11, but, if anything they can help.