I always set the options in the cmd itself, like this for 20H1/2/21H1: Code: @setlocal DisableDelayedExpansion @set uiv=v9.3 @echo off :: enable debug mode, you must also set target and repo (if updates are not beside the script) set _Debug=0 :: when changing below options, recommended to set the new values between = and " marks :: target distribution, wim file or offline image :: leave it blank to update current online os, or automatically detect wim file next to the script set "Target=%~dp019041_Work_x64_US" :: updates location :: leave it blank to automatically detect the current script directory set "Repo=%~dp019041.1_Updates_x64" :: dism.exe tool custom path (if Host OS is not Win10 and no Win10 ADK installed) set "DismRoot=dism.exe" :: enable .NET 3.5 feature set Net35=1 :: optional, specify custom "folder" path for microsoft-windows-netfx3-ondemand-package.cab set "Net35Source=%~dp019041.1_SXS_x64" :: Cleanup OS images to "compress" superseded components (might take long time to complete) set Cleanup=1 :: Rebase OS images to "remove" superseded components (warning: break "Reset this PC" feature) :: require first to set Cleanup=1 set ResetBase=1 :: update winre.wim if detected inside install.wim set WinRE=1 Result: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-594#post-1645857
Nothing, there is a bug is 9.3. To replicate: Place the W10UI_9.3 folder into root. Create a subfolder "updates". Put update(s) into this folder. Run W10UI.cmd as admin. Press 2. Copy the path for the updates folder. Paste that path into the W10UI_9.3 window. Press enter. See an error that absolutely does not happen with 9.2 (or earlier).
That is not replicating what I showed, create a subfolder and put al of your updates in that folder. Then copy that colder path from the address bar and paste it into option 2.
That scenario is working for me, copy/paste the repo location when using the interactive menu, but the ssu is not renamed / recognized. https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-595#post-1645993
Hi guys!!! In Original images from Microsoft MSDN Microsoft Windows 10.0.19042.804 Version 20H2 (Updated February 2021) - integrated into boot.wim instead of windows10.0-kb4586858-DU for SafeOS (for boot.wim & winre.wim only), windows10.0- kb4562830 (Enablement Package, includes Edge Chromium). Can anyone explain.
Hi guys!!! In Original images from Microsoft MSDN Microsoft Windows 10.0.19042.804 RU Version 20H2 (Updated February 2021) - integrated into boot.wim instead of windows10.0-kb4586858-DU for SafeOS (for boot.wim & winre.wim only), windows10.0- kb4562830 (Enablement Package, includes Edge Chromium). Can anyone explain.
This is the content of the 19042.804 boot.wim: Code: Package Identity : Package_for_KB4562830~31bf3856ad364e35~x86~~10.0.1.2 [20H2 EP] State : Installed Release Type : Update Install Time : 05/02/2021 01:49 Package Identity : Package_for_KB4598481~31bf3856ad364e35~x86~~19041.740.1.1 [SSU] State : Installed Release Type : Security Update Install Time : 05/02/2021 01:46 Package Identity : Package_for_RollupFix~31bf3856ad364e35~x86~~19041.804.1.4 [LCU] State : Installed Release Type : Security Update Install Time : 05/02/2021 01:48 Seems ok to me? Edit: This is the 19042.746 Jan. Updated 2021 ISO boot.wim: Code: Package Identity : Package_for_KB4598481~31bf3856ad364e35~x86~~19041.740.1.1 State : Installed Release Type : Security Update Install Time : 10/01/2021 01:23 Package Identity : Package_for_RollupFix~31bf3856ad364e35~x86~~19041.746.1.6 State : Installed Release Type : Security Update Install Time : 10/01/2021 01:26 EP is integrated in Feb. 2021 ISO, not in Jan. 2021 ISO
There should be windows10.0-kb4586858-DU for SafeOS (boot.wim & winre.wim only), instead of kb4562830 (Enablement Package, includes Edge Chromium) https://forums.mydigitallife.net/th...-20h1-2-vb_release.80763/page-16#post-1571109
I have to go out but will download an early 20H2 ISO to verify, the du for safeos was not in 19042.745 either, iirc boot wim is not updated with the du but with the full CU. Winre only should get the du.
That's my fault if it's not accurate anymore, but the official ISOs seem to not have the du for safeOS integrated anymore into boot.wim, but the full LCU is used (19042.631 and 19042.508 too, no EP in boot.wim of those 2 though). Code: Package Identity : Package_for_KB4577266~31bf3856ad364e35~amd64~~19041.504.1.2 State : Installed Release Type : Security Update Install Time : 27/09/2020 20:55 Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.508.1.9 State : Installed Release Type : Update Install Time : 27/09/2020 20:58 W10UI still only integrates the DU for SafeOS instead of the LCU, will wait for input from @abbodi1406 about it before i change the updates overview post info Now really out to walk the dog