[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

jim_p · Oct 4, 2019

ipx said: ↑

that link has oct 18 & may 19 isos only.

untouched sept 19 isos.
Click to expand...

It seems I will download them and check their sums to verify what they really are.
Ms has named them like so "win10_1903_v2_(language)_(architecture).iso", e.g. win10_1903_v2_english_x64.iso, and that v2 in their name makes me think it is the updated iso for September, as I had mentioned on post 5506 here
https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-276#post-1551360

erpsterm35 · Oct 4, 2019

Warkratos said: ↑

Clean Installed 1909, and today I got updated to 18363.388 without Windows Insider.

Via Windows Update
Click to expand...

also updated 1909 to build 18363.388 on my end, non-insider but not using windows update. I manually downloaded & installed KB4524147 update thru MUC (ms update catalog)

Carlos Detweiller · Oct 4, 2019

I got 18363.388 using the Offline mode of WuMgr.

Enthousiast · Oct 4, 2019

Windows 10 User said: ↑

Does IDM make a difference in terms of download speed? I used it some years ago and in some cases even after using a key to force file downloads with it I had problems and lost the download ticket so I stopped using it. Are there many websites which still have these problems?

Why do all Windows updates have a different release date (support.microsoft vs. catalog.update)?
Click to expand...

Edge caught up with IDM, and finished at around the same time, i never had to use any "accelerator" to be able to get my max speed of 500Mbit/s, that's all depending on the file host server.

IDM is maybe useful for multiple files downloads.

Enthousiast · Oct 4, 2019

jim_p said: ↑

It seems I will download them and check their sums to verify what they really are.
Ms has named them like so "win10_1903_v2_(language)_(architecture).iso", e.g. win10_1903_v2_english_x64.iso, and that v2 in their name makes me think it is the updated iso for September, as I had mentioned on post 5506 here
https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-276#post-1551360
Click to expand...

https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-278#post-1551675

spedia · Oct 4, 2019

You need to login to view this posts content.

jim_p · Oct 4, 2019

@Enthousiast
Thank you... although all that seems chinese to me

SM03 · Oct 4, 2019

Dalai Lamer said: ↑

hi all

given the upcoming 1909 general availability and the subsequent release of clean official isos, I'd like to get some clarifications regarding LanguagePacks

AFAIK:
after a LP is installed on top of an up-to-date W10 installation, the most recent CU will be redownloaded/reapplied by WU
the same goes for customized ISOs: if I integrate the LP onto W10 refreshed media, the first thing that WU will do after the system setup as been completed would be installing the CU again
in short: when creating customized W10 media, it's always better starting with both main ISO and LP based of the same W10 build and to integrate the SSU/CU later

is this still the case nowadays?

since the 1909 release will be basically a 1903+SSU+CU+EP, will microsoft release an updated 1909 language pack as well?
Click to expand...

We will see that eventually, nobody here is from MS and really don't know what they 'd do or gonna release. Personal, I too have the same Q & already asked here several times and folks here are saying (read presuming) that as 1909 is not any major release for MS, it's more likely a servicing update for them from 1903 to 1909, so they ain't gonna release any full-fledged 1909 LP+FOD DVD2 ISO that they release for every (major) Windows release.

LilBlinx · Oct 4, 2019

Enthousiast said: ↑

Now we can't trust Jason Howard anymore

Media Content: 1903 September Update Refresh ISOs

Code:

Name: en_windows_10_business_editions_version_1903_updated_sept_2019_x86_dvd_da0312da.iso
Size: 3680307200 bytes (3509 MiB)
CRC32: B6BC99E3
CRC64: EF47EF1C0E380DD3
SHA256: 54928B7768DD009BDD8A7C8270560525A75631557EABFB35D9577620C82E7DFA
SHA1: 8D90C4895C734F835915E2FBF5E396BE5C99082E
BLAKE2sp: B20942608587DC6ACE6B421D72B4B0892DDB3F50D5ADFF28B8028F83FB7FBF0A

SKUs ISO:

Code:

[01] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Education | Education
[02] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Education N | EducationN
[03] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Enterprise | Enterprise
[04] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Enterprise N | EnterpriseN
[05] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Pro | Professional
[06] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Pro N | ProfessionalN
[07] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Pro Education | ProfessionalEducation
[08] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Pro Education N | ProfessionalEducationN
[09] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Pro for Workstations | ProfessionalWorkstation
[10] 9/9/2019 en-US x86 10.0.18362.356 Windows 10 Pro N for Workstations | ProfessionalWorkstationN

SKUs ESD:

Code:

Name: en_windows_10_consumer_editions_version_1903_updated_sept_2019_x64_dvd_ef2f7737.iso
Size: 5369317376 bytes (5120 MiB)
CRC32: C5389A23
CRC64: C9EA355A366F3341
SHA256: 0560E2840CA076EC1777C178FCD1DD200DEE0C3E712314F5146D224D1BC3EC0E
SHA1: B7CA3CCDFE292E0466F2A62FFBEAB18972A7C7F9
BLAKE2sp: 97578FF5E0B077315E75F1AAF3765FFE57798F358B9D7D7A2FBB3A2B6CD9A71A

SKUs ISO:

Code:

[01] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Home | Core
[02] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Home N | CoreN
[03] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Home Single Language | CoreSingleLanguage
[04] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Education | Education
[05] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Education N | EducationN
[06] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Pro | Professional
[07] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Pro N | ProfessionalN
[08] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Pro Education | ProfessionalEducation
[09] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Pro Education N | ProfessionalEducationN
[10] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Pro for Workstations | ProfessionalWorkstation
[11] 9/9/2019 en-US x64 10.0.18362.356 Windows 10 Pro N for Workstations | ProfessionalWorkstationN

Package List:

Code:

Package Identity : Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3003 (KB4514359)
State : Installed
Release Type : Update
Install Time : 9/9/2019 5:40 PM

Package Identity : Package_for_KB4513661~31bf3856ad364e35~amd64~~10.0.1.16 (DU SafeOS)
State : Installed
Release Type : Update
Install Time : 9/9/2019 5:40 PM

Package Identity : Package_for_KB4515383~31bf3856ad364e35~amd64~~18362.350.1.0 (SSU)
State : Installed
Release Type : Security Update
Install Time : 9/9/2019 5:40 PM

Package Identity : Package_for_KB4516115~31bf3856ad364e35~amd64~~10.0.1.0 (FLASH)
State : Installed
Release Type : Security Update
Install Time : 9/9/2019 5:48 PM

Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.356.1.9 (CU KB4515384)
State : Installed
Release Type : Update
Install Time : 9/9/2019 5:48 PM

Click to expand...

May I know how and which tool is used to get this info, especially the package list?

Enthousiast · Oct 4, 2019

You need to login to view this posts content.

panosxidis · Oct 4, 2019

Maybe 18363.3XX is RTM build

Enthousiast · Oct 4, 2019

LilBlinx said: ↑

May I know how and which tool is used to get this info, especially the package list?
Click to expand...

Most is by a query in the old WimEditionSwitcher by s1ave77 (deprecated)

Package list is a simple dism command:

Offline:
Code:
DISM /Image:x:\Mount /get-Packages
Online:
Code:
DISM /online /get-Packages

Kargeras · Oct 4, 2019

My Windows 18363.356 decided to update (via Windows Update service) and asked me to reboot.

Rebooted once, asked for another reboot.

On the 2nd reboot, I can't enter Windows anymore, says it's missing ReFS.sys and pci.sys files.
Both files actually exist in their correct path.

endbase · Oct 4, 2019

Kargeras said: ↑

My Windows 18363.356 decided to update (via Windows Update service) and asked me to reboot.

Rebooted once, asked for another reboot.

On the 2nd reboot, I can't enter Windows anymore, says it's missing ReFS.sys and pci.sys files.
Both files actually exist in their correct path.

Click to expand...

If you have a usb with windows install files on it you can fix that mostly trough recovery

Kargeras · Oct 4, 2019

You need to login to view this posts content.

Enthousiast · Oct 4, 2019

Added this to the OP (first post of this thread), section 1909/19H2:

1909 Explained In Simple Words https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-282#post-1551877

I hope this will clarify it a bit more.

endbase · Oct 4, 2019

You need to login to view this posts content.

3zero3 · Oct 4, 2019

Enthousiast said: ↑

Integrate/install this simple 20kb update:

And you will magically be on 1909/18363.xxx
Click to expand...

Did You try to install (or integrate) EP on 18362.1 UUP? Just curious about 18363.1 ISO.

Enthousiast · Oct 4, 2019

You need to login to view this posts content.

bfoos · Oct 4, 2019

All this new build madness (Newbuilditis?) over a 20KB enablement package. Hahaha

[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

jim_p MDL Member

erpsterm35 MDL Expert

Carlos Detweiller MDL Spinning Tortoise

Enthousiast MDL Tester

Enthousiast MDL Tester

spedia MDL Senior Member

jim_p MDL Member

SM03 MDL Addicted

LilBlinx MDL Novice

Enthousiast MDL Tester

panosxidis MDL Member

Enthousiast MDL Tester

Kargeras MDL Novice

endbase MDL Guru

Kargeras MDL Novice

Enthousiast MDL Tester

endbase MDL Guru

3zero3 MDL Senior Member

Enthousiast MDL Tester

bfoos MDL Guide Dog