Abbodi1406 thanks for your help I applied your solution and it worked , now installing windows without any problem I want to ask whether the same problem exists for 1809 LTSC or not ? thank you again
Thanks usro A lot of nice solutions for this issue I already applied abbodi's solution and everything seems good so far Actually all solutions basically have the same logic Thank you and Cheers !
boot.wim from official ISO/ESD files in \sources\ are protected by TrustedInstaller, they cannot be replaced without taking ownership, and they should not be replaced manually boot.wim from UUP ISO files in \sources\ can be replaced (because they are added manually in the first place during uup conversion) Yes, DU KB4601389 contain setup.exe it could be the same version for setup.exe from LCU, but it's recommended to follow the same steps
I would let it be young man Code: \Windows\WinSxS\Backup\ \Windows\WinSxS\Temp\PendingDeletes\ \Windows\Assembly\NativeImages_v4.0.30319_32\ \Windows\Assembly\NativeImages_v4.0.30319_64\ \Windows\WinSxS\Temp\TransformerRollbackData\ \Windows\CbsTemp\ Aus diesem Ordner alle .bin Dateien \Windows\WinSxS\ManifestCache\*.bin Aus diesem alle .log Dateien \Windows\inf\*.log“ Und diese Ordner werden komplett gelöscht \$Recycle.Bin \PerfLogs so long ago, i don't do this anymore In the past I always wanted to use iso finish under 4 GB, today that is no longer relevant
some question for the safe os , if i use the LCU (e.g. KB4601382) to update winre.wim is it no need the KB4586858 ? or the winre.wim is just need the KB4586858 ?
They can be replaced, either by taking ownership, using nsudo etc. But yes, they shouldn't be replaced manually. Unfortunately most of the advanced users here tend to use and also recommend the UUP ISO as the base rather than the official ISO/Techbench ISO/MVS refresh ISO/MCT ISO-ESD
If I'm using W10UI to add updates to a UUP Dump 19042.1 extracted ISO, do I need to enable the: :: update winre.wim if detected inside install.wim set WinRE=0 @Enthousiast @abbodi1406
@abbodi1406 I used W10UI 9.6 to create 19043.844 image from vanilla 19041.1. Installed and runs like a dream. However, Windows Update downloads the complete KB4601382 (LCU 844) and installs it again even if it was integrated using your script.. Any solution for this?
Windows Update (WU), for various Windows 10 installs, has been re-offering the last LCU for a long time (months). I recently installed the latest MVS ISO and WU offered the last LCU! So if you install 19042.804, don't be surprised if WU offers you 804. Sorry, I don't know why it does this, but it seems harmless.
For setup purposes it's only needed/mentioned for the setup index (#2) but best to integrate it into both indexes.
If I'm using W10UI to add updates to a UUP Dump 19042.1 extracted ISO, do I need to enable the: :: update winre.wim if detected inside install.wim set WinRE=0
It's enabled by default: Code: :: update winre.wim if detected inside install.wim set WinRE=1 When you don't want to update winre.wim set it to 0.