When you export settings, the default suggested file name is ooshutup10.cfg.cfg. Note the double .cfg. Then when you try to import your setting, the program can see it in explorer so you are not able to select it but you can still paste its full path to load it. It needs to be fixed.
Could you tell me what method is used to prevent automatic driver update through WU? Because I can see any changes in the windows device installation setting as described here.
There are 2 settings in ShutUp10 to disable automatic WU. In my french version, it is not so explicit which does what. They share the same description.
The 1st one could be translated as "Automatic update of windows update is disabled".
If I enable it and reboot I don't know if Windows automatic update is really disabled but I can still manually run the update. Good, this is what I would expect: let me control when I want to run update. However after that the windows update advanced settings to download other microsoft products update can't be enabled. So what does this first ShutUp10 settings really do?
The 2nd one could be translated as "Automatic update of windows is disabled". If I enable it, I can't no longer run WU, it returns me an error. So it seems that it disables all update feature. If so the settings label in ShutUp10 should be changed to "Windows update is disabled"
In Windows Update section, there are 3 options to disable WU through P2P with same label and description. It is not very helpful for end user to determine what each option does and why one should enable one instead of the other one. Please explain what each option does or mix them in only one option.
Like many users report, during windows update process, windows 10 1607 is eating all the internet bandwidth including for other computer connected in the same local network. It makes other programs using internet unusable (browser and so on). There may be some tweaks to limit WU bandwidth and priority.
Some reports registry tweak such as:
Code: Alles auswählen
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\BITS] "EnableBITSMaxBandwidth"=dword:00000001 "MaxTransferRateOnSchedule"=dword:000007d0 "MaxTransferRateOffSchedule"=dword:000007d0 "UseSystemMaximum"=dword:00000000
The same can be achieved and manually set with Group Policy→Administrative Templates→Network→Background Intelligent Transfer Service (BITS)→Limit the maximum network bandwidth for BITS background transfers. But it needs some investigations because some guys reported it won't work, the rule is not respected unless maybe update through P2P is completely disabled. Interesting discussion about it here.
It seems that we have to look at Group Policy Editor > Local computer strategy > Computer configuration > Administrative templates > Windows components > Delivery optimization. Here you can set the Max Upload Bandwidth in KBytes/s this time and other stuffs. Delivery optimization→download mode set to 100 should force BITS to be used instead of P2P.
It would be great that ShutUp10 investigate on this and offer options in feature release to limit WU bandwidth.