Yes x86 doesn't offer anything better than x64 but it's just that my Laptop specification is not suitable for x64 OS.
Yes did that too first integrating DX9c and then removed the components from an image without any updates and still couldn't replicate the error.
Yes the image tested was Russian (ru-RU) 17763.1 without any updates and the MapControl was removed when System Apps was removed. Will checkout tomorrow with only removing Map Control and see the result.
It's obvious many of you live in first world countries where you can get a relatively modern system without spending a 2 months salary. Here in South America, x86 is still popular because of systems with 2GB DDR2 that are not really suited for x64. Cheers.
the metro was removed via dism, the toolkit 9.2 used to remove the map control, as a result, the system did not pass the sfc / scannow check.
I have made a little progress with error I was receiving. If I replace ToolKitHelper.exe in Toolkit v9.2 with ToolKitHelper.exe from v9.1, the Toolkit does not produce any errors. Something I have noticed, however, is the process is much slower. Toolkit v9.1 has ToolKitHelper.exe v1.0.1404.0 Toolkit v9.2 has ToolKitHelper.exe v1.0.1512.0 I do not like to say this, as I know how work @MSMG puts into this Toolkit, but it seems like ToolKitHelper.exe is at fault here and not my system.
Try removing these Apps and System Apps + Advanced Components using ToolKit WalletService StickyNotes Photos CommunicationsApps Camera Calculator BingWeather Alarms 3DViewer AdvertisingXaml DesktopAppInstaller FeedbackHub GetHelp Getstarted HEIFImageExtension Maps Messaging MixedRealityPortal Paint3D People and remove the rest of Apps using the DISM.
The slowness is due to the code protection added to the .exe ToolKitHelper.exe v1.0.1404.0 compiled using VS2017 ToolKitHelper.exe v1.0.1512.0 compiled using VS2019 RC2 But that shouldn't matter since I did the testing on a different system without the VS installed it is working, the ToolKitHelper.exe only requires NETFX472
Code: Microsoft Windows [Version 10.0.16299.1029] (c) 2017 Microsoft Corporation. All rights reserved. C:\Windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. I'm not sure what to do now, the problem still exists.
@MSMG I have now tested this on a laptop with Windows 10 Enterprise 1809 x64 and I get the same error.
I can confirm this. On the removal stage, nearly all components error out with the same message as posted by others. Only two components removed OK: Microsoft.Windows.PeopleExperienceHost and Microsoft.XboxGameCallableUI. I've finished the image regardless, but still have to test if it works or not. Edit: Installed fine, but Windows Update was broken, it did not install the CU that was (strangely) offered again. Also, camera app and alarms and clock were not working. I've missed something but don't know what. As there were only a few appx bundles in the apps folder, I had to download some of them from adguard. No big deal and seemed to integrate fine. Here's the error I got while removing, source OS is English LTSC and target is Spanish LTSC: Cheers. Edit: Some more info about my workflow... - Used first released LTSC - Integrated updates downloaded with WHDownloader and integrated with Abbodi's W10UI - Mounted the resulting images with MSMG - Integrate Edge, alarms and clock, camera app, store all ok - Integrate DART and DX9 - Proceed to removal stage and error... Last edit: SFC came up dirty. Fixed some errors but the CU still did not install from WU. Trying manually with the installer says it is already installed. The two apps sorted out themselves, opening the store updated something and they started working. Sadly this round was not successful.