Thanks for pointing that BITS is no longer used. I did not know that and this explains why the BITS network policy are NOT respected.
I'm fed up seeing Windows Update trying EVERYDAY to download a new image , taking ALL my bandwidth, using several dozens of sessions (all to the SAME server 13.107.4.50 in Microsoft's IP space, this address changes occasionnaly but all active sesssions are
on the same address, always in 13.107.*.*) instead of just jour like for regular internet traffic, and this for hours.
Microsoft should read the RFC's !
This irritates me because each time this is for trying to download again and again the same BROKEN Windows 10 image, and trying to reboot my PC every night and freezing it on the green screen while trying to "resurect" a version of Windows that it does not
find.
Then each morning I need to press the reset button, and then Windows will attempt to boot, but will rollback all changes. And the next evening it will download again the same image.
This makes my Internet connection busy when I need it for someting else; it breaks my TV programs, or when I'm looking at **paid** VOD and suddenly my program is frozen to unusable state.
Really Microsoft has reinvented Bittorrent but not used the policy implemetned notavely in all BitTorrents client I know.
So my be BITS was a mess, but WUDO now is also a mess (and the fact that Microsoft does not document the policy setting and uses an extremely aggressive configuration is really BAD!)
(I could also speak about the fact that Windows 10 wants to reboot and install the same image everyday and makes my PC stopping working normally as it freezes it completely during the update: if an update fails for some reasons, it should NOT restart automatically
(and notably if this was after a revert on boot). It should not even download it again without explicit instruction. It may download other updates, but certainly not those broken Windows 10 builds (that are almost impossible to diagnose of why they fail: I've
looked for all solutions on the Internet, none of them apply: I already had that problem since mostly one year after the initial Windows 10 release; it was finally solved in June where I could install a build, but just a few weeks later, a new build comes
in, that freezes again with the same symptoms at 22% on the green screen for the boot installer ("can't resurrect in VDS, Windows host not found").
These constant problems of installation (or reinstallations) of Windows 10 is a nightmare. Many people did not want to upgrade from Windows 7 because of that. All these problems have been present in Windows 10 even before the commercial release last year.
Microsoft did not make any efforts to solve them or diagnose them correctly (in fact even the Microsoft support does not know what to do, I've spent hours with them, and in fact they did not understood the problem and did not know the diagnostic tools I used,
even though they were written by Microsoft, but not known by their support!)
Seriously, the fact that Microsoft forces people to upgrade and now want them to pay to get the version with an ultimatum ending in 15 days is really bad. And if people have attempted to use the "free" offer, they can't benefit it as Windows 10 fails to
install completely in order to register their licence.
When Microsoft will have solved this issue, the offer will be terminated... users that won't have been able to upgrade since one year will need to pay without knowing if this will ever work or will fail again.
But for now I need a way to stop these downloads or at least reduce their usage. Microsoft MUST honor the policies and MUST read the RFCs: never more than 4 sessions per target server: this is a severe problem also for those that have routers shared by several
users on a LAN: a single PC affects everyone (on my PC Windows Update uses more than 120 parallel sessions to force using all bandwidth available, this is really not fair at all, and in fact abusive...