Media Creation Tool updated

sportsfan148 · 22 Oct 2019

I just wanted to pass on a bit of info to the forum. The Media Creation Tool 1903 version has been updated to build 18362.418 on Microsoft website

Brink · 22 Oct 2019

Download Windows 10 ISO File

Create Bootable USB Flash Drive to Install Windows 10

muchomurka · 22 Oct 2019

Direct download (not using MCT) of 19H2 ISO not working yet in continental Europe.

Bree · 22 Oct 2019

sportsfan148 said:

I just wanted to pass on a bit of info to the forum. The Media Creation Tool 1903 version has been updated to build 18362.418 on Microsoft website

Yes, the tool has been updated...

...but that has nothing to do with the build of the ISO it will create. That is determined by the Products.xml file that it downloads each time it is run. And that still instructs the tool to download files for 18362.356. In fact, any MediaCreationTool from 1809 onwards will build 18362.356 at the moment, because they all will get the same Products.xml file from the server.

Code:

          <File>
            <FileName>18362.356.190909-1636.19h1_release_svc_refresh_CLIENTCONSUMER_RET_x64FRE_en-us.esd</FileName>
            <LanguageCode>en-us</LanguageCode>
            <Language>English (United States)</Language>
            <Edition>Professional</Edition>
            <Architecture>x64</Architecture>
            <Size>3564527804</Size>
            <Sha1>be0e7e220234af13911a3dee426b80bb28caa19d</Sha1>
            <FilePath>http://dl.delivery.mp.microsoft.com/filestreamingservice/files/98e68b3e-e4d3-4769-8cd5-7ac465bb07f5/18362.356.190909-1636.19h1_release_svc_refresh_CLIENTCONSUMER_RET_x64FRE_en-us.esd</FilePath>
            <Key />
            <Architecture_Loc>%ARCH_64%</Architecture_Loc>
            <Edition_Loc>%CLIENT%</Edition_Loc>
            <IsRetailOnly>False</IsRetailOnly>
          </File>

sportsfan148 · 22 Oct 2019

Bree said:

Yes, the tool has been updated...

...but that has nothing to do with the build of the ISO it will create. That is determined by the Products.xml file that it downloads each time it is run. And that still instructs the tool to download files for 18362.356. In fact, any MediaCreationTool from 1809 onwards will build 18362.356 at the moment, because they all will get the same Products.xml file from the server.

Code:

          <File>
            <FileName>18362.356.190909-1636.19h1_release_svc_refresh_CLIENTCONSUMER_RET_x64FRE_en-us.esd</FileName>
            <LanguageCode>en-us</LanguageCode>
            <Language>English (United States)</Language>
            <Edition>Professional</Edition>
            <Architecture>x64</Architecture>
            <Size>3564527804</Size>
            <Sha1>be0e7e220234af13911a3dee426b80bb28caa19d</Sha1>
            <FilePath>http://dl.delivery.mp.microsoft.com/filestreamingservice/files/98e68b3e-e4d3-4769-8cd5-7ac465bb07f5/18362.356.190909-1636.19h1_release_svc_refresh_CLIENTCONSUMER_RET_x64FRE_en-us.esd</FilePath>
            <Key />
            <Architecture_Loc>%ARCH_64%</Architecture_Loc>
            <Edition_Loc>%CLIENT%</Edition_Loc>
            <IsRetailOnly>False</IsRetailOnly>
          </File>

That's a bit confusing then. Normally under MCT properties/details it just says 10.0.18362. When you have used the Iso to clean install Windows 10..only then do you find out what build has been installed when you go and check under System settings.
I presumed when I saw 10.0.18362.418 that Microsoft must have started giving better information on what exact build the Iso would install because that coincides with the current latest build on my main Windows 10 Home PC. But If Build 18362.356 is going to be installed when I use the Iso I don't see what the point was of listing the file version as 10.0.18362.418. Any idea why they have done that?

Superfly · 22 Oct 2019

sportsfan148 said:

Any idea why they have done that?

Absolutely None, I'm afraid..

I have given up on the management decisions being made at Redmond TBH... so many basic things are wishy-washy and left out to dry....

Bree · 22 Oct 2019

sportsfan148 said:

That's a bit confusing then. Normally under MCT properties/details it just says 10.0.18362. When you have used the Iso to clean install Windows 10..only then do you find out what build has been installed...

There are two ways to check the build it will install before that, The one I used is to run the MCT as far as the licensing notice, then read the Products.xml found in C:\$Windows.~WS\Sources. Thre other is to run the MCT to make the USB or ISO, then check its build with DISM.

See Full Details about a Windows 10 ISO file

I presumed when I saw 10.0.18362.418 that Microsoft must have started giving better information on what exact build the Iso would install...

