>> Somebody is not paying attention in class. All right.
Here we go.
>> That's really lovely, we can see.
>> Mine just happens to be super like- All right.
Video and audio. We're back in business. All right.
>> Yey.
>> So, let's try this again.
>> Eight minutes.
>> Eight minutes passed but you know what?
Whenever we do Microsoft meeting we start on time,
so why should the webcast be any different?
We'll just keep the tradition going.
>> Hey, I was here early for you.
>> I know. I know. I know and it's my fault. All right.
Hey, now we're past the technical difficulties.
Hopefully, everybody is up and running
and I can see the video and audio correctly.
If you have any other problems,
drop some note and Chat and we'll see if we
need to make some adjustments on our side.
Let me pop over to the presentation.
There we go.
Welcome to the first monthly Windows Insider Webcast.
It is, at least here in the States, Friday, April 28.
Do quick introductions of
everybody who is here in the room.
So first off I'm Jason.
You know me as NorthFaceHiker on Twitter.
You also see me a lot at the Windows Insider handle.
If you see a little carrot JH
behind any of those tweets, that is me.
You also see me out on the Pinterest forums.
I'm just Jason on there
so the same profile picture, you'll know who I am.
We'll go around the room real quick
for anybody who doesn't know who
we are. Next up is Jen.
>> Hi. I'm Jen Jennel. I work on the Shell team.
Probably better known as JenMsft.
I am not the only Jen at Microsoft
but I guess anyone tuning on
the streams hopefully knows me.
I work on all kinds of stuff.
>> Lots of stuff. That is actually true.
>> That's a lot.
>> Not only is Jen on Twitter.
She is also one of the awesome folks who post on
Reddit all the time so you can find her
there on Reddit as well in the Windows section.
Same handle? Is it JenMSFT?
>> Ye, same handle on Reddit.
So, if you're on Reddit, you can find her there as well.
Brandon? Brandon is the blogging coms guys.
He's super awesome. I'll let Brandon introduce himself
and give a quick story about what he is wearing today.
>> I've got my awesome Xbox onesie.
>> How did you come by this onesie?
>> I wanted one. I told him
that I would wear for all of our webcasts.
>> Sounds good. From the Xbox team?
>> Yeah.
>> And they shipped it here from Australia?
>> Yep.
>> So they're awesome. They're very awesome.
>> So now, you have to keep wearing it.
Every time we do a webcast,
Brandon is going to be here
sitting in his Xbox sponsored onesie.
>> I will probably not be wearing it at Build.
>> That's unfortunate. You should at least bring it.
You can do laps with it around the building.
>> You'll see this creepy guy walking around.
>> All right.
So Brandon, what do you do around this place?
>> I write a lot
of the- I put together a lot of the content.
Write us some content for a lot of the flights.
Help get content out to Insiders feedback com.
Whatever you tell me. Whatever Donna tells me to d,
mishmash stuff. I tweet.
>> Yes. You're definitely active on Twitter.
>> Yeah, I mean I just-
>> All right, Danny?
>> I'm Danny and I do- I write stuff mostly.
Not like other people
I write stuff about in TechNet and Docs.
In tech community, I
try to follow up wherever it is possible.
Not on Twitter though but feel free to reach out to me.
Send me any questions you have and I'll follow up
with people within the company.
>> Awesome. And then
behind the scenes as usual, Reid get over here.
Get in the picture. Here we go.
>> I'm in the picture now.
>> He's Reid. You can
see his Twitter handle there ReidMSFT.
Reid is the tech guy.
>> I'm the Beam Machine.
>> Yeah. He's actually running
the Beam Machine right now.
>> The Beam Machine.
>> He's trying to tame the beast.
So, yes, let's just hop into this.
So, quick agenda, things we're going to cover today.
I want to talk about the webcast themselves real quick.
And then, of course, we are going to
talk about the Beam Machine,
which we've been hyping for a couple of weeks now.
At least I have been because it's been
a great experience building another machine.
It's been a little bit since I've done one.
So, putting this monstrosity together was quite a task,
but it was a whole lot of fun.
We'll do a quick feedback and flighting review.
Talk a little bit about what Builds are out there
currently and some reminders about sharing
feedback because there have been some questions
come up across Twitter as of late.
So, I do want to cover some of that stuff.
We'll talk about the new dev branch Builds.
The Builds that are coming out and
the artist pre-release branch
as well as the featured two mobile Builds.
We'll talk about Build cadence.
Some of the app flighting and
then hardware app diversity which is
a very important topic that I
do want to spend a nice chunk of time on later.
Of course, we will have an in-depth Q&A session.
We'll be answering questions along the way.
And then at the end I want to do a recap
and some requests for next session,
see what you want to see covered
in these monthly webcast as we move forward.
So, first things first, let's talk about the webcasts.
Everybody likes a cat pictures on the Internet, right?
So here's your first cat picture
of the day. We're doing a webcast.
So, when we did the bug bash webcast back in February,
there was a lot of requests from many of you were
actually on the stream currently and
we began doing this on a regular basis.
This is your feedback
so here we are. This is the first one.
Taking a little bit to get things put
together, working out the timing,
the process, and of course,
the actual Beam Machine built to do it.
I'm going to head on some of that here in a moment.
But one of the questions that came up out of
the last webcast was, how do we do this?
Although it's not super in-depth
technically, this is how it's put together.
We do this on a monthly cadence.
Video on Demand, that was
a request out of the last webcast as well
so we had our partners over at Beam set our account up.
The Video on Demand will be there.
It pops up later in
the day after the webcast is completed.
It will be posted,
I think the timeline is two weeks.
I will validate that but I do believe
it will be up for two weeks once it posts.
And you'll just access it directly on
the same Beam page that you are on currently.
And, of course, obviously, I'll cover the quick agenda.
We'll have Q&A sessions.
And then, in the future, also we're going to do
some guest speakers so we will have
different partners from different product areas come in
and talk about the things they are working
on and their latest release cycle,
take your questions about
current inmarket products and things that are already in
flight as well as
taking suggestions for things
you want to see in the future.
From a technology perspective,
you can see the images below, right?
Demo laptop, which is actually
my personal service book that
I use here at work for today.
We broadcast into an Elgato HD60,
which is the stream capturing software which passes that
along with the Logitech Rio 4K webcam that we now have.
Those two things are plugged into the Beam Machine.
That compiles the stream,
throws it up to the Beam service,
and then down to the Insiders where
you are actively watching it on the web.
Gives me nightmares to see your product.
Oh goodness, the mobile questions start already.
Why am I not surprised?
Yes, VOD, I know.
That was a super big thing that
folks wanted to see. All right.
So, from a timing perspective, where am I on time?
9:46, awesome. So, let's talk about the Beam Machine.
Okay. So, the Build blog,
this link is not active yet.
It will redirect you just to
the generic Windows Insiders web page.
Brandon is working on actually
publishing the post it is
because I put too many pictures in it.
I think there is probably 20 or 30 photos
in their of the various stages of the Build.
You going to see a couple of them here in a second.
But later today, we will tweet
out when that is ready to go live.
So, you can actually go through and do
read the entire review that I
did on the Build on why we chose some of the parts.
Well, let's actually talk about the Beam Machine itself.
So, processors.
The new AMD Ryzen 7 1800x.
Of course, we had to go with the higher end one,
right? Got to do it right away.
Three point six gigahertz eight core,
16 hyper threaded with
four gigahertz turbo boost mode
RAM is the G skill Trident Z RGB.
There's 32 gigs of RAM in this beast.
Based upon the BIOS updates,
this is something not covered in the blog
but I will touch on it real quick.
When we first put the machine together,
it wouldn't run the RAM speed above 2133 Megahertz.
Fortunately, MSI has come out with
a couple BiOS updates are actually on 1.3 now.
So, 1.1 and 1.2 that gradually
enable and we jumped up and then 1.3
is actually enabled us to get up to 2667
so the RAM on this machine should top out around 29 33,
given that it's DDR 43,000 but we will need
another BiOS revision to finish enabling that.
MSI is just in essence stepping up in gradual bits to
ensure stability so they do
not get flooded with a tonne of
requests of why are we breaking peoples machines.
As noted, the motherboard is a MSI motherboard
it is the x370 gaming Carbon Pro.
Solid State Drive it is the Samsung EVO 960 M.2 NVME.
What's so special about this drive?
It is the read and write speeds.
This will read at nearly three gigabits a
second and it will write it
nearly one and a half gigabits a second.
This is the exact same drive that now that our Dev teams
are moving over into get and doing their Build compiles.
They are actually getting these exact same hard drives
because of how fast they are.
It is one of the things that we are doing to
try and reduce Build times on our side
so it can get out Builds faster which would in turn Build
faster flights to all of you in the Insider prog.
Graphics. So, graphics was an interesting one.
Of course, if you are a hardcore gamer,
you are looking at this video card and be like,
"It is not a bad card."
You are right it is not a bad card.
But it is not the new name 1080
Ti and the question is probably why.
For video streaming, we
do not need the latest and greatest.
It is just being candid about the reason.
It is not,
video streaming is CPU and RAM intensive which is of
course why we built the big machine but
it is not super heavy from a graphics perspective.
So from this end it was more about just having a display.
We could have gone even a further step down.
But hey you know might as
well put something good in the machine right?
From a cooling perspective.
There was the eternal debate between air and
liquid cooling off course
at least for me it wasn't even a question.
Wanted to go liquid cooling.
So as part of the Build we went with the
Corsair H110i liquid cooling set up.
Why this particular set up?
Given the fast turnaround of
how quickly we put this machine together,
one of the really good benefits aside
from this particular set of having great reviews,
was that they already came with the proper AMD4 bracket
for the Ryzen processor.
So, we didn't have to order anything special,
we didn't have to contact Corsair
to get the bracket which you can actually do
if you have one of the older Corsair
liquid cooling units you
can actually reach out to them and
they will brag the bracket for free.
So, check their website if you're in
that situation and decide to Build a Ryzen setup.
But for us it was a out of the box,
had everything you needed and it had great reviews.
So hey why not go liquid cooling?
In the case itself there is two fans 240
millimeter fans on the radiator
for the liquid cooling setup
and then there is three just case fans to pull air in two
in the front one in the rear to
pull in and blow over all the components.
The case itself has
a Thermaltake Core X71 it is a full tower.
This thing is huge.
We probably could have gone with X31 which is it's
slightly smaller brother but hey why not right?
Might as well go big or go home.
And one of the things that you won't see in
the few photos that I have in the blog.
But we'll actually give you a preview
photo of it here today
is the LED lighting because well
the motherboard happens to have a jumper header
to plug in LED's too and MSI has
their gaming software that you install on
the drive machine that lets you custom control it.
Well, I will actually take the
webcam here in a minute and actually
show you the Beam Machine itself.
So, this is what the aftermath looks
like of putting this beast together parts,
manuals, boxes trash thrown all over the office.
I kind of kicked it all together in
a corner so I can take a picture of it.
I know some of you have been in
this particular situation yourselves.
It's been a while since I have done this at
home but I have to say that having
gone through this experience
and put this machine together.
And having done some of the tests on it,
and I'll talk about some of those here in a minute,
it makes me want to go home and
toss my computer out and Build a new one.
I know right. This machine is definitely a workhorse.
I will tell you we did some some testing
on my personal bean channel where in.
We had it streaming a full
1080p and I will
talk about that here in a second of why it was a 4K.
Streaming a full 1080p 60 frames a
second just like we are now.
While recording the stream locally to
the hard drive or the SSD I should say.
Which is not a surprise.
It is fast enough that it can
capture the stream no problem.
But we were also doing
some additional software install like
the MSI gaming software.
We were installing the Skype desktop client.
And wow in essence triple tasking doing all of
these CPU usage never passed 35 percent.
So from that perspective I think we
are pretty good on the specs of this machine.
And we won't have some of the in
essence like lagging and glitching.
I know that there was some video upload streaming
issues when we did
the webcast for the Bugbash back in February.
That was in essence because
of the machine that we were using.
Like I said we took it to heart the feedback that
we got and put it to good use.
So probably wonder I know that
there's been a few photos tweeted out on Twitter.
There was one of me building
the machine in conjunction with Reed.
There was another one that showed
the RAM and the water cooling block up close.
But here is a slightly zoomed out photo
of what it actually looks like now.
Yes. So, you can actually see some of
the LED strips reflecting up on the top.
They are in a rectangle pattern all the way
around the edge of the case they run up through
the side and actually down in the back
because in the back side of
the case and I will actually take.
Like I said, I'll take the webcam here and show you in
just a minute but some of that, some of the routing,
we actually have it in Rotation mode
so where it's just a solid blue color
inside the case for this particular photo.
We actually have it matching the RAM where
the RAM rainbow stromes because it is the RGB RAM.
We have the LED's matching in
a Similar RGB rotating fashion.
So actually know what, here I am just going
to take and actually show you
the Beam Machine real quick one second.
Let me move this out of the way.
See if I can not destroy the stream.
I know this right it is going to be super blurry alright.
And here is the Beam Machine.
Oh, it's going to get a bunch of reflection on the glass.
There we go. In real time,
you can see I know there's lots of light coming in from
outside so it is not super easy to see,
but you can see the reflection of some of the lights.
If you look at the MSI logo in there the gaming pro,
you can see it rotating
colors the same thing with the MSI board header.
And then, you can actually see the
LED's on the back of the motherboard.
If I can get it just right there you go.
They are rotating in color as well.
The only thing in the machine that is
a static color is the two fans and
that is because the fans that come in
this Thermaltake case just happened
to be solid blue LED's.
One other interesting thing if for this particular case,
if you decide to go with
a full custom water cooling setup,
and I only actually open this real quick,
it's got a triple bracket setup so you can mount
a full water cooling radiators set up right here.
As you can see, up
a little rubber grommets on the base and then the back
it allows you to do your cable management
what you can see we did a really good job
of tucking in the wires in there.
But you can run your
water cooling tubing down through
there and you can also take out your hard drive bracket,
which I do not know how clearly that's coming through.
But you can remove that and use that as well.
One of the really interesting things about this Build is
the Corsair 750 watt power supply unit
as you can see the fan on it is not even spinning.
It is rated E gold.
So, it is super efficient.
And the interesting thing is even while we were
stress testing and burning this machine in,
using Prime 95 and then
FurMark for the graphics card the fan never picked on.
It's not that the fan does not work because it spins up
during boot to do the self check.
But it is so efficient and stays so cool inside
this case that I have only seen it on one time.
So that ladies and gentlemen is the Beam Machine
you can actually see
the fans from the front. Thermaltake logo.
Oh, another cool thing and I actually call this out on
the blog for ease of cleaning.
It's got a magnetic dust cover that you can
remove and you can actually see some
of the LED'd in the back and there's
the radiator venting air out through
the top of the machine and it just sticks
back on the top when you are done back into place.
There we go. All right.
Now we put the web cam back in place.
How is that? Hopefully, that is close to what it was.
So there you have it.
That is [inaudible].
Yes I am super excited about this because you
know and this is for the Ds-cam.
Oh hey I have seen you on twitter [inaudible] times,
hey what's up men?
I am super excited
about this number one because it is for the insiders,
right? We are doing this for you guys.
This awesome machine enables us to put
together this great Webcast, stream it to you.
This beast better do VR.
Donna, we're going to need a different graphics card for
that but hey I will just come and hit you up for
budget when it is time.
So there is a few questions in here about the machine [inaudible]
cooling solution such an awesome machine.
Yes I love this machine it is fantastic.
I am looking through the comments real quick.
>> Asked What Build is it running?
>> What Build is it running?
It is on the insider fast rate.
So it is running 16 179.
This machine is actually going to be
the machine that I will be using in
conjunction with Build releases to
make sure that we check and
say that hey yes a Build has
actually been released properly.
So from that perspective there is something I want
to do because well Donna is on the Webcast right.
So say Hi Donna. Oh she is over [inaudible].
>> If we need more money let us get a bake sale on.
>> Yeah. We're kind of need a bake sale.
So, well GW,
I do not even know how to pronounce your screen name.
It is kind of funny that you say that
because Donna is not here to tell me no.
So, when was the last time you saw this thing?
>> I don't think they can see it.
>> Well they are going to see it.
When was the last time you saw the red button in person.
Yeah [inaudible] webcast.
Yeah it is the red button.
So I do not know,
you think Donna is going to get mad if I try to release
a Build while she is gone?
Oh snap is right.
Why is that button on the table. Yeah exactly.
Cause I'm going to release a Build and she
is not actually here to stop me so should we do this?
Should we actually drop
a Build while Donna is gone and cannot
tell me no. Oh my goodness.
If I get fired next week for doing this.
Somebody you know, give me a job send me referrals.
I am going to need a little something here.
Do it. I won't do it.
Red Buttons. Okay. Well,
I think I have been pretty well tempted into doing this.
Brandon should we do it?
>> You should do it.
>> Do we need a timer, a countdown?
>> I don't know.
>> I say we do it.
>> I think we should do it.
>> So with that I completely ignored
my boss and oh
I ignored Jeremiah because he thought it is a bad idea.
Let's check for new Builds.
So I am actually going to
since The Beam Machine is on a fast train.
My laptop is on self host so let's
check and see what is out in the update world.
They better be something this [inaudible] better have
worked or else it is going to look terrible for me.
Not only did I ignore my Boss.
Yes it's going to be pretty bad if
I try to release a Build and it does not work.
>> Meanwhile refreshing.
>> Well, keep in line that it has to go
through like once you hit it.
It has to go through.
>> It doesn't mean that I am not impatient right?
And I'm super excited I
just got through talking about The Beam Machine.
And Not to mention the mountain dew that I've
been dumping down all morning right. Oh look at that!
Would you look at that,
16184 in the House. Anybody else seeing this.
Yes. Yes. Oh and somebody seeing 15208 on mobile.
Brandon I think it is time you publish that one.
>> I will get that up very shortly.
>> This is fantastic.
Yes of course I did. Do you not
see the button switch activated.
So go check for updates everybody.
Sorry boss yeah it just happened.
Yeah. So I know
everybody is going to be downloading the Build.
But you got to wait till after the webcast to install it.
It is probably not fair of me to ask because your
probably actually watching this on
the machine that you're finding. So maybe it wasn't.
>> So it has to be three machines.
>> I know, wow! So maybe it wasn't such a good idea
for me to push the button but whatever.
But like I said if I get fired you
still see my Twitter cause I will get on there and
still Chat with you all.
Oh my goodness this is fun.
I love doing this.
So let me shift back and
finish talking about The Beam Machine
momentarily because I have a trivia question for you.
So relating to The Beam Machine.
Total download. You've already
finished downloading that is fantastic.
All right. So here is the trivia question your ready?
On the first boot of The Beam Machine,
the first full boot.
We did a post boot just to
make sure that it actually would pose to read
the ram that all the hardware is
installed correctly right that was the
technical first but on the first actual boot of
the beam machine where we
had the Windows installation on an ISO.
How long did it take to install
the creators update RTM Build
15063 from scratch while on a USB 3.0 drive?
I want you to type
your answers in the Chat window please.
Oh and a side note, this
did include formatting the Hard drive,
creating a partition because
well there is a brand new drive and
nothing had ever been on it before.
So, 0.5 seconds and that's
not quite realistic but all right.
It would be awesome if Windows
installed in half a second so five minutes.
Yes Donna is going to kill me and
walder98 yeah it is probably going to
happen when she gets back.
Seven minutes, 15 minutes,
three minutes, Paul, four minutes,
22 minutes, 17 minutes 11, 13,
16, eight, 34 45, 11.
All right, I'll give another Second
for folks that finish chiming in.
Zero minutes. Yeah I
Wish it was zero minutes that would be great.
>> It came pre-installed.
>> It came pre-installed.
Samsung's not quite there with their drives yet.
Well here we go. So your answer.
From power on, all the way
through formatting the drive creating the partition,
unpacking it installing the OS,
till that first window where it
asked you to start entering your credentials
and then ask you language
and country and things of that nature.
Four minutes and 27 seconds.
So those of you that said four minutes to
five minutes right on target.
Yes, and that was with
the RAM running at the slower speed of only 21,
100 and 33 megahertz.
So if we did it again at this point,
now that the RAM is running at
a much higher speed and once we actually
get the next BiOS revision that should fully unlock 29,
100 and 33 megahertz,
it would actually be even
faster because the RAM would be able
to push the data back and forth faster.
But how hot does it get?
Oh okay so that's actually a really good question.
So, Mirro how hot does the machine get?
So I mentioned earlier that we did burn in on
this machine after we put it
together and actually had the OS installed.
We did the driver installs to get everything up today.
We took the cumulative updates
that you've all been receiving
before jumping to the new Builds
that are coming out in the RS [inaudible] branch.
So it was, what software did we end up using?
>> IDA 64.
>> So IDA 64 which completely taxes the CPU right.
So all eight cores
all 16 hyper threads running
at a 100 percent utilization.
We left it going for two straight hours just siting.
Oh yes with FurMark running and
burning in the graphics card at the same time.
So this machine was completely maxed out.
Graphics RAM and CPU,
all being 100 percent utilized. Yes it does.
My name is Mary
and that is another reason we have gone for Rizon.
On top of their fantastic video capabilities.
So this CPU completely
maxed out everything in the case maxed out.
The CPU capped out temperature wise at 39 degrees
Celsius and the graphics card
capped out at 58 degrees Celsius.
It's liquid cooling setup is insane.
How does it stand next to KDLINK?
Comparing Ryzen in the KDLINK.
From a in-market perspective,
obviously rise and is still on
the adoption curve, because it's relatively new.
I mean, their process has been
going on for the past month or so.
The initial feedback.
It depends on what you're doing.
If you're gaming, it can be like beats up a little bit.
Most of the things that I've seen is
between five to eight percent.
KDLINK has a slight edge.
If you're doing like advanced video editing,
and things that are set up to do multi-threading.
The Ryzen actually has
an edge on KDLINK
from the initial reviews that I've seen.
It doesn't mean that with further updates, BiOS updates,
chipset drivers, things like that,
it doesn't mean that the you know,
they won't go back and forth.
But, It's actually stands
its ground and it's the newest edge.
One of the things though is this an a core processor.
Some of the new KDLINK like ones are 10 cores.
I mean just from that perspective,
you were trying to compare
eight-core machine to a 10-core machine.
Obviously, the 10-core machine is
going to have an advantage presuming it has
the appropriate supporting hardware
of the right motherboard.
And then, of course, the turn of RAM to
support it on the backside and
it can't get four and half gigahertz. I don't know.
That's one of the things that I actually
want to try with this machine.
We'll see how it goes.
I'm going to overclock this machine.
That's something I haven't told Donna.
Not only that I'm watching
flight today without telling her,
I'm going to overclock this machine.
It's going to happen.
Any of you out there that
happened to be overclocking fans,
you're going to get to see some stats.
I'm going to take you through that process.
I want to do a tech write up on it.
I'll give you a little background on why.
My name is more- you're actually,
it's pretty close to what you're saying.
The 10 core costs four times the price.
If you look at, hopefully,
many are familiar with Newegg.
It's a very popular site to buy computer parts from.
The AMD Ryzen 7 1800X,
which is the top in model right now is $500.
It's not cheap by any means,
but from a performance and
price perspective, it's rock solid.
The newest KDLINK processors that are 10 cores,
you're looking well into the $1,000 plus grounds.
Some of the eight-core processors from Intel
are a $1,100 just for the processor.
So, from that perspective,
yes there there's a huge price difference.
I mentioned earlier like it
was just like with anything else,
we're working under a budget, right?
I didn't get to go spend $5,000 building the bin machine.
That would've been nice, but honestly,
there was no need to.
We wanted to Build a high end but
solid enthusiast type machine that would
do exactly what we needed it to
do but without just throwing money down you know,
then throwing money into a Build that did need
to be spent in that fashion.
There's been a couple questions on the cost.
The Build was around $1,700.
Not cheap, but as
I mentioned earlier with some of the stats that
I quoted off on how efficient it is,
and that given that we were triple
tasking it with recording the stream,
broadcasting, and installing software,
we are only using about 30 CPU capacity
unless we end up needing to add more RAM later,
which I don't foresee given
that we have 32 gigs in there,
this machine will be future proof for quite some time.
Again, Donna mentioned in the Chat about VR,
so we may need to look at
the graphics card again at some point,
but we're a little
ways away from that so we'll see how that goes.
Oh yeah, My People. So, I'm actually going to drop
my slideshow for a second because, Hi Twitter.
>> Do the demo for us.
>> what?
>> Get it right.
>> You can do the demo for us.
>> I just want to say real quick.
I installed this Build previously.
So, if you want
a quick shortcut because when you install this Build,
by default you will see the people icon, still brackets.
I have to end this. Okay,one second.
This is operator/presenter error so let me,
in slide show, okay.
Now, can you see my desktop? There we go.
All right. This is what I want you to see.
So, as you can see,
I am already running 16184.
So, I have the Build that has just got released to you
all and it has the My People feature enable,
which is awesome. It's about time.
I know this is a big thing kind of
creators update. People were disappointed.
They didn't make it, but
there were some pushes to get it finished,
but we didn't want to release it unfinished.
But here it is.
It's like the first round of it is
already showing up and we are what, three buildd in,
four buildd in, just the third rows 170,
176, 179, and 184.
Yes, so this is the fourth Build into
the new development cycle
and My People feature is already here.
When it first installs, you will actually
see icon here but
it's a quick way to turn it on or
turn it off depending if you want it on or not.
Just right click on your task bar,
go to task bar settings,
and then come down to the bottom
and you will see right here,
"Show People on the Taskbar".
This will let you turn it on and off as you see fit.
Flip on and immediately you know there it is.
So, I didn't want to spoil in case I accidentally
showed my desktop this morning.
So, I have not yet set it up,
but it's super simple.
Click there, you could get
started and then walk through the set up.
But I don't it want
to steal your thunder. Jen, do you want to do a demo?
>> I want to.
>> Yes. I told you we are going to do a demo.
I'm totally putting her on the spot here.
I promise you this was not planned.
>>Who are you friends with?
>> I don't know, who I'm I friends with.
>> I don't know who are you with.
>> Should I click it?
>> I mean, I think you should.
>> I'm kind of worried.
>> Is there a Twitter in here?
>> It's just Skype and mail for now.
>> Skype and mail and of course people's connected.
Great social network, right.
So, first round of this.
As you can tell,
I have not set this feature up yet.
It's probably my bad.
But, you can connect your Skype,
you can connect your mail, grab
your friends, create contacts.
Do you have your
set up and obviously
you do with them. You can send me an email.
>> You can do a pull on.
>> You can just pick on admin's contact?
>> Live demos always rock.
Yes, live demos rock.
Oh, so these are
couple people that work here Microsoft with me.
Mike Monju. He's actually,
Mike Monju is actually going to be
coming over and working engineering.
He starts over here in a couple of weeks.
Did you just see?
So, new contact.
>> You going to have to show my-
>> I don't want to add any contact,
I want to- Okay, go drag this.
>> We should cam for spin most the set up,
to show what I mean.
>> I mean much as I love when there's insiders.
>> There you go. Actually, in my contacts list.
That's unfortunate.
>> Yes. Can you use admin?
>> All right.
We'll take the long answer so, June.
>> You have to keep a cute picture of a cat, not me.
I'm just saying, they're standards.
>> What email do you want me to use for this contact?
>> Have a Chat.
I have an office stream for that.
>> So, we're adding Jane and you will you'll forgive me.
I don't want to broadcast
over personal information across the web.
Hopefully, you understand.
No, this is absolutely not scripted as you can tell.
Its completely on the flight here.
>> We thought that this was scripted.
I thought that you're very clear.
>> In case there was any question,
none of the web cast we;vedone creating to be.
>> We are all scrambling.
That's not about to delay that.
>> And I haven't even tweeted
via the Windows insider Twitter handle,
that we released to be Build, so.
>> We're all sit down type.
>> Yes. I need to actually get the blacklisting
from me so I can post that real quick.
>> Let me- How would you like me to get that to use?
Can I use My People?
>> You know with that email yesterday, Brandon?
>> Are we Skype friends?
>> I don't know if we're Skype friends?
I don't know if we are actual Skype Skype friends.
>> No. I have you taken my taskbar.
>> Okay. Hold on so let me.
>> Do you remember that email yesterday, Jason?
I was like, "Hey, Jason.
Do you want to set up for a people demo?"
And you were like, "Maybe."
>> Can you Skype me link real quick.
>> Okay. Okay. All right.
So, now Jen set up as a contact.
So, now I can close this window, right?
>> Yeah.
>> Okay. I'm going to close this this window.
>> See at the "Add Contacts",
those are suggested so they the ones that
you communicate with the rest.
>> Do you want to share
your email when we added that contact?
>> Now we could-
>> There we go.
>> -go back to the demo.
No more secret information down there.
>> There we go. All right.
We had my work Skype account.
So now, I have Jen
pin down to my taskbar as one of my contacts.
She has her own logo,
identification of who she is,
reach out to people or mail.
At this point, we just click mail
and it pops up mail and I can run drop you mail, correct?
>> Yeah.
>> So, is it going to show
your email address or is it
just going to show the to Jen?
>> Let me just check.
>> Again this is the joy of doing live demos.
>> Yes. It definitely shows my email address
>> Well, at this point this is where you will click mail,
and it would bring up
your email app and allow you to quit
composing email to whatever contact you have selected.
>> You could add,
what is it down there?
>> Oh, Brandon is sending me in the Twitter links.
So, quickly, you could see.
>> The address, yeah.
>> Hey, yes.
>> Real ad.
>> Yes, I can do that.
>> Skype.
>> So, I need to tweet real quick.
>> After you're done with that,
you want to add me on Skype.
>> I was going to say Skype contact.
>> If you add me on Skype as Skype contact,
we can try to
Skype the integration because that's really cool.
>> One O five, two O eight.
Let's try this again.
Sometimes it doesn't like formatting
the link out of Skype.
So, I have to do it this way.
Here we go.
Although it's late, here we go.
You now have your tweet link
from the Windows Insider handle.
>> You got a live streaming there.
>> Hey. I can see myself on Twitter.
>> That's funny.
>> That's a looping chain and me pressing the button.
That's fantastic.
Yes.That is awesome. Thank you for doing that.
I need to save that Gif.
I'm not trying to start the Gif versus Jif debate.
I'm going to skip over that one like they didn't happen.
>> You are using the Windows Insider Skype in this.
>> I could.
>> I am just thinking that we could
become friends in Skype.
>> Okay.
Yes, I did red button it.
ORFLW, yes that happened.
This is States. I love this.
I love my job like this is one of the best jobs ever.
>> What's your?
>> My Skype?
>> Yes.
>> I don't even know.
>> It's the one here.
>> The one that is online.
Do you want my personal one or my work one.
>> I mean whichever one will make
Skype contact should work.
>> This is the one that is on that machine.
>> You should cut this.
>> There isn't one on this machine.
This is my work machine.
So, I don't have that one installed in here.
We are going to do some details as you can tell.
So, let me get back to the presentation.
>> I can make a totally fake email account
and we can totally communicate.
Sorry, look.com. I am a real person.
>> Okay. Here we go. All right.
So, we're back to the presentation.
So, let's get back on track here.
I do want to save, it is 10:20 here.
We have another 40 minutes.
So, when I finish covering the things
that I have in this presentation and then I'm
going to save plenty of time for Q&A because there is
probably lots of questions that you want to ask.
Like I said, this first one,
set it up for an hour and a half.
If it turns out that we need to
go a little longer in the future,
if it need to be two hours then we can adjust.
>> I skipped a meeting for Jason.
>> Yes. She skipped a meeting for me.
I know Brandon skipped two meetings for me.
The pre-release stuff as well as some Comps meeting.
>> I did not skipped a meeting.
>> Really?
>> I clearly did.
>> Now you did.
>> Do you get a free laptop and you work for Donna Sarkar?
>> No.
>> If you come to work for Microsoft,
if you become a FTE at Microsoft,
the company will provide you a work laptop to use.
In this case, I have a Surface book.
We already dealt with this stuff. Let me get through.
So quick feedback and fighting review.
These parts are breeze.
This won't take me long to zip through.
So, one of the questions that has come up
about filing feedback is
the difference between mobile and PC.
One of the things that we do want to remind folks of
is you cannot file
feedback for one device type from another device type.
So, if you are unable to get
updates on your mobile device,
you need to file that feedback from
the mobile device that is actually having the issue.
You can't file it from your PC.
The reason this is the case at
least on it's on this side, it's pretty straightforward.
When you file that feedback especially if you
use monitor mode, which we highly encourage,
which is a reminder here about that,
it grabs logs from the device
that you're filing the feedback from.
So, if on your 950,
you're having trouble downloading
an update and you file it from your PC,
it's going to send us logs from your PC.
And if your PC is not having problems,
then we're going to get PC logs
that aren't showing any problems.
So, do make sure that
the correct submission is coming from the correct device.
If you can't file feedback, right?
This is one of the questions be like,
"I have no network connectivity on my particular device."
It's the reason I can't find feedback or
the Feedback Hub won't launch because on occasion there's
been a glitch with Feedback Hub where it errors
out or there was actually broken in
one of the Builds that be released
unfortunately back then the anniversary update.
It's been a long time.
We haven't made that mistake again.
Ping us on Twitter because
if your Feedback Hub is broken.
>> I wish I had an account that exists.
>> If your Feedback Hub is
broken then we will work with you as best we
can to get the logs that we
need manually from your machine.
That is one of the beautiful things about
Feedback Hub is that it automates
that process so that there's no back and forth,
navigate this path, this log
or this other place got me this log.
Especially, from an update perspective,
some of the logs are quite large especially if there's
a lengthy error log from a download failure
or installation failure especially
from set up installation failures.
That's the Setuperr.log file
that you can find in your machine.
Those tend to get pretty big sometimes.
So, it's much easier just to have the feedback pipeline,
grab those logs from your machine and send them
over as opposed to us saying, "Hey,
send these all over and zip them up,
email them to us going
through that lengthy and lengthy process."
>> The importance of using Feedback Hub on
the device is having the issue becomes even more
important because the team is actually
working to bring in
even more extensive log
and logging and other things
that could help us troubleshoot issues.
>> For sure.
>> So, I don't know if someone was hired,
was made to be familiar with the tool Field Medic.
We are combining a lot of what that
provided into the Feedback Hub in the future.
So, definitely Feedback Hub really is critical
to sending us feedback to issues you are having.
>> Brandon is spot on this.
One of the things that's actually underway
between the diagnostics team who
sets up the configurations
on the back-side of the Feedback Hub that says,
"Hey, if a user is filing feedback under
a specific feedback path sort of like download updates."
There is a team that is responsible
for configuring which logs we'll get from your machine.
So, that team owns the Field Medic App
for phone which was
the previous way of getting logs from a device.
And some of that functionality
hasn't yet been put in the Feedback Hub,
but they're actually working on duplicating it there.
So that, hopefully in
the future the use of the Field Medic App as
a separate App become a thing in the past
and you can use your Feedback Hub
to do it all in one place.
No more multiple tools.
Simplification, that's one of the things that I've harped
on repeatedly is always about simplification.
That is one of the things that we are moving towards with
some of these efforts.
So, that's a separate thing that I'm
working on is the ease of getting device IDs.
That's a topic for a later date.
We'll talk about that one in your future webcast.
>> And you have a double space in this stupid tweet.
>> Really?
>>Yes. You can see it. It's right there.
>> A double space is after all a punctuation.
>> I know. That's why I have been trying
to fix in your blog post.
>> I'm not the only one who use
double spaces after punctuations.
>> Yes.
>> Or we can have
this conversation right now on the webcast.
>> Yes. How old are you Jason?
>> I am too old.
I learned how to double space.
I learned how to type on a typewriter.
They didn't even have computers in school.
>> Yes, we did.
>> I don't know what a typewriter is.
I have never seen one.
>> Get out of here. So, let
me finish this latter real quick so we can keep going.
Including details, I mean
those of you who that are old hat to this,
of course, include your Repro steps,
what's going on with the issue, your device information.
Don't put your device ID in the feedback.
It's a unique identifier
that's specific to whatever device you're using.
Don't put that in the feedback.
But if you're not downloading updates on a Surface Pro 3.
Say, "Hey, I have got a Surface
Pro 3 and I can't get updates."
Things like that, kind of generic attributes
of the machine that
would help us potentially identify
whether it's something that's broadly spread out.
Like if you file feedback and also there's a bunch of
people on Dells and HPs and Surfaces.
They can't get an update. We have a broad problem.
But there have been
specific instances such as like the Surface Pro 3.
One Issue that we found
that if you had an SD card inserted,
it wouldn't install the Build.
So in that regard, it actually was
specific to that particular machine.
And it actually took some driver updates to fix.
But again, send us all the relevant details
that you can think of and
then just how you're configured.
If you are on fast ring, if you are on slow ring,
release preview, anything special
about your machine that may.
>> No. Stop. I got it. It's fun.
>> If I can go back real quick.
And it should stop.
Anything that's going to help us diagnose and
troubleshoot what may be
potentially happening in your scenario.
And of course, don't forget monitor mode.
I showed this off in the last webcast.
Monitor mode is super important.
It's even more important
especially on Build download failures.
So, when you scan for a Build and it
that says we couldn't do such and
such because of error
800 something, something, something.
When you use monitor mode to capture that,
it captures all the interactions between your machine and
the Windows Update Server and the UUP service in between.
So, if we're failing
because of targeting, we'll get back.
For failure because your particular skew
or variant of the OS isn't
published, well we'll get that.
And that includes like language variants and regions and
similar language pack issues that we've had before where
certain language packs weren't
published and that prevented you from getting updates.
That actually gets captured in monitor mode.
Again, just a recap on how important it
is to use those features when submitting feedback.
So, what's out and where right now.
Well, this technically is out-of-date
now. So which Builds are where?
So, PC 16179, now that's not right anymore.
It's 16184 now.
And then on the mobile side of the house,
207 was in the fast ring but now we have 208.
So as you all know,
we just launched those Builds this morning.
And in 15063 is still available in
the slow ring for
both PC and mobile as well as the release preview ring.
I didn't put the DoT Builds there.
Some folks have gotten most recent
DoT Builds as they've been released.
Some folks don't have it yet. But if you're on 15063,
you're at least on the last major core Build.
But if you're on that Build,
double check for your updates and make sure you have
the most recent cumulative update for your device.
Next topic real quick, before
we actually end up going to the Q&A sessions,
is the New Dev Branch Builds.
So obviously, the creators update is finished.
We have started pushing it out.
Is showing up on PCs,
slowly starting to roll the phones.
So, there's three topics in.
I don't have a ton of Build out
here just because I wanted to wing it with you all.
I can ask Jason
to show the Bean machine again the [inaudible] talent.
Yes, of course I'm happy to.
I'll do it on the Q&A session.
I'll grab the webcam and spin it around again.
So go cadence.
So, this is one of the things
that we get asked about all the time, right?
So, I'm not even going to ask Donna to
reply with how many times she gets
tweeted every day if we're releasing a new Build.
It happens every day, seven days a week.
Multiple times a day from tons of Insiders.
I know it's all about excitement. Totally get it.
So, on a release cadence perspective,
this is not guaranteed timelines,
but what we generally shoot for is for Fast Ring Builds.
We try to at least once a week.
We happen to release today, as you can see.
Last week, I think it was on Wednesday or Thursday?
>> Friday.
>> Was it Friday last week?
>> Yeah, it was.
>> Please give me a couple,
I'll give you at least Builds.
Was it Thursday last week or was it Friday?
>> Monday it was.
>> Monday. It's was Monday. We actually
released two Builds for mobile this week.
Monday and then again today.
And I know we released PCU last week.
>> That was Thursday.
>> Yes, I think it was Thursday and
the week before, it was Wednesday.
So anyway, we try to
release once a week for Fast Ring Builds.
And then, yes, you wrote him out.
And then for Slow Ring, right?
Because Slow Ring is not yet
on the new set of Dev Builds.
Obviously, you have the Ring promotion criteria where it
goes from plenary internally
to our internal self-built Rings,
then it will jump out to the Insider Fast Ring,
and then Insider Slow, and
then at the end of the release cycle,
we want to release preview.
In essence, we have a few bugs, we're tackling it fast.
That's why it hasn't gone to Slow yet.
Our goal, this is our goal.
Internally this is what we strive for.
We would like to get a new Build to
the Slow Ring faster than once a month.
I know that seems like a long time period,
but the Slow Ring really is
that safe Ring where we want to have as few regressions,
as few bugs, super stable Builds.
So, our goal is
to actually go faster than that Slow Ring.
Want it to be two to three weeks.
But if it ends up extending out to about a month,
hey, it kind of happens, right?
Just want to make sure that the quality is
there when we actually release to that Ring.
>> Can't wait to get my mobile to Slow Ring.
>> Yeah. And hopefully, my mom,
quick shout out to my mom who
I think is actually watching the webcast.
I need to get her on the Slow Ring.
So Mom, we're going to have a Chat.
Next on this list is App flooding.
Let me make sure I'm not missing
any questions here real quick.
Tuesday, got a Defender update on Edge.
Every single day. Gears are moving now.
I'm redeeming myself. Hey, I don't know what I did,
but I'm glad to redeem myself.
We have a Medium Ring that is faster than Slow,
but slower than Fast.
It kind of defeats the produce.
>> There is a reason,
I mean, there are things that are Slow blocking.
>> Yeah. They're blocking for a reason
that we don't want to add any more Rings.
We don't want to add more complexity to this.
You can go Fast if you want,
and you can get through a lot of
the pain of being on really,
really super pre-release Builds.
>> Yes.
>> And then Slow is for people that could
be like our mothers
who we want to test and try
out some of the new features
that are coming in the next Windows 10 update.
>> Yeah.
>> And so, I think that we already have a good balance,
and I'll think that adding a Middle Ring
there create much value.
>> I know this is
something that's been discussed
internally at Linked, right?
>> Oh, yeah.
>> We've actually talked about it several times on,
do we have the right number of Rings, right?
Between Fast Forward and the Release Preview there are
three external Rings. Are they enough?
And everything that we've seen between user feedback,
broadly, I know this is a different request here,
but broadly between user feedback,
and then between the data that we get on the quality of
data we're receiving from the users who
are on the Fast Ring and giving us feedback.
And in the same thing again, to
use the Slow Ring and then Release Preview,
it seems like we have the right Build cadence.
The thing that we do rightfully
get a bit of a flack for is,
when we go a long period of time,
especially in Fast without releasing a Build.
Fast Ring users want the
latest and greatest. And I won't blame you.
I mean, I'm on the Fast Ring as well on The Beam Machine.
And I'm on CellForce, which is even
faster on my actual work machine.
It's all about what kind
of bugs do we not want to release publicly, right?
Where are we okay with potentially sending out?
Which is the known issues section in the blog
versus what are the things we don't
actually want to affect you guys with.
So from that perspective,
let me jump to App flighting.
App flighting was a super hot
topic during the previous update.
And we've got a ton of feedback,
and I want to take a moment and
say thank you to everyone who gave us this feedback.
During this development cycle,
we got a lot of feedback because
preview app Builds were
being released to the Slow Ring instead of the Fast Ring.
I know there's probably a few
either watching the webcast are like, yes,
I had to switch the Slow Ring to get the Builds,
super frustrating, totally acknowledge it.
And let me just say this.
The plan isn't completely hammered out yet,
but I was sitting in meetings yesterday
on this very topic.
We are working through this,
and we'll do the right thing for as Insiders.
Fast Ring should get the app updates.
I mean, that's the purpose of
having the Fast Ring, right?
To have the latest and greatest
the fastest before anybody else.
So, to see something skip
the Fast Ring and actually show up in Slow,
your frustration, I get it.
The team gets it. Everybody here who
put that in place understands it.
There is a bit
of extra insight that I'm going to share with you.
So hopefully, I'm going to get my hand slapped for this,
but we'll see what happens.
When it comes to the end of our release cycle,
so as we were finishing the creators update,
there is a need to test what are called the Inbox apps.
So, the version of
the app that is actually going to show up in
install with the RTM version of the creators update.
So we needed to keep a pool of users with the Inbox apps.
And this is where your frustration came in,
and it was the Fast Ring that was chosen to
keep those Inbox apps at
that point rather than it
being Slow Ring or potentially Released Previews.
And Release Previews obviously,
because they were still on the anniversary update,
hadn't received the creator's update Build,
it wasn't really the appropriate Ring to use that for.
So, the selection had come down to Fast and Slow.
The teams discussed, they chose Fast.
We got your feedback and
were making the adjustment moving forward.
So obviously, we'll do
a big announce once we get the ideas hammered out,
and once you get you the updates made.
As of right now, outside our RTM
for the creator's update,
not anything new we're working on right now.
We're in a completely new development cycle.
So, don't get ahead of me there Adam.
>> Adam Jason.
>> I know, right?
I know, right? We're nowhere
near RTM, near development cycle.
We just launched the fourth Build.
We're just getting going.
The full year development
yet to come on this new release cycle.
So from that perspective, like I said,
we'll get things ironed out on our side,
and we'll make some announcements once ready to go there.
You should be getting the preview app Builds
in both Rings currently, I do believe.
>> It is definitely next week.
>> Yeah. And then once we move forward,
we go to what would be the Inbox version,
because just like the OS stops
taking major updates at some point,
and it's called Feature Complete,
then it works into only bugs fixes after that,
the same thing with the version of the app that
will show up in a RTM Build.
It will reach Feature Complete for the app.
They'll work on the last minute bugs
they need to fix, and that version of the app,
and then that's what will actually be packaged into
the RTM update that gets released to all the folks in
the release preview Ring as well as globally to
all of the folks who don't
participate in them when it's inside our program.
>> And despite popular belief,
it is important for us to get
coverage on the app versions that are in the OS.
>> Yeah.
>> Because there are a lot of people in
certain countries that they don't
have access to a lot of online stuff.
And they're bandwidth is very precious.
And so some of these folks they they don't want to spend
their bandwidth downloading the tons
of app updates from the Store.
So that means that Skype
and the Mail and Counter app and the Photos app,
all those apps need to work great for them out of box.
>> Yeah.
>> Because their bandwidth are so precious.
And so, I know there's a lot of debate about that.
It's easy for us in countries where there's a lot
of ample bandwidth to kind
of not really think that's the case.
But there are places where it's super important.
>> Absolutely true.
I don't think I have much else to add on top
of that since it's spot on.
And like I mentioned, when you're doing
the bug fixes at the end of a release cycle,
it's super important to make sure that
you don't break anything else.
If you're on preview app Builds from the next app cycle,
it doesn't do much good to make sure that we
didn't break the current version of an inbox app it is
going to shift in the RTM Build out to retail
so that's where that comes in.
Last but not least, Hardware Application Diversity.
This is a super huge topic for me, personally,
and I'm going to give a shout out to
a couple of folks
for something that we found at the Creators Update.
I might end up doing a big write up about this,
but I think both
of them are potentially watching the stream,
so I wanted to give them a quick shout out.
There were two insiders that ping me earlier this year,
while we were still working on the Creators Update.
So, in essence, back in January,
and then I found the second user in February.
Each of them was reporting not being able to install
any Build 15002 or greater.
So, every time they install
Build it would fail and would just draw them
back and it was just these two users and it
was really hard to pinpoint because
when you have one person reporting an issue.
It's like, "Okay, what's
happening on this person's machine?"
As opposed to when I have 10, 20,
30 or even more people reporting about it, right?
When it's one person reporting something,
it can be super difficult to dig into.
>> Usually, when the flight goes out,
the first thing we do is like,
"Is it just one person reporting
something or should we correlate.
Are there people who bring it across
Twitter and tried it?
How big is the scale ship that's going to impact?
>> These two folks may win.
Yes, that's Tony.
Sorry. I hope your mom use her real name.
Tony, thank you for showing up.
Tony is one of the two folks
that was involved in
the scenario that I'm talking about here.
So, they reported this particular issue,
and so I put it together into a Twitter Chat,
because their symptoms sounded very similar.
And it turns out they
were running the exact same machine.
When users here in the US,
when user Tony is over Canada,
and we just happened to be
same HP but just different model number,
and it turns out I had one has
eight gigs of RAM, the other was 12 gigs of RAM.
So, we started digging through
this particular issue and yes, rest to NZ.
Yes, it's a system PTE misuse. It is that bug.
We started digging into the issue and
none of the feedback that was filed
from your machine would give us what we needed.
Come to find out the machine was
failing at the kernel level when it
was trying to boot and install the new OS.
It was failing at that level
so there were no locks coming back.
It was just empty because there's
no tracing coming on at
that low-level instance of the OS.
So, started working with
Kernel team and the deployment team here,
and through trial and error, some WebLink sharing,
and a bunch of back and forth and a ton of
education on my side because
I've never done kernel debugging before,
I got to set up and we started doing kernel debugging,
and if we connect and
then fail and we wouldn't get what we needed.
So, it was proof that there was something happening at
the kernel level but it was happening so far down,
that even a kernel debugger
wasn't granting it appropriately.
So, at that point, it was time to break out
the big guns and we
had- it's called the
base team it's where the kernel codes live.
We had them reach out straight to
HP and we pulled it folks from HP both here
in the US as well as some of their engineers from
Taiwan and we packed
as much information as we could over to them,
machine information, BiOS information, chipset drivers,
graphics card data, and
so that I don't keep running on and on about the story,
like come to find out it was
a BiOS farmer and memory set that was being
allocated and written and was
supposed to be locked because it was
actually interacting at a super low-level in the kernel,
which there's some details I can't talk
about until it gets fixed.
It was being overwritten. So, there were
some data that was supposed to be helping memory
that wasn't being held in memory and
so when the OS would go to
check and then start writing the new OS, it would fail.
If it wasn't for these two users who had
reported it and happening to connect,
in fact they were getting the same issue,
we wouldn't have found out about this.
It would have been, it would have looked like
two separate one user instances that were
just filed in feedback or on Twitter.
Any other scenario potentially
sharing our answers or Reddit.
It really does sometimes take
a human interacting in the middle
to try and connect the dots.
So, come to find out there weren't a lot of
insiders that we know of
running this particular hardware set.
But once you get out globally,
we don't have tons of data on
retail users right because we don't get as much imagery
back from retail as we do
from insiders who are flighting.
Let's just say there's a lot of people in
the world that are running this hardware.
HP shares some information on
sales numbers and things like that so we
can hardly guesstimate on
how many users were affected by
this. Unless you say, it was a lot.
So, we had two insiders
representing a small pool
of insiders using the same type of hardware,
but these two insiders report
in the issue hitting the smaller pool of
insiders who represent
a gigantic chunk of users globally.
It would have hit this in the retail space.
Because of the effort of them reporting this
and giving these to us enough digging
in and really chasing through this,
we found something that was going to hit a whole lot of
folks and put them in in a really bad scenario.
And you can imagine if we pushed this
out and all these folks had gotten this,
they would have failed updates
so they would be wasting their bandwidth.
They've been wasting their time to install the Build.
And not only that,
I mean I that we've been creating
a terrible experience for them,
when, "Hey, if your Builds are not installing.
What are we going to do?
You're going to reach out try to get support.
They would have either been contacting Microsoft Support
or potentially HP Support
to try to figure out what's going on here.
So, as a result of all these,
we were able to put a block in place so that,
as the creators of data is rolling
out to all these retail customers,
the users with these particular machines will be
offered to Build until we get it fixed.
HP is actually working on the fix currently.
These two insiders are super awesome I can't thank them
enough for everything they've
done in the past four months.
I actually have worked with HP and I'm going to get
the BiOS from them and actually
these two insiders are going
to get the test the fix first.
They will be the first two people
outside of HP and Microsoft to get
their hands on this and it's
all because they were insiders,
took the time to report this,
and that they spent their time to
work with us to get through this issue.
It's a little way of us saying thanks,
and hopefully the fix
works and we can get these particular machines up and
running with that BiOS is released
broadly but don't go out to the
HP Support System Software,
which comes pre-installed in
all the HP laptops and desktops.
And then once the users take the update,
then don't get the Creators Update.
It's kind of a good news story.
Like I said, we'll do a much bigger write up on this,
share as more details in the upcoming weeks,
but yet it's just an awesome example
of what you all, as insiders,
can do when combined with us
here on the engineering side of us listening to you,
you taking the time to talk with us,
and then working together to reason
and count through these issues
because some bugs are easy to fix,
and other bugs like this are not easy to fix at all.
I told you this whole story for a reason.
One was to share
an awesome success story of the insider program itself,
but to the topic itself
at had its hardware application version.
So, one of the things that I want to focus
on with you, as insiders,
but broadly as new insiders come into
the program is that exact thing
is diversity of the hardware being used,
and diversity of applications being used.
I'll use myself as an example.
At home, like many of you,
I have a home built machine,
and we put together the machine.
This is my first PC built.
So, at home, I don't have a standard Dell machine,
or a standard HP, or
any other OEM out there. I have a home-built.
It's got an MSI motherboard in it.
It's got an AMD chipset in it so I
don't represent retail users
all that well from a hardware perspective.
From an OS perspective, sure,
I'm right on the the same preview Build that you all are.
But how the preview Build functions on my system,
is it a good representation of how it's going to
function on my mom's machine?
She happens to have a HP laptop.
So, from that perspective,
I'm not doing a service to that regard.
And then from an application perspective,
the apps that I use on my machine on
a daily basis are
definitely different than what my mom would be using,
or potentially any of your family members.
It's probably different than what you use on any basis.
So, I use the web browser. I'm using Excel,
I'm using Word, I'm using PowerPoint, I'm using a lot.
Obviously, my work machine I use a lot of
corporate apps that we have here internally,
but I don't necessarily play
games like to
the same extent that many of the insiders do.
There's a bunch of regional apps
like Weibo and QQ that are super popular in China,
but I don't use here in the US.
Again, I'm using myself as an example.
No doubt, the same thing exists between
the US and you know countries in Europe and
countries in Asia and in countries like India
and Australia and we have folks here from New Zealand.
So, it's local and regional apps.
If you know there's things that you use,
you may be one of those people that is
10 or 15 insiders that happen to be using
a particular app or a particular piece of hardware.
And like Donna has said before,
there's the millions that represent the billions,
is the insiders that are
representing the rest of the world.
Without even knowing it, you may be one of
these users that's representing
a very small number of people on the insider population,
but you're representing a huge number of people
globally and you don't even know it.
And we don't know it until we find out.
So from that perspective,
if there is an application that
is super near and dear to your heart,
and it's not working right,
make sure you to pop an email.
Make sure you take the time to share this information.
And if it happens to be a regional app say,
"Hey," put a special column in the feedback saying, "Hey,
this is something that's super popular in my
location," be it in the US
or Canada or India or wherever.
Make that note. One of
the things that we can do is as we start doing,
testing and automated testing as it
jumps through the internal rings
before it even goes to insiders,
we can potentially implement
additional tests and we catch some of
these super popular apps that we may not catch otherwise.
Let me check on the comments real quick.
Make sure I'm not missing anything
related to this conversation.
I love seeing people from all over the world tuning in.
Like, you guys rock.
Like, that's one of
the beautiful things about the Insider,
is seeing the number of people from around
the world that read our tweets,
and read the blog posts,
and take time out of your day
to come and spend your afternoon,
evening, or daytime, or nighttime,
or wherever you're at and come and Chat with us.
And listen to us talk,
and hopefully spend the time to Chat back
with us. So, awesome.
Will Edge be unbundled from the OS so it can be
updated more frequently? Good question.
That's a question for the Edge team.
One of the things that- let me segue
way from here for a moment.
At the beginning of the webcast,
one of the things that I was talking about
doing in our monthly series is having guest speakers.
So, one of the things that I really,
really want to do is
have owners from different areas
of the product, lets use Edge as an example.
If next month I can get folks from
the Edge team to come in and represent,
I would like them to talk about their product.
The plans for their product,
current bugs, current issues they're
facing, to take your feedback.
That's one of the things that I would
like this webcast series
to spin into is to go a little bit deeper into
different areas of the operating system or
particular apps that come from
Microsoft to answer some of the questions that you have.
Yes Raphael, one of the Insiders with
the firmware bug, yes, he is here.
Are there any other questions like that?
All right. So, with that,
we've got about 10 minutes left.
Hopefully that's enough time. Let me open it up for Q&A.
This is going to be strictly
off of the chat window, obviously.
Let me ask folks here in the room real quick.
Did I miss anything that any
of you potentially wanted to cover today?
I know I've been kind of rambling
on for nearly an hour and
a half with a little break
of excitement for a Build launch,
which I don't want to add to the relaunch of other Build,
so let me close that real quick.
Have I missed anything and you potentially want to cover?
>> I think it's been pretty good.
>> Great. Okay.
>> Yeah. I mean, we're getting goals out.
Decided to get people trying out.
>> You've got to skip out on the chaos of-
>> The release.
>> -Build stuff.
>> Okay.
>> Hey all.
Has the Build installed yet?
How's it going?
>> Oh my goodness.
>> People are reporting progress
on installing the new Build-
>> So, there's pretty much one word
coming across the Chat stream right now.
Okay. Okay. So those of you who
continue typing mobile again and again and again,
your point is well landed.
Okay. Simmer down. Simmer down.
You have my attention. Mobile is still getting built.
It might be a differently named branch
but we're still releasing mobile Builds.
Mobile isn't dead. I mean,
if it was dead we wouldn't be releasing anything for it.
I don't have a great way to answer
your questions just from the simple perspective of,
hey, we're releasing Builds. There's more stuff coming.
As we make progress with those Builds,
we'll keep fixing bugs.
When feature shows up,
they'll be announced in the blog post.
We haven't abandoned it.
I mean, like I said before,
if we had abandoned mobile,
you wouldn't be getting Builds on it.
There would be no devices
on this new development cycle at all.
I mean, it wouldn't be worth the effort to keep
creating Builds and keep sharing them out to Insiders.
That arm of the entire program
wouldn't be alive if mobile was truly dead.
>> Another word came through.
>> Say what?
>> You've got another word is coming through now.
>> So RS3. I mean,
RS3 is just the code name internally for
a series of Builds that we're
working on in a dev cycle right now.
Just because they're different branches it
doesn't mean anything crazy.
>> Trying to tie what we name branches and how
we number our Builds to imply anything
with regards to product strategy doesn't work.
We could easily name a branch white and red.
>> I mean we had FBL Impressive in the past.
We had FBL Awesome.
>> Awesome.
>> Yeah. We've had some crazy branch names.
So it's just Future 2 is
just the branch that mobile is in currently.
I mean, that's really all it is.
It's just the name of a branch.
>> Our branch name is not
indicative of just what the product strategy is.
Yeah. Mobile is alive and kicking.
>> We could have called
it Feature Awesome and it would still be the same thing.
It's just a branch name.
I don't have a better explanation than that.
I doubt that that's going to
satisfy the curiosity that some of you have,
but honestly that's the answer.
It's just the name of
the mobile branch that
the Builds are coming from currently.
Are we going to have
FBL Ninja Cat? That would be awesome though.
Flash streaming from One Drive for Groove. Oh, hey.
I can take that and share that back to
the Groove team. That would be interesting.
>> Somebody made a OneNote of
all the questions asked so far.
>> Oh, sweet. Dang Tony. All right.
Tony, tweet me that link. Where is Donna?
What's Gripe Integrate with Beam? The ETA for My People.
Wow. This is going to be super
helpful because I can- wow.
>> Donna is in San Diego with Carmen.
No? You didn't watch Carmen Sandiego?
>> Where in the world is Carmen Sandiego?
>> Oh yeah. Totally watched that as a kid.
When will new features show up?
That's completely dependent on
the teams working on things.
There is no set cadence.
Like that My People feature showing up now,
it's just because they got checked in early.
>> New features are showing up already.
>> Yeah. Like, there's literally no cadence on that.
It's, when a team has something ready,
it is stable, and it's ready to check in,
that's when a team will do that.
It will show up and then,
once it gets proven through the internal rings,
it'll show up in a flight.
Literally just like the My
People feature that showed up in desktop too.
>> And the thing is, to stress a little bit,
it's that your teams are going to
start checking features early.
And their feature, like My People, is not complete.
And so, it may seem
basic now but integrations with other things,
like someone had asked about Beam integration with
My People or Twitter or whatever.
The team is working
really hard on doing some cool stuff with My People.
You know for someone, I deal with people
like my dad down in Oregon,
and having him on my taskbar to engage with,
to send files to, to e-mail,
to Chat with, it's pretty cool.
And so the team, they're working really hard to kind
of finish and flesh out the feature.
So don't judge the feature yet.
And that will be the same for
many other features that will get checked
in that won't be entirely finished when you see them.
So just keep that in mind as you're
looking at stuff and as features are starting to show up.
>> You have understand most of the people assume soon.
>> Soon trademark.
>> Yes.
>> And Jason,
your post are being published for your Beam update.
>> Awesome. Oh, okay. Actually, you know what?
Somebody asked in Chat if we're going to have
specific shout outs on IoT stuff in flights.
>> That is a good question.
That's actually a great question.
Donna and I have been talking a lot about IoT.
I'm excited about tinkering with doing this 10 IoT stuff.
We're talking to the IoT guys and
we do think that there is an opportunity
to integrate their stuff into ours.
And so, I i don't have anything specific
to share but we're really talking about that.
I think it would be great if we could
integrate their stuff into ours.
So, I would love to hear more from
Insiders who are in to IoT and have done any projects.
Donna and I would both love to see some of it.
>> I have to do the leak work real quick,
okay. Is it still showing?
>> It's showing you now.
>> Okay, good. Okay. So I sent out
the link for the- Brandon,
can you spec me the link to the blog post so I can
update the account you're on?
>> I did.
>> I'm working on it right now.
Okay. So I'm actually going to do this real quick.
>> I just told people to reach out to you on Twitter.
>> Fantastic.
They know where to find me.
>> Browser open. And I apologize ladies and gentlemen,
I am working on fixing the AKA link that I just shared.
It's probably still routing to the to the Insider page.
I'm working on fixing that right now.
So, it will take just a minute.
So keep your questions coming.
As soon as I finish this I will be right back to them.
>> It's wide.
>> And edit on URLs.
That is it. Next page.
Okay. That should save.
It'll take a minute or two to propagate.
And then that short URL that I sent
out will be ready to go.
And then you can check out the
full write up that I did on The Beam Machine.
>> Somebody is wondering if there's a better way to
say thank you from the post's feedback.
>> We get thanks all the time.
I mean, it's extremely gratifying.
I can't tell you how awesome
it is to when people
come to us and are like, hey, thanks.
It may seem like a simple gesture, but it's.
>> We have a general e-mails about it.
>> Yeah. It's a rewarding feeling
to get feedback from folks.
Good or bad, right?
Constructive or you know.
>> I know.
>> I don't know.
>> The feel good stuff too, right?
>> Yeah. It's constructive.
It's okay to be criticized.
It's okay to tell us something is not right,
but like, do something in a constructive way.
Coming to us and saying, this sucks.
This suck so badly. That's not constructive.
That doesn't tell us why it sucks.
And so like, we're not afraid to hear the bad and ugly.
It's just that our expectation is
that there's some level of respect from our people too.
>> Yeah.
>> You know we have feelings.
>> It can make Brandon cry in his OneZ.
>> Thanks. We should give a shout out
to Britney and the Frisco Texas store at Microsoft store.
They are watching our webcast in their stores, so.
>> What's up Frisco? How you doing?
>> Hopefully, they're still watching.
They were watching about 51 minutes ago.
>> Okay. Well, if they're still watching, awesome.
If not, sorry we missed your Chat comments.
But representing nonetheless.
Yeah, I mean, there's really,
you could send feedback back or
you could just catch us online,
like drop us a note at Twitter, Windows Insider.
If there's one of us
individually you want to say something to,
I had our handles at the beginning of the presentation,
I can flip back to that.
>> And all of our handles were also,
well not, all of them, didn't have to.
But the blog post today have a lot of our handles,
our team handles. Since today's flight.
>> Let's see, that shift flipping
over on the presentation.
>> With that being said,
I have to go to a doctors appointment. So.
>> All right, man.
>> Have fun?
>> Well, it's doctor's appointment. No.
>> Have fun driving there.
>> Yeah. So, sorry I had to flip
back other on the slides but,
like I said, if you ever want to reach out to us,
just add us up.
Like, you know how you get a hold of this.
There's answer's forum. You could
send thanks from the feedback hub.
Or you can just reach us individually here.
And then don't forget, Jeremiah Marble,
he's @JeremiahMarble on Twitter.
Donna Sarkar is @DonaSarkar.
I'm sure you probably know that from
all of her awesome tweets that go out.
But I will give a shout out to Tony, number one,
because he was one of the HP guys who were up to just,
to dig in to the Kernel issue, but number two,
for the list of questions that he has helped
compile from all of you on the webcast
because I've spent more
talking and less time reading this time around.
But I will say thank you.
We'll go through, look at the questions and answer.
I don't know if how I'll be able to answer all of them.
Some may be confidential type stuff.
I haven't seen the full list.
But I promise you, I will work through them
and find a way to get answers out to you guys,
even if it's just on Twitter.
If I have to create an answers forum thread and
post answers in there, I will do what I can.
Certainly could get lost in the Chat. Yeah, of course.
Let me flip over to my web browser real quick.
And I'll check here. The Beam Machine blog.
The Beam Machine, there you go. That is
the link to the new The Beam Machine blog.
Let me see if it's actually working now.
Yes. And it is working.
Okay. So that link is active and ready to go.
And so I do know there was
a request earlier for us to run through and
show The Beam Machine once
again for those of you that either tuned in
late or have not seen it on Twitter or what not.
You can actually see the Build images in that link.
But if you want to see the machine in action,
I will show one more time before we close up for the day.
So I'm going to grab the web cam.
Sorry. We're going to have
a shaky moment here real quick but.
Set that around.
All right.
This, again, is The Beam Machine.
>> I'll turn off the light.
>> Yeah, if you can go.
So we're going to turn off the lights, so it's a little
bit better and easier to see in here.
And I'm going to minimize this
so I can actually watch and see what I'm showing you all.
That RGB RAM is awesome.
I love it. Change in colors.
And as you can see, the LEDs in
the machine are changing colors.
It's way cooler in my office
because I have super dark lighting in there.
>> We're not sitting in the dark. Just for you, guys.
>> Yeah. Right now, you're
getting a bunch of like reflected light
from outside from the conference room.
But, as you can see,
the LED fans that are in the Thermaltake case,
you can see the reflection of
all the LED strip lighting
that is inside the case itself.
You can see the logos on
the motherboard are actually changing color.
Here's the MSI logo tucked away.
You can see the LEDs
behind the motherboard. They're actually integrated.
Those little dots back there
are integrated into the motherboard.
And then, of course,
as you've been able to see the whole time,
the RGB RAM, which is
just like one of the coolest things ever.
Interesting enough, even when you
power the machine off or put it to sleep,
the brand keeps changing colors.
So people walking by my office even
after I've powered it off and gone on for the day,
people have said 'I stopped
at your office and was just watching
the RAM sit there and do
the rainbow dropdown colors. It looks like the matrix.
It's kind of funny.'
And then, although we do have a water cooling setup,
this particular case supports
the big radiator. There's the power supply.
So efficient. The fan's not even working.
And we've been broadcasting this entire time.
The fan has not kicked on
the power supply. That's how cool it stays.
That's how efficient it is.
And then just one more quick around.
Drive base. We don't actually have
any disk drives in here currently,
because we just use USBs for
everything on the backside of the case.
All right. Nothing too crazy.
The top, that's
the keyboard and mouse plugs for what we're using.
The mesh dust panel.
And then you can actually see
the radiator for the liquid cooling setup in there.
Just kind of awesome. And then
a quick view around the back, in case you're interested.
We have thumb drive with some files on there.
And then just your base.
And then one of
the really cool things is, does it show? Can you?
I can't see the screen from here. Can you see
the VR ready on that USB port?
>> Yes.
>> So that's super awesome
is where I was talking earlier about
trying to future proof this machine for
when VR becomes the thing.
Well, this motherboard and
processor will definitely handle
that when the time comes.
We don't have to upgrade that part.
It would just be a graphics card change for VR.
So, again, then we've got a little bit over.
We got started a little bit late.
So, let's just call it make up time.
So, send us some feedback.
Let me flip to the slide.
As I mentioned at the beginning and
as you can see on this slide,
if you want I can flip to that one real quick.
Tell us what you want to see in future webcasts.
Right? I know we've covered,
The Beam Machine was kind of the highlight today because
this was the first one. So we're going to get in here.
But if there's product features that you want to see,
if there's special guest you want to see on here,
which Ryzen I use in the 1800X.
Let us know what you want to see. I will
go through some of the comments after the fact.
Definitely, if you can, send us tweets.
Tell us, hey, I want to see this in
your future webcast or drop us something.
If somebody wants to start a thread
on the answer's forums that says
Future Webcast Request, just post in there.
Like any of you can start that thread.
I'll let somebody get going with
that. We'd love to hear your feedback.
And if there's anything about
today's presentation that you like,
that you didn't like,
again, feel free to show that as well.
As it could be constructive, but let us know.
Because if there's something we
can do better, we'd love to do it.
So, I will review the OneNote of questions.
I will answer as many of those as I can.
>> Maybe next time, we can do a proper people's demo.
>> Yeah. We'll do a better people demo the next time
around rather than me trying to set it up midstream.
Like I said, these are completely unscripted other
than having a basic agenda of things I want to cover.
Just because it's way more fun that way.
So, until next time.
Thank you all for tuning in.
Thank you all for being Insiders.
And as Donna always says, keep hustling.
For more infomation >> Tutoriel Comment faire un boomerang en carton - Duration: 3:19. 
For more infomation >> Tuyệt chiêu đăng ký tài khoản google adsense mới nhất 30 3 2018 - Duration: 20:27. 
For more infomation >> Cùng Xem Sự Đáng Yêu Của TOKI UNI5 | #QUANGTRỌNGPHẢILÀTHẦNTHÁI - Duration: 0:37. 
For more infomation >> i test a electric gum - Duration: 5:36. 
For more infomation >> El horóscopo de hoy, 30 de marzo de 2018, por el astrólogo Mario Vannucci | Un Nuevo Día | Telemundo - Duration: 3:28. 
For more infomation >> News Conference: Loyola Chicago - Preview - Duration: 24:46. 
For more infomation >> News Conference: Michigan - Preview - Duration: 23:41. 
For more infomation >> ТРИ ПОРОСЕНКА. Диснеевская сказка для детей с картинками. Слушать аудиосказки онлайн в качестве HD. - Duration: 9:03. 
For more infomation >> ¡Guatemala celebra la Semana Santa con fe y tradiciones! | Un Nuevo Día | Telemundo - Duration: 4:02. 
Không có nhận xét nào:
Đăng nhận xét