The Integrate Windows Update feature leaves the integration order to DISM itself and that's why the LCU is integrated first and then SSU. Use Integrate WHD Update Pack feature to integrate in proper order for Windows 10.
The Publisher .xml is already there in the <Packs\OfficeUWP> folder. Still I haven't got the .xml files for Onenote and SkypeforBusiness, will upload once I do get it.
No, it doesn't, first SSU, next all others, last CU = correct order. The 14393 CU case should proof it. When SSU is not integrated first, the CU won't integrate.
Is it possible to remove the UAC with MSMG ToolKit? I think it is connected to the administrative rights, i. e., being able to edit, say, the hosts.file and access some folders without having to do those boring file and folders permission changes when I even have a local account with administrative rights.
UAC is Windows feature, not self-standing application or app. As long as You can disable or ignore it (I mean checking user), not needed to do nothing more. This is built in option, not app.
Hey! I have some (probably newbie) questions about toolkit and windows, so here's the list: - What is the right method to determine which updates I need to download and integrate into an msdn iso? What tools should I use for to download these? (for example: Windows 7 Ultimate SP1 x64 | 7601 build | modified by microsoft: 07/07/2016) - Differences between Windows Updates & WHD Update Packs? (What does WHD stands for?) - How can I run batch files/scripts in the post-setup phase or after the installation? (Is it a right choice to install visual C redist packages in one of these or not?) - .exe installers (with multiple folders) are compatible with the Driver Integration menu? Thanks for the answers in advance!
Is there a way of not having to change the file permissions to access or edit some files and folders?
My ISO grew by several hundred MB, and I couldn't apply the update to only the install image. So in the end I just put SSU in the update folder and applied updated - then I deleted SSU and put CU in the update folder and I updated again. This time ISO grew less than 1 MB.
I don't know what resetbase is. I first tried mounting all images (rescue, boot, install, etc) - this was when my image grew in size when I chose to "Integrate to Windows Setup Boot, Install & Recovery Image". The size shrank by about 100MB when I tried "Integrate to Windows Setup Install & Recovery Image". So I thought maybe if I mount only install.wim I can use "Integrate to Windows Setup Install & Recovery Image" to update install.wim and get a similar size like when I use integrate Windows Updates. But this gave me an error stating the recovery image was not mounted. So I gave up and put the updates in Update folder one-by-one as I described about. This doesn't seem to be a fault with the MSMG Toolkit, it is just following an order to install Windows Updates. But I don't want to use the WHD method when my image size increases so much.
You can't update recovery (winre.wim) when it is not mounted (you said you only mounted install.wim). If you want to only install.wim (not recommended), just mount the install.wim and put the update in: "x:\ToolKit-v8.7\Updates\w10\x64\" (or x86).
This is what I do normally - just put the CU in the Update folder and integrate the update. This has never given any problems in the past, so I am now uncertain why this is not recommended, particularlly when MSMG Toolkit has the option to integrate Windows Updates. Or maybe I don't understand as normal.