That sounds even better! While I don't really care about #1 since I block WU specific handler, your #2 is exactly why I've been on this lame Home edition for a month - to see what MS are serving to peasants. It's head-scratching at times and I'm fed up.
Now that you mentioned "block WU specific handler," I am sorry but I have to say that it won't work for me. Neither your script, nor I manually applied it according to your script. (The Windows 10 Feature update, version ??? still pops up. No kidding.)
That's the old script. The new work is not published until I can verify it's reliable across the board, and microsoft keeps making it harder to reach a conclusion.
1. No. You don't need to install it. It is prohibited by Product policy only. 2. No, not tampering Product policy.
@xinso One question do is possible get 19041.1 "Microsoft-Windows-StarterEdition" (starter.esd) I think file exist but no show in uup list files how professional.esd or core.esd all index version in wim is created from this stages and then need get all esd files for create install.wim
Quick question, what are microsoft-windows-editionpack-cloud-package.esd & microsoft-windows-editionspecific-cloude-package.esd (And "N" packages), as a part of AzureHCI 20H2 UUP? Inside there are: Microsoft-Windows-Editions-CloudE-Package~31bf3856ad364e35~amd64~~10.0.17784.1068.mum, Microsoft-Windows-EditionSpecific-CloudE-Package~31bf3856ad364e35~amd64~~10.0.17784.1068.mum, Microsoft-Windows-CloudE-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.17784.1068.mum, Microsoft-Windows-Branding-CloudE-Package~31bf3856ad364e35~amd64~~10.0.17784.1068.mum among others. Can we apply that to 19041.1 somehow? )
You were right. Installed and updated since 11/30/2020 and running very good very light. So good I wanna cry cause I never ever had a Wndows running so light fast and without issues so far, except Windows Damnfender of course. Special thanks to @xinso Chapeau bro... Spoiler