@Enthousiast - I've been wondering about this for awhile and just want to ask. 1) What is the ideal settings (and why?) for 1809 (LTSC)? I'm mostly referring to section starting at Net35 down to SkipEdge. 2) Do you change these values depending on what edition of 10 is in Target? (1809, 1909, 20H1, etc) These are my current values: Code: [W10UI-Configuration] Target =e: Repo =z:\Projects\OS\Windows\Client\10\updates DismRoot =dism.exe Net35 =1 Net35Source = Cleanup =1 ResetBase =1 WinRE =1 SkipEdge =0 _CabDir =%TEMP%\W10UItemp MountDir =%TEMP%\W10UImount WinreMount =%TEMP%\W10UImountre wim2esd =0 wim2swm =0 ISO =1 ISODir =Z:\Projects\OS\Windows\Client\10 Delete_Source =1 AutoStart =0
Is edge chromium even installed by the LCU on Enterprise 2019 LTSC? I leave it as it is. Code: ResetBase =1 Will break the "Reset this PC" option on 1809, i only use cleanup for that build.
I integrate KB4584642 separately since from what I understand Edge is not installed in 1809, despite the CU being 100 MB larger as of 2-3 months ago. I don't use Reset this PC so that's a non-issue for me.
W10UI_10.4 PSF also handles win 10: Code: ============================================================ Info: ============================================================ Windows NT 10.0 Updates Installer Automated script to install or integrate updates for: - Windows 10 - Windows 11 - Windows Server 2016, 2019, 2022 It also contains cdimage.exe inside the bin folder. For online installing updates, I would leave these entries default, not all users have a D partition/drive. Put it next to the cmd and it will be extracted by the script.
I have two M.2 drives, my O/S and the second for storage. I ran W10UI with updates folder and source folder with extracted ISO files on my storage D:\ drive, which took 16 minutes and 3 seconds. Then I ran W10UI with sources folder on my C:\ O/S drive and updates on my storage D:\ drive and again it took 16 minutes and 3 seconds. Either with M.2s it really doesn't matter if you have both folders on the same drive, or on the separate drives run, the sources folder drive being my O/S drive slows me down so it makes no difference.
you don't have to unpack the iso 19041.1, you can mount it directly, for example with ultraiso. And then you enter at [1] Target (x64): Current OS simply enter the drive letter where the 19041.1 was mounted. Then at [2] Select updates location, enter the path of the updates and start.
https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit-v1-8.83724/ Removes Secure Boot and TPM requirements from a Windows 11 ISO. All credit goes to @Enthousiast
Hi I cant get it to work, zero-> 0 does nothing. I'm probably missing something obvious. Or I'm not doing it right. I didn't touch anything below the hash's. Code: @setlocal DisableDelayedExpansion @set uiv=v10.7 @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=E:\" :: updates location :: leave it blank to automatically detect the current script directory set "Repo=D:\2" :: dism.exe tool custom path (if Host OS is not Win10 and no Win10 ADK installed) set "DismRoot=C:\Windows\System32\dism.exe" :: enable .NET 3.5 feature set Net35=1 :: optional, specify custom "folder" path for microsoft-windows-netfx3-ondemand-package.cab set "Net35Source=" :: 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 :: 1 = do not install EdgeChromium with Enablement Package or Cumulative Update :: 2 = alternative workaround to avoid EdgeChromium with Cumulative Update only set SkipEdge=1 :: optional, set directory for temporary extracted files (default is on the same drive as the script) set "_CabDir=W10UItemp" :: optional, set mount directory for updating wim files (default is on the same drive as the script) set "MountDir=W10UImount" set "WinreMount=W10UImountre" :: start the process directly once you execute the script, as long as the other options are correctly set set AutoStart=0 :: # Options for distribution target only # :: convert install.wim to install.esd :: warning: the process will consume very high amount of CPU and RAM resources set wim2esd=0 :: split install.wim into multiple install.swm files :: note: if both options are 1, install.esd takes precedence over split install.swm set wim2swm=0 :: create new iso file :: require Win10 ADK, or place oscdimg.exe or cdimage.exe next to the script, or inside bin folder set ISO=1 :: folder path for iso file, leave it blank to create ISO in the script current directory set "ISODir=" :: delete DVD distribution folder after creating updated ISO set Delete_Source=0 :: ################################################################### :: # NORMALLY THERE IS NO NEED TO CHANGE ANYTHING BELOW THIS COMMENT # :: ###################################################################
The only thing I can think of is you're not actually clicked on the CMD window. Try making sure you're actually on the W10UI window, then press 0.
Yep the command window was highlighted. I mounted the image with PowerISO could that cause a problem? I've never done this kind of thing before.
Ok I had to uninstall PSO so windows would recognise the ISO. edited the target to F: but still no luck. 0 does nothing, 9 does exit (I'm on Win8.1 Enterprise)
Try making a folder D:\1 extract the ISO with WinRar with D:\1, then change the target to D:\1 Also try installing ADK.