Facing the same problem here Windows update taking ages to download the update Did you find the cause? Has to be one of those windows components.
I've notice WU does take a long time to check for updates. But I don't think it got to do with this toolkit.
Check the download links I have upload the Language Pack for es-MX W10 RS2 x86/x64 required for ToolKit.
Yes I do sometime use the WU on my spare PC to get IP build and it worked properly without any issues.
I saw that in WU after disabling the Microsoft Account Sign-in Assistant service. If you have it disabled, try setting it back to manual.
wim ServicePack Build is defined by kernel32.dll version inside the image it seems got updated for RS1 not sure if you use wimlib but you could rely on this mum file to detect image build info Code: wimlib-imagex extract install.wim 1 Windows\servicing\Packages\Microsoft-Windows-Foundation-Package*.mum --dest-dir=temp --no-acls >nul for /f "tokens=4,5,6,7 delims=~." %%i in ('dir /b temp\Microsoft-Windows-Foundation-Package*~~*.mum') do ( set ImageVersion=%%i.%%j.%%k set ImageServicePackBuild=%%l ) del temp\Microsoft-Windows-Foundation-Package*.mum >nul
Doesn't Nvidia installer also add some registry keys? When integrating then those keys will be missing. So will there be a need to install the driver after OS installation or does everything work when integrating, like playing games and Physx?
Code: =============================================================================== MSMG ToolKit - Integrate Microsoft .NET Framework 3.5 =============================================================================== Microsoft .NET Framework 3.5 Pack folder <Packs\NetFX35\w10> is Empty... Please Copy Microsoft .NET Framework 3.5 Pack files to Respective folder... =============================================================================== The folder is NOT empty... it contains Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~x86~~10.0.15063.0.cab Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cab Why is this happening?
Ok, i can answer myself... MSMG Toolkit points to <Packs\NetFX35\w10> being empty but this is misleading. I just remembered reporting this long long time ago (and once again i got ignored), this error shows when you DON'T have the <\sxs> folder inside <\sources> ... The option Remove Windows Manual Setup Feature under Remove Advanced Windows Components Menu removes the sxs folder but once you copy it back, MSMG Toolkit integrates .NET Framework 3.5 just fine. Hope you can FIX this now...
Yes, and i had to restore it (the sxs folder) copying back from the standard iso in order to work, but what i mean is the MSMG Toolkit is not using the <Packs\NetFX35\w10> at all, even if the cabs are present there and this is a bug that needs to be fixed.