Windows 10 Build 10240.16384 RTM en-US Pro/Home MS Original OEM Image

I have no idea, I'm not a insider anymore, opted out for normal install on 29th, but theirs something different, the whole thing is just quicker, don't know why

 

Basically they are of the same based on packages info, with the exception I found in the first installation, it has no

Code:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability]
"FlightingOwnerGUID"="Y-O-U-R-OWN"
"EnablePreviewBuilds"=dword:00000000
"Ring"="Retail"
"RingBackup"="WIF"

Edit: The ESD has the same effect.

 

Thanks bud for the info

 

I'm thinking that has to be the case as well...

 

No worries. Remember to use the correct Flags (EditionID) while creating a custom image.

It is a deadly must. Unlike Name/Description and DisplayName/DisplayDescription.

 

So there is something related to Preview Builds in the ESD, while in the img file it was disabled?

 

Well, I need to have a good look at it. Nevertheless, the Insider Program Option in Settings remains the same.

 

I installed from the insider version and my [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] is empty.

 

You need to login to view this posts content.

 

Bout bloody time. Finally have an iso that will take an oem pack

 

I would really like to have some info from you if you please:

Why the Windows 10 System once upgraded in-place (e.g. from Core to Pro) would not get upgraded to newer build thru WU?

Thanks.

 

OEM's usually download dvd layer & join them with ms tool to create .img. This time they can direct download .img.
This is bootable the same as .iso. No need to decrypt esd & build custom iso.

 

Thanks bud for info

Figured as much
IMO this build is notable cause they removed the debugging code... A lot faster

 

Indeed it makes it easier to distribute builds amongst the oem partners. That way you just send out one thing instead of adding multiple layers of complexity.

 

Is this a fact (removed the debugging code) or just your feeling (a lot faster)?

 

... a 'sophisticated' guess .

 

Just my personal opinion

 

my esd leaked build 10240 is still showing the NT current version 6.3 in registry editor
(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion)
Does this OEM install have same version of 6.3 or different?

 

This leads to the next dumb question

How can you tell if your version has or has not the "debugging code"??????????????????

 

I have a notebook with legit win7 pro 64bit. I've been using it with adk to build winpe & update/integrate wims.
The latest dism doesn't run correctly under win7 so I ran win10 setup & upgraded - it would not activate! (dism/adk works fine though).
Dumped a clean install of win7 & tried upgrade again - Activated.
Clean install win10 pro using default retail key - activated.
Clean install win10 pro using default manufactures key (without OA3) - Activated.
What the?
View attachment 37317