Getting the Windows 10 November 2019 Update Ready for Release Insider

Fisher Mann said:

I believe it is. I am on 1909 on my RP machine with 18363 installed.


OOPS, looks like it may have been the cumulative update from Brinks post.

f14tomcat said:

I did an edit to my post, Josey. Take a look.

Winver says it is 1909 but the Feedback Hub says 19H1. I saw TC.

Superfly said:

Well as you asked so nicely, here are some more pics

Attachment 250850

After applying latest CU - kernel build still the same build.

My point being what's basically a roll-up should not be classed as a new build unless the kernel itself is new.

Gotcha. Somebody, somewhere, in the dark recesses of the Redmond Campus, decided that to avoid confusion and make a "distinction" between 19H1 and 19H2, they would bump the build number by 1. There's a blog on it somewhere, about a month ago.

I still do not have all of the features described.

Josey Wales said:

Winver says it is 1909 but the Feedback Hub says 19H1. I saw TC.

Ok, then somebody didn't update the Feedback Hub. Really has no bearing on what anyone's machine actually shows. Feedback site needs attention and updating.

f14tomcat said:

Ok, then somebody didn't update the Feedback Hub. Really has no bearing on what anyone's machine actually shows. Feedback site needs attention and updating.

But then again I do not have all of the features for it either and in my registry is shows 18362.418???

f14tomcat said:

Gotcha. Somebody, somewhere, in the dark recesses of the Redmond Campus, decided that to avoid confusion and make a "distinction" between 19H1 and 19H2, they would bump the build number by 1. There's a blog on it somewhere, about a month ago.

Yah I think it's a bit retarded -- some time ago developers had huge issues getting Windows version from the Environment API (reporting wrong version) and resorted to using the kernel file build version to check which Win version their apps were running - with this scenario those apps are all gong tits-up - it won't be a train smash as it's still Win 10 but just saying...

Josey Wales said:

But then again I do not have all of the features for it either and in my registry is shows 18362.418???

Maybe you didn't get the enabling CU to flip it correctly to 18363. I really don't know on your machine. My RP is 18363.418 and has all of what it's suppose to have. I never used any UUP Dump ISO's to manipulate my RP, it's strictly by the rules on Insider, with all the CUs comely when they were suppose to, and updating in sequence. Maybe that's why I was in the Early Release 10% who got it (18363) almost a month ago.

kado897 said:

That's confusing for Insiders in the Slow Ring. Are they saying change now or wait until it is updated to 18363.xxx?

You're right Keith, it is confusing for the Slow Ring. Microsoft did say they would give us the heads up when it's time to change thogh. From various things I've read the Slow Ring will be moved over to 20H1 after 19H2 is released.

f14tomcat said:

Maybe you didn't get the enabling CU to flip it correctly to 18363. I really don't know on your machine. My RP is 18363.418 and has all of what it's suppose to have. I never used any UUP Dump ISO's to manipulate my RP, it's strictly by the rules on Insider, with all the CUs comely when they were suppose to, and updating in sequence. Maybe that's why I was in the Early Release 10% who got it (18363) almost a month ago.

I got it from Windows Update,, I just installed it yesterday after I got out of 20H1 because it would not restart and today I found out why , it is a bug and there is a fix for it.