It's probably better to just "CALL W10UI.cmd" from your own script. Makes it easier when new versions of scripts are released...
Hi, I have a question, I have Update my windows 10 v1803 with W10UI_5.0, to the newest build 17134.191 all ok. But if i make a iso from it, it's not bootable or if i want to install i get this, where is the bootable medium ? W10UI_5.0 adjusts boot.wim and install.wim. Do you know how to install windows? And can make an iso of it.
Personally, I just take the official 1803 iso, I open it (with ultraiso for example) and I replace the file "install.wim" (in the "source" folder) by the one generated by W10UI. Then I save it
But how many file's are updated ? boot.wim install.wim setup.exe i think. I have now make a .iso with Windows 10 ADK 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:\Win10NL-NL.iso -l17134.191 But how can W10UI make an .iso automaticcly ? if he is finished.
By default, the script creates a ISO image. You can burn a DVD using this image or mount the ISO image, format a USB stick and copy the content of the mounted image to the stick. The stick is bootable. Caution : if you have an gpt/uefi system, format rhe stick as fat32. If the .wim exceed the 4 GO size for a fat32 file, you have to split the .wim with dism.
oscdimg . With AiO WIMs splitting might lead to the nasty 'licensing info missing' error . Converting to ESD will reduce size by ~25%.
s1ave77 you said oscdimg . But i only have seen finished, and i had oscdimg.exe also in the folder. Must i something change in the W10UI.cmd for making the .iso ?
In the readme I see this standing. # iso create new iso file if the target is a distribution folder require ADK installed, or placing oscdimg.exe or cdimage.exe next to the script. I had oscdimg.exe next to the script. But did not make a .iso
I just created a Iso image : In one folder i copyed w10mui.cmd 5, the updates (CU, Dervice stack, flash player) and oscdimg.exe Mounted the DVD image of Windows 10 17134.1 and copyed the content into c:\temp Modified W10mui.cmd : set "target=c:\temp" Execute W10mui.cmd as administrator Result : a iso image is created in the folder containing w10mui.cms. That's all folks.
Use it this way. Code: oscdimg.exe -h -m -o -u2 -udfver102 -bootdata:2#p0,e,b<PATH to Extracted ISO>\boot\etfsboot.com#pEF,e,b<PATH to Extracted ISO>\efi\microsoft\boot\efisys.bin -l<Description of ISO if Desired> %USERPROFILE%\Desktop\<Name of ISO>.ISO This will save the ISO to your desktop. Best to copy, and past this as there are spaces which may not be evident. Put oscdimg.exe in \Windows\System32 folder to make it easier.
I, like another poster upstream, have an untouched Windows 10 LTSB 2016 1607 x64 iso file into which I wish to slipstream Cumulative Update KB4346877. It repeatedly fails to integrate. I have no problem integrating the 2018-04 update into untouched iso. (I am also unable to integrate the 2018-07 KB4346877 into the preceding 2018-04 slipstreamed iso.) I also installed the Windows 10 LTSB 2016 1607 and attempted to update the system using the KB4346877 standalone installer, but it fails with the following error: "The update is not applicable to your computer." Applying the 2018-04 update is not a problem. (Applying the KB4346877 after the 2018-04 update gives the same error as above.) has anyone encountered this problem? Any solutions/workarounds? Thanks.
Totally unrelated, just figured out you can change themes on the website, Material Dark Blue is awesome!!