I have that column in Windows 8.1 (not added by default)

Feature Experience Pack - Browse known builds - UUP dump


Those will also not enable full features of 21H1

19043 EP will activate what is silent in 19041 :)

Enablement Package is more than changing DisplayVersion registry from 19042/20H2 to 19043/21H119043 EP will activate what is silent in 19041 :)
...

How did you get 19043 in the first place? used the silly mum files adding trick? for what? that does not activate 21H1 features, it's just fake registry changes

when you installed the new .789...

News articles don't understand the situation

what's stopping you from confirm it yourself? :)
open latest CU for 2004 or 20H2 in Microsoft Catalog and see if you find any other update...

Incorrect

1. SSU had been always deployed with LCU via WU
2. SSU will never be implemented inside LCU, they will always be separate updates
3. the change only affect WSUS and other Update...

Yeah, but you have "UUP Dump Miniserver" section in the TUT
it would not hurt to add a note about VC++ 2017 x86 requirement :)

thanks

You need both x64 and x86 vcredist installed

php.exe is 32-bit program, and work with x86 runtimes

You need to convert/create the ISO on Windows 10 OS to get normal boot.wim

There no no other editions than Home/Pro/N/China since 17063
all other editions are virtual
they can be created by changing/setting edition on Pro wim file
or simply use product key after...

On x64 system, you need to install both x64 & x86 redistributables

Install Visual C++ Redistributable for Visual Studio 2017
Downloads | IDE, Code, Team Foundation Server | Visual Studio

at the bottom

I think WindowsUpdateBox.exe download is added because uup-converter-wimlib author has found a way to use it to perform upgrade directly from UUP files, for those who don't want to create iso...

No, that will not work

UUP Dump uses php.exe which require VC++ redist 2017 x86 installed
either that or just copy vcruntime140.dll file and place it next to php.exe

Microsoft "unified" editions since WIP 17063

only Pro and Home are real editions, other editions are "virtual" (there word not mine)

so, the only way to get Enterprise is either by modifying...

Unlike complete ESD files, UUP distribution do not contain any boot.wim images

however, as far as i know, latest releases of uup-converter-wimlib script (currently v13) contain a workaround to...

Use ALT+option number (the normal keyboard button, not numpad)
or disable the new cmd experience

apprently it's a bug in cmd V2 for this build, or msft changed something in choice.exe

I was talking about the upgrade process through WU, i didn't mean the ISO created with script

UUP files lacks both boot.wim images, the edition file (e.g. Professional_en-us.esd) only contain iso...

It's only included in the traditional complete ESD file, but it's not used or even extracted from ESD file

what upgrade files exactly? you mean ISO?


no
i'm just a regular attendant at MDL...

boot.wim never get used in complete ESD upgrade process, winrw.wim (SafeOS) handle all that
that's why Microsoft Decided to cut off boot.wim, because the whole point of UUP is to reduce downloded...

1- It is not a bug, it is how Microsoft build UUP files, they choose to deliver winre.wim only
because technically, boot.wim is not required for WU upgrade process

2- A workaround already had...