Is the source is v1809 LTSC/Pro or v1903? Map control is the component required for Maps App, apart from that the app needs the VCLibs, .Net Native Framework and Runtimes. The Toolkit doesn't remove the VCLibs, .Net Native Framework and Runtimes.
No, no I strictly follow your steps from readme always! First, I removed components and then integrate WHD updates. Those above are what I removed/disabled/enabled - nothing crucial. This starts to happen from version 9.4.0. It is frustrating never had such an issue before! Tried couple of time with different settings but the result is the same This happens when editing LTSC When I am editing Windows 10 PRO everything goes smooth without any error but I get the blue screen of death with barcode just after Getting services ready and before OOBE. I get the blue screen with the PRO even if I do not integrate WHD updates.
Did you ran the image cleanup twice as specified in the readme.txt?, will check with removing components and integrating the updates and report back.
Yes twice, first time after integrating components and before removing packages (Note: Only if using Step [F]) and a second time after customizing the Image and before integrating tje Frameworks 3.5 and 4.8 Thanks
1809 enterprise I'll do a clean install again to test and double confirm. If you don't mind, do test as well.
Yes I know, as I have said before I'm working on to fix the components getting returned and also to add support for images with updates integrated. And so I've been testing a new version to support W10 v1903 images with updates integrated and so far the build as passed for two recent CU's with minor changes, based on future CU's the development will move forward if it's feasible or else will stick back with the base image without updates and possibly with a fix for component's returning. Will be posting a new test version of ToolKitHelper.exe today with support for v1903 (en-US) with current CU integrated for user testing and feedback. Since v1909 is v1903 + CU + Enablement Package, I'm thinking of whether to dump v1903 totally and move on with v1909 if MS releases fresh LP's for v1909. One more problem was with the x86 Enablement Package which wrongly set the architecture key to amd64 for x86 images and this was causing issues with ToolKitHelper in detecting the architecture, I don't know whether it's fixed or not yet, only will be known when the x86 ESD are available.