Portable Devices Pack is for N Editions only, the below two packages exist for v1903/v1909 will check for other Windows 10 versions and fix the Toolkit script. Code: Microsoft-Windows-Portable-Devices-WOW64-Package~31bf3856ad364e35~wow64~~10.0.18362.1 Microsoft-Windows-Portable-Devices-WOW64-Package~31bf3856ad364e35~wow64~en-US~10.0.18362.1
Although I haven't yet added the support for integrating language packs or updates to Windows 11, you can try Integrating the updates using [4] - > [1] Integrate Windows Updates menu. Make sure you copy the windows10.0-kb5005189-x64.psf too along with windows10.0-kb5005189-x64.cab. With Windows 11 now the cumulative update contain two files one a cab file and other .psf file, both are required for integration.
The pack file Microsoft-Windows-Portable-Devices-WOW64-Package~31bf3856ad364e35~wow64~ exist for W10 1903/1909, need to check for other version and will modify the script to suit the Windows 10 versions. Yes VC2022 is backward compatible, it's just I haven't created the pack for W7/W81 yet, will be uploading them once it's done.
Thank you sir. Just recently I noticed that the difference between a component cleaned 1909 and component uncleaned 21H1 is just a mere 500 MB. So it doesn't matter to me. And yesterday I obtained 1909 and 21h1 ISOs with updates from uupdump.net and after servicing these with the latest 11.7 toolkit without component cleaning both came without any sfc errors. Today tried with the official ltsc 2019 iso (en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.iso) with the same steps (for iso obtained from uupdump) used in 11.7 without component cleaning and there are sfc errors. So now what I think these sfc errors also (and mainly) depends upon the source iso. Correct me if I am wrong sir. Thank you
@MSMG , I have released Mouri Optimization Plugin 9.0.2668.0 Technical Preview in recent days in https://forums.mydigitallife.net/threads/59268/page-29#post-1682427. I hope it can help you to improve MSMG Toolkit.
What is the CU number in your official LTSC ISO? You must integrate into the image the CU that is specified in Current Change Log for Toolkit v11.7 (or Changelog.txt in archive with Toolkit) for compatibility with ToolkitHelper.exe : + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809 (v10.0.17763.2061) Source OS. Otherwise, it is quite possible that you will get errors again after removing the components, even if the original ISO does not contain them.
Thanks a lot for that very fast answer. That helps me a lot to get started. At my try with the 11.4 intros, I was using the ISO placed into the ISO Folder and ended up with an error for to able to create the Install.WIM from the .ESD file. OK, let see how it would work now?! And again, thanks a lot for your help.
Thank you buddy. I queried the ISO with dism and got the following output. Sorry but i don't know how to find the CU version in the ISO. Kindly guide me on how to proceed after this. Thank you Index : 1 Name : Windows 10 Enterprise LTSC Description : Windows 10 Enterprise LTSC Size : 12,684,483,229 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.17763 ServicePack Build : 1 ServicePack Level : 0 Edition : EnterpriseS Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 17387 Files : 75395 Created : 15-09-2018 - 14:56:40 Modified : 15-09-2018 - 15:11:41 Languages : en-US (Default)
Pl use Abbodi psfx v4 tool to create full cab package from LCU cab + psf pack. Then integerate that full cab package into offline image or install on current os as your wish
Hi Bira, Excuse me but because you do not send a private message to our Master abbodi1406 I'm sure it will solve your problem / doubt ...
@Bira, only posted the translation of the speech of the friend @sergey130270, with the answer to him. But @mdl052020 had already answered.