Defending for what? You don't have to satisfy everyone. This thread is not only about applying updates to online images (OS) but also about applying updates to offline images.
I also integrate the updates into the ISO, and have the SSU less to integrate is still have that to gain But doing a lot of testing, I reinstall every 2 months or so
I build images for a lot of people so I do test builds all the time just to make sure everything works without any surprises, like the when LCU has the SSU integrated. I like to mess around with it so when I need to work with it, nothing strange pops up. Hardware also also changed a lot. A really fast PC with a fast internet connection makes building an up to date image a relatively quick process and since most of the process is automated, you don't even need to do much actual work.
small question: after compare official iso brand new feb's and w10ui made iso. the offical iso's boot.wim patched Feature Update to Windows 10 20H2 via Enablement Package (KB4562830), and w10ui not have.
Hi Abbodi1406 and Enthousiast I have also this problem. When i extract DU for ISO distribution to sources folder and when i try to install windows it says "no bootable media found" (or something else like this , i can not remember the exact phrase now) Can you please explain the solution here for setup.exe conflict between boot.wim and DU for ISO distribution ? Thank you
1- If you update boot.wim, extract sources\setup.exe from index 2, into iso\sources 2- extract DU to temporary folder, and delete setup.exe before copying other files to iso\sources
uuuhhhh I have been dealing with this for an hour on a new system I have never touched before, was 100% sure I had a missing boot driver. I'm going to retry this without updating DU. UPDATE: Excluding the DU update fixes this issue.
In Italian version, have this errors in cleanup image (both boot.wim and install.wim): Code: >if exist "!mumtarget!\Windows\WinSxS\ManifestCache\*.bin" ( takeown /f "!mumtarget!\Windows\WinSxS\ManifestCache\*.bin" /A icacls "!mumtarget!\Windows\WinSxS\ManifestCache\*.bin" /grant *S-1-5-32-544:F del /f /q "!mumtarget!\Windows\WinSxS\ManifestCache\*.bin" ) >if exist "!mumtarget!\Windows\WinSxS\Temp\PendingDeletes\*" ( takeown /f "!mumtarget!\Windows\WinSxS\Temp\PendingDeletes\*" /A icacls "!mumtarget!\Windows\WinSxS\Temp\PendingDeletes\*" /grant *S-1-5-32-544:F del /f /q "!mumtarget!\Windows\WinSxS\Temp\PendingDeletes\*" ) INFORMAZIONI: impossibile trovare file o cartelle nel percorso specificato. Elaborazione completata per 0 file. Elaborazione non riuscita per 0 file The folder PendingDeletes in wim file created is empty, because this errors? I have used Debug for checking this errors, in attahcment the complete log debug file
Adding DU-source which contains the setup.exe update (eg KB4599861), only into the source folder on the installation media will cause the problem of missing media drivers during installation due to a mismatch of the setup.exe version between what's in the source folder in index:2 of the boot.wim and what's in the source folder on the installation media. To avoid this you need to copy the update of the setup.exe with its dependencies (eg setup.exe, setupcompat.dll, setupcore.dll, setuphost.exe, setupmgr.dll, setupplatform.dll, setupplatform.exe, setupprep.exe) or simply copy only the update of the setup.exe from DU-source into the source folder at index:2 of the boot.wim too. Or simply delete the setup.exe update from DU-source before copying it into the source folder on the installation media as abbodi suggests, so you don't have to copy the same file into the source folder at index:2 of the boot.wim.
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