Is the sxs folder still in the sources folder or did you only copy the wims to dvd:\sources? There was a bug before, iirc, the kit first checks if the original sxs folder is present. There is no netfx35 package for msmg for rs4 available yet.
The kit searches for the .7z packaged pack. Manually it works: Code: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:d:\ToolKit-v7.7\Mount\Install\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.17025.1000 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:d:\ToolKit-v7.7\Mount\Install\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.17025.1000 Processing 1 of 1 - Adding package Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~10.0.17025.1000 [==========================100.0%==========================] The operation completed successfully. C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>
manually i did n it works well i knew but what if i mounted 11 images and want to enable it in all images , that is why i was asking , by deployement kit it takes too much time and energy , any way thanx for helping
14093 and earlier, keep the Xbox Identity Provider App. 15063+, all Xbox stuff can be given the heap-ho and Store will work fine. You need to keep the Xbox Identity Provider.
So let MSMG mount all indices at once and copy/paste the commands (adjust to your scenario) in the DISM cmd: Code: DISM /Image:d:\ToolKit-v7.7\Mount\Install\1\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\2\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\3\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\4\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\5\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\6\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\7\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\8\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\9\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\10\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\11\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\netfx3\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\1\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\2\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\3\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\4\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\5\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\6\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\7\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\8\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\9\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\10\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\ DISM /Image:d:\ToolKit-v7.7\Mount\Install\11\ /Add-Package /PackagePath:d:\ToolKit-v7.7\DVD\sources\sxs\dotnet35\mui\
You aren't getting an answer because this is completely off topic for the thread. The topic is about MSMG tooklit, not Nvidia driver issues or Windows issues with games. Just because it is working on an ISO created by MSMG toolkit does not mean this issue or the solution has anything to do with MSMG toolkit... I will give some fast advice though: Clean the driver with DDU and install 388.00. If that doesn't work for you I recommending asking about it on guru3d forums in a driver feedback thread.
Thanks so much for this Excellent and very useful tool. I am using it to just integrate the 'General' updates in an extracted and new generated *.ISO file containing only the 'Windows 10 Fall Creators Update Enterprise x64 es-ES', and it works like a charm. The unical tool who has helped me a lot to integrate without any problem the updates. I have two questions; A) If i make more changes like delete apps (bloatware), delete Cortana, etc, at the ISO and after when installed the O.S. i use the update (with the 'Windows Update Mini Tool' from here), Will the Apps, Cortana, and others appears again in the Operative System? B) If i integate .Net Frameworks and other softwares like drivers, etc, Will they appears good in the O.S. like if they were installed in a normal way? Awaiting answer i give my thanks so much for this magnific tool. Take Care and C U Soon !!!
@ InstantAli3n When this error happens cause of toolkit its not offtopic. Thats what I try to clearify. Just to say in advance this issue has nothing to do with msmg toolkit does not mean it doesen't. Thas just speculative. If the issue comes form the toolkit its ok, no problem. MSMG said before version 7.7 support not Win1709 complete. I use DDU with every driver update but thank you. And yes I know guru3d but when I ask for support I will surly get the answer that I shouldn't use the toolkit. So I try to begann my search and the source. Sure i didn't expect to find gamers in this thread but to say this is offtopic seems unfair to me. @ endbase Sorry, I don't know what you mean :/.
not sure whats up but after applying my usual removals 4-1 and 4-3... or whether or not these have any implication at all windows feels laggy. something is sluggish. anyone feel it?
Yes but till the next toolkit version the removing is incomplete and some services are running in the background. Besides toolkit I'm using the regfile from GodHand. But nonetheless one service defender service stays alive. https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-201#post-1378233
Hail MSMG!!! Tell me what commands need to apply to clear the contents of folders \Windows \ winsxs \ Backup \Windows\winsxs\ManifestCache Thank you
Has anyone noticed that the winre.wim has grown in size substantially after integrating stuff with MSMG toolkit? I had to adjust my recovery partition because the winre.wim would not fit anymore. Dart is not the problem, it seems to be because of the updates. It's now at 505MB, x64. Cheers.
The Toolkit already cleans the \Windows\WinSxS\ManifestCache folder and some others when you save the image. It just does not clear the \Windows\WinSxS\Backup folder. I have made a script that cleans all the folders that are cleaned by the Toolkit (which are cleaned by the scripts to integrate/install updates by abbodi1406) with addition of the \Windows\WinSxS\Backup. However when cleaning the Backup folder I noticed that there is no reduction in the size of install.wim. Spoiler Code: @echo off :: Checking administrative rights %windir%\system32\reg.exe query "HKU\S-1-5-19" >nul 2>&1 || ( echo "Run as Administrator" goto :Stop ) :: Adjust the path of the mounted image set "target=D:\Apps\MSMGToolkit\Mount\Install" :: Main echo Cleaning in %target%... echo. if exist "%target%\Windows\WinSxS\Backup\*.*" ( takeown /f "%target%\Windows\WinSxS\Backup\*.*" /A >nul 2>&1 icacls "%target%\Windows\WinSxS\Backup\*.*" /grant *S-1-5-32-544:F >nul 2>&1 del /f /q "%target%\Windows\WinSxS\Backup\*.*" >nul 2>&1 ) if exist "%target%\Windows\WinSxS\ManifestCache\*.bin" ( takeown /f "%target%\Windows\WinSxS\ManifestCache\*.bin" /A >nul 2>&1 icacls "%target%\Windows\WinSxS\ManifestCache\*.bin" /grant *S-1-5-32-544:F >nul 2>&1 del /f /q "%target%\Windows\WinSxS\ManifestCache\*.bin" >nul 2>&1 ) if exist "%target%\Windows\WinSxS\Temp\PendingDeletes\*" ( takeown /f "%target%\Windows\WinSxS\Temp\PendingDeletes\*" /A >nul 2>&1 icacls "%target%\Windows\WinSxS\Temp\PendingDeletes\*" /grant *S-1-5-32-544:F >nul 2>&1 del /f /q "%target%\Windows\WinSxS\Temp\PendingDeletes\*" >nul 2>&1 ) if exist "%target%\Windows\WinSxS\Temp\TransformerRollbackData\*" ( takeown /f "%target%\Windows\WinSxS\Temp\TransformerRollbackData\*" /R /A >nul 2>&1 icacls "%target%\Windows\WinSxS\Temp\TransformerRollbackData\*" /grant *S-1-5-32-544:F /T >nul 2>&1 del /s /f /q "%target%\Windows\WinSxS\Temp\TransformerRollbackData\*" >nul 2>&1 ) if exist "%target%\Windows\inf\*.log" ( del /f /q "%target%\Windows\inf\*.log" >nul 2>&1 ) if exist "%target%\Windows\CbsTemp\*" ( for /f %%i in ('"dir /s /b /ad %target%\Windows\CbsTemp\*" 2^>nul') do (RD /S /Q %%i >nul 2>&1) del /s /f /q "%target%\Windows\CbsTemp\*" >nul 2>&1 ) :Stop echo. echo Press any key to exit... pause >nul exit /b
Anyone willing to test if windefender makes the running 1709 machine sluggish? It wasn't like this in 1703 and below. How I tested: download sysinternals suite, extract files, copy all files to another folder. without windefender, split second with windefender, a few seconds, maybe more, i dont remember.