What happens if you don;t use the toolkit to integrate them? As in use the dism command I posted earlier? Do they show up then, and do they work? I'm not an expert on dism by a long shot, but I wonder if the dism output from the toolkit integration might have contained some clues? I recently purchased motherboards with USB Audio, so I couldn't use the standard HDA drivers. Because of Microsoft's interference and that I don't use the store or Microsoft accounts I had to manually integrate the Realtek Audio Console, which thankfully the toolkit caters for. But I had lots of issues. I integrated it with the toolkit but it still didn't work, until I also integrated it manually after installing the OS. Something definitely seems awry there, but I'm not sure where. Perhaps @MSMG can shed more light on this subject.
I'll try it out when I have time tomorrow and let you know how it goes. I haven't tried integrating it to a Pro image yet, so I can do that and see if it gets integrated correctly or not. If it does, I can compare the log the toolkit gives me and check them against each other. Not sure if you meant the log when you said dism output or just what it says in the toolkit window when integrating apps, but maybe checking the log will reveal something to me that we can both use. I hope integrating manually after installation works, but I'd like to install the image on several computers, so if I could get everything working in the Toolkit so the iso is ready to go without much further work, that'd be great. Thank you for all your help so far! EDIT #1: Using this command to integrate HEVC after installing and booting LTSC 2021 for the first time works perfectly. I've tested it with both 19044.1288 and 19044.3324. Will try to integrate the apps into Windows 10 Pro 19044.3324 with the Toolkit and see if it works then. EDIT #2: Did not work with integrating apps to Windows 10 Pro 19044.3324. Still only Dolby Audio Extensions, HEIF Image Extensions, OpenCL™ and OpenGL® Compability Pack, Web Media Extensions and Webp Image Extensions have become integrated, none of the others have been integrated. Not visible in either "Apps & Features" or by running dism command "dism /online /get-provisionedappxpackages" in elevated command prompt. Starting to suspect something may be wrong with my computer or the Windows installation on it. I'll try and borrow another computer to test the Toolkit with. EDIT #3: Same thing happened when I used another computer to create the image, so that wasn't it.
You need to go to the removal menu and check the descriptions and dependencies to be able to fix your list. It's not good to take the template and remove only what you want to remain in the ISO and remove the rest without knowing about the problems. Also you can always check about new additions of components for removal, so you will already know about the dangers. Testing the ISO made before performing the inplace update is a good habit. It is recommended that you always do this. For example, for this new 22631 23H2 I had a lot of problems, I still haven't been successful in testing via VM. Not that it's not functional, but it didn't pass my scrutiny for daily use.
Thanks for the response interActionVRI. I thought of that, but how would I know what the inplace upgrade needs? I also tried to find those some description/dependencies somewhere so maybe I could figure it out but I could not. (jeez that windows documentation is overwhelming....) I was hoping that someone would say, in place upgrade require XYZ and I would remove that from the removal list. My other option, rather than going on a testing rotation is to only remove the most unwanted items (privacy, explorer etc) and see how that goes. I'm going to try to copy and paste and read through all the descriptions in MSMG and see if that might help. (I already did, but I'm going to print them out and go deeper into details. Thanks again for the response. TangoBravo
This is in compatibility menu "Windows Upgrade" option. MSMG, describe in the below message the components for inplace update function working well (if you have the hardware requirements for W11) if not, for inplace upgrade you may need the @Enthousiast tool for baypassing hw requirements. https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/
I'm updating LTSC 2019 to LTSC 2021 (nothing with W11) but I will test leaving in all windows update pgks (and easytransfer) intact to see if that works..
Anyone know if it is acceptable practice to dump new drivers into the MSMG folder and integrate them overtop of a previously compiled image or is it better to extract a new ISO and start from scratch?
Hello everyone, I wanted to integrate some fonts but I couldn't find the integrate fonts item in the menu. Is the road correct? I have already copied the fonts into the Custom/Fonts folder MSMG ToolKit 13.6 =============================================================================== MSMG ToolKit - Integrate Menu =============================================================================== [1] Windows Language Packs [2] Windows Drivers [3] Windows Features [4] Windows Updates [5] Windows Inbox Apps [6] Windows Custom Features [X] Go Back ===============================================================================
Good question! From the point of view of the order of the menus and considering that the MSMG said to customize the ISO following the order of the menus. I assume drivers must be entered before integrating updates. But I also think it's worth testing to see if the result is satisfactory. And give feedback to the community. Regarding the drivers to integrate, I believe it is good to export with dism and import with dism. I implemented this in IMCK, it makes a backup of the host machine's drivers, and you could integrate it into the ISO, but I never tested it again. It worked on w10, on w11 I only tested it on the 22000, there in the first builds.
===== Immagine: Install.wim Indice immagine: 1,2 Architettura dell'immagine: x64 Versione immagine: 10.0.22631.2361.0 -------------------------------------------------- ----------------------- ####Integrazione di caratteri personalizzati########################################### ######## -------------------------------------------------- ----------------------- ===========================[Install.wim, Indice: 1]============== ============== Integrazione del carattere AlphanumericQR (File) (AlphanumericQR.ttf)... cpi : Impossibile trovare il percorso 'C:\Utenti\Casa\Desktop\Toolkit_v13.6\Custom\Fonts\AlphanumericQR.ttf' perché non esiste. In C:\Users\Casa\Desktop\Toolkit_v13.6\Bin\AddFonts.ps1:19 car:3 + cpi $fPath -destinazione $mountPath -force + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OggettoNonTrovato: (C:\Utenti\Casa\...hanumericQR.t tf:String) [Copy-Item], ItemNotFoundException + FullyQualifiedErrorId: PathNotFound,Microsoft.PowerShell.Commands.CopyI temCommand
run Start.cmd (administrator) menu integrate custom fonts error: AddFonts.ps1 cpi $fPath -destination $mountPath -force ttf file names do not contain spaces or special characters
Bug report: MSMG 13.6 Remove privacy components menu tab [10] * Windows error reporting unable to allow removing. Reason: "Windows error reporting" is missing in new Compatibility menu.
Hmm, I thinking it may not all be me. If I ONLY remove the privacy items (via the remove option, all privacy items, without using the removepkglist) I lose the ability to do an inplace upgrade. Is something up with MSMG v13.6 itself? It's got to be me. What am I doing wrong? UPDATE: I did the following: 1. Mounted the source image (re-extracted) 2. No changes to the source other than remove the non "n" version 3. Applied the changes 4. Created the ISO Result: inplace upgrade option was greyed out. (issue I'm trying to resolve). Update 2: Repeated the last procedure except this time, for some unknown reason, I went with kept the non N version and removed the N version. Result: IT WORKED. Removed pretty much everything using removepkglist except certain key items.(windows update, manualsetup, easytranfer, etc) but all privacy, and a lot of other things. So if anyone has any similar issues (can't do an inplace upgrade), you may want to try using the "non N'" version of LTSC 2021 as your base. Thanks to all who responded and hope this helps someone else.