Now’s a good time to squirrel away a copy of Win10 version 1909

Topic

New Reply

With the next version of Win10 (version 2004) now available for download on the Microsoft Developer Network, and due to appear everywhere shortly, rig
[See the full post at: Now’s a good time to squirrel away a copy of Win10 version 1909]

11 users thanked author for this post.

WildChild, Elly, J C, Vincenzo, Microfix, LHiggins, CAS, RiverRat42, abbodi86, geekdom

Reply | Quote

Replies

[EP]

the problem in getting the 1909 ISO from MS is that it’s the 1909 V1 version with build 18363.418 which has the “missing” feature update deferral bug (the days to defer feature updates will no longer appear when set to any value other than 0) and the inability to keep existing files & apps when doing an in-place upgrade or repair install of 1909 – these issues were fixed in 18363.446 & higher cumulative updates for 1909.

sometimes I wished that MS released the “refreshed” or revised 1909 ISOs (aka V2 or better) to the general public that would have these problems fixed like with MSDN users are getting before releasing the next big feature update like 2004

• This reply was modified 3 years, 4 months ago by EP.

Reply | Quote

Won’t using the MCT make a later ISO than 18363.418 instead of downloading the ISO directly from MS?

Reply | Quote

If you download the ISO right now, using the Creation Tool, you get build 18363.592. (See the article.)

2 users thanked author for this post.

Elly, Microfix

Reply | Quote

I just made a USB of 1909 from the MCT.

Is there a way to easily look into the USB contents to verify what version it is?

