thank you for this clear response. i suppose that the goal of using ConvenienceRollupKB3125574 is to take several updates and mix them together so that you get one huge update at the end, is that correct ?
Instead it does, there is a "search superseded" button bottom left download page and if there are found, it moves them in superseded directory. Not needed if you let WHD download all the necessary hotfixes from scratch, but very useful if you have a folder containing already manually downloaded files.
i downloaded yesterday 48 general updates for win8.1 x86 using WHDownloader and integrated them into win8.1 iso and today after running once again WHDownloader, to my suprise, i noticed that the tool offers me new general updates for win8.1 x86, there were exactly 49 other new general updates, so is this normal ?
Thanks for the update. things are working fine here now. NOTE : 1.Source OS's : en_windows_8.1_enterprise_with_update_x64_dvd_6054382.iso IR5_CCRA_X64FRER_EN-US_DV9.iso IR5_CPRA_X64FRER_EN-US_DV9.iso IR5_CPWMCA_X64FRER_EN-US_DV9.iso IR5_CSLA_X64FRER_EN-US_DV9.iso 2.Host OS : 10 14393.1593 Enterprise 64-bit OS. 3.Update list used : Windows8.1-Update3-x64.wh released on 8th august 2017. 4.Script used : WHD-Windows8.1-Updates-Installer_2.5.zip (i chose the following settings : http://imgur.com/l4nrdxF)
W10UI 3.4 Fixed (thnks Reducer) when selected target is mounted boot.wim index 2, detection conflict will cause the script to hang
Dear @abbodi1406 I've read the note here about Other than increasing the overall install.wim size, the MS (citing your very same words) sloppy work has another nasty annoying side effect, that is, when clean-installing from a clientcombined iso, wiping all the partitions away and letting the windows setup recreating them, than winre.wim size is also increased that it doesn't fit anymore in the 450MB recovery partition. I bet you are already aware because your scripts are a step ahead infact, the same clientcombined (either june or july update), but made from techbench esd with your ESD > ISO tool, or else just integrating into it hotfixes with W10UI, perfectly resolves this issue. Besides, this was only an useless rant of mine against MS :lol: so I just thank you again once more.
1) Creating install.wim/install.esd instead ISO would give you that nevertheless, you may edit decrypt.cmd to add option for it Spoiler add this line at the top after CheckWinre Code: SET SkipISO=1 search for these lines: Code: 1>nul 2>nul call :GUID IF %UnifyWinre%==1 CALL :WINRE and add this line after them: Code: IF %SkipISO%==1 (echo.&echo Done. You chose not to create iso file&echo Press any key to exit.&pause >nul&GOTO :QUIT) 2) How exactly it doesn't allow it? the script only check for OS build 9600 (which is the same in both)
I love your scripts! I only have one little issue - W10UI closes itself whenever I point it to a different directory for DISM. I wanted to use MSMG Toolkit's latest DISM and pointed W10UI there, which just closed itself. I then tried a different directory and different version of DISM, but the same thing happened. I am mostly concerned because 1607-14393 is the preferred OS version for me, but I do update 15063 images offline and I am not sure if using DISM 14393 to update 15063 images is a good idea... EDIT: I don't want to be off-topic, but another little issue is that I could never get KMS_VL_ALL SetupComplete.cmd portion to work. It does not activate Pro VL and if I try to run it manually, I get a message about some missing instances... Does SetupCompletel.cmd from KMS_VL_ALL package require internet connection? I always unplug my network cable when installing Windows to prevent any updates from taking place (without touching services) until I am done customizing it. And would you know where and how to change WIM image Service Pack info? For example, some official MS WIM ID tag states "14393.0, Service Pack 1198", and I want it to say "14393.1670" or "14393.0, Service Pack 1670". Its just for the purpose of tagging images accurately. It seems more appropriate and proper than just using custom names for ISO tags.
Are you pointing it to a diff directory from within running the script, or editing the var in the batch file? If the former, make sure not to use quotes, and that dism.exe is part of the path (iirc)
And you can even use 10240 dism to service 15063 most dism operation works as a front-end, the actual servicing operation are done with the loaded image servicing stack modules no, KMS_VL_ALL doesn't require external connection maybe the components removals you do prevent its work you can't change it, it's set automatically based on kernel32.dll version inside the image
I have one more request, if W10UI.cmd can work with the cab/msu from current location without copying over to temp location, or to delete cab/msu right after it finishes extracting. reason i ask is im working with softperfect ram disk (for temp and mount folder) and every gig counts! thanks again!!!
https://racaty.com/u8tmvtgc97mb https://app.box.com/s/t08h1vsyz83l7ekm6ndimtqvuncnxk2w tested briefly, feedback is welcomed
Heya @abbodi1406, would like to request a little feature to read a path sent with the invoke from another script. That would spare any copy failures and shorten the proces when used from uup.downloader. Kinda : Code: if [%~1] neq [] ( set "UUP=%~1" if exist "%~1\*.esd" goto :check ) if exist "%CD%\UUPs\*.esd" set "UUP=%CD%\UUPs"&goto :check Thanks .
That's actually that i already added Code: if not [%1]==[] (if exist "%~1\*.esd" set "UUP=%~1"&goto :check) along with arm64 support and sub script to create multi_arch_iso i'm just finalizing and testing things
BTW: You should opt for a GIT for this project . Very comfortably maintainably from Explorer/TC via right-click .