The Windows v1903 component removal is yet to be started, when I do add it, it will support all languages.
UPDATE 2 This time I used v17763.1 instead of v17763.107 and both DISM and SFC scans were clean. Everything seems to be working fine. I'm running Windows 10 LTSC en-us x64. RESULTS DISM: No component store corruption detected. SFC: Windows Resource Protection did not find any integrity violations. List of removed apps and components in categories: PREINSTALLED ADDONS & MEDIA - AADBrokerPlugin - AdobeFlashForWindows - EdgeDevToolsClient - GameExplorer - InternetExplorer - KernelDebugging - Paint - SkypeORTC - SnippingTool - WindowsMediaPlayer - WindowsPhotoViewer - WindowsReaderPDF BLOATWARE - AssignedAccess - AssignedAccessLockApp - ParentalControls - PeopleExperienceHost - QuickAssist - RetailDemoContent - WindowsMixedReality - XboxApp - XboxGameCallableUI PRIVACY - BioEnrollment - ContentDeliveryManager - CustomerExperienceImprovementProgram - FaceRecognition - LocationService - MapControl - SettingSync - UnifiedTelemetryClient (Asimov) - WindowsErrorReporting @MSMG
Thanks for testing, next time when you do the test, please do remove all components and share the result as it will be to helpful to know the overall results. One suggestion, do avoid those colors in the post, use plain black color for posting, it will be helpful to read without straining the eyes.
Sure will do I was actually planning on testing that as well! I'm using the dark version theme on MDL and did the colors according to that and the severity levels of the apps/components. But I'll make sure to use plain colors next time, sorry I'm also happy to see many more users reporting good results, may the success continue and hard work pay off for all contributors. Thanks to all the developers and testers!
Each one has its pros and cons. Test the 2 (VirtualBox and VMware) and see which one pleases you the most. My personal experience is that VMware has better overall performance and better compatibility and performance with varying graphics environments (Linux in that case) so maybe it performs better with the Windows 10 graphical environment. But I have not tested Win10 in VirtualBox. My tests were done with Windows 10 OS as a host.
Why the wrong order? W10 pro x64 en us 17763.1. I know I did the integration and component removal reversed but I remember msmg once said its better to remove components before update integration So I thought since msmg got an error with the x64 image he created I would try that order (assuming msmg did the updates integration first) and I saw no errors whatsoever
No you did as I requested you to do the test and it's working for you but for me it's giving setup error for x64 bit images. Earlier for 32-bit images it was working now with the latest CU it's giving some error at OOBE and proceeds to desktop after sometime. I will re-check the image with a new compilation of ToolKitHelper.exe and see if it works and also will upload a newer version of ToolKitHelper.exe today for user testing.
Are you referring to 17763.437 or the 439 that just came out yesterday I used 437 Btw I will try the same thing but this time everything will be removed (meaning IE as well)