HA! I think I know what the problem is - the file structure of what is inside DVD folder changes after all the changes I made - the SOURCE folder has only 6 files in it and original ISO had way more. What I did to make it work is simply extracted original ISO into DVD folder, and then replaced WIM files with mine and NetFX35 was detected just fine.
It does not say anywhere that "Removing this will prevent the toolkit from detecting NetFX35 folder". I have installed this OS without MANUAL SETUP and it worked fine and how would that affect Toolkit's ability to detect its own NetFX35 folder???
Not any developer can be prepared for what you throw at them, you never do something the same twice, you ask one thing and before someone answers it you already did something else.
Did you use the right version of .net 3.5 pack? There is 4 diff version if you are integrating on RS2 then you should use the NetFX35_W10_RS2.7z.
This is posted by MSMG and I have revise to reflect the latest changes. For Win10 1) Integrate all the features you want to add except for DirectX 9.0c and .NET Framework 3.5 using the Integrate Feature Menu. 2) Integrate the Language pack you want if required 3) Integrate the Updates. 4) Remove the Apps you don't want 5) Remove the Components you don't want 6) Apply Changes, this will perform the Cleanup 7) Re-Mount the Source 8) Add the .NET Framework 3.5 using the Integrate Feature Menu. 9) Add the DirectX 9.0c using the Integrate Feature Menu. 10) Apply Changes. 11) Re-Build the Image
If you have added custom files like drivers and etc be prepared that the file size will grow exponentially even after rebuilding the wim with maximum compression, it is impossible to reduce the size unless you manually remove some of the original drivers that came with win10 and add in the driver you want to integrate.
I don't understand why people feel so difficult to Integrate .NET Framework 3.5 and I have specified many times in different post The ToolKit searches for "microsoft-windows-netfx3-ondemand-package.cab" in <DVD\sources\sxs> folder and if it available then it will start the integration process. If the "microsoft-windows-netfx3-ondemand-package.cab" is not present in <DVD\sources\sxs> folder then, the ToolKit will search for "Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~<Architecture>~~<Version>.<ServicePackBuild>.cab" file <Packs\NetFX35\w10> folder and if it available then it will start the integration process. For example: "Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~<Architecture>~~<Version>.<ServicePackBuild>.cab" for Windows 10 Redstone 2 would be x86 - Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~x86~~10.0.15063.0.cab x64 - Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cab If one want's to use the NetFX35 Pack, then download the correct NetFX35 Pack file for example NetFX35_W10_RS2.7z to Pack folder and right-click on the Pack file and choose extract here, which will extract the NetFX35 folder to Pack folder, So that the resultant folder structure will be <Packs\NetFX35\w10>. This extraction method applies to all the Packs files made for the ToolKit.
Removing Manual Setup will remove the files/folder required to setup Windows from Windows Explorer (In-Place Upgrade) And so it leaves only the files required for Installing the OS by Booting from the Installation Media.
You can do Integrate DirectX 9.0c with the new pack without issues it's only the NetFX3.5 needs to be integrated at the last and one more thing Removing Manual Setup should be done only after NetFX3.5 Integration as this will remove the SXS folder and if there's no NetFX35 files present in the Packs folder then you can't integrate NetFX3.5
yep still MSMG is very simple install NETFX3 after system installed and runing only using media (DVD) using Dism I think several people's have a lot of lazy is not possible that them don't know how to make this
Bah, what I did worked! Both NetFX 3.5 and that other DX9 pack worked perfectly. That is exactly what I wanted and that is what I got - an install.wim with 2 of those things working! Yey!
FYI, I copied Install.wim made with Manual Setup removed into original ISO extracted into DVD folder, integrated NETFX 3.5, then moved the Install.wim BACK into DVD folder that had Manual Setup removed, ran another WimLib CLC Optimize pass and made an ISO, from which I got that near-perfect Windows installation... Not perfect because the SysWOW64 version for the TestSign package was not removed, but that is my fault - I had no idea or memory of there being one and I had to spend good 30 seconds of my precious time using CBSEnum to get rid of it! I hope something can be learned from all this: - Manual Setup is not required for NetFX35 integration (at least if you are willing to do the copy back and forth trick I did) - The Other DirectX 9 package works - MonarchX makes the impossible possible by randomly trying this and that "fudging"
You again missed what I wrote in my previous post Removing Manual Setup will remove the sxs folder from DVD and also if you don't have the NetFX35 files at <Packs\NetFX35\<OS>> folder, then you can't integrate .Net FX35 as the .Net FX35 files are not present in sxs or <Packs\NetFX35\<OS>> folder. This doesn't mean that Manual Feature is required for NetFX35 Integration but instead What i meant was the order of Integration. By copying the modified install.wim to original ISO extracted into DVD folder and integrating NetFX35 will definitely work as the sxs folder is there.
I have a similar problem. remove all Apps and Components. clean install adjust Date/Time pin something to start Windows 10 15063 Enterprise x64 en-US