You need to check once by installing the OS and see if the system requires and then integrate them But if you integrate them for non-required systems too it won't break anything.
Yes. First thing I tried. It works perfect for all games, including the W7 games for W10 from WinAero. The trick is to find which file.
Damn it. So my only choice is to do it this way; 1. Extract fresh 17763.1 image 2. With MSMG install Samsung NVMe drivers 3. Integrate Win32 Calc, Directx 9.0c 4. Remove All Windows apps 5. Remove 1 system app. Once all system apps have been tried, move onto Advanced Components. 6. Add NetFX3.5 7. Rebuild image 8. Install OS, DISM /online /rebuild-image /startcomponentcleanup once and then test. 9. If it doesn't work, go back to step 1. Steps 1 - 8 take about 2 hours all up. I know I have not listed every step, but that is just for brevity. I am following the readme.txt every time. I am not integrating updates for reasons of time and just trying to keep it as simple as possible. It's also possible one component is not causing the problem. So this get really complex if I get to a point where I have to try every possible combination of two components at a time. I'll cross that bridge if I get to it.
Why you do all the steps, just - Mount the Image - Integrate Samsung NVMe drivers - Integrate DirectX 9.0c - Save and Rebuild the Image Now make a copy of the install.wim to be used as base image for further tests. - Mount the Image - Remove All Windows Apps - Save and Rebuild the Image - Install the OS and check with Games Pack, if this works then make this image as the new base image - Mount the Image - Remove first 5 System Apps - Save and Rebuild the Image - Install the OS and check with Games Pack - If this works then make this image as the new base image, If it fails then discard the image and use the previous base image and remove the first 2-3 components out of the 5 Apps and then do the test again Repeat the steps for rest of the components in a set of 5 Apps/Components, then you can finish it soon.
"DISM /Cleanup-Image /StartComponentCleanup == DISM /Cleanup-Image /StartComponentCleanup /ResetBase" - It's correct in Windows 10. Dism++ uses this way to make the cleanup process fast. (Because without resetbase, the OS will use the delta.) But I don't think it is a good idea. Because the Microsoft has released some updates which the KB number is same so you may need to install your OS instance. (If you enable the Windows Insider, even the Release Preview.) Also, I hope you can modify the credit info in the ToolKit.cmd because NSudo is belongs to M2-Team and Dism++CUI is belongs to Chuyu Team. Thanks. In the end, I want to get suggestions of the future version of NSudo from you. Mouri
[/QUOTE] 16. Install the OS. 17. Run DISM / Online / Cleanup-Image / StartComponentCleanup / ResetBase once[/QUOTE] Hi I'm reffering to #9365, and am a bit confused what to do with Nr.17 (Run Dism ..) after installing the OS. Where to start ? Powershell ?, CMD ?, MSMG ? Thanks in advance
16. Install the OS. 17. Run DISM / Online / Cleanup-Image / StartComponentCleanup / ResetBase once[/QUOTE] Hi I'm reffering to #9365, and am a bit confused what to do with Nr.17 (Run Dism ..) after installing the OS. Where to start ? Powershell ?, CMD ?, MSMG ? Thanks in advance[/QUOTE] run cmd type the thing and enter wait
Yes will update the credits part with the corrections. NSudo is too good and does the job perfectly, will let you know if I have any suggestions.
@MSMG https://forums.mydigitallife.net/th...07-194-253-pc-rs5.77945/page-234#post-1497745 I want to confirm that you are working on 17763.253 as a base image in case MS has updated that since you started working on RS5.
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).