If you're an advanced enough user to where that's not an issue, then you can just modify the batch fie to remove the version checks. MSMG wants the toolkit to never result in any problems so long as the script is unmodified, to make bugfixing easier.
Apologies if it's been asked a lot, but what should I do to convert all the ESD files you get for Cumulative Updates to CAB files so you can apply them with MSMG Toolkit?
I have not found this problem here.At that time, it was an integrated task that was executed over the scope of the version.I used ToolKit v9.2 to process Build 18362.1,not prompt any SFC error in the process and experience modification version.
@MSMG - please let me know which msmg version is compatible with the latest windows 10 ltsc refresh images. I think 17763.316 is the latest ltsc refresh. Correct me if I am wrong. Thank you.
yep i know, i just don't get why restrict the toolkit like that to specific releases, because there will be always errors it depends on how each user use the toolkit and it will never be the same experience for everyone, still to this date, still users report errors while trying the toolkit, this will always happen no matter what so why the restriction, just doesn't make any sense to me
@Windows 10 User, I'm afraid that @intro had right, component removal from PkgsList does not work however. I have installed created image and systems apps + advanced are still there. I have misunderstood @MSMG that advanced component removal is not working only in the ToolKit menu. We have to wait for proper release.
Tested Toolkit v9.3.1 with the Servicing Stack and Cumulative updates released yesterday and SFC passed after installation and also after Windows Updates. Files used for x86: ISO: 17763.1.180914-1434.RS5_RELEASE_CLIENTENTERPRISE_VOL_X86FRE_EN-GB.ISO SSU: windows10.0-kb4499728-x86_999cd7a0d2565ce3769afa361c0362e755231108.msu CU: windows10.0-kb4494441-x86_83f1e00d2082f615d52e2b2b73d2a065f9ad71a7.msu Files used for x64: ISO: 17763.1.180914-1434.RS5_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-GB.ISO SSU: windows10.0-kb4499728-x64_36248692f756ec842e644b8b79fb7e1c0d64085d.msu CU: windows10.0-kb4494441-x64_8910e3c3ee2743e9ff1241557a5c447ef853f495.msu
I'll do a quick test with 17763.1 ltsc x64 en us to see if I get any sfc errors but not till I get home from work in about 9 hours lol.
MSMG has enough to do without delving into how to modify the toolkit to support any refreshed image you want to throw at it. I think what he is doing now is more than enough. He is doing this for free. I really don't get why it's so hard for some people to work with an original image? It couldn't get any easier.
darn been busy, so many pages, anybody got a quick short summary for me on what important stuff isnt working atm? time for me to make a fresh 1903 image. i mostly remove useless components, i dont integrate anything except drivers and updates. and have my own script to disable certain features. basically just wanna debloat.
@MSMG i tried to remove windows apps but got error "unsupported windows OS image service pack Build". I tried multiple times but same error. Hours of time wasted. My Image version is 10.0.18362.53.0 So upto or which windows 10 pro version is supported. and which version of Window LTSC 2019 IS supported? please help
The MSMG Toolkit supports only non-refreshed images You have to download 10.0.18362.1 Here is the link https://forums.mydigitallife.net/th...ump-download-windows-10-uups-with-ease.75052/
But you must know that the latest MSMG Toolkit 9.3.1 does not fully support 10.0.18362.1 I hope MSMG will release full supported version sooner )