I have added known reg entries to disable Windows Update, if you know anything extra tweaks need to be added let me know, will add them. Will check with wub to know what extra tweaks does it applies to disable Windows Update.
Added to the list, will implement it in future. Microsoft hasn't yet officially announced the Windows 11 and adding support for Insider Preview builds is a waste of time as the present component removal is a manually process.
Actually right now the MultimediaRestrictedCodecs integration is only for Server editions, need to add the Dolby codes pack and modify the script code to support LTSC and Server editions.
OK. For a while I will add dll files I posed before via Custom option. (Same as the New Icons) I have a question. Do I need to register dll files somehow in the mounted image? Or dll-s will be registered automatically after installation? (Anyway I always have an ability to run register commands after OS installation).
Yes, pt-BR. I know you're busy. A few days ago... I had sent PM to you. I await your reply, so I can proceed here.
@MSMG - A BUG FOUND (v11.6) , LTSC Hard crashing when using an option: Integrate -> Windows Updates -> Integrate WHD Update Pack -> Integrate Windows Setup Media Updates DU for Sources (SetupMedia) from LTSC OP : windows10.0-kb5003714-x64_c08b34a80c679cb862f624e5e1de86652ba11e7c.cab cab was placed into WHD folder. Previous steps (NetFX48, DirectX9c packs & WU integrations) completed successfully. But crash on Setup Media Updates integration step (nothing else, e.g. Custom files weren't added at that moment yet). Reproduced 3 times on 2 machines, with different Win10 versions - same result.
The Integrate Windows Setup Media Updates doesn't uses the cab file to update the Setup Media instead is manually fetches the files from boot.wim and install.wim mounted images when CU is integrated. DU for Sources cab files is integrated while using Integrate WHD Update Pack, if the boot image is selected while mounting the source images. Will check with the crashing to fix any issues.
@MSMG Yes, all *.wim were chosen for mounting. - So such cab placing is wrong? I don't understand your post. - Does it mean we don't need Windows Setup Media Updates any more (because they are included in the CU?) ? - Is such situation possible, when CU contains old Setup Media, but cab shared in M$ WU Catalog is more rescent? I think, yes. - Then, when we need choose Integrate Windows Setup Media Updates option? If I didn't ask I never would have known.
The Integrate Windows Setup Media Updates menu was used earlier before MS started releasing DU for Sources. Although this can be used to update Sources folder for W7-W10, with DU for Sources now available for Windows 10, I have added the integration inside the Integrate Windows WHD Update menu for Windows 10. So if using Windows 10, the DU for Sources cab files present and have chosen boot.wim and winre.wim while mounting the sources then you can skip this Integrate Windows Setup Media Updates menu.
@MSMG So I just need only place cab and skip menu option (when boot.wim and winre.wim are mounted), everything will be done automatically. OK. Looking odd. But thanks for this useful information. Will update my own manual.
@MSMG I followed your advice and didn't used to Integrate Windows Setup Media Updates option, having the cab for Setup Media in the WHD folder. Windows installation FAILED. Same error as when Setup Media was not integrated: So using the last v11.6 I can't prepare ISO at all. --------------- My advices: 1. Leave Integrate Windows Setup Media Updates option as it was - separate option just for intended purpose. People will not forget about this update, the menu item will remind them. And none confusing about when it applies. 2. Rename everywere "Setup Media" to "DU for Sources". As I mentioned before several times, old naming looks confusing for non-English users, especially for newcomers.
Hey, friends, do you agree with me and @RaiyvaN the black background and light-yellow font is much better by default? For "Toolkit.cmd" : Code: color 0E
Spoiler Deployment Image Servicing and Management tool Version: 10.0.21382.1 Error: 87 An error occurred while processing the command. Ensure that the command-line arguments are valid. For more information, review the log file. The DISM log file can be found at B:\Toolkit\Logs\Dism.txt The log is attached to this post I mentioned my problem. Tested on x86 and x64, downloaded again, but the error persists. I'm going to download another image from UUP, but I thought it might be something related to tpk's index number. Just a guess. I had problems with cross-referenced files on my mechanical hard drive, but I have replaced the hard drive and re-downloaded packages that were having problems with me, but nothing has changed. Language pack integration for testing, only returned errors on arch x64. x86 is all right. I downloaded the pack again, but errors persist. Spoiler =============================[Boot.wim, Index : 2]============================= ------------------------------------------------------------------------------- Integrating WinPE - Setup Pack [pt-BR] to Windows Boot Image... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.21382.1 Image Version: 10.0.18362.1556 Processing 1 of 1 - Adding package WinPE-Setup-Package~31bf3856ad364e35~amd64~pt-BR~10.0.18362.1 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at B:\Toolkit\Logs\Dism.txt ------------------------------------------------------------------------------- Integrating WinPE - Setup Client Pack [pt-BR] to Windows Boot Image... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.21382.1 Image Version: 10.0.18362.1556 Processing 1 of 1 - Adding package WinPE-Setup-Client-Package~31bf3856ad364e35~amd64~pt-BR~10.0.18362.1 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at B:\Toolkit\Logs\Dism.txt Thanks!
Hello MSMG are you already preparing yourself mentally for autumn when the new Wondows 11 comes out? Or do you dislike it at the moment, because it's not autumn yet there is already a leak on the Internet from Windows 11, maybe you can try it out or so...