Does ltsc 2019 file have ProductKey setting? either remove it or add KMS key (it's the same for ltsc 2019 and 2021)
Thanks Abbodi1406 Actually Ltsc 2019 does not have any ProductKey setting A month back , i was able to install ltsc 2021 with 2019.Ltsc autounattend.xml but something changed and it does not accept 2019.autounattend.xml anymore I dont know why P.S. I used MSMG toolkit and i removed all packages for getting a de-bloated iso Can the error occur because of this ? Any ideas ?
Is it possible to convert LTSC N 2021 to IoT? I'm having some trouble so thinking the N may be the problem here, but would like to confirm.
Clean install is an extreme measure that should be taken in a really worst case scenario. An in place upgrade would be more than enough to fix 99% of the troubles, in this specific case MFP should be sufficient.
Don't be that destructive Sure N is pointless for the typical end user needs. But if you need a lean VM for a specific purpose that has noting to do with multimedia, N can be the right choice
This is the 1st time I've heard of Regulated Packages. I'm always behind. Can someone explain and should they be installed? There are none listed in my Packages.txt for LTSC 19044.1415
It allow to install Wireless Display cast, and some Media codecs it's system package, it does not show up normally with support editions (non EnterpriseS) any package added manually will be visible in Packages.txt
I'm a huge fan of debloated Windows versions, but in my experience N versions don't remove anything substantial that would increase performance or save a significant amount of space. As far as I can tell, you basically just get the same Windows version but with the missing media codecs and no windows media player and a few other minor things. I don't really see the point in this situation. The difference is so minor. I think you only save like 30-50mb or something. To each their own, but it seems like there are more downsides with missing codecs and potential activation issues than upsides.
Sure they are. You are talking about the hard linked files, but in such case the number wouldn't be 11GB, would be, as in the screenshots above, 14GB or so Don't confuse the miscalculation done by Explorer with the real space taken at block level BTW you can reach the same conclusion, just looking at the size of the MFP package, it's in the range of 120/150MB when compressed, once it's expanded you are back in the 400/500MB range. No matter how you put it, math don't lie.