If you installed 18362.239 you're fine, whatever of the two options you did select. The reason of my snappy reply is because of the so, so, soooo many repeated questions which mostly are answered in the linked tutorial, although it needs an update at the edition selection options.
Thank you for clearing that up. I thought the Cumulative was for a clean install. I just need and expert to confirm it! I I have Windows Server 2019. Can I use the Windows Server Cumulative Update and would my Windows Server 2019 be update? Again, thank you
One last question. How would I be able to use the multi-arch.cmd with UUP? This is my settings for ConvertConfig.ini Spoiler: ConvertConfig.ini [convert-UUP] AutoStart =1 AddUpdates =1 ResetBase =0 NetFx3 =1 StartVirtual =1 wim2esd =0 SkipISO =0 SkipWinRE =0 ForceDism =0 RefESD =0 [create_virtual_editions] vAutoStart =1 vDeleteSource=0 vPreserve =0 vwim2esd =0 vSkipISO =0 vAutoEditions= and this is my convert-UUP.cmd Spoiler: convert-UUP.cmd <!-- : Begin batch script @echo off :: Change to 1 to start the process directly, it will create ISO with install.wim by default set AutoStart=0 :: Change to 1 to integrate updates (if detected) into install.wim/winre.wim set AddUpdates=1 :: Change to 1 to rebase OS image and remove superseded components with updates (faster than default delta-compress) set ResetBase=0 :: Change to 1 to enable .NET 3.5 feature with updates set NetFx3=1 :: Change to 1 to start create_virtual_editions.cmd directly after conversion set StartVirtual=0 :: Change to 1 to convert install.wim to install.esd set wim2esd=0 :: Change to 1 for not creating ISO file, result distribution folder will be kept set SkipISO=1 :: Change to 1 for not adding winre.wim to install.wim/install.esd set SkipWinRE=0 :: Change to 1 to use dism.exe for creating boot.wim set ForceDism=0 :: Change to 1 to keep converted Reference ESDs set RefESD=0 I would really appreciate it very much for any and all assistance concerning this matter. Thank You...
- multi-arch.cmd has no configuration options to use it: create two distributions (iso or folder) or run it and past the path to the iso file for each architecture - options inside convert-UUP.cmd has no effect with ConvertConfig.ini presence - what do need exactly?
What I want to do is download the two Windows 10 (x86 & x64) with UUP and have multi-arch.cmd create one ISO. What I did before was I have two ISOs to create the x86/x64 ISO. That took a while. I was hoping to have it done all with UUCP. When I use the multi-arch.cmd and it asks me for the ISO/Directly, should I point it to the C:\Users\vze2mp9g\Downloads\18362.264_amd64_en-us_all_3f076ff2_convert\UUPs\ directory? Thank you..
multi-arch.cmd is bonus, it's not related to UUP and will never be engaged with point to ready .iso file, one for x64 and one for x86
Thank you for clearing that up. Can I mount the two ISO files, one for x86 and one for x64? Than can I run the multi-arch.cmd F: and G: ? Again, Thank you...
Thank you for clearing that up. Can I mount the two ISO files, one for x86 and one for x64? Than can I run the multi-arch.cmd F: and G: ? Again, Thank you...
Just do what @abbodi1406 said before, either put the x86 and x64 iso*, or already extracted folders, next the cmd and run it. Or enter the full path to the iso including iso filename and .iso extension, like shown here: https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/page-40#post-1536910
What's the newest stable, the one called targeted (I'm not sure of the name, I mean the one stable extra-stable) version Windows 10 Pro 64-bit? Is it Feature update to Windows 10, version 1809 (17763.652) amd64?
Just to let you know, if you are on 1803 & want to Upgrade Microsoft will skip 1809 & install 1903. Microsoft is pushing 1903 over 1809.
Thanks for clarifying that! And what about my other question? Am I on the right track installing AIK for W7?
Read the message again. You have to install Windows 10 ADK on Windows 7 (Deployment Tools is enough).