Seriously, you did! I know you are looking for an easy exit, sir. However, the Consumer Preview in that context is meant for the Public as per what really differentiate it from private build( a small group made of people who are meant not to diverge it to the public at that particular time or in time to come) regardless of the source types(private or logging) you are alluding to here.
That baffles me a lot! Really, I think they misunderstood me all along. I would have to quit from showing my enthusiasm for Windows OS here.
First time(guess the only time too) I clicked tks on your post, it's your one and only sensible post I guess.
Come on guys this is a 400 page thread please make sure to keep it about Windows 10 because some of us are checking all the new posts daily and it's becoming difficult and boring to keep up in this pace. Don't bloat the thread, contribute to it. Don't insult other members, try to guide them to the right direction. If you want to agree with someone don't create a 4 word post just press Like/Thanks (whichever one is more appropriate on each use-case). If you want to reply to a lot of posts just quote all of them on a single post don't post 3 times in a row. Those are not rules or warnings, these are just my personal opinion on how we can make this thread and eventually the whole sub-forum better. Next time you are ready to press "Post" ask yourself "Do I contribute with this post? Do I join and conversation and support my opinion, give insight, note something that others haven't?" Also make sure you use the "Findings" and the "Discussion" thread in line with their description, I believe all findings should be forwarded in the Discussion thread, but we should first post them on the "Findings" thread so it will not miss out and lose it's usability. PS1: I know I am just a novice member in the forum, but I wrote this paragraph for the best of the thread, its quality, its quantity, its ease of reading. PS2: I really care about your opinions but don't start quoting me and derail the thread once again.
so does this mean that those on 9901 can fix the update issues mentioned by MS by changing the branch to fbl_awesome1501 and the update process will work? Is it currently "broken" because the default branch is fbl_awesome?
Where can I find the reg. fix to make the old update work in control panel. Can someone please post the link or post number My update in settings stopped working This is all I get now
Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX] "IsConvergedUpdateStackEnabled"=dword:00000000 I couldn't find the link, it's somewhere within the 70+ page LEAK thread for 9901. So I just copied it from my own archive for you. Credit obviously goes to the original poster. If I remember correctly it was ace2. Do you think this fix should be added to the REPO?
Every build starts out as a private build, not distributed outside MS, then MS picks a build to distribute, at that point it becomes public, so it's perfectly normal for fbl_awesome builds to be internal for now. Look at fbl_release for example, there were tons of builds that were never released, or released to partner only, but not to Insiders. Only builds marked as Flight Level: Low in Buildfeed are released to the Insider Program. At some point MS will decide that a certain fbl_awesome build is stable enough to be the January build, only after they decided a build is stable enough ("signed off") it becomes public. And oh, a word of warning, I'm never looking for an easy exit, when you get me started on something I can keep going on for weeks, just ask Faikee Just remember it's nothing personal, also let's not keep on debating about this
Couldn't see why I was mentioned....if you mean Win365, then it took months not weeks(and maybe a few months further) for the facts to come out, ATM I couldn't say anything further on it.