|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
So given that the tea leaves look like that 1903 is coming soon, I’m making sure that I’m downloading 1809 from the media download site and parking it
[See the full post at: Patch Lady – downloading the 1809 iso]
Susan Bradley Patch Lady/Prudent patcher
I downloaded 1809 Bld 17763.1 this morning to a Flash Drive for safe keeping. I’m still on 1803 but at some point I’m sure 1809 will be in my future.
Don't take yourself so seriously, no one else does 
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
OH NO!
The 1809 ISO that you should be downloading should be at least the build 17763.107 version. the 1809 iso download that had build 17763.1 had the user file deletion problem and was pulled several days later and MS re-released the 1809 ISOs on Nov. 13, 2018, containing the 17763.107 version which fixed the problem.
I used the MCT this morning to create the USB ISO and to see what build it was, I right clicked on setup.exe>properties, that’s where I got that build number from. Maybe I am looking in the wrong place?
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Use dism /Get-WimInfo /WimFile:X:\sources\install.wim /index:1 in an Administrator command prompt window (use the USB ISO’s drive letter in place of the X: shown here) and look at:
Version : 10.0.17763 ServicePack Build : 107 ServicePack Level : 0
It is the same for all other indices as well.
Note: Use dism /Get-WimInfo /WimFile:X:\sources\install.esd /index:1 if the ISO was downloaded using the Media Creation tool.
It say’s it can’t find the file specified.
Microsoft Windows [Version 10.0.17134.590]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>dism /Get-Wiminfo /WimFile:F:\sources\install.wim /index:1
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Error: 2
The system cannot find the file specified.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
It seems really odd to me that previous downloaders of the ISO got current Bld’s and that the ISO today would be clear back to the 1st Bld. Evidently I am not looking where I need to be looking to find the Bld on this ISO unless MS played a switcheroo.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
From “How to Extract Install.ESD to Install.WIM (Windows 10/8)”
When you download a Windows 10 or 8 ISO file, by using the Media Creation tool, you will realize that there is an “install.esd” file under the “sources” folder (X:\Source\install.esd). The install.esd file is a compressed and encrypted file that contains a full copy of the Windows operating system in a protecting container.
From “Find the Windows version, build and edition from ISO or DVD”
5. Open an elevated Command Prompt window, and then type the following command:
dism /Get-WimInfo /WimFile:F:\sources\install.wim /index:1In the ISO file, if you have install.esd instead of install.wim, you’d type:
dism /Get-WimInfo /WimFile:F:\sources\install.esd /index:1DISM can handle both these file formats (.wim & .esd), at least in Windows 10.
Ahhh, thanks, that did it. So it’s bld 253
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Details for image : F:\sources\install.esd
Index : 1
Name : Windows 10 Home
Description : Windows 10 Home
Size : 14,446,840,204 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.17763
ServicePack Build : 253
ServicePack Level : 0
Edition : Core
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 20506
Files : 93685
Created : 1/7/2019 – 6:36:05 PM
Modified : 3/20/2019 – 9:56:29 AM
Languages :
en-US (Default)
The operation completed successfully.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Thanks.
Got the same. But I need Windows 10 Pro x64, Not Windows 10 Home.
Details for image : E:\sources\install.esd
Index : 1
Name : Windows 10 Home
Description : Windows 10 Home
Size : 14,446,840,204 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.17763
ServicePack Build : 253
ServicePack Level : 0
Edition : Core
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 20506
Files : 93685
Created : 08-Jan-19 – 3:36:05 AM
Modified : 20-Mar-19 – 10:31:09 PM
Languages :
en-US (Default)
edit: I suppose the index 2….N will display additional Win 10 versions
W10 ISO’s usually have ALL versions in them. The “Home” version is generic.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
Got my copy back on Thursday, February 21, 2019 using wget.exe which reported:
Content-Disposition: attachment; filename=Win10_1809Oct_English_x64.iso Date: Thu, 21 Feb 2019 21:51:15 GMT Last-Modified: Wed, 31 Oct 2018 19:03:31 GMT Content-Length: 5075539968
Running fciv.exe -both Win10_1809Oct_English_x64.iso gives:
MD5: 7a19f70f948614b55b716a6ee0ca5274 SHA-1: bee211937f3ed11606590b541b2f5b97237ac09d
To check that the iso file contains the 17763.107 version I use information from “How to determine the version of your Windows ISO file“. In Windows 10 I click on Win10_1809Oct_English_x64.iso to mount it, in my case this is on G:, then open an Administrator command prompt window and enter this:
dism /Get-WimInfo /WimFile:G:\sources\install.wim /index:1
Index : 1 Name : Windows 10 Home Description : Windows 10 Home Size : 14,367,948,244 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.17763 ServicePack Build : 107 ServicePack Level : 0 Edition : Core Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 19280 Files : 89357 Created : 10/29/2018 – 4:53:01 PM Modified : 10/29/2018 – 5:33:20 PM Languages : en-US (Default)
Perhaps also of interest I enter:
FOR /L %v IN (1,1,11) DO @dism /Get-WimInfo /WimFile:G:\sources\install.wim /index:%v|findstr “Name”
Name : Windows 10 Home Name : Windows 10 Home N Name : Windows 10 Home Single Language Name : Windows 10 Education Name : Windows 10 Education N Name : Windows 10 Pro Name : Windows 10 Pro N Name : Windows 10 Pro Education Name : Windows 10 Pro Education N Name : Windows 10 Pro for Workstations Name : Windows 10 Pro N for Workstations
Note: Use install.esd instead of install.wim where shown above if the ISO was downloaded using the Media Creation tool.
Because the cost of materials and time is very small. Because having it on hand, not installed, does not harm your computing experience. Because things can always get worse. And when they do, having more options always beats less options. Even when you do not use those options. Think of it in terms of the same reasons you keep multiple backups in different locations. For some this seems like overkill. But a lot of geeks were scouts. And “Be prepared” sticks with you.
I am not someone who likes or approves of W10… and yet I’ve downloaded an ISO for every version. When I have extra time and energy, I can check it out on a VM, especially since I’m the sort that does better seeing and experiencing, rather than just trying to learn its terminology at a greater distance. It certainly helps to be on the same page as other people.
Some ISO versions I’ve used on friends’ computers. Its amazing how someone will need something once it is no longer available.
It is a sometimes useful resource and cheap insurance… and although 1809 has had its share of problems, it is currently at its most stable. Based on past experience, it is unlikely that 1903 will start out more stable than 1809 currently is… and if someone gets a new computer after 1903 is pushed out, they may well want to go back to an older, more stable version. It isn’t unheard of an update failing, and then rolling back versions failing (hmm… seen it, been there). An ISO is invaluable at that point. And yes, whether its my computer, or a friend or family member’s, I’m compulsive about backing up, so the data is never at risk.
Non-techy Win 10 Pro and Linux Mint experimenter
OK, here goes a less than brief (but, hopefully, enlightening and not too technical) explanation to help our puzzled readers out there while downloading 1809 (and 1903 and other, future Windows 10 ISOs)…
When executed, the Media Creation Tool creates a few temporary directories:
C:\$WINDOWS.~BT
C:\$WINDOWS.~WS
C:\ESD
The files at
C:\$WINDOWS.~WS\Sources
(keep in mind that ‘C:\$WINDOWS.~WS‘ is a hidden directory)
do seem to be referring to v10.0.17763.1… but digging into the main log file
C:\$WINDOWS.~WS\Sources\Panther\setupact.log
and searching for “Download Url” reveals that the OS image being downloaded by the tool is actually the v10.0.17763.253 one:
MOUPG GetWebSetupUserInput: Execute: Download Url X64 = [http(...)/17763.253.(...).esd].
Once the ISO file finishes downloading, if you “mount” it and take a closer look at its contents you will find that the tool downloads the v10.0.17763.1 “BASELINE” (ignore the tool’s Jan 8, 2019 date stamping – to match the KB4480116, OS Build 17763.253: it is misleading, because the files are digitally signed Sep 15, 2018… matching the timeline of the last preview builds and the public release of OS Build 17763.1 on Oct 2, 2018!) – and adds (only) 3 files to the ‘sources’ directory:
ws.dat
boot.wim
install.esd
Now open up an elevated command-line. Peeking into the first file (replace the X: below for the drive letter you’re “mounting” the ISO on)
type X:\sources\ws.dat
only adds to the confusion, because the first three lines of the output misleadingly read:
[WebSetup]
ClientVersion=10.0.17763.1
IsUpgradeNow=FALSE
The key point to figure out what’s going on here is to understand the nature of those other two files. By typing
dism /Get-WimInfo /WimFile:X:\sources\boot.wim|findstr "Name"
dism /Get-WimInfo /WimFile:X:\sources\install.esd|findstr "Name"
you learn that ‘boot.wim‘ is a container for both Windows PE and the Windows Setup and that ‘install.esd‘ is a compressed, encrypted copy of several OS “editions” in a protecting container (as noted here). In fact, these two files act as the core elements of how the “BASELINE” ISO gets “updated” to the more recent build being offered (currently, v10.0.17763.253)!
Thus, typing (again, replace the X: below for the drive letter you’re “mounting” the ISO on)
dism /Get-WimInfo /WimFile:X:\sources\boot.wim /index:1
and
dism /Get-WimInfo /WimFile:X:\sources\boot.wim /index:2
and
dism /Get-WimInfo /WimFile:X:\sources\install.esd /index:N
(with N being any integer between 1 and the total number of indexes, or OS “editions” included in your ‘install.esd‘ file – usually 7 or more)
confirms on all outputs (in the “Version” and “ServicePack Build” text lines) that, indeed, you’ve downloaded:
Version : 10.0.17763
ServicePack Build : 253
Last but not least: if you’re NOT planning to upgrade to 1809 yet, after you’re done with the ISO download make sure to get rid of (remove) those
C:\$WINDOWS.~BT
C:\$WINDOWS.~WS
C:\ESD
directories… 
I deleted Folders C:\$WINDOWS.~BT, and C:\ESD, but had to turn on “Hidden Files/Folders to see C:\$WINDOWS.~WS before deleting. Just a “Heads Up” if you don’t see the WS folder.
I see that it was mentioned at the start of the helpful instructions but I previously missed it.
Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
I grabbed the Media Creation Tool, and built the USB installer for 1809, so it is ready to go when I need it!
I did this on my Win 10 Pro 1803 workstation, but I also have a laptop with Win 10 Home 1803.
Can the same installer be used to update either a Pro or Home edition?
Windows 10 Pro 22H2
When I ran the Media Creation Tool for 1809 I was puzzled that it did not ask about which edition of Windows 10 to build for (Home or Pro, etc.). The only edition available in the tool was “Windows 10”.
So I found this recent “How-to” guide that illustrates what I saw during my USB build process. How to install Windows 10 from USB with UEFI support
It appears that Microsoft has streamlined the media build process and now provides for all editions of Windows 10 by default. The chart in step 4 in the “to install Windows 10 on a different PC” section of the installation media guide appears to confirm that “Windows 10” is currently the target edition for all Windows OS install/upgrades now. Create Windows 10 installation media
Windows 10 Pro 22H2
Microsoft started to push 1809 to everyone (except those with the incompatible Intel display driver) :
Get the Windows 10 October 2018 Update :
Windows 10 will automatically download the October 2018 Update on your eligible device if you’ve turned on automatic updates in Windows Update settings. When the update is ready, you’ll be asked to pick a time to install it. After it’s installed, your device will be running Windows 10, version 1809. (To check whether you’re already running the version 1809 update, click View update history on the Windows Update settings page.)…
https://support.microsoft.com/en-us/help/4028685/windows-10-get-the-update
Last Updated: Mar 20, 2019
A beta version of Rufus released five days ago includes a feature/script which downloads most ISOs from Microsoft sources:
Rufus 3.5 with Windows 10 and 8.1 download option (at ghacks.net)
oh abbodi86:
I ran the 1809 Media Creation tool just now and it is now downloading newer refreshed 1809 ESDs/ISOs with build 17763.379 (1809 + March 2019 CU). products.xml file now has a date of 3/14/2019
Probably soon. I just updated a recalcitrant laptop today to 1809 that has been stuck on 1803, by going directly to the Microsoft website and clicking “update now”.
It seems that I received 10.017763.437 (the April update). As there was no monthly update for April waiting for me after the feature update, I ran “Winver”, and sure enough I was up to date!
The good news is that it seems to be running well. Disclaimer: I am running Windows Defender on this laptop, so no 3rd party AV to cause trouble here!
Windows 10 Pro 22H2
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Notifications