I think they have updated it in advance of releasing 1909. But until they update the Products.xml that it downloads, it will still make 18362.356. There were a lot of disappointed people back when a 1903 MCT was leaked about a month ahead on the launch. Although the MCT version was 1903, up until the launch day it could only find the Products.xml for 1809 so that was the ISO it made.

sportsfan148 · 23 Oct 2019

Bree said:

There are two ways to check the build it will install before that, The one I used is to run the MCT as far as the licensing notice, then read the Products.xml found in C:\$Windows.~WS\Sources. Thre other is to run the MCT to make the USB or ISO, then check its build with DISM.

See Full Details about a Windows 10 ISO file

I think they have updated it in advance of releasing 1909. But until they update the Products.xml that it downloads, it will still make 18362.356. There were a lot of disappointed people back when a 1903 MCT was leaked about a month ahead on the launch. Although the MCT version was 1903, up until the launch day it could only find the Products.xml for 1809 so that was the ISO it made.

Hi again Bree, I also noticed that under the properties for the latest MCT the Digital Signature (which for 1903 has always previously been March 29 2019) has now been updated to 6 October 2019 along with them also changing the file properties to 10.0.18362.418 which coincidentally coincided approximately with the date that the KB4517389 cumulative update which took the build up to 10.0.18362.418 was released. Its weird if they didn't also update the Products.xml that you described at the same time. Like you said, if they didn't that would mean that the Iso that this latest version of the Media Creation Tool creates would still be 10.0.18362.356!

Ive just read this..

fridaysource.com/2019/10/17/windows-10-version-1903-build-18362-418-aio-dual-boot-20in1-oem-esd-october-8-2019/

According to this link the latest Media Creation Tool does include Build 10.0.18362.418 now. Im not sure if its correct or not though but it would explain what I was seeing when I downloaded the Media Creation Tool from the Microsoft website yesterday

- - - Updated - - -

Brink said:

Download Windows 10 ISO File

Create Bootable USB Flash Drive to Install Windows 10

Hi Shawn, Ive been discussing with Bree whether the latest MCT has now been updated or not by Microsoft and whether or not it is now creating the Iso with build 18362.418. Your links say that build 18362.356 will be created.
I came across the following link

fridaysource.com/2019/10/17/windows-10-version-1903-build-18362-418-aio-dual-boot-20in1-oem-esd-october-8-2019/

I'm not sure how reliable this link is but it seems to suggest the Iso was updated a couple of weeks ago to include build 18362.418. That would explain what I was seeing under the latest MCT properties yesterday where it showed that the date of the Digital Signature (which for 1903 has always previously been March 29 2019) has now been updated to 6 October 2019 which coincidentally coincided approximately with the date that the KB4517389 cumulative update which took the build up to 10.0.18362.418 was released.

Brink · 23 Oct 2019

sportsfan148 said:

Hi again Bree, I also noticed that under the properties for the latest MCT the Digital Signature (which for 1903 has always previously been March 29 2019) has now been updated to 6 October 2019 along with them also changing the file properties to 10.0.18362.418 which coincidentally coincided approximately with the date that the KB4517389 cumulative update which took the build up to 10.0.18362.418 was released. Its weird if they didn't also update the Products.xml that you described at the same time. Like you said, if they didn't that would mean that the Iso that this latest version of the Media Creation Tool creates would still be 10.0.18362.356!

Ive just read this..

fridaysource.com/2019/10/17/windows-10-version-1903-build-18362-418-aio-dual-boot-20in1-oem-esd-october-8-2019/

According to this link the latest Media Creation Tool does include Build 10.0.18362.418 now. Im not sure if its correct or not though but it would explain what I was seeing when I downloaded the Media Creation Tool from the Microsoft website yesterday

- - - Updated - - -

Hi Shawn, Ive been discussing with Bree whether the latest MCT has now been updated or not by Microsoft and whether or not it is now creating the Iso with build 18362.418. Your links say that build 18362.356 will be created.
I came across the following link

fridaysource.com/2019/10/17/windows-10-version-1903-build-18362-418-aio-dual-boot-20in1-oem-esd-october-8-2019/

I'm not sure how reliable this link is but it seems to suggest the Iso was updated a couple of weeks ago to include build 18362.418. That would explain what I was seeing under the latest MCT properties yesterday where it showed that the date of the Digital Signature (which for 1903 has always previously been March 29 2019) has now been updated to 6 October 2019 which coincidentally coincided approximately with the date that the KB4517389 cumulative update which took the build up to 10.0.18362.418 was released.

I tested last night, and the ISO is still for build 18362.356.

Bree · 23 Oct 2019

sportsfan148 said:

... Its weird if they didn't also update the Products.xml that you described at the same time....

No doubt they already have a 1909 Products.xml for internal use, but releasing it on the update servers would only be done when 1909 goes public.

Such a Products.xml, if leaked, can be used with the current MCT with a /SelfHost option, but the last time one was leaked was for 1809.