does not work anyway. why? can not understand host OS W10 v1709 x64 en-us modificate image W10 v1709 x64 en-us multi original VLSC iso
It's always better to keep the path as short as possible, some pckage names and paths are already deep, when it goes beyond the max. limit, it won't work anymore.
You can try to do it in the next order: 1)Mount clean image 2)Remove System Restore 3)Remove other advanced components 4)Remove all (non-advanced) components 5)Remove Metro-apps 6)Integrate all you need 7)Apply changes 8)Rebuild image 9)Make ISO This worked for me.
This applies to anything. Files, programs, scripts, etc. Windows has a hard limit on path length, which can sometimes cause issues. It made sense to try this, because Windows packages are named quite lengthy, and that combined with storing them in several layers of subfolders can lead to various issues. From what I read, I think this didn't fix the issue, but, just wanted to elaborate on that Always try to avoid using lengthy paths in Windows.
What about my error? Need to run Start.cmd or ToolKit.cmd? Need to run ToolKitHelper first? AV is off. How this is works???
Thanks for the updates MSMG, 7.9 seems to have resolved the earlier issues. First, everything worked as it should with 7.9/1629915/en-US. integrated DX9.0c and the update to 1629919. All Metro Apps and Windows components removed - I left Edge. No errors and the resulting image installs and seems to work as expected. Second. What would be the best way to integrate scripts to disable services/tasks. Thanks.
The new method is only for Windows Defender, SmartScreen, People Experience Host, Xbox Game CallableUI and that too only for W10 RS3 en-gb/en-us and only when removed using menus from Remove Windows Components or Remove Advanced Windows Components.
The ToolKit calls the ToolKitHelper.exe from <ToolKit\Bin\ToolKitHelper.exe> path and if this changes then you get that error. May be using other features of ToolKit in combination might be changing the current path of ToolKit and so it's giving that error. I advise you to remove the components that uses the ToolKitHelper.exe at last and see if it works.
Use the [3] Import Custom StartMenu Layout from XML File from Customize menu, this will remove all tiles from StartMenu and Creates only One Notepad Shortcut Tile, which you can un-pin later. If you want remove all tiles from StartMenu, then you need to edit the DefaultLayouts.xml inside the Mounted WIM Image. Removing Store Purchase App should work But I haven't tried it yet.
It seems some combination of Component removal along with the new method is causing the reference assembly not found error for Search, Store Client and System Restore. So I do advise people to remove the features that use the new Component removal engine at last and try out.
The ToolKit doesn't work if there is a space in between the folder path, make sure it doesn't contain a space.