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.
What I am saying is that I don't need to do that(enable the bug) in the first place. I quite understand your notion regarding this bug.
Yes i know, i was talking about Windows 10 Enterprises Final (Windows 10 Enterprise will not be free for the first year).
believe me, these also will show in x-files section when due I certainly will not provide "medicine" but one day even this problem gets solved ... lol