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)
MSMG just a quick question Is there a reason I have to mount at least the recovery image as well to be able to integrate the updates?
The option was added to keep the recovery enviorment to be too updated but in the next version I have added another option to integrate updates to only install.wim. You can mount the image with the Toolkit and remove the componetns and then integrate the updates separately using a command prompt and then save back the image using the Toolkit.
Ok-----Did another test with w10 pro x64 en us 17763.1 1-integrate intel management interface driver 2-integrate calculator and direct x 3-cleanup source image 4-remove all windows and system apps 5-remove all advance components 6-cleanup source image 7-integrate the ssu update,.net update and cumulative update(latest cu update 17763.475) 8-cleanup source image 9-customize image 1,2,4,5 10-apply and save 11-rebuild Install went fine,sfc scan passed,windows update was fine---all seems fine
Did another test but this time with w10 ltsc x64 en us 17763.1 with this procedure. Once again everything went perfectly. 1-integrate intel management interface driver 2-integrate calculator and direct x 3-cleanup source image 4-remove all windows and system apps 5-remove all advance components 6-cleanup source image 7-integrate the ssu update,.net update and cumulative update(latest cu update 17763.475) 8-cleanup source image 9-customize image 1,2,4,5 10-apply and save 11-rebuild