SG Broadband Community

I had to do this to get this WMO service working properly.
Afterwards TCP Optimizer could read most of the values via PowerShell.

1. Disable and stop the WMI service: (using the Old Command Prompt)

sc config winmgmt start= disabled (note that there is a blank between '=' and 'disabled')
net ...

Thanks Philip. I found the log made by the app and saw a lot of Powershell errors, so I did check the settings in Powershell manually.
Most of the settings are correct as per the "Optimized" settings in the app.

In case it helps, here is the log: (it says Win10, but I am using Win11 23H2)
I could ...

I applied the "optimal" settings to Win 11 via TCP Optimizer 4.1.1 and rebooted.

When I look at "Current" settings in TCP Optimizer, the following fields are blank:
TCP Window Auto-tuning
Congestion Control Provider
RSS
RSC
TTL
ECN Capability
TCP Chimney Offload
TCP 1323 Timestamps

Max SYN ...

Seems there is something on your machine preventing the program from even getting the settings information from PowerShell.
I am running Windows 10 Pro about the same build as yours, and I don't see any of those errors, either the TCP Optimizer is not running as Administrator, or there is some ...

What OS? What version did you upgrade from?
Is your user an administrator? (or you can right-click and "Run as Administrator")
We haven't changed the code much, it seems to read those fine in my Windows 10 machines.

Windows 10 x64 20H2 build 19042.685.
I am the Administrator run the program as ...

I updated to v4.1.1 and the General Settings tab no longer reads the following values: (they are blank). TCP Window Auto-tuning, Congestion Control Provider, RSS, RSC, ECN Capability, TCP Chimney Offload, TCP 1323 Timestamps.

CUBIC is now the default in Windows 10 (since the April 2018 v1803 update).
I would like to think Microsoft have made this change for a good reason.
I have switched between CTCP and CUBIC to test but cannot see any noticeable difference.
Very interested to hear from Philip, and any other experts ...

My Windows 8.1 WMI was indeed really messed up. Microsoft's wmidiag.vbs confirmed multiple registry entries were missing.
The fixes I tried didn't work, so I did a clean install of Windows 8.1. WMI and Powershell "get-nettcpsetting" command now works.

Thanks for the tip.

No, using speedtest.net results wont be an issue with newer Windows variants, and the we are experimenting with the "experimental" mode for very high bandwidth setups, if you'd like to be a bit more conservative just put the slider under 90Mbps and it should return to "normal"..

My conection runs ...

Thanks for testing and the constructive feedback, much appreciated - will look into that. How did you determine what sticks from the general settings tab ? Did you use the "Get-NetTcpSetting" PowerShell cmdlet to check parameters from the General tab, or did you just look at what the Optimizer ...

Hi there Philip,

I have tried Optimizer 4.0 on Windows 8.1 64-bit and here is what happened.

Most of the tweaks on the "Advanced Settings" tab did stick after reboot. The only two that didn't stick as specified by the TCP Optimizer were:

Max SYN Retransmissions - default instead of 2 ...

I don't understand why TCP Optimizer hasn't been updated to work with Windows 8 and 8.1.

We will definitely update the information/Optimizer, I expect to have a Windows 8 testing machine setup later this month. Thanks for the links..

Well, it is a year and a half since 5-Feb-13.

1. Does TCP Optimizer work on properly on Windows 8.1?

2. If not, will TCP Optimizer ever be updated to ...