wrote:
Uggh... sometimes I miss the days of manual RWIN tweaking in the registry... there were some nice tools that made it easy button clicks and a quick reboot.
If switching Auto tune mode doesn't resolve it, may want to try giving the stack a reset of sorts. Similar command setup, just telling it to reset the tcp interface. Haven't used it in a while (last time was in 8.1), but it should still be valid in Win10. A bit foggy on the exact syntax, but should be able to google it and get an official hit from the Microsoft site if it errors out:
netsh int ip reset c:\resetlog.txt
Note these netsh commands need to be run from an administrative command prompt (search "cmd", right click the command it finds and select "run as admin"). You have to tell it where to dump output to, doesn't have to be tbe specific file given, but you have to tell it where to put it.
That command should basically set the stack back as if you had just installed the drivers (DHCP, auto DNA config, etc.). So if you were running static numbers you would need to go back and change them. It is sort of a last-ditch thing to try before dumping the network card in device manager and re-installing it again.
EDIT: originally put the wrong interface of tcp, modified to ip as demonstrated here:
https://support.microsoft.com/en-us/help/299357/how-to-reset-tcp-ip-by-using-the-netshell-utility
A couple of mentions,
No one should do registry edits unless they are computer savvey and know what they are doing. The same is true for becoming a Windows 10 Insider to do Beta Testing for Fast Ring/Slow Ring releases. Wrong turns could lead you to having to reinstall Windows.
Does the user own their own modem? If you rent from Spectrum, you won't be able to update the modem on your own. You may have to have Spectrum come out and see what is going on about the speeds. Don't reboot for six hours toward the time of your appointment. The tech needs to see the error codes.
Satch