Yes. I tried integrating the cumulative update only but the same error. KB4025342 also has this error. I will try your suggestion now.
Any GUI that is mass removing integral system applications, programs or files is going to mess up updates. Windows 10 v1703 is extremely more sensitive to any form of corruption than v1607. Though these programs like NTLite work well at the surface and will do what you want, the truth is that they simply cannot remove full system components cleanly. In order to do that you need to use the DISM API to allocate all package structures into a heap and map the complete offline image's contents to a supported directory where it can be queued for complete removal from the offline image using the DismDelete function. This is the only way I will even consider adding a custom Windows installation to the Microsoft Deployment Toolkit on my server, so I ONLY use PShell, VBS and C# scripts as DISM API wrappers to service WIMs. Lastly, there are many ways to actually disable, and even prevent from even installing during setup, pretty much everything in Windows by using registry key additions, changes or removals that will not only make the system appear like you used NTLite on it, but also maintains the integrity of the system so Microsoft's servicing and update features work properly. Most people are not familiar with editing services, Group Policy, registry hives, layout designs, etc. in an offline image unless they have a Windows Server they also use for custom Windows deployments and have spent time with Microsoft Deployment ToolKit and Administrative ADMX templates. That said, the same custom scripts one can create for server deployments using these server tools can also be used on client computers for image servicing.
It went wrong because the integration of the non dism integrateble update, when left out it should go fine with the sstack, cu and flash.
Which is exactly what it does on the backend. The difference is it puts it into a user interface that the average home user could understand, as opposed to showing you lines of code executing in a command prompt (which it does do, in the background, out of view). Giving a user interface to a script does not make it a poor one. Even MSMG has plans to add a user interface.
I hope he gives us a decent UI. I found that NTLite UI extremely difficult as well as the DISM++ interface. I will NOT use either. I would rather use MSMG as it is today or write my own scripts (which I do) than use a bad UI.
This update does not need to be integrated into the image! You just need to unzip this update to the /Sources folder.
I understand why people like it, and I'm not sure what viable wrappers are executing lines of code in a command prompt for you to just stare at. And I can safely say that if more people relied solely on the execution of commands and code, then that would be an utter disaster and forums would be flooded with "HELP!!!" requests. I am not old, but I can remember back to when we had to use DOS for a lot of things on Windows. No pre-installation environments, no built-in troubleshooters and no system restore. It was great for those who knew DOS well, because you could do anything with it, but it was unforgiving if you made a single mistake. There are people on this forum that were unable to use install_wim_tweak commands without ruining something, and that's as basic as it comes regarding commands and system component removals. Nah, GUI tools are fine. My original post was never intended to make it seem otherwise. I was just saying that when it comes to the ease of how NTLite works, and the fact that most of the descriptions for what a component does are either missing or confusing, the end result will likely be less than desirable. And as of late I've had a lot of people say they can't use a lot of various features in Windows after modifying their image with it (mainly Windows' built in troubleshooters fail, and the system can't be updated due to package failures). Besides, I was speaking fairly exclusively of NTLite since that's what his comment was about. MSMG would always be a no-brainer choice for me if I had to pick between the two. AND THAT'S MY .2 CENTS!!
Fair enough. Nothing wrong with having an opinion, we all have our own. I originally mistook your post as you suggesting that NTlite did not function correctly. Which is exactly what it does on the backend. Which is why I felt the need to point out the difference is it puts it into a user interface that the average home user could understand, as opposed to showing you lines of code executing in a command prompt (which it does do, in the background, out of view). I too recall the old day of using DOS commands. Being someone who uses Linux more and more, as opposed to Microsoft Windows, I still find myself using terminals regularly. But even on Windows 10, using a terminal (command prompt) can still have its uses. But I am one of those individuals who continues to look forward to using it less and less. Perhaps as I get older, while the knowledge is there, the will is not so much. Sorry I misunderstood your first comment.
My taskbar doesn't work at least once in a day so I have to restart explorer.exe. I don't know if this is caused by this tool.