You can use builds below the upper limit of the support. I used it with 19044.1706 homebrew ISO and it went fine. EDIT: Nope, don't do it.
Yes by the time the next update to Toolkit is released it will come with next Patch Tuesday update support.
The debug files are different for 22621 build, if you don't use the crash debugging feature then you can use it.
I didn't realize this. Good thing I didn't deploy the build on my PCs yet. Still in VM. I also used it on an Enterprise IoT LTSC 19044.1288 ISO from MVS. Seems like it did break updates to newer CUs since I'm getting a 0x800f0988 error when installing updates. Tried a lot of troubleshooting but to no avail. This must be the explanation. Thanks! I'll download 19044.1 and start over. EDIT: But how do I get LTSC 19044.1 ISO? Got it for the other editions using above mentioned method.
All 19044, 19043 and 19042 iso's are 19041 with enablement package. 19041.1 is the base iso for all current windows 10 versions(20h2/21h1/21h2).
Right, so what I downloaded was 19041.1. So instead of keeping a build that old I just bit the bullet and used the latest one (as of now, 19044.1739) which is supported by this toolkit for component removal. I will proceed with this but my question is if I wanna do a component removal on LTSC 19044.1288. How can I do that?
Both won't create a 19044.1 ISO. 19044.1739 is an Insider release preview update, when installing that build you will get older OOBE update installed during OOBE when connected plus it can and most likely will be problematic at the next LCU install.
Well, I'm coming on forum after a couple years now so I just wanted to remove some useless system apps and the other pre-loaded apps from recent ISOs. They have so much preloaded apps now it's just a horrible experience after a fresh install.
It will work but if you do the update after the component removal then removed components except Windows Apps do return due to Microsoft new update package system.