Yes, this makes sense. That's why i got 17134.111 after downloading a few minutes after release time.
No problems here, did you update boot.wim and install.wim as i've showed a few posts back and how did you create the iso? Make sure that setup.exe from "boot.wim\index2\sources" is the same as the one in "iso:\sources\". Copy over the one from "boot.wim\index2\sources" to "iso:\sources" and save the iso.
Yes, I did it as shown. I use CDIMAGE.exe to create the ISO Code: %CDIMAGE% -bootdata:2#p0,e,b"DVD\boot\etfsboot.com"#pEF,e,b"DVD\efi\Microsoft\boot\efisys.bin" -o -m -u2 -udfver102 -lCCSA_%arch%FREV_%LANG%_DV5 DVD "%build%.%SLevel%.%Mod%_%EDITION%_%arch1%_%LANG%.ISO The x86 version has no problems only the x64 version has this problems. And a Big thanks, the copy of Setup.exe solves the problem.
I always use @abbodi1406 W10UI scripts and let it create the iso after updating, it does all by itself, always a correct iso
I install ADK with Deployment Tools and Windows Preinstallation Environment (Windows PE), run from the Start Menu, Windows Kits, Windows ADK, 'Deployment And Imaging Tools Environment' and use this command. Code: oscdimg.exe -m -o -u2 -udfver102 -bootdata:2#p0,e,bd:\2\boot\etfsboot.com#pEF,e,bd:\2\efi\microsoft\boot\efisys.bin d:\2 d:\Win10MultiEN-US.iso -l17134.112 from the extracted and W10UI updated ISO in D:\2 folder and makes the ISO in my D:\ drive directly. Works perfectly.
every time integration i decide not dism patch the boot.wim. i think it's waste time to patch that. im correct?
for sure you had (previously, before update) some damaged system files or files/folders/registry permissions, that why after the update you started to noticed these issues. so, check your system using… "dism /online /cleanup-image /restorehealth" and then… "sfc /scannow".