So that link you offered has been removed for ToS violations and I meant 2016 LTSB sorry I have the 2015 version i mis typed. I am 100% looking for the 2016 LTSB iso. Thank you.
As long as you have the latest Security Update that's all you need. The latest update has all the previous updates.
@summersuns run command prompt as administrator, then change to W10UI.cmd folder path execute W10UI.cmd and press "0" to start the process this mightshow the reason to terminating
Thanks for reply: Code: ============================================================ Running W10UI v10.15 ============================================================ All applicable updates are detected as installed ============================================================ Removing temporary extracted files... ============================================================ 0 was unexpected at this time. c:\WORK\W10UI_10.15f>
@ abbodi1406 I noticed you liked my post but have nothing more to say about it. Does this mean you do not know what might be preventing the process from summarily terminating? I ran the script in a VirtualBox image of Windows 10 2021 LTSc while waiting for a reply but that proved to be exactly the same: complete the options press" 0" and watch to script window vanish! However I was able to browse the script reademe many times and cannot see where I am making an error. Cheers
@summersuns I gave you a like as well. Do you want to add me to the equation as well? Na, don't mind. Cheers
Still investigating are you trying to update the current VM? or extracted ISO? you could set the options correctly in W10UI.ini then edit W10UI.cmd and enable debug mode save and run then share the Debug.log or tmp.log
abbodi1406 Managed to run the W10UI script successfully. Produced an updated ISO Thanks for your interest in troubleshooting
I have done some testing integrating the latest updates (as listed in my post #1115 above) into install.wim. Because of the size of LCU (1.6 GB) there are significant differences in the size of the updated install.wim, depending on the integration method: 2.82 GB - original file 2.92 GB - W10UI_10.15f with both Cleanup and ResetBase set to 1 4.11 GB - W10UI_10.15f with both Cleanup and ResetBase set to 0 4.72 GB - standard dism with both Cleanup and ResetBase set to 1 It seems that abbodi's W10UI script performs some extra cleanup compared to the standard dism method (as shown in the Spoiler below). I usually install Windows directly from install.wim using dism and then install BCD files and partition or disk boot code manually. This way I do not need boot.wim or ISO file for anything, that is why they were not included in my tests. Spoiler: Standard dism code :: Integrate updates into Win10 Enterprise 2016 LTSB source :: :: change WKDIR variable as needed (Work Directory) :: place install.wim in WKDIR :: place updates in WKDIR\Updates (cab or msu files, each file on the separate line) @echo off set WKDIR=E:\WinISO mkdir %WKDIR%\WIN Dism /Mount-Image /ImageFile:%WKDIR%\install.wim /index:1 /MountDir:%WKDIR%\WIN Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb5005698-x64_ff882b0a9dccc0c3f52673ba3ecf4a2a3b2386ca.msu Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb4486129-x64_0b61d9a03db731562e0a0b49383342a4d8cbe36a.msu Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb4577586-x64_809b9640d04c5af4c7e78499052abaa936cb670a.msu Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb4589210-v2-x64_bbbf54336d6e22da5de8d63891401d8f6077d2ce.msu Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb5007152-x64-ndp48_5631ba2bdcb5a06578ebbd83970739fb87a3ac4f.msu Dism /Image:%WKDIR%\WIN /Add-Package /PackagePath:%WKDIR%\Updates\windows10.0-kb5008601-x64_c0fddabd5b9698548d741effbdfd03a4f2440ba2.msu Dism /Image:%WKDIR%\WIN /Cleanup-Image /StartComponentCleanup /ResetBase Dism /Unmount-Image /MountDir:%WKDIR%\WIN /Commit rmdir %WKDIR%\WIN
ResetBase is disabled by default for all Windows 10 you need to run standard dism cleanup twice Code: Dism /Image:%WKDIR%\WIN /Cleanup-Image /StartComponentCleanup Dism /Image:%WKDIR%\WIN /Cleanup-Image /StartComponentCleanup /ResetBase P.S. manual cleanup that W10UI perform: Spoiler Code: takeown /f "%WKDIR%\WIN\Windows\WinSxS\ManifestCache\*.bin" /A 2>nul icacls "%WKDIR%\WIN\Windows\WinSxS\ManifestCache\*.bin" /grant *S-1-5-32-544:F 2>nul del /f /q "%WKDIR%\WIN\Windows\WinSxS\ManifestCache\*.bin" 2>nul takeown /f "%WKDIR%\WIN\Windows\WinSxS\Temp\PendingDeletes\*" /A 2>nul icacls "%WKDIR%\WIN\Windows\WinSxS\Temp\PendingDeletes\*" /grant *S-1-5-32-544:F 2>nul del /f /q "%WKDIR%\WIN\Windows\WinSxS\Temp\PendingDeletes\*" 2>nul takeown /f "%WKDIR%\WIN\Windows\WinSxS\Temp\TransformerRollbackData\*" /R /A 2>nul icacls "%WKDIR%\WIN\Windows\WinSxS\Temp\TransformerRollbackData\*" /grant *S-1-5-32-544:F /T 2>nul del /s /f /q "%WKDIR%\WIN\Windows\WinSxS\Temp\TransformerRollbackData\*" 2>nul del /f /q "%WKDIR%\WIN\Windows\inf\*.log" 2>nul for /f "tokens=* delims=" %# in ('dir /b /ad "%WKDIR%\WIN\Windows\CbsTemp\" 2^>nul') do rmdir /s /q "%WKDIR%\WIN\Windows\CbsTemp\%#\" 2>nul del /s /f /q "%WKDIR%\WIN\Windows\CbsTemp\*" 2>nul
I am using dism v10.0.22000.1 in Windows 11 (22000.348) and running Cleanup-Image twice does not seem to be necessary. The size of install.wim is as follows: 5,069,004,682 bytes - single Cleanup-Image line as shown below: Code: Dism /Image:%WKDIR%\WIN /Cleanup-Image /StartComponentCleanup /ResetBase 5,068,537,288 bytes - two Cleanup-Image lines as shown below: Code: Dism /Image:%WKDIR%\WIN /Cleanup-Image /StartComponentCleanup Dism /Image:%WKDIR%\WIN /Cleanup-Image /StartComponentCleanup /ResetBase So the difference is negligible. In the end, what really matters here is that your code is much more efficient than standard dism code.