I have a new found respect for people who test these tools. It's a laborious task. OK, so all I need to keep in the install.wim. What about Netfx3. Once it's integrated doesn't that break something? I've narrowed it down to one of the advanced Windows components.
Probably not, LTSC or Server 2019 don't get refresh iso's and iirc MSMG Toolkit is always based on the baseline iso.
If I just want to remove one or two components to know if I'll have problems do I need to go through all those steps (Cleanup Source Images, Component Removal, Cleanup Source Images, Apply & Save Changes to Source Images, Rebuild Source Images and Make a DVD ISO Image) in RS5 (and not only) instead of only following the Component Removal, Apply & Save Changes to Source Images and Make a DVD ISO Image steps (or even following the Cleanup Source Images step before this two and after the Component Removal one) or I might have even more errors or different results? I don't want this process to take so much time when only one component is at stake and I just want to know if I might have errors in a future install after I only follow some of the steps.
No need for multiple cleanup sources images, just do one at the end (before you set the pending flag).
The baseline ISO is not longer available to the average Joe/Jane, they would need to dig for that. Sure its easy for the geeks but most less experienced people will just grab the base image from the media creation tool and start modifying. We should let MSMG weigh in on what is best here.
The new baseline is 17763.107, only because 1809 got a total re-release, ALL sku's were re-released, normally they never release refresh iso's of LTSB/C. And they still don't, only Consumer and Business ISO's got refresh iso's, 17763.194 and 17763.253, LTSC only got 17763.1 and 17763.107. In the past, the toolkit couldn't handle refresh (already updated) iso's at all.
But in the README it states in the RS5 case (at least) to do it two times (steps G and I), before and after the component removal. At least I have to delete the ISO content every time after creating an ISO (and extract it again afterwards before doing another operation), right? It states in the README that removing Internet Explorer breaks Settings->Apps->Default Apps->Web Browser but I removed it and in my case it didn't. It also states that SFC /SCANNOW can throw errors and restore the removed components and although it detected some corrupted files and successfully repaired them Internet Explorer didn't return (at least it doesn't appear in the Optional features list and iexplore.exe didn't return).
Let me ask this a different way. Let's say someone uses the media creation tool to grab 1809 and then tries to modify it only to discover an error with MSMG, what is offered as support?
taking Windows 10 User's comment a step further; Which is what installing NetFX3.5 does?? So if I was going to do multiple tests removing one or two components at a time, I'd be best NOT to integrate NetFX3.5?
Just do .net 3.5 post deployment with Abbodi's installer. It's quick and you don't have to deal with the pending flag. Cheers.
I never do use a refreshed image as a base image unless it's entirely a new build with new refreshed language packs.
.NetFX3 will be integrated at the last and so when you have the working image then you can integrate it, it won't break anything. Which is the component that broke Games Pack.
There' s no other way test which component is breaking unless you know what the error is associated with. If you are doing just the component removal then you need to do the cleanup twice, once before and once after the removal otherwise the cleanup will give errors after the component removal an that's why I have advised to do it twice. Component removal is like beta testing your OS, today there might not be having issues but tomorrow may or may not the bug can crop up.
Do you know if I remove .NET Framework 2.0, 3.0 and 3.5 and the .NET Cache Assembly and configure Windows 10 to always use the latest CLR for .NET Assemblies I might have problems with certain UWP/Win32 apps (like old ones)?
Yep I had this. Even when set to always use the latest .Net, some app would break if 3.5 was not configured. I would certainly like to get rid of it, but can't risk to break apps that need that specific version. Cheers.
I don't remove those which you speak, but I don't add the .NET3.5, and configure Windows to always use latest CLR, and don't run into any problems.
Still working through it. The latest image has removed items A,B,D,E,F,G,H,I,J,M from advanced components. Should be ready to test shortly.
MSMG: If I do not remove / 1. MSMG: If i do not touch any of these, but remove others, i wont get sfc errors right? 2. that rd /s /q del /q -- how does this affect anyone who used v9.1? I plan to do an important deployment tomorrow and I can't delay it any longer. I need to know what's on the line.