kirb
Adjust estimated time for updates
Hello there,
I have noticed that most of the time the estimated time for updates is very short, usually 2 to 5 minutes and to be honest that seems like a very unrealistic amount of time considering the hardware we run this on (hard drives, old wifi/ethernet adapters, old processors).
Even though I don't expect estimated times to be real, it would be a nice fix if times were changed to something more realistic, from 15 minutes to 2 hours (in my experience).
The estimate is just for download, not anything else like install time. Even then, I hardcoded it to assume your connection is 15 Mbps (or something like that). That seemed like a safe enough number initially - best case, it beats expectations, worst case, you know your internet is slower than that anyway.
The original Windows Update website had some logic to figure out which network adapter you're using, and would grab the speed from that. That doesn't work for LANs though, where the connection to your router might be 100 Mbps or 1 Gbps, but the connection from your router to the internet will be something very different. So I didn't bother writing the code for that in the ActiveX control, and hardcoded it to a safe value.
Your true internet speed can only be determined by a speed test, as in, downloading a file and seeing how quickly it downloads X megabytes. I've thought about having Legacy Update do that, but I'm not sure if it makes sense to "waste" a bit of your bandwidth for a little number in the corner you might not even notice. Honestly, it might make more sense to hide it entirely, because the slow part isn't downloading any more - it's installation. Internet (and Microsoft's CDN) is fast enough now we don't need to care so much about the download speed. Meanwhile, installation speed has significantly gone down (some later updates such as for .NET Framework 3.x/4.x are horrendously slow) but that can't really be estimated.
