Discussion in 'Windows 10' started by pisthai, Dec 21, 2014.
You need to login to view this posts content.
Looks like this branch possibly got a dead-line to remind everybody when the awesomeness is due : fbl_awesome1501 - January 15?
Did a clean 9901 install, change the branch to fbl_awesome1501, don't see anything here...
Edit: Doing a clean install of 9879 now and updating that to 9901, will report when finished.
An update is available. It will:
? - That doesn't even make sense lol
for what i understand....u cant upgrade 9901 Enterprise. u have do a clean install.
No new build this year.
Make sure that you install the latest Windows Updates on 9879 first before you upgrade to 9901. I am assuming that it worked because of the recent update(s) in 9879 which changes the branch to fbl_awesome1501. It could be that when you manually add it with the registry trick, it fails. And when done the way that the OP has done it with the proper Windows Updates, maybe that is why it showed up that way. That is just my assumption anyways. What I mean is, if you clean install 9879 and then upgrade straight to 9901 (without doing the updates) and then add the registry tricks manually in 9901, it may still not show for you. Although I just wanted to send this quick message as a friendly reminder but I am sure you probably will do the updates first while on 9879 anyways. Cheers!
where more counting on leaks then new builds released the legit way
Does not give me that.
I can not change it. I am using 9888
Will check it tonight when I get back in.
Is this fake?
Are you fake ?
the all of us know @pisthai long enough that he wouldn't be the last to bring in faked stuff though
I'm on 9901 and changed my branch to fbl_awesome1501
New build is offered but errors with 0x80246017
Seems to agree with what Buildfeed says
I get error after add fbl_awesome1501 in
Windows Registry Editor Version 5.00
I've seen this done before, you won't get updates if tweak the registry and you op out of the insider program.
Don't tweak the registry and wait for the official leaks
Guys, first of all, for the new preview build to appear, you need to change ring to fast (it's unselected by default). Only then will the new build be offered.
Secondly, preview build update is broken in 9901, it's been confirmed officially, so don't hold your breath.
I'd post the link for the source but MDL won't let me, 20 posts needed, whatever. Gabriel Aul tweeted about it, look it up if you want.
Can all you do is edit it, or can you add multiple branches?
I can confirm what pisthai was seeing now. It shows the new build available, gives you the Download button, works for about 5-10 seconds and fails with the same error. There are no logs or activity showing here though: C:\Windows\SoftwareDistribution\Download
This is likely only available internal at Microsoft test groups. But I have no idea why it is showing up. I am wondering now what would happen if we used the other Consumer product key. There must be a key that relates, but likely internal testing only.
Did anyone test this with 9888 leaked build? Since it's internal updater is still in tact.
Would you like to tell that I bring in faked stuff? Because that's what your writing means!
Please clarify! Thanks.
As I wrote in the OP:
While installing all on my laptop again, this time clean install of 9879 and updated that to 9901 I was get the following while checking for Updates:
I got the outcome, shown in those pictures, directly after the installation of the 9901 as my first step we were to check for additional updates. That pictures are not fake in any means from my side, that's just the original screenshots. If they show any wrong, it's triggered by Microsoft and may existing error's, which that build 9901 for sure still will have a lot of!
In those installs I'd done from ISO before on the clean way, didn't have shown those outcomes, even it was pointing to the fbl_awesome1501 branch for updates. The pointing to the 9908 was on an from 9879 updates to 9901 install, which didn't have any extra Apps installed except those Updates from MS via Settings in 9879.
Just to mention: I didn't use an Enterprise version of 9901 and even didn't try to change to that! Frankly, I didn't like to alter system files in an Pre-Release any stage!