Snuffy, as the parameter is boolean, non-existence equals to false (as opposed to some that treat a parameter as an integer for a list option, such as for example, Windows Update settings). Also this Microsoft Community thread is outdated, because KB3035129 sets ThresholdRiskLevel to medium, also when Internal is not set or false, RiskLevel is ignored - ThresholdOptedIn sets ring to fast, not risklevel.
Could you guys (or a mod) please take the AeroGlass discussion elsewhere? It's cluttering up the thread IMO. I'm sure there are other people who just don't care for Aero, it would be nice if this Thread was just for vanilla Windows 10. Of course that's just my humble opinion, feel free to ignore it
I don't see the 'bug' as an issue that would prevent users from receiving future updates nor does it prevent any feature from working properly. I am still able to do my Windows Update despite the Build download issue.
This parameter was there since 4 months, just that with this "bug" it became broader knowledge. FYI when any previous build was publicly released for example 9879, if you had internal set, you couldn't download the public drop, because flighting was offering you builds newer than it. You can go and install that old build, or 9860/9841 and set internal on and branch to fbl_awesome1501. WU will "offer" you 9933/9934, not the public 9926. Not to mention leaked 9888/9901 where internal was set by default.
Why should I do that in the first place? All I need to do, if I have those old Builds installed on my system, is to upgrade normally as the KB file responsible for the bug is not available in those old Builds.