The MCT 1909.exe file MCT just downloaded shows Properties 10.0.18362.418 (same file as I downloaded 11/14/2019 and yes – 18362 (v1903?).

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

1903 and 1909 have the same content. Just make the ISO. It will be build 18363.592 like Woody said.

1 user thanked author for this post.

Microfix

Reply | Quote

PKCano said:
1903 and 1909 have the same content. Just make the ISO. It will be build 18363.592 like Woody said.

Did you mean that Win 10 release 1903 v18362.592 (10 Jan 2020) is identical to Win 10 release 1909 v18363.592 (14 Jan 2020) ?

If so, why the different versioning, & why are different releases & versions being offered to different users via different channels ?

If not, how does one obtain the ISO for Win 10 release 1909 v18363.592 (14 Jan 2020) mentioned in Woody’s ComputerWorld article ?

As verified multiple times by running DISM & also manually checking the internal files inside the generated ISOs, both are definitely Win 10 release 1903 v18362 (albeit of different build nos.), namely:

• v18362.592 (10 Jan 2020 internal files’ timestamp) — via latest Media Creation Tool
• v18362.418 (07 Oct 2019 internal files’ timestamp) — via latest website download using spoofed user-agent string, or via Heidoc’s ISO download tool (which I suppose is getting ISO download links by spoofing a browser)

Reply | Quote

[PKCano]

The base for 1903 and 1909 are the same.
They have the same content.
The difference is only the packet for 1909 that turns on the extra Features for 1909.

If the MCT said 1909 in the file name, that is the version it will install.
If you downloaded and used the MCT to make the ISO before Jan.2020, you will have have .418 because .592 had not been released.
If you downloaded and used the MCT recently, you will get .592

• This reply was modified 3 years, 4 months ago by PKCano.

Reply | Quote

PKCano said:
The difference is only the packet for 1909 that turns on the extra Features for 1909.

So the Win 10 r1903 v18362.592 ISO (May 2019 release, 10 Jan 2020 build) will somehow install Win 10 r1909 v18363.592 (Nov 2019 release, 14 Jan 2020 build), but without r1909 Features ?

Can the user manually “turn on” the said r1909 Features, & does this step require Windows Update during/after OS installation ?

Background: I’m a new Win 10 user. My Win 7 laptop died in Apr 2020, & the new OEM laptop comes pre-installed with Win 10 r1909 + Windows Updates already current to Mar 2020. Using an analogy, a Win 7 RTP ISO will not install Win 7 SP1 with SP1 features “turned off”/ silenced.

Do Win 10 ISOs of different releases work “cumulatively”, & require user intervention after installation to “turn on” (further download ?) the missing features ?

In any case, it doesn’t answer my query: Why are some users able to download Win 10 r1909 (Nov 2019) v18363.xxx ISO, while other users can only download Win 10 r1903 (May 2019) v18362.xxx ISO instead — as of May 2020 ?

The latter is not an isolated issue, as flagged by several users in this discussion thread alone. Is Microsoft using some backend-detection hardcoding to serve the Win 10 r1909 ISO to Win 10 Pro users, while Win 10 Home users receive the Win 10 r1903 ISO — even when users access the download via the same channels (be it the Media Creation Tool, MS website download, or Heidoc ISO download tool) within the same time period ?

 

PKCano said:
If the MCT said 1909 in the file name, that is the version it will install.

Talking about the Media Creation Tool’s filename … I’d been wondering about the glaring contradiction between MCT1909’s filename & its file version. For reference …

MediaCreationTool1909.exe
File Properties: v10.0.18362.418
MS File Server Timestamp: 06 Oct 2019
Internal Files Timestamp: 05 Oct 2019

Based on the above MCT’s actual file version, maybe this is the reason it will only download the Win 10 r1903 v18362.xxx (latest build = 592) ISO — regardless of what its filename implies. Unless one is a Win 10 Pro user perhaps ?

MediaCreationTool1903.exe
File Properties: v10.0.18362.1
MS File Server Timestamp: 22 Mar 2019
Internal Files Timestamp: 18 Mar 2019

Likewise, based on its file version (which happens to tally with its filename), I suppose this MCT will also download the Win 10 r1903 v18362.xxx (latest build = 592) ISO.

And both Win 10 r1903 ISO files will apparently install as Win 10 r1909, but without r1909 Features ?

Reply | Quote

The CONTENT is the same for 1903 and 1909.
They both get the same CUs.
They both get the same SSUs.
The difference is that the extra Features are turned ON in 1909 but not in 1903.
If you download now and execute the MCT 1909.exe it will install with the 1909 Features turned on and you should get .592 (which will be/is 18363)

Reply | Quote

PKCano said:
If you download now and execute the MCT 1909.exe it will install with the 1909 Features turned on and you should get .592 (which will be/is 18363)

Thanks for the info. Running MCT1909.exe definitely gets me the Win 10 r1903 v1862.592 ISO (& nothing else) — & based on what you say, this will apparently transform into r1909 v1863 upon installation.

But Microsoft seems to be saying something else — ie. it’s not going to morph into r1909 w/o further user action (ie. running Windows Update to get another “package”), because the r1909 new features are not built into r1903 itself.

Summarized outline based on what Microsoft appears to be saying … (references quoted at bottom):

1. Even though Win 10 r1909 (19H2) & r1903 share the same core system files, the newer r1909 (19H2) new features are “dormant/disabled” (MS’s own words) in r1903.

r1903 only comes with the r1909 “master switch” (again MS’s description) aka shell, but does not actually contain the sparkly new light bulb (= r1909 features).

2. To enable (MS: “activate”) the “dormant/disabled” r1909 shell, one needs to install an additional so-called “enablement package” (yes, MS’s words) by carrying out one of the following:-

• run Windows Update to get something called “Feature Update to Windows 10, version 1909”; or
• get KB 4517245 from WSUS — not applicable to Win 10 Home users

I suppose the above is somewhat analogous to Win 10 users having to download MS .NET Framework 3.5.1 via Windows Update (or if not successful, using DISM to install it from the Win 10 ISO), & then manually switching on .NET 3.5.1 in Features.

3. The Win 10 r1909 “enablement package” is not offered as a standalone download via the MS Update Catalog. (Why ? Sounds like a huge X.x gigabyte download ?)

4. Win 10 r1909 v1863 (of whatever XXX build no.) is supposedly available via the MS Software Download Center (via Media Creation Tool) since 12 Nov 2019.

But from my & several users’ recent experiences (May 2020, including my recent attempts a couple of hours ago), using MCT very definitely fetches the r1903 v1862.592 (10 Jan 2020) ISO — instead of r1909 v1863.592 (14 Jan 2020) that some other users seem able to get.

If this is not an oversight by Microsoft, perhaps the workflow is what I’d guessed: Win 10 Home users get r1903, while Win 10 Biz/Enterprise/(?)Pro users get r1909 via the same MCT release channel — as Microsoft seems to also suggest (see “What’s New for IT Pros” quoted at the very bottom).

Therefore, for Win 10 Home users, this means being stuck at Pt. 1 — ie. r1909’s new features come as a “dormant/disabled” shell after installing Win 10 from the r1903 v1862.592 ISO obtained via MCT (the only method so far to get .592). Which in turn requires performing Pt. 2 — ie. running Windows Update to download, install & “activate” the r1909 shell.

 

Relevant Microsoft references are excerpted as follows …

Windows 10, version 1909 Delivery Options (12 Nov 2019)
What’s New about Delivering Windows 10, version 1909
The new features in Windows 10, version 1909 were included in the latest monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are currently in a dormant/disabled state.

These new features will remain dormant until they are turned on via an “enablement package,” a small, quick-to-install “master switch” that simply activates the Windows 10, version 1909 features.

How to Get Windows 10, version 1909

For Devices Managed by Windows Update
If you receive updates directly from Windows Update, the Windows 10, version 1909 update will be presented just like any feature update.

For Self-Managed Devices
We are making the Windows 10, version 1909 enablement package available on WSUS as KB4517245, which can be deployed on existing deployments of Windows 10, version 1903.

 

KB4517245: Feature Update via Windows 10, version 1909 Enablement Package (13 Nov 2019)
Microsoft Update Catalog
No. This update is only available through the other release channels.

 

What’s New for IT Pros in Windows 10, version 1909 (12 Nov 2019)
Windows 10, version 1909 is now available through Windows Server Update Services (WSUS) and Windows Update for Business, and can be downloaded from Visual Studio Subscriptions, the Software Download Center (via the Media Creation Tool), and the Volume Licensing Service Center.

Reply | Quote

[PKCano]

Disregard everything I’ve said.
Please download the MRT 1909.exe now
Create an ISO from it
Install the OS from the ISO
Report back whether you get 1903 or 1909.
You may be surprised.

EDIT:
A word of warning: the MCT 1909.exe that you downloaded now (May 18) will produce a 1909 ISO now.
So created, the ISO will install 1909 whenever you use it for an install later.
BUT
After v2004 is released, the ISO that is created by the
use of MCT 1909.exe then may produce a v2004 ISO. So if you use it to create an ISO after 2004 release, check the version before you use the ISO to install.

• This reply was modified 3 years, 4 months ago by PKCano.

1 user thanked author for this post.

Elly

Reply | Quote

Unfortunately, it’s complicated.

From an elevated command prompt, run

dism /Get-WimInfo /WimFile:x:\sources\install.esd /index:1

where “x” is the drive letter for your USB drive.

2 users thanked author for this post.

KP

Reply | Quote

Here tis – looks to be ServicePack Build: 592

Why does it show Window 10 Home when I have Pro?

 

 

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I am playing around, try index 6:

dism /Get-WimInfo /WimFile:x:\sources\install.esd /index:6

Name: Windows 10 Pro

I am guessing all versions are there, up to index 11. I get an error on index 12.

Reply | Quote

I did not use the MCT but changed the browser UserAgent to download an ISO. When I mounted the ISO, I had to change the command:

dism /Get-WimInfo /WimFile:x:\sources\install.wim /index:1

I got a different ServicePack Level: 418

That PC needed the x86 architecture.

 

Reply | Quote

[WildChild]

Woody,  I downloaded both the ISO and the Flash drive version of Win1909 on 5/18/20 on a Win10 PC running 1903.  The MCT 1909.exe file downloaded shows Properties 10.0.18362.418.  Please note 362 not 363 like some have indicated.

1. I have not checked the ISO or Flash drive created to see what version they are and I am not really sure how to check them without triggering installation of 1909.
2. I have a question concerning the use of the USB Flash drive I am hoping someone can answer.  I have 1903 and 1909 on seperate USB Flash drives and I know that you much use a clean Flash drive to keep the contents from being over written.  Can you copy the contents of the flash drive into a folder, say 1903 for 1903 files and 1909 for 1909 files and then move the contents from the version you want (1903 or 1909) to the root of the drive for installation of the OS?
3. I am new to the Win10 forced updates since 11/2019 only having started with version 1903 on a clean install.  My question here is how long do you keep versions of an installer before dumping it and could you possibly install Version 1903 say in a year or two from now?

Any help would be greatly appreciated in understanding this convoluted mess that MSFT has imposed on us.

Oh, BTW Woody, Wow, I thought I was asking a simple question 🙂   Thanks for pointing me to this thread.

• This reply was modified 3 years, 4 months ago by WildChild.

Reply | Quote

Please read through my posts above for the explanation.
Although there is one anonymous poster who does not believe me, the ISO created from the recent MCT 1909.exe WILL give you v1909.

Reply | Quote

I did read your posts and I am not doubting what you said.  I wanted to provide the info as well as get help on dealing with Win10 going forward.  Could it be that the MCT version makes no difference in getting the latest version in ISO or Flash drive format?  That may be what is confusing people or have I totally missed the boat on this.

Reply | Quote

Disregard everything I’ve said.
Just try the ISO made from MCT 1909.exe
You will get v1909.

Reply | Quote

[WildChild]

I am assuming that applies to allowing the MCT to create the flash drive for 1909 also.

Do you know if you can put multiple Installs on a flash drive by copying the created contents on the flash drive to a folder and then moving the contents back to the root of the flash drive for the install you want to use?  I am trying to figure a way to keep from using a flash drive for each version 1903,1909 & 2004.  This would be similar to Win7 Backups.  My thought is to have a folder 1903 with contents copied from MCT created flash drive and the same for 1909.  Then you copy the contents of the folder to the root of the flash drive for install of the version you want.  This would effectively allow about 6 versions on a single flash drive. I would leave the latest version being used in the root so you do not need a 2nd PC to be able to use the flash drive although that is not a problem for me.  Any thoughts on this would be appreciated.  In case I have not mentioned it, thanks for your posts as I find them enlightening.

• This reply was modified 3 years, 4 months ago by WildChild.

Reply | Quote

A word of warning: the MCT 1909.exe that you downloaded now (May 18) will produce a 1909 ISO now.
So created, the ISO will install 1909 whenever you use it for an install later.
BUT
After v2004 is released, the ISO that is created by the
use of MCT 1909.exe then may produce a v2004 ISO. So if you use it to create an ISO after 2004 release, check the version before you use the ISO to install.

1 user thanked author for this post.

WildChild

Reply | Quote

Clear as mud. If I download a 1909 iso today and squirrel it away, and the next disasterous release 2004?? goes awry and I use the 1909 iso I downloaded today will miraculously produce another 2004? Then what is the point of squirreling away anything if it’s not going to be what you want ANYWAY. That would just be…well DUMB.

So I will ignore all thats been said with respect to this issue

Reply | Quote

[PKCano]

There is a DIFFERENCE between the ISO and the MCT – they are NOT the same.

The IOS you save today will produce v1909. It is the image of v1909.

It’s the MCT that won’t produce a v1909 ISO after the 2004 ISO is released. The MCT is just the Media creation tool/program to download and create an ISO. It is NOT the ISO.

• This reply was modified 3 years, 4 months ago by PKCano.

2 users thanked author for this post.

gjacwel, Elly

Reply | Quote

WildChild wrote:

Do you know if you can put multiple Installs on a flash drive by copying the created contents on the flash drive to a folder and then moving the contents back to the root of the flash drive for the install you want to use? I am trying to figure a way to keep from using a flash drive for each version 1903,1909 & 2004.

The easy way is to download the installers as iso files, not directly to a USB stick. When you use the MCT to download the Win10 installer, it offers you the choice to save to a USB stick or to a iso file. Choose iso. Rename each iso file to include the version number so you can keep them straight.

You can store all your isos to an external HDD for safekeeping. When you want install one of them, use Rufus to make a bootable USB stick from the iso file. After you’re done, you can reformat the USB stick and reuse it for something else.

Another method is to prep a USB stick with a multiboot installer, such as Yumi or Ventoy, described here. Once prepped, you can copy multiple iso files to the USB stick. When you boot from the USB stick, it will give you menu from which you can select which iso to install.

Disclaimer: Ventoy supposedly can multi-boot in either MBR or UEFI mode, but I haven’t figured out how to get it to boot in UEFI yet, so if you need UEFI the Rufus single-boot method may be more reliable.

3 users thanked author for this post.

Elly, WildChild

Reply | Quote

An alternate way of getting ISOs — not just 1909, but all versions of Windows 10, 8.1 and even 7 is using the Microsoft Windows and Office ISO Download tool from heidoc.net. https://heidoc.net/joomla/technology-science/microsoft/67-microsoft-windows-and-office-iso-download-tool . Text at this link notes:

This tool allows an easy and comfortable way to download genuine Windows 7, Windows 8.1 and Windows 10 disk images (ISO) directly from Microsoft’s servers, as well as Office 2010, Office 2013, Office 2016, Office 2019, Expression Studio and Office for Mac.

As noted, this tool downloads directly from Microsoft, and all supported versions, including Home, Pro, and Education editions,  32 and 64, N and K versions, and all available languages.  The tool also offers downloads for Office (including Mac versions), as well as Developer and Insider Preview releases, and Dell OEM images.

Going this route, you can get the version you want, when you want it, and from any computer that runs Windows (and any version) and you don’t have to be subject to whatever version that Microsoft is currently making available through normal release channels.

7 users thanked author for this post.

Fletch1441, gjacwel, Elly, petesmst, zat_so, RiverRat42, woody

Reply | Quote

Heidoc is a great resource, run by a guy who really knows his stuff. It pulls the ISOs from Microsoft’s site.

Still, the Creation Tool is free, easy, and 100% guaranteed legitimate, with the Microsoft imprimatur.

1 user thanked author for this post.

Elly

Reply | Quote

[KP]

I tried heidoc.net on a PC that was not mine; this was after Windows 7 EoL  (so after Jan. 2020) and hoping to get Windows 7 SP1 ISO, it was not available.

{An Aside: I could only get this to work on the one PC, which I don’t currently have access to. Note you need at a minimum, admin access.}

• This reply was modified 3 years, 4 months ago by KP.

Reply | Quote

@ KP:

On page 5 of the Heidoc.net website, on the FAQ page, is stated:

Q: I’m getting the message “This file is currently unavailable. Please check again later.”

A: The file can’t currently be made available. The number of different downloads for Windows 7 and Office 2010 that we can offer at the same time is very limited. The files to be unlocked next are determined by community demand. Currently available downloads are highlighted in green. You can wait until your file becomes available again, or alternatively download the Windows 7 August 2018 update, or one of the DELL OEM images.

I read the following someplace else, either on the website, or in the downloader app when it fails to find a desired ISO: The number of files available for download is re-set at the beginning of the month, have to fast and/or lucky to get a copy.

3 users thanked author for this post.

gjacwel, Elly, KP

Reply | Quote

Tex265 wrote:

I just made a USB of 1909 from the MCT.

Is there a way to easily look into the USB contents to verify what version it is?

The MCT 1909.exe file MCT just downloaded shows Properties 10.0.18362.418 (same file as I downloaded 11/14/2019 and yes – 18362 (v1903?).

https://www.winhelponline.com/blog/iso-find-windows-build-version-edition-using-dism/

Download 1909 on Apr. 27 and got build 18363.592.

Reply | Quote

Thanks, see my reply post above.

Looks like the actual version inside the USB is 18362.592

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Tex265 wrote:

Looks like the actual version inside the USB is 18362.592

That’s correct, it’s not 18363.592 as reported earlier. 18362.592 is what it show’s from the ESD command.

Tex265 wrote:

Why does it show Window 10 Home when I have Pro?

It always shows Home.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Once again, the “administrator” trap.   Just clicking on the media creation tool and then UAC-ing up to admin isn’t enough: when you get all the way through you’re told that you have to be *running* in an adminstrator account to proceed.   Is there a way around this?

 

Reply | Quote

Winaero Tweaker has a setting that disables UAC mode …quite a handy dandy tool for disabling many W10 settings in fact team …

If there is magic on this earth ... it's in the water.

Reply | Quote

How-To Geek published an article detailing steps on how to get the Windows 10 ISO image without using the Media Creation Tool even if you’re on Windows. https://www.howtogeek.com/427223/how-to-download-a-windows-10-iso-without-the-media-creation-tool/

The trick is as follows:

1. Visit the Windows 10 download page
2. Open up Developer Tools (in Chrome, it’s Ctrl-Shift-I)
3. Click on the menu icon, go to “More tools”, and then “Network conditions”
4. Under the “User Agent” option, uncheck “Select automatically”
5. Click on the drop-down menu to select a different user agent. You can select anything that isn’t Windows.
6. Keep the Developer Tools panel open. Refresh the page (Ctrl-R)

You can then download the ISO image directly without all the hassle of the Media Creation Tool. I’ve done this myself to get an ISO image for VirtualBox and I still have it tucked away.

Reply | Quote

I just did that and got build 418 instead of 592.  See first entry at top… someone else did too!

Reply | Quote

If you use a different user agent, or you use a different OS, you are downloading the ISO, which is 418, directly from Microsoft.

If you use the Media Creation Tool, the ISO is created on your PC and it is 592.

The reason 592 is preferable, is because 418 has an error in Windows Update that causes the disappearance of some of the Windows Update GUI settings. That is corrected in 592.

Reply | Quote

On Firefox, you don’t need to be in Developer Tools. Have a look at the link titled “our guide to spoof your user agent without installing an extension” in the HowToGeek.com article.

Using the User Agent method, I did not get as current an ISO version (ServicePack Level: 418) as MCT. I would download the Monthly Cumulative Rollup before hand separately and apply them offline to avoid the problems in ServicePack Level: 418 .

Reply | Quote

@Tex265 “Why does it show Window 10 Home when I have Pro?”

It shows HOME when running the command with /index:1
Change the index to 2, 3…

Reply | Quote

anonymous wrote:

How-To Geek published an article detailing steps on how to get the Windows 10 ISO image without using the Media Creation Tool even if you’re on Windows.

There in no need for a trick. Just use HiDoc.Net app.

Reply | Quote

Clarification: the Media Creation Tool is offered on Windows 7 as well, and likely all versions of Windows. Hence you can use the instructions in the first section, despite it saying it’s only for Win10.

My Win7 computer has a bigger hard drive, and is a better place to store files I might need for my Win10 computer, IMHO. I had expected to not have to use the tool, but wound up having to. along with Microsoft slowly “getting things ready” that were entirely pointless.

Reply | Quote

Only been on Win 10 a few month, but i assume the feature update wont be forced on people like the security updates, and until 1909 isnt supported its an optional update?

Reply | Quote

2004 should stay in the optional “download and install now” section on Home (or however long you have Feature Updates deferred on Pro) if you are currently on 1909.

Reply | Quote

Feature updates are delayed 90 days on my PCs.
I let the curious users expose the flaws.

Of course I do full drive backups monthly.

Byte me!

Reply | Quote

woody wrote:

If you download the ISO right now, using the Creation Tool, you get build 18363.592. (See the article.)

Hi Woody,

just to let you know, that  (this holds for int. English – haven’t checked others)

I have downloaded using the media creation tool and got 18362.592

I used a fake browser header and got 18362.418

I used the heidoc downloader and got 18362.418

All checked with DISM.  Be warned!!

1 user thanked author for this post.

SkipH

Reply | Quote

See #2262548 above.

Reply | Quote

PKCano wrote:

See #2262548 above.

Yes, but that does not explain why Microsoft provides 418 instead of 592 in its ISO downloads.

You are restating as a fact that which I have determined empirically.  The question is, did you know this in advance, and if so how?   If there is some MS information page which explains the current state of affairs, it would be useful to have a link.

Otherwise, are you implying that MS only freeze ONE build Version/ServicePack Build for a downloadable ISO?  If so, it would be nice to see that stated categorically somewhere, because creating the media on the flay is a bit of a pain…

Thanks!

 

Reply | Quote

The first ISO they create stays on the ISO download site until/unless they create a later ISO.
If the MCT is used, the ISO is created on the computer and (given it is a sufficiently later date than the download site ISO), after a certain point it is a later Build.
This has been true from the git-go as far as I know. Later in a version life-cycle, the MCT will give you a later Build.

Reply | Quote

Good to know, thanks.  But how do we know when they do create a later ISO?  I suppose the MCT is the only answer, sadly.

 

Cheers!

Reply | Quote

[Elly]

I have 18362.418

 

• This reply was modified 3 years, 4 months ago by Elly.

Reply | Quote

For information on the Builds in the ISOs, see #2262548.

2 users thanked author for this post.

Elly, Linda2019

Reply | Quote

Has Woody ever created step by step instructions on how to use a mounted ISO file to recover your operating system?  It would be great to have those instructions.

Reply | Quote

If you have any ISO on your hard disk you can double click on it and Windows will mount it as a new disk. You can then run any program on it as you would any disk.

For an in place upgrade of Windows you run the setup.exe from newly mounted disk.

cheers, Paul

Reply | Quote

OK I followed the instructions step by step perfectly and selected a USB hard disk that had lots of space plus backups to create the backup media, thinking I would just download an ISO.  The media creation tool completely erased everything else from the drive except the windows installation package.  Should I have been expecting just an ISO file download?  Maybe I clicked wrong somewhere.   If I was right, Woody you need to warn folks to use a new USB drive or it will erase all of the existing files !!

Reply | Quote

This is the expected behaviour. I would expect a warning from the MCT about wiping the disk?
If there is an option to save the Windows update to disk then you can use the ISO from the disk.

cheers, Paul

Reply | Quote

Paul T wrote:

If you have any ISO on your hard disk you can double click on it and Windows will mount it as a new disk. You can then run any program on it as you would any disk.

And not to forget to Eject the new drive 🙂

Reply | Quote

bwims wrote:

Good to know, thanks.  But how do we know when they do create a later ISO?  I suppose the MCT is the only answer, sadly.

 

Cheers!

MCT version/build is NOT the Windows 10 ISO build.
Downloading the ISO will get you 18363.592 and maybe now a newer build.

Reply | Quote

Thanks for the reminder Woody/ PKCano, MCT tool done the business for the collection. Which in-turn reminded me, I need more offline storage..tsk

No problem can be solved from the same level of consciousness that created IT- AE

Reply | Quote

woody said:
If you download the ISO right now, using the Creation Tool, you get build 18363.592.

As of 16/17 May 2020, the latest stable Windows 10 v1909 (Nov 2019 update) appears to be build 18362.592 — not 18363.592. Is the latter a typo ?

Properties of Win 10 x64 Home ISO file generated by Media Creation Tool v10.0.183362.418 (06 Oct 2019) just downloaded from: https://www.microsoft.com/en-us/software-download/windows10

• ISO Filesize: 3.99 GB (10 Jan 2020)
• ISO MD5 Hash: 372885231BC074A152315D6583112604
• Contains: \sources\install.esd

> dism /Get-WimInfo /WimFile:”X:sources\install.esd” /index:1

Size : 14,508,975,561 bytes
Version : 10.0.18362
ServicePack Build : 592
Directories : 21574
Files : 93180
Created : 10/1/2020 – 5:34:16 AM

The Media Creation Tool:

1. Fetched a newer & significantly smaller ISO file (by 1+ GB) than the ISO file downloaded from the re-directed URL using a non-Windows browser user-agent string — as shown at the bottom.
2. Wrote several log & telemetry-related (?) files (totalling 360 KB) at the root of the system drive in the below newly-spawned folders, even though I saved the ISO file to a subfolder at a non-system drive:

• C:\\$WINDOWS.~BT\
• C:\$Windows.~WS\    [hidden folder]
• C:\ESD\

 

Properties of Win 10 x64 Home ISO file just downloaded from: https://www.microsoft.com/en-us/software-download/windows10ISO

• ISO Filesize: 5.05 GB (07 Oct 2019)
• ISO MD5 Hash: 86C16116EBACF9B29E4766DD479B5A79
• Contains: \sources\install.wim

> dism /Get-WimInfo /WimFile:”X:sources\\install.wim” /index:1

Size : 14,513,453,277 bytes
Version : 10.0.18362
ServicePack Build : 418
Directories : 21327
Files : 92708
Created : 7/10/2019 – 11:07:10 AM

Reply | Quote

It seems like most here are downloading this as .iso file. I have already created a bootable installation drive of 1909 using the MS tool. Is there an advantage to having the .iso file?

Thanks

Reply | Quote

I did get AN iso file via msft tool (windows.iso?) a few weeks back when first suggested but I would think after dl and install, then image the install, what is the iso for??

Reply | Quote

The ISO is in case you need to reinstall from scratch – maybe your computer dies and you get a second hand one…

cheers, Paul

Reply | Quote

anonymous wrote:

appears to be build 18362.592 — not 18363.592. Is the latter a typo ?

18362 is W10 1903 while 18363 is W10 1909.
The .nnn build is the same for both.

You should run through index=1 – n to see all versions.

Reply | Quote

Alex5723 said:

18362 is W10 1903 while 18363 is W10 1909.
The .nnn build is the same for both.
You should run through index=1 – n to see all versions.

Thanks, running the DISM command for index (N) = 1 to 7 does show the available editions (such as: Home, Pro, Education), while N = 8 & higher display “Error: 87”.

That wasn’t my query though, which is about the latest stable release version available to end-users. Regardless of which method I’d tried (Media Creation Tool vs. downloading via browser), the generated ISO files are both for the older (version) v18362 (Win 10 1903 – May 2019 Update).

The only difference is that the Media Creation Tool fetches v18362 build 592 (10 Jan 2020), while the browser method fetches the older v18362 build 418 (07 Oct 2019).

So how one get the newer stable v18363 (Win 10 1909 – Nov 2019) — preferably build 592 (aka “Jan. 14 flavor, known as build 18363.592“), which apparently isn’t afflicted with the “disappearing GUI settings” bug affecting the build 418 ?

Reply | Quote

[Pierre77]

Finally managed to download – however just a warning. Had a power failure in the middle of the download. After power was restored and brought system(s) and modem back up the trouble started. Noticed that download indicator was running without intervention but unable to interrupt. Powered everything down and up – same result. Finally re-activated download exe and that stopped download. Indicator had stopped but had incremented to 10gig+. No sign of where downloaded data was located. Scratching my head – only conclusion download had grabbed PC data ?……??????? Comment please.

• This reply was modified 3 years, 4 months ago by Pierre77. Reason: TYPOS

Reply | Quote

Vincenzo wrote:

Is there an advantage to having the .iso file?

For the day you “misplace” your bootable copy and need another one. But you can create it from your bootable copy with ISO recorder, or similar.

cheers, Paul

Reply | Quote

anonymous wrote:

So how one get the newer stable v18363 (Win 10 1909 – Nov 2019)

Using HiDoc.net you can get Nov. 2019 version

Reply | Quote

 Alex5723 said:
Using HiDoc.net you can get Nov. 2019 version

I can’t view the attached file(s), but I suppose you mean heidoc.net.

Unfortunately, as user bwims pointed out earlier (quoted below), using Heidoc’s ISO Download Tool fetches the much outdated Win 10 v18362.418 (May 2019 release) — not the supposedly latest-available stable Nov 2019 release v18363.592 (14 Jan 2020) or even v18363.418 (08/21 Oct  2019).

bwims said:
I have downloaded using the media creation tool and got 18362.592
I used a fake browser header and got 18362.418
I used the heidoc downloader and got 18362.418

Reply | Quote

anonymous wrote:

Unfortunately, as user bwims pointed out earlier (quoted below), using Heidoc’s ISO Download Tool fetches the much outdated Win 10 v18362.418 (May 2019 release) — not the supposedly latest-available stable Nov 2019 release v18363.592 (14 Jan 2020) or even v18363.418 (08/21 Oct  2019).

Wrong. See the jpg posted above.

Reply | Quote

Alex5723 said:
Wrong. See the jpg posted above.

Thanks for the JPG screenshot of Heidoc.net Windows ISO Downloader v8.24.0.132.

Did you actually try downloading the ISO, as well as verifying its file release-version-build nos. (via the DISM command) & checking the internal files timestamp yourself ?

Using the latest Heidoc tool v8.36.0142 (06 May 2020), under the ‘Select Edition’ dropdown menu, choosing the latest ‘Window 10 November 2019 Update – November 2019’ > ‘Windows 10 Home/Pro’ option for 64-bit (screenshots) results in a downloaded ISO for Win 10 r1903 (May 2019 Update) v1862 build 418 (06 Oct 2019) instead.

As previously mentioned by me & other users like bwims, the ISO file downloaded by getting the link from Heidoc’s tool is identical to the ISO (release-version-build no., filesize, hash, timestamp, contents) downloaded from Microsoft’s Win 10 ISO download webpage (screenshot — accessed using a non-Win OS user-agent string).  **

In other words, I’d basically wasted bandwidth downloading an identical (outdated) 5.05 GB file again. So how did you obtain the latest Win 10 r1909 (Nov 2019) v1863.592 (14 Jan 2020) ISO file-link via the Heidoc tool — if this is indeed what you downloaded ?

On the other hand, under the ‘Windows > Insider Preview’ section in the Heidoc tool, there is a v18363 (= r1909 Nov 2019 Update) of unknown build no. (older than 592 ?). But the only Home edition available is for Win 10 Home China Insider Preview edition (screenshot) — which is not relevant to users outside of China. Moreover, this sounds like some unstable alpha build from the Insider Ring.

 

** PS: In case it is not obvious enough, the Heidoc tool (which uses IE 8+ as the HTML rendering engine for its GUI) displays an identical interface as the aforementioned Microsoft’s Win 10 ISO download webpage.

Heidoc’s modus operandus is apparently spoofing the browser user-agent & IP address in order to pull the relevant ISO download links from MS’s file server. This explains why download links are sometimes not available via Heidoc’s tool (eg. when the same pool of spoofed browser user-agent strings & IP addresses has been used too many times within a short span of time.)

As such, there is no reason why the ISO file obtained via the 2 above channels would differ no matter how many attempts one makes, since Heidoc is fetching the same file from the same link from MS’s file server.

Reply | Quote

I’ve tried every method as you, and my every downloaded version of ISO was 18362, not 3. :/

Reply | Quote

I’ve just downloaded MediaCreationTool1909.exe and used it on my PC (Windows 7 Ultimate x64) to get Windows 10 x64 ISO (MCT’s default parameters).

I’ve got Windows.iso file, 4,289,134,592 bytes.

I’ve unpacked this ISO using WinRAR and used this command:

dism /Get-WimInfo /WimFile:D:\sources\boot.wim /index:1

I’ve got this info:

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Details for image : D:\sources\boot.wim

Index : 1
Name : Microsoft Windows PE (x64)
Description : Microsoft Windows PE (x64)
Size : 1,706,317,122 bytes
Architecture : x64
Hal : <undefined>
Version : 10.0.18362
ServicePack Build : 592
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 3999
Files : 16720
Created : 2019-03-19 – 06:10:55
Modified : 2020-05-19 – 07:52:37
Languages :
en-US (Default)

The operation completed successfully.

It’s 10.0.18362.592, not 10.0.18363.592 – what am I doing wrong?

Reply | Quote

Hi, can you tell me what the version number of the MediaCreationTool1909.exe file is when looking at the files properties?

Reply | Quote

It’s 10.0.18362.418.

Reply | Quote

Mine is exactly the same downloaded on a Win10 1903 x64 system.

Reply | Quote

I believe 10.0.18362.xxx is home, and 10.0.18363.xxx is pro.  When you use command dism /Get-WimInfo /WimFile:D:\sources\boot.wim /index:1 it shows a number that matches home.  But when you install from the media, you will sometimes get pro installed, if you are entitled to it.  If you do, then when you run winver command on your installed version it will show 10.0.18363.xxx .

Also take note of post #2263548 that saving the mediacreationtool for later I believe does not work, collect the ISO now not later.

Reply | Quote

anonymous wrote:

I believe 10.0.18362.xxx is home, and 10.0.18363.xxx is pro.

That is NOT correct.
Given the same version, the Build number is the same for both Home and Pro
i.e. Build 18363.836 will be the Build number for both Home and Pro v1909 with May CU installed.

Reply | Quote

anonymous wrote:

Details for image : D:\sources\boot.wim Index : 1 Name : Microsoft Windows PE (x64) Description : Microsoft Windows PE (x64)  – what am I doing wrong?

Try index:2, index:3 etc.

cheers, Paul

Reply | Quote

It seems that my downloaded Windows 10 ISO has only two indexes:

> dism /Get-WimInfo /WimFile:D:\sources\boot.wim

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Details for image : D:\sources\boot.wim

Index : 1
Name : Microsoft Windows PE (x64)
Description : Microsoft Windows PE (x64)
Size : 1,706,317,122 bytes

Index : 2
Name : Microsoft Windows Setup (x64)
Description : Microsoft Windows Setup (x64)
Size : 1,882,672,563 bytes

The operation completed successfully.

 

… and index:2 gives 10.0.18362.592 as well:

> dism /Get-WimInfo /WimFile:D:\!test\sources\boot.wim /index:2

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Details for image : D:\sources\boot.wim

Index : 2
Name : Microsoft Windows Setup (x64)
Description : Microsoft Windows Setup (x64)
Size : 1,882,672,563 bytes
Architecture : x64
Hal : <undefined>
Version : 10.0.18362
ServicePack Build : 592
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 4043
Files : 17254
Created : 2019-03-19 – 06:11:09
Modified : 2020-05-19 – 07:52:45
Languages :
en-US (Default)

The operation completed successfully.

Reply | Quote

anonymous wrote:

I believe 10.0.18362.xxx is home, and 10.0.18363.xxx is pro

No. 18362 is 1903, 18363 is 1909. xxx is the same for both.

Reply | Quote

anonymous wrote:

Mine is exactly the same downloaded on a Win10 1903 x64 system.

The MCT version is the same as the October 2019 build but doesn’t effect the ISO download build version.

Reply | Quote

Is there any known solution for people like me who are not able to download latest 18363.592?

I’m using the current version of MediaCreationTool1909.exe I’m still downloading 18362.592 every time.

What should be the size of 18363.592 ISO in bytes?

My 18362.592 ISO is smaller than directly (without MCT) downloaded 18362.418 ISO.

Reply | Quote

Lex wrote:

I’m using the current version of MediaCreationTool1909.exe I’m still downloading 18362.592 every time.

Save that ISO – back it up to an external HDD and mark it as v1909
OR
Burn the ISO to a bootable DVD/USB and mark it v1909

You will be surprised to find that it WILL install v1909 when you use it.
No matter what you may think now.

Reply | Quote

[Lex]

PKCano wrote:

Lex wrote:

I’m using the current version of MediaCreationTool1909.exe I’m still downloading 18362.592 every time.

Save that ISO – back it up to an external HDD and mark it as v1909
OR
Burn the ISO to a bootable DVD/USB and mark it v1909

You will be surprised to find that it WILL install v1909 when you use it.
No matter what you may think now.

I will save it. So you think my DISM’s reports are wrong?

Is there any other way to check the actual version of this ISO?

Is that OK that MTC’s ISO (592) is so much smaller than directly downloaded, older (418) version? (418 is bigger by 1.2 GB)

• This reply was modified 3 years, 4 months ago by Lex.

Reply | Quote

Lex wrote:
Is that OK that MTC’s ISO (592) is so much smaller than directly downloaded, older (418) version? (418 is bigger by 1.2 GB)

Any chance older (418) version is multi-arch (i.e., both x64 & x86) vs single arch for newer (592) version?

Reply | Quote

Multi-arch ISO files that include both 32-bit and 64-bit versions of Windows should have \x86\sources\ and \x64\sources\ paths – my directly downloaded ISO (version 418), has only \sources\ path.

Reply | Quote

There is a place to choose whether you want to make an ISO based on your machine’s specs, or for other machines. The ISO for your machine, will only have what is needed for your machine. If you choose for other machines, they included the different options.

I always choose for other machines, so I can use it on any hardware that may come my way (friends and family).

Non-techy Win 10 Pro and Linux Mint experimenter

Reply | Quote

Your DISM reports are not wrong.
I tried to explain it earlier in this thread.
But nobody seems to take my explanation.
However, I have an ISO that I made in March that says the same thing and it installs v1909 Build 592.

Reply | Quote

Is it installing 1909 w/o internet access??
I went thru this once and was thinking it just upgraded during the install.

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

I have a question about Woody’s instructions for squirreling away a clean copy of Win10 Version 1909.

I have chosen the “ISO file” option. I want to put it on a flash drive. [His instructions say that you can ignore the part about burning the ISO to a DVD later.]

I am now at the section that says “When you get to the point where you choose a place to put the file”. For me, is the “place” the flash drive, which is USB Drive (D:)??

Sorry if this sounds like a dumb question – this is the first time I’ve created installation media.

Another question: I have two laptops both with Version 1909, up-to-date through the April Patch Tuesday patches and the May MSRT and the May .Net Framework. [Holding off on 2020-05 CU KB4556799 and any associated SSU until MS-DEFCON=3]. So, I have Build 18363.778

Will this one iso file on one USB flash drive work for both laptops? Or do I need to create an iso file on two separate USB flash drives (one for each machine)?

Reply | Quote

WCHS wrote:

For me, is the “place” the flash drive, which is USB Drive (D:)??

Or do I save the iso file to the laptop and then move it/copy it to the flash drive?

Reply | Quote

Has v2004 been released yet??

Reply | Quote

Not yet. I think they said something about May28th.

Reply | Quote

@PKCano: Do you have any answer to where to save iso file? , same iso file for two different laptops?

Reply | Quote

The ISO file is used to create bootable install media the equivalent of the CD/DVD you used to get with a new PC. The ISO is a one-file solution for handling all the files and folders that make up the installer (wouldn’t you love to have to deal with hundreds of files instead of just the one! 🙂 So basically you can think of it as a container.

When you burn the ISO to a DVD or USB, it expands all the files/folders so they are accessible. You can also mount the ISO as a drive and do the same thing.

So you can save what you have downloaded in two ways.
You can COPY the ISO to an external drive or storage device to save it in the same way you copy any single file to a storage device to save it.
OR, you can burn it to a DVD/USB and it becomes an installer for Windows OS like any other program you install from media of some type.

Now, the ISO (or bootable media) can be used wherever it is appropriate to install the contents. It’s like having a DVD to install Office – you can use it anywhere you can install Office. But you have to have the license for each individual installation, and it only installs the program/version/Edition that was used to make it.

Reply | Quote

PKCano wrote:

So you can save what you have downloaded in two ways.

I haven’t downloaded anything yet.  I’m still not getting this.

I’ve got this screen:

So, I make the 2nd choice:  “ISO file”

And then I get this screen, which shows that I can save it to the USB Drive (D) flash drive.  Is this a download?  Or a copy?  Or a burn?

If I understand you, a copy means that I have to mount the iso file to get inside it?  and a burn means that the “insides” are visible without mounting? Or something different?

I am still trying to figure this out!!

 

 

 

 

Reply | Quote

If you are using the Media Creation Tool(?) then it creates the ISO wherever you want to save it. I usually save it to my desktop, then copy it to where I want to store it from there. Your second screenshot shows File Explorer and you can save it wherever you want.

It is also allowing you to name the file. I usually call it something like Win10 Pro v1909 x64 (or whatever you chose). If it asks, tell it “not for this PC” and it will create a generic installer that you can use anywhere.

Once you save the ISO to other storage, you can delete from whatever location you put it originally. It’s just a BIG file.

You can use the ISO later to create bootable install media.

Reply | Quote

If you need further information/instruction on what to do with the ISO, please create a separate Topic for you individual help.

1 user thanked author for this post.

Reply | Quote

See continuation as another topic

Reply | Quote

Just a quick question. Now that 2004 is out – is it too late to store away a copy of 1909? I had tried doing that earlier and ran into some internet issues, and now that things seem to be better, I was wondering if it was too late to do it.

Thanks!

Reply | Quote

It is too late to use the Media Creation Tool to create a v1909 ISO. The current MCT will give you a v2004 ISO.

However, you can download the ISO for Win10 v1909 from heidoc.net using their Microsoft Windows and Office ISO Download Tool.

1 user thanked author for this post.

LHiggins

Reply | Quote

Great – thanks so much! I’ll take a look at that. I thought it was too late, but figured I’d ask!

Thanks again!

Reply | Quote

I can confirm that your only option right now is version 2004 – even if you go to the site with a different operating system or non-Windows PC.

Drat.

Yep, as PKCano says, heidoc is the way to go…..

1 user thanked author for this post.

LHiggins

Reply | Quote

If you don’t care for the HieDoc app, Rufus has been updated to support the current release and several back releases.

https://rufus.ie/

~ Group "Weekend" ~

3 users thanked author for this post.

wavy, Kirsty, LHiggins

Reply | Quote

But – OK – now I have a question. I went to the heidoc site and can’t seem to find where to download the Win 10 1909 Pro iso? All seemed a bit confusing and it looked like I was on a page where Win 7 was available – not 10. Or was it maybe because I was not on the Win 10 laptop when I was just looking??

Above my pay grade, maybe – LOL?

Anyway, thanks for a little more clarification on how to do it.

Reply | Quote

You have to download the tool (not the ISO) from Heidoc and run the tool on your computer. Then choose the ISO you want to download.

1 user thanked author for this post.

LHiggins

Reply | Quote

OK – I think I’ve got it! Thanks!!

Reply | Quote

Would this be a good way to get the Windows Creation tool 1909.  It shows as

“MediaCreationTool1909.exe”

https://www.snapfiles.com/downloads/windows10/dlwindows10.html

 

 

Reply | Quote

You can try it and let us know what you get – assuming you have plenty of data on your plan.

cheers, Paul

Reply | Quote

ECWS wrote:

Would this be a good way to get the Windows Creation tool 1909.  It shows as

“MediaCreationTool1909.exe”

https://www.snapfiles.com/downloads/windows10/dlwindows10.html

 

 

You won’t be able to download 1909 from Microsoft using the tool.
You will probably get 2004.
Download 1909 from Heidoc.net

Reply | Quote

[ECWS]

I did not pay close enough attention when Woody said to save a copy of Win10 version 1909 18363.592.

I am not sure how to make a bootable USB drive with Rufus or Ventoy.  There seems to be numerous choices when I checked the website.  However, I did save a copy of 1909 from heidoc.

Thinking it may be easier to just get a copy of the Media Creation tool.  Since Woody said it is possible to save a copy, is the copy that I downloaded above valid?  I was able to download it and it did say 1909.  If the file I downloaded is not valid, what would a valid file that Woody refers to look like?  Also, where could it get it from?  If anyone has copy, can they upload to a response?

Also – wouldn’t it be easier to work from the Media Creation tool if I could get a copy of 1909?

• This reply was modified 3 years, 4 months ago by ECWS.

Reply | Quote

[PKCano]

If you use the MCT you have, even it says 1909, it will download v2004 now. v1909 is no longer available through the MCT.

If you want the v1909 ISO, the only way to get it now is through Heidoc.

• This reply was modified 3 years, 4 months ago by PKCano.

Reply | Quote

PK,

Guess I do not understand.  When Woody said to save a copy and if you did, how would you be able to use it?  Or did it have to be used before 2oo4 came out meaning the saved copy was useless?

Reply | Quote

The MCT (Media Creation Tool) is the tool used to create an ISO. The MCT doesn’t care what version is available. It is just the tool to download the files and create an image of whatever version MS has available for the purpose.

Before 2004 was released, the current (latest) version was 1909, so that was the image in the ISO created before May 27. After 2004 was released, the current version available on MS for download became 2004 and the ISO created was an image of 2004.

The ISO is the image of the Windows OS, whatever version that was used to create it. It is the ISO that’s created by the MCT that you squirrel away. After you have the ISO (image of Windows OS), you no longer need the MCT. It is the ISO that installs whatever version it contains.

It is the ISO you can mount and install Windows. It is the ISO you can use to create bootable install media. The MCT (tool) is a throw-away after it’s done its job of creating the ISO (image).

Reply | Quote

ECWS wrote:

However, I did save a copy of 1909 from heidoc.

You don’t need a USB boot device.
Just click on the 1909 ISO. Windows will mount the file as a HDD drive.
Open the drive and run setup.exe. Follow the instructions (clean install, save software and data..)
At the end of the upgrade eject the new drive.

Reply | Quote

Alex5723 wrote:

You don’t need a USB boot device.
Just click on the 1909 ISO. Windows will mount the file as a HDD drive.
Open the drive and run setup.exe. Follow the instructions (clean install, save software and data..)
At the end of the upgrade eject the new drive.

I had the same questions about this. There are screenshots of this procedure, from PKCano, at creating an iso file

There are posts following this that are also helpful.

Reply | Quote

The ISO is the 1909 update.
You can also download a 1903 ISO or a 2004 ISO.

You don’t actually need to have a copy of the 1909 update if you are happy to go to 2004 late this year. Current reports suggest 2004 is reasonably bug free.

cheers, Paul

Reply | Quote

Paul T wrote:

Current reports suggest 2004 is reasonably bug free

That is a bold statement judging by the long list of compatibility bugs, Microsoft notice to thousand/hundreds of thousands/millions of users that Windows 10 2004 isn’t fit yet for their PCs…and every day a new bug is found : https://www.askwoody.com/forums/topic/windows-10-2004-has-left-the-barn/page/2/#post-2269458&#8230;

Reply | Quote

Ok, this is helpful.  Got sidetracked thinking I needed to use Rufus or Ventoy.  Seems like PK’s instructions say it is not really necessary.  I have 1909 downloaded to another hard drive which I can now copy to a 8GB USB drive.

Just for clarification – when would I need Rufus or Ventoy to make the USB a bootable drive?   Is there any advantage to doing that?  Not that I can figure out.

Now – looks like before I upgrade I should make an image.  How big of a hard drive will I need knowing that I have a 256 SSD with not much else on it except Windows 7 Pro?

Also – should I use the Windows 7 Image option or something else?  Which one is best?

Reply | Quote

You don’t need the ISO on a USB, a copy on local disk is fine, then double click to load it as a drive.
If the ISO is on another machine, use Rufus to create a bootable USB. Plug the USB in, navigate to setup.exe and double click to run. You don’t need to boot from it.

I use 1TB external disks for backup, but you can use whatever you have to hand. Anything over 60GB should be enough for a single backup/image.
I would use one of the free 3rd party backup programs. You can make the external disk bootable and then backup to it – all things in one place.
Software: Aomei Backupper (easy to use), Macrium Reflect (somewhat techie), EaseUs Todo etc.

cheers, Paul

Reply | Quote

If the ISO is on another machine, use Rufus to create a bootable USB. Plug the USB in, navigate to setup.exe and double click to run. You don’t need to boot from it.

Be aware that the contents of the USB (either a USB flash drive or a USB hard/external drive) will be wiped before the bootable drive is created.  So, be sure that there is nothing on the USB that you want.

Reply | Quote

WCHS wrote:

Be aware that the contents of the USB (either a USB flash drive or a USB hard/external drive) will be wiped before the bootable drive is created. So, be sure that there is nothing on the USB that you want.

I think I made a mistake here.  I think this is true only if you are using the Media Creation Tool (MCT) to make a bootable USB.

Reply | Quote

I finally got it.

If I use setup from while the ISO is on my computer, I do not need Rufus or Ventoy.

If I want to use the ISO from a USB, THEN I need Rufus or Ventoy.

Now that I figured that out, is there any benefit to using one over the other except for not having to create a bootable USB?

Also – if using a 1TB external drive, can more than one image be put on the drive?

Reply | Quote

ECWS wrote:

Also – if using a 1TB external drive, can more than one image be put on the drive?

With Ventoy you can put any number of ISO files of any OS (Windows, Linux, MacOs…) on the USB device and select any ISO to run.
Rufus is 1 ISO for USB on USB device.

Reply | Quote

Both work, it’s your choice. For a one off upgrade Rufus is all you need.

You can, and should, use the 1TB (or larger) disk for multiple backups. See this article for more details.

cheers, Paul

Reply | Quote

Like @paul-t, I also store Win 10 ISOs for a rainy day.

In addition, when I create a bootable USB stick, I also back it up using this freeware, portable USB Image Tool. I just find it faster than using Rufus to re-create an earlier Win 10 installer, especially since I make changes.

Hope this helps…

1 user thanked author for this post.

Elly

Reply | Quote

You should use Ventoy on a USB HDD, then just dump all the ISOs on it.

cheers, Paul

Reply | Quote

Rick_Corbett wrote:
I also store Win 10 ISOs for a rainy day.

Hello Rick.

Yes, I myself store recent/”current” (i.e., “current”ly-supported) Win 10 ISOs. And yes, storage is cheap. And yes, it’s always possible to come up with a creative corporate corner case or two to justify almost anything.

But I do find myself wondering… from your perspective, realistically, what utility is there in continuing to save older ISOs (like Win10_1703_EnglishInt_Home+Pro_x64.iso) after EOL? What is your expected use case? Just what kind of monsoon are you preparing for?

What am I missing? Please help me understand, thanks.

Reply | Quote

[WCHS]

To Rick Corbett:
Why is your 1909 iso file that large? 

I used MediaCreationTool1909.exe on May 26 to create my iso file.  It is 4,188,608 KB (type: ISO image).  I checked the box for “Use the recommended options for this PC”. After I created the ISO file, I used dism /Get-WimInfo /WimFile:E:sourcesinstall.esd /index:6  to check it and this is what it says:

@PKCano say at#2263355 that although it says version 10.0.18362, it is really 18363.

• This reply was modified 3 years, 3 months ago by WCHS.
• This reply was modified 3 years, 3 months ago by WCHS.

Reply | Quote

You made the ISO file with “Use the recommended options for this PC” checked. That made the ISO only for your 64-bit Pro English version.

You can make an ISO that works on “All” PCs. (see highlighted). It could contain both the 64-bit and 32-bit OS, both Home and Pro, maybe even multi-languages. In that case the ISO will be larger.

1 user thanked author for this post.

Reply | Quote

And to get ‘all’, then you don’t check the box?

I checked the box. And if I use index=1, 2 ,3, 4, 5, or 7, in the DISM command, it would say Home,
Windows 10 Home N, Windows 10 Home Single Language, Windows 10 Education, Window 10 Education N, Windows Pro N, respectively.

So, that means that these other six x64 editions are in the iso file, too ??

Reply | Quote

We have a few systems that updated to 2004 and have caused issues with printing in our environment. That being said, I am trying to find a 1909 ISO to download to update other systems. Every time I find a link or try to use the update assistant it points to 2004. I scanned the web and all links either point to 2004 or are not valid. Any suggestions?

Reply | Quote

Download the Windows ISO Download Tool from Heidoc.net.
Run it on your computer and download the ISO (s) you need .

Reply | Quote