Whick key? So, which is quicker, manually extracting the ISO contents and loading them in MSMG or let NTLite extract the ISO contents and afterwards load it or it is indifferent?
- [6] Customize -> [5] Tweaks -> [9] Enable DISM Image Cleanup with Full ResetBase - ToolKit uses the command-line 7z.exe to extract the ISO and NTLite uses Windows Api function, don't know which is faster better you do the test.
Directx 9.0c - Of course! We have several old games that require it. WER - Me neither - Originally I just removed everything. When I left Parental controls in the image, I I left these other two in as well. I wasn't actually looking for a solution to why driver installs seemed to be hanging... I just noticed that when I left those components in the installs run at normal speed. Perhaps it was just a coincidence. Once I get this damned audio issue sorted out, I'll take another look at that one.
No problems. I tried using DISM /online /remove-package /packagename:<blah> and whilst dism said it worked, the packages were still there. I can say with reasonable certainty that the Windows Apps that are NOT causing the loss of audio because I removed all of them and audio still worked.
Ok, but how can I know if it will appear in WU after I install Windows 10 in the host before installing it in order to know if I should integrate it or not?
Ok, did you tested the games pack with untouched image, is the sound working for Games? May be some dependent file is getting removed when the components are removed.
Yes DISM won't fully remove the package. Better check with System Apps and Advanced Components by removing a set of component and test the OS, if it works then proceed with the next set of components.
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.