Optimizer puts in wrong values?

[Kerry Chipman]

This is with Win 10 and the optimizer 4.0 beta.
Note the MaxUserPort: shows 65534 in the app but in the registry under HKLM System\CurrentControlSet\Services\Tcpip\Parameters\ it adds 17408 or 0x00004400 hex.
I tried this several times and even manually changed the value and saw optimizer put it back to 17408, again even though the app shows 65534.

Until recently I was connecting to my 5ghz wifi fine. But now it's started saying "Can't connect to this network", even though I know the network is fine because i connect to it from my Win7 machine. And interestingly my Win 10 can still connect to the 2.4Ghz WiFi.

There are a few other problems such as some values appear to not being written at all.
I run the app as administrator. This Win10 is an upgrade from Win7. But i tried sfc /scannow and it found nothing, also ran a disk check and found no problems.

Would really like to be able to connect to my 5ghz wifi again. Thanks, Kerry

[Philip]

The default value is most likely 17408. Are you running the TCP Optimizer as administrator ? Does it work if you go to "custom" mode using the radio buttons at the bottom, then manually type 65534 and "Apply" the changes ?

It seems to work under Windows 8.1, I don't have a Windows 10 machine handy at the moment. Please let me know if you test it with the "custom" mode, or if anyone else is experiencing the same issue as the original post.

[Kerry Chipman]

I run as administrator. I actually have the app set for "Run this program as an Administrator" in Compatibility for all users from the Compatability Tab-Change settings for all users, from right click properties.
I have a Win 7 machine that does not have the issue. I believe i tried custom before and it had the same issue, will try again right now.
Just for kicks i'm typing in 65533 instead of 65534. Hit apply changes, The review screen shows MaxUserPort with Old value 65534, New value 65533, default value n/a, and path HKLM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort. Hit OK. After what feels like an excessive time, several seconds, I get the message to reboot. With the message still up I see the correct value in! Restart the system and it's still correct. Good call on checking typing in a value with custom. I will try procmon to see if i can see the reg writes going on.

[Kerry Chipman]

ProcMon shows that TCPOptimizer is writing the correct value but c:\windows\sytem32\wbem\wmiprvse.exe is writing the 17408 a second after TCPOptimizer.
With custom there is only one write from TCPOptimizer. With Optimal there are two writes, one from wmi setting the wrong value. I find it quite curious that this happens. When you figure it out please send me a summary of what the root cause is.

[Philip]

wmiprvse.exe is the Windows Management Instrumentation (WMI) host process. The WMI process runs WMI queries for any other process making them, so wmiprvse.exe is simply an intermediary... WMI can be used to query for system information (processor usage, running processes, who is logged on, etc.).

I just tested with Windows 10, and the "Optimal" settings seem to write the value correctly as well. There may be some other non-Windows service overwriting the value in your case, such as vendor-specific Wifi discovery service, or virtual router, tethering, VPN, Internet sharing, just as a few possible examples... Is this a laptop ? Are there any non-Windows services running related to networking, like "HP Wireless Assistant Service", for example ?

[Kerry Chipman]

this is an old computer that i have upgrade for years, so anything is possible. I dont know of what 3rd party service might be causing this. I am running avg, but same on the win7 computer.It's also the same network card and similar hardware otherwise.
I agree with your assessment, but i cant imagine what would be causing this specific issue. Maybe i can monitor WMI and figure out what is calling it? Might be too much trouble to bother.