Updated the OP with new 18362/3.418 SSU/CU, DU for Sources and a new 1909 EP (plus renaming scripts).
There is a transition path from 18362.10022 (1903) to 18363.418 (1909). 18362.10022--->18362.356+kb4517245+kb4521863+kb4517389=18363.418 1) Backup your existing Windows 10 instllation. Preferably make a clone. 2) Disconnect from the internet. 3) Using the 1903 V2 ISO, perform an in-place Windows 10 DOWNGRADE from 18362.10022 to 18362.356. This means that you must first boot into windows and then have a DVD or bootable USB with Windows 10 1903 (18362.356) on it. Insert the DVD or USB and run the Setup.exe on the DVD or USB. Run the in-place downgrade to completion. 4) Re-activate Windows 10 using KMS_VL_ALL 5) Put these updates into the root directory of your C: drive. windows10.0-kb4517245-x64.cab windows10.0-kb4521863-x64.cab windows10.0-kb4517389-x64.cab 6) Using DISM, install the latest enablement update kb4517245. This changes the build from 18362.356 to 18363.356 and changes the update ring from the Slow Ring to the Release-Preview Ring. At a command prompt window, run the following command: DISM.exe /Online /Add-Package /PackagePath:C:\windows10.0-kb4517245-x64.cab 7) Re-activate Windows 10 using KMS_VL_ALL 8) Install the latest Servicing Stack Update (SSU): DISM.exe /Online /Add-Package /PackagePath:C:\windows10.0-kb4521863-x64.cab 9) Install the latest Cumulative Update (CU): DISM.exe /Online /Add-Package /PackagePath:C:\windows10.0-kb4517389-x64.cab The result is 18363.418 It is very time consuming, but you shouldn't have to reinstall programs. You will lose registry tweaks and may need to reinstall drivers. You will have a Windows.Old directory. But this should transition you from 18362.10022 to 18363.418. If it doesn't work, then re-deploy the backup you made in Step 1). .
above is not 1909 just 1909 in sheeps clothing no different than 10022 which i will stay with for now with the many issues of 1903 last few patches mess
Updated my PC to 1909 through RP Insider ring this morning from 1903 Retail after the CU the came out yesterday. As a note here; it didn't download anything, after clicking Download and Install 1909 in Windows Update, and instead went straight to install in the progress percentage and asked to restart after a couple of minutes. - As for changes... Honestly, i can't tell what's new other than Explorer looking a little different and my PC feeling a little bit snappier - though this may be placebo. Edit: some notification changes here and calendar too
That is for the RP Ring. The question is what will Microsoft do with the Slow Ring which has not been updated yet from 18362.10022
some comments here are stupid. yawn.. the Insider Programme is pretty self explanatory... not even sure why im responding. My guess would be that both fast and slow are combined, one gets the 20H1 on a monthly basis (slow) and the the other gets weekly (fast). - edit:fixed typos
they can't combine fast and slow, fast has actual new 20H1 builds while slow has 19H2 preview updates/servicepacks for 18362 users were joining slow for 19H@ with the expectation that the final build will also be offered as a service pack what they can do (and probably will), is combine production, rp and slow under 18362/3.100XX Or possibly (because enterprise agreements) systems with KB4517245 will be getting .10XXX patches while those without get sub-.10000 patches
Oh well, on a VM with 1909 18363.418 installed, running the setup of an iso with the same version still doesn't allow to keep files and apps (only "Nothing" is available) when doing an in-place upgrade.
On 18363 you can't inplace upgrade with keeping all files and apps*, but from 18362 > 18363 you can upgrade using a 18363.32x+ ISO. *https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-274#post-1551221
Yes, the option to keep stuff was present when using the same 18363.418* iso on a 18362.418 system. I was just checking if there was any change to the situation you've previously reported. *made via uupdump
Sorry, but the procedure I provided is just one of several that can transition you to a genuine version of 1909. Many of these procedures are simply performing an inplace re-install of Windows 10. As long as the resulting build number and service pack number are less than 18363.418, one can usually transition to 18363.418. The update (Release-Preview) ring is correct. You can run an sfc /scannow or a DISM image repair and it's going to be genuine 1909.