Choosing Optimal -> Reboot -> Choosing Optimal again, every time says there are differences. Then, doing an export of the Current settings and comparing them to an export of the Optimal settings gives these differences - first value is Current, second is Optimal:
[netsh]
AutoTuningLevelLocal=4
AutoTuningLevelLocal=3
EcnCapability=2
EcnCapability=0
Chimney=2
Chimney=1
EnableDCA=2
EnableDCA=1
[System\CurrentControlSet\Services\Tcpip\QoS]
Do not use NLA_SEL=1
Do not use NLA_SEL=0
[SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
SystemResponsiveness_SEL=10
SystemResponsiveness_SEL=0
[Wi-Fi Connection]
NetAdapterRsc=2
NetAdapterRsc=1
Large Send Offload=-5
Large Send Offload=2
Checksum Offload=-5
Checksum Offload=1
[Ethernet Connection]
NetAdapterRsc=2
NetAdapterRsc=1
Checksum Offload=-5
Checksum Offload=1
Modify All Network Adapters is ticked and Large Send Offload does not work on my WiFi-adapter, so I can understand that.
But for the Ethernet Connection and the other sections/values I don't have a clue...
Tia,
MaKi
Issues in TCP Optimizer 4.0.2: Optimal values not not "stick"
I will look over those in detail to make sure Windows is not resetting anything after reboot, thanks for the info.
Keep in mind that some may have the same "default/optimal" value, and some may not be read at program start (NIC-specific).
For "Checksum Offload" and LSO, the value of -5 means "no change"
For those:
Note that you will have two values for each, i.e.
SystemResponsiveness=nnn (actual registry value that is read currently, provided you are exporting current settings)
SystemResponsiveness_SEL=nn (just visually what is currently selected in the combo box)
Keep in mind that some may have the same "default/optimal" value, and some may not be read at program start (NIC-specific).
For "Checksum Offload" and LSO, the value of -5 means "no change"
For those:
Those are just the currently selected values in the program (visually). They are not the actual registry values. This is true for anything with "_SEL" in the export files.[System\CurrentControlSet\Services\Tcpip\QoS]
Do not use NLA_SEL=1
Do not use NLA_SEL=0
[SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
SystemResponsiveness_SEL=10
SystemResponsiveness_SEL=0
Note that you will have two values for each, i.e.
SystemResponsiveness=nnn (actual registry value that is read currently, provided you are exporting current settings)
SystemResponsiveness_SEL=nn (just visually what is currently selected in the combo box)
Fair enough, but why did I have to enable them manually using PowerShell?Philip wrote:The values that are "blank" are not read at program start (since they may be set differently for different network adapters on the system).
We changed the TCP Optimizer behavior with version 4.0.3 to show blanks instead of "default" for values that are not read at program start.
If you reenter the same command, PowerShell will run it every time and return "Ok". That by itself is not an indication that the command wasn't executed before, or that it didn't stick. You'd have to get the information out using the cmdlets described in our article here: http://www.speedguide.net/articles/wind ... weaks-5077
For example, to see the current RSS value for each RSS-capable network adapter, you'd have to use:
Get-NetAdapterRss -Name *
You'd have to do something similar for each value you're testing If you notice something that is not properly applied by the Optimizer, but works in PowerShell, we definitely want to know. Note that not all NICs support all settings.
For example, to see the current RSS value for each RSS-capable network adapter, you'd have to use:
Get-NetAdapterRss -Name *
You'd have to do something similar for each value you're testing If you notice something that is not properly applied by the Optimizer, but works in PowerShell, we definitely want to know. Note that not all NICs support all settings.