My WSUS console sees machines which have installed the enablement package as still 18362.xxx instead of 18363.xxx, but there's an ongoing issue where they forget to change the WSUS-seen version number about 70% of the time when a CU is released.
AFAIK, WSUS version shows the version of wuaueng.dll there is not any file released that is versioned 18363, it's just registry version
To be fair, for me it's about a 20K enablement package and a reboot or two. A clean install ISO is just a couple less things to do in my deployment environment. The other thing I noticed, which could just be an image creation thing, is 18363's install.wims are *way* larger than 18362's install.wims. It's not slight. Even the boot.wim for 18363 is almost 20% larger than an 18362.
How could it be larger, all the updates are the same, the 1909 enablement package adds just 20kb to the wim. Rebuild the wim files. 18363.388 x86 NL with dotnetfx35 pre-enabled and resetbased.: Code: Name: install.wim Size: 2643101573 bytes (2520 MiB) SKUs: Code: [01] 10/4/2019 nl-NL x86 10.0.18363.388 Windows 10 Home | Core [02] 10/4/2019 nl-NL x86 10.0.18363.388 Windows 10 Home N | CoreN Packages: Code: Package Identity : Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~x86~~10.0.18362.1 State : Install Pending Release Type : OnDemand Pack Install Time : 10/4/2019 7:00 PM Package Identity : Package_for_DotNetRollup~31bf3856ad364e35~x86~~10.0.1.3012 State : Installed Release Type : Update Install Time : 10/4/2019 6:47 PM Package Identity : Package_for_KB4516115~31bf3856ad364e35~x86~~10.0.1.0 State : Installed Release Type : Security Update Install Time : 10/4/2019 6:47 PM Package Identity : Package_for_KB4517245~31bf3856ad364e35~x86~~10.0.1.1 State : Installed Release Type : Update Install Time : 10/4/2019 6:47 PM Package Identity : Package_for_KB4520390~31bf3856ad364e35~x86~~18362.387.1.2 State : Installed Release Type : Security Update Install Time : 10/4/2019 6:47 PM Package Identity : Package_for_RollupFix~31bf3856ad364e35~x86~~18362.388.1.0 State : Installed Release Type : Update Install Time : 10/4/2019 6:55 PM Boot.wim x86 NL: Code: Name: boot.wim Size: 381257215 bytes (363 MiB) =================================================================== vs =================================================================== 18362.388 x86 NL with dotnetfx35 pre-enabled and resetbased.: Code: Name: install.wim Size: 2643429149 bytes (2520 MiB) Code: [01] 10/4/2019 nl-NL x86 10.0.18362.388 Windows 10 Home | Core [02] 10/4/2019 nl-NL x86 10.0.18362.388 Windows 10 Home N | CoreN Packages: Code: Package Identity : Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~x86~~10.0.18362.1 State : Install Pending Release Type : OnDemand Pack Install Time : 10/4/2019 9:32 PM Package Identity : Package_for_DotNetRollup~31bf3856ad364e35~x86~~10.0.1.3012 State : Installed Release Type : Update Install Time : 10/4/2019 9:19 PM Package Identity : Package_for_KB4516115~31bf3856ad364e35~x86~~10.0.1.0 State : Installed Release Type : Security Update Install Time : 10/4/2019 9:19 PM Package Identity : Package_for_KB4520390~31bf3856ad364e35~x86~~18362.387.1.2 State : Installed Release Type : Security Update Install Time : 10/4/2019 9:18 PM Package Identity : Package_for_RollupFix~31bf3856ad364e35~x86~~18362.388.1.0 State : Installed Release Type : Update Install Time : 10/4/2019 9:26 PM Boot.wim: Code: Name: boot.wim Size: 381666247 bytes (363 MiB) No difference in size.
I made my own clean install ISO. My post was referencing the unending requests to the psychic hotline when MS will release this or that. When it's not that serious. All of the bits are already here in their underwhelming glory. It's the same story every 6 months. It'll begin anew next spring when we get a meatier release.
I know, which is why I said it will begin anew next spring when we get a meatier (IE: larger, more robust, substantial) release.
1st you have to join the Insiders Beta Program BEFORE you get access to the Rings. There are 4 Rings (Skip Ahead, Fast, Slow, Release Preview). If you have NO experiance running Beta Software, This Is Not For You. There is a chance you could loose Data & have to clean install your Laptop.
Interesting, 18363.388 is considered Beta Software? If yes, what is the latest WIN10 non-Beta Software version (aka official & stable & for the common user)? P.S. Seems I lost data already from an auto-update via WU (Windows Update) from 18363.356 to .388 (?). Didn't quite check what updates it decided to download and install. Folders were missing from C:\ and WIN10 refused to boot. I had to re-install the entire OS.
Thank you, first command worked. 2nd command replied with "Access Denied". In the end I couldn't do anything, no method worked despite having the 18363.356 USB I initially installed from. I reinstalled... currently running 18363.388. I wish I knew the answers on how to fix it, could've helped in the future if it should happen again.
The latest updates that are available in the Retail Ring is the CU which pushes the build number to 18362.356.
i have an issue, im still on 18362.295 windows update not find anything, say its updated... whats wrong ?