Large Send Offload (LSO) says enabled after reboot

Get help and discuss anything related to tweaking your internet connection, as well as the different tools and registry patches on the site. TCP Optimizer settings and Analyzer results should be posted here.
Post Reply
User avatar
shoober420
New Member
Posts: 17
Joined: Sun Oct 13, 2024 6:36 pm

Large Send Offload (LSO) says enabled after reboot

Post by shoober420 »

When disabling Large Send Offload (LSO) via TCPOptimizer and doing a reboot, the setting claims to still be enabled when opening TCPOptimizer after reboot. When going to NIC properties, LSO says its disabled, for both V1 and V2, along with IPv4 and IPv6. I have a Marvell AQtion 10GBASE-T NIC with the latest drivers (3.1.10). Could this be because Im on Windows 11 canary 27723?
User avatar
Philip
SG VIP
Posts: 11699
Joined: Sat May 08, 1999 5:00 am
Location: Jacksonville, Florida

Re: Large Send Offload (LSO) says enabled after reboot

Post by Philip »

Are you starting the TCP Optimizer "As administrator"?
When you click on the "Apply" settings in the TCP Optimizer, it shows exactly what Registry entries and PowerShell cmdlets are executed. You can then open PowerShell and view the settings and confirm they're changed with Get-NetTCPSetting

To see network adapters that support LSO, the cmdlet is:
Get-NetAdapterLso -Name *

To set:
Enable-NetAdapterLso -Name *

I am not aware of changes in the Windows 11 setting.
User avatar
shoober420
New Member
Posts: 17
Joined: Sun Oct 13, 2024 6:36 pm

Re: Large Send Offload (LSO) says enabled after reboot

Post by shoober420 »

So running "Get-NetAdapterLso -Name *" does confirm its disabled, but TCPOptimizer still reads enabled. Do you think its a bug with TCPOptimizer reading the setting? Heres a pic to show you what I mean. Im on the wired Ethernet profile.

https://ibb.co/djy68mG
User avatar
Philip
SG VIP
Posts: 11699
Joined: Sat May 08, 1999 5:00 am
Location: Jacksonville, Florida

Re: Large Send Offload (LSO) says enabled after reboot

Post by Philip »

Maybe the TCP Optimizer is reading the setting from a different network adapter in your particular case, not sure why. It reads them from a Registry hive, I'd have to look into it further.
Post Reply