Screenshot of Windows 10 9913 Update appearing in WU

[gus33000]

@AngelWZR or @rlinev did leak by inadvertence a screenshot of the update showing in WU.
He removed the tweet shortly after but I managed to save the picture he posted :


With the following message in the tweet :
"Am I dreaming or what?"

Do you think 9913 will be the January Technical Preview or this is just a WU Bug ?

[Overdoze]

This is likely to happen.

[hounsell]

I doubt 9913 will be the January TP. I'd think it'll be one compiled this month, probably in the next week.

[ThePowerMaker2015]

@AngelWZR or @rlinev did leak by inadvertence a screenshot of the update showing in WU.
He removed the tweet shortly after but I managed to save the picture he posted :


With the following message in the tweet :
"Am I dreaming or what?"

Do you think 9913 will be the January Technical Preview or this is just a WU Bug ?

I think this is indeed the January TP.

And i also think it will show up before January 21st.


Build 9913 is on the "fbl_awesome" branch, and it's source type is "Private Leak".

Another thing i noticed is that builds 9888 and 9901 already say "© 2015 Microsoft Corporation. All Rights Reserved."

https://buildfeed.net/actions/info/1181/

Besides, Gabriel Aul mentioned via twitter that a new build is coming in the next few weeks.

[rthdribl]

Build 9913 is on the "fbl_awesome" branch, and it's source type is "Private Leak".

That's not how build numbers work. There obviously is a 9913 build in winmain.

[betaluva]

according to nsane this build is fake ( not my opinion!,look at the Shoutbox ): http://www.nsaneforums.com

[hounsell]

10.0.9913.0.fbl_awesome1501.141217-1931 has been private leak on buildfeed.net --> is a FAKE!
g0ldlod1 @ 06:43 PM, Sat

Hah. Well, if he says so, it must be true.

I can't imagine why I would have personally added it to BuildFeed unless I was certain...

[ThePowerMaker2015]

10.0.9913.0.fbl_awesome1501.141217-1931 has been private leak on buildfeed.net --> is a FAKE!
g0ldlod1 @ 06:43 PM, Sat

Hah. Well, if he says so, it must be true.

I can't imagine why I would have personally added it to BuildFeed unless I was certain...

How can we check if a build is a fake or not?

[hounsell]

You work it out for yourself.

Personally, I don't allow fakes on Buildfeed. While I can't honestly claim that the list is perfect as it stands, I will happily comment on individual cases and I certainly will double-check any specific build upon request if you have doubts.

For reference, 9913.fbl_awesome1501 is not fake, and anyone claiming that it is a fake is a complete and utter muppet who doesn't know what they're talking about.

[MrUTB]

Tricking regedit you could to see the Build in WU, but failed when It's starting to download

[Lukas Marsik]

Tricking regedit you could to see the Build in WU, but failed when It's starting to download

How would you do that?

[MrUTB]

Warning: By changing these registry keys you do affect the builds that get targeted to your PC; unfortunately you won’t be able to get any of these builds unless you are a Microsoft Employee and have access to internal network.

tl;dr

If you do that, you couldn't get future builds, do it is in your own responsability.

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability]
"BranchName"="fbl_awesome1501"
"ThresholdRiskLevel"="high"
"ThresholdOptedIn"=dword:00000001
"ThresholdInternal"=dword:00000001

[hounsell]

But that's in flighting, not the Windows Update window as depicted, and the most recent fbl_awesome1501 build in the flighting system is 10.0.9908.0.fbl_awesome1501.141212-1838, I believe?

[MrUTB]

If there is a private leak, then there is a previous build via flighting system, don't you think?

In fact, I don't know why in Buildfeed doesn't listed yet.

[Lukas Marsik]

If there is a private leak, then there is a previous build via flighting system, don't you think?

hounsell's point is that you are wrong because doing that affects flighting and makes it show 9908

[MrUTB]

Oh... I see.