Is there any reason why the "Recovery" partition is now created after the main data partition, when we do a clean install in UEFI mode?
Reading the official info by BLB (link is at the OP), says 19041.207 is the final build but it will probably get more updates before GA or maybe oldskool just one at GA. MSFT got a new leader, 2004 is the first major new build after 1903 and all is new, for us to discover along the way
yes, just a few more hours now to official 207 bits. although, if you want to be "safer" wait for GA / next build.
It's expected to be 7 days https://forums.mydigitallife.net/th...pc-20h1-vb_release.80763/page-89#post-1591538
IS there a way to update to 19041.207 from 18363.778 without freshly installing the 19041? Sorry if asked already.
1. By running setup.exe from the mounted 19041.xxx ISO 2. By enrolling in the RP ring and let WU do it.
I expected official confirmation that the 207 slow ring ISO = RP bits, but alas that did not happen. Anyway, decided against test with RP because of these bugs that were seen in a few 1909 machines (fixed in 21-April 1909 CU, fix coming in 2004 GA?): Addresses an issue that prevents the touch keyboard from appearing during sign in when the user is prompted for the password. Addresses an issue that causes the Trusted Platform Module (TPM) initialization to fail with system event error 14 and prevents Windows from accessing the TPM. Addresses an issue that causes communication with the TPM to time out and fail.
BLB published that 19041.207 now is RP ring. If the deltabuild doesn't change but the ring does, it's the same content.
To test the rollout on ISO we'd need confirmation that the Slow Ring ISO is bit-identical with the RP ISO. There may be small differences in unattend scripts etc. and we don't want to call MS and be asked "Have you tried the RP ISO?"
If the build is the same, the content is the same. The delta build is by the CU and 19041.207 = 19041.1 + SSU/CU (kb4545706/kb4550936).
That's all theoretical. On my home machine I could install 207 using x number of ways and it wouldn't matter. On a wider scale test rollout, you run into a problem, you call tech, one of the things is to ask you to try the ISO, which is a fair question.