OK. I totally understand. Also, I have the drivers already exported anyway. While waiting for you to respond, I mounted an install.wim, and integrated all drivers from FileRepository. There were 669 of them. LOL. At some point I will try installing this on one of my partitions.
Thanks for that command BTW, I knew it was possible but I had never actually looked it up. Building an install image for my NUC8i7HVK tonight, this new technology has a mountain of drivers not included in the base Windows 10 image, 1.7 GB worth.
From what I read in the NTLite forum there were some CUs from the month of June that failed to install if you removed Windows Apps on version 1803 RS4 but with newer CU it does not occur anymore. Have you tried with the latest CU? Removed Windows Apps with MSMG Toolkit?
Have you tried without removing telemetry? I have this error removing telemetry on Win8.1 with NTLite.
Yes, I tried with the latest CU but used NTLite to remove the apps because apparently its method is more complete than MSMG's and it removes apps the other doesn't.
This is norm when you remove something that M$ doesn't wants you to remove, and with each newer build more components and packaged become more dependent on each other to prevent user from tempering with the components... Win10 itself is very unstable by default and when you removed components that may be required or used by newer patch released by M$ the whole OS break. So it is always safer to rebuild from scratch with the untouched iso and newer patch.
It'll be safe not to remove manually what Windows components that are splitted into various independent packages. Especially since RS5.
...or still simply use W10 EnterpriseS 2016 without removing nothing only disable a lot of things via Gpedit.msc or via Registry; at least here my O.S> never had issues a long long time until now
Using Toolkit v8.6 or v8.7 i can't seem to integrate the latest Microsoft CU KB4338822 into my Windows 10 Enterprise 2016 LTSB MSDN image. It says "the package is not applicable to this image" but it is because i installed my 2016 LTSB image first and then applied this update straight after, and i'm using it now. Just wanted to make an updated image that's all. Any ideas please ? ####Integrating Windows Updates################################################ ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.17661.1000 Image Version: 10.0.14393.0 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2395.1.7 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at D:\ToolKit-v8.6\Logs\Dism.txt
The latest CU for 14393 = KB4346877 Many reported having problems installing the previous CU's, maybe it works with this one? PS, did you install the most current SSU too?
Ah yes i see now your KB is 3 days newer. Blimey 2 CU's in three days. My windows never got the newer one only the previous one, hence i did not realise there was a newer one etc. Thanks.
System Apps are listed as Windows Components in the MSMG Toolkit. MSMG uses Dism to remove the Metro Apps that is officially supported by Microsoft so it probably will not cause problems. You can also use Powershell for this (there are several tutorials just search). But I do not know if Windows Apps are really the problem.