That's how it normally works - the 1909 usually refers to when it gets finalised, not when it is released.
I'm using HWID since 2 years now and always use my MS account to login and I never had a problem! So I suppose it's safe
You misunderstand. Insiders will get Final Build this Month (Sept.) The General Public will get in Oct. .
I activated Home, Pro, Pro workstation and enterprise (i believe) and get activated every time i format on the same computer. Currently I am using Home because I don't use enterprise features like hyper v
If you mean when you link a non normal hwid like enterprise or education, etcetc, when using the activation trouble shooter for re-activation, it can be possible msft says you have a hwid for pro. I have all possible HWID's from home >>> 2016 LTSB (iirc 15 different ones in total) but never linked any of them to my MSA(s), with the current HWID developments i never needed it.
What process and a link to HWID/KMS38 is not allowed to be posted here (i can remember me sending you a link in the past, the complete $OEM$ folder).
Yes, just checked, you PMed, after that I asked /wrote something there, but you never reverted. (AON)
You don't need to convert your local account to an MS one, just create a secondary account under family and other users > other users Then use that to bind the digital license, and your local account won't be affected.
Thanks for the detailed explanation @abbodi1406 I am more interested in what you call in your post "the change", not related to the out of band preview updates and not related to running full resetbase, but the regular dism /online /cleanup-image /startcomponentcleanup I think in some cases the chain of updates broken by PSFX can be repaired by running full CU install downloaded from catalog, but I may be wrong in relation to the current implementation. I certainly fixed earlier Flash updates and their install/uninstall using this method following psfx releases. Again and this is to clarify for everyone else reading this, my posts are not in the context of the preview updates which are known to create dubious supersedence chains on other OS than Windows 10 as well and as such I tend to avoid for any serious work, unless purely for the fun of testing. This mess was created apparently by the psfx concept in Windows 10, however other implementations on other components have experienced supersedence issues on occasion, much easier to understand and repair though.
The problem is, with IP updates there is no MSU on catalog available. And the .CAB file fails too, when applied manually. At least with the SLOW ring 10019 update no problem occurred when running any cleanup.
Inplace upgrade (like a normal upgrade but now with the same build). Mount ISO of the same build in explorer and run setup.exe.
Did you try to open any 1903 CU cab file with 7-zip and see the contents? or check C:\Windows\servicing\Packages after installing it you may notice there are no more numbered sub-packages for the CU (Package_1_for_KBxxxxx, Package_25_for_KBxxxxx,... files) instead you find new versions files for the default system packages 1903 CUs are truely service packs 3/4 part of the mess is caused by the above change, PSFX thing did not fit well with that change