Could it be that it's related to the vulnerability they found in pre .388 and fixed in .388? https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-460#post-1550347 Yes.
Nothing happened to it. The thread merge broke the link. Here is the post... https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-241#post-1545472
Understood, bonesz, although I have to consider that fact that the necessity to disconnect from network to create local accounts may not be apparent to most users, and this so-called dark pattern does not reflect well in my opinion of Windows 10.
What would be considered the Upgrade Path for 18362.10022 ? Go straight to 18363.388 ? Or something less like 18363.356 ?
10022 is from the 356 range? i didn't test but it probably gets a new update to the same build as 18363 is at that time, but that is all speculation/guessing. The actual bumping to 18363 is done by the SSU/CU, but only when 1909 EP is installed too.
OK Thank you. Patch Tuesday is only 2 Day's away, so maybe Microsoft will have something to say then ?
Code: [QUOTE="SAM-R, post: 1552255, member: 486745"]OK Thank you. Patch Tuesday is only 2 Day's away, so maybe Microsoft will have something to say then ?[/QUOTE] just wait and see - or be a member of one 0day`s group`s :D
Me too, even when I have a non-telemetry (non phoning-home) System, with the next update all changes will be gone. Or there are problems while updating.
My current version is also 18362.10022. All the pre-release .esd images are converting to 18362.356 isos, even though they are all labeled "18363.356.190918-2052.19H2_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL...". This is confusing. So it appears that the alternative is simply to wait until update Tuesday to see how the update path will be resolved.
Which version of the esd-decrypter-wimlib you are using? v52 is the newest, you can download it at https://forums.mydigitallife.net/posts/992731/ (If you use decrypt-multi-release, just try this script)
I used abbodi's esd-decrypter-wimlib-52.7z. I convert ESD to ISO, then I mount the ISO to a drive letter and then run DISM to discern the version of the install.wim. I use the following command line: dism /Get-WimInfo /WimFile:X:\sources\install.wim /index:1 Where X is the driver letter and index is one of the versions of Windows 10 that is on the ISO. Every version is reported to be 18362.256.