Few more updates: - As we all know starting from Windows 10 Post RS1, the win32calc.exe functionality is broken (Unit Conversion) and only the TH1/RS1 win32calc.exe is fully functional, so I'm planning to use TH1/RS1 win32calc.exe for all Windows 10 versions from now on. - Windows Accessibility Braille, OpenSSH Server, Developer Mode .CAB files aren't integrating with Windows 10 RS5 image and so I'm dropping these features for the next release until it's fixed.
Going to be fun testing this out. Every time i get stuck working on a stock Windows 10 system I always get the same feeling "uuuhhh, thank god this toolkit exists".
I have never seen a compelling reason to let Windows update drivers. We are in a custom image thread so its probably a good place to mention that your custom image should include all current drivers and updates, first boot should show nothing in windows updates at all. From there it is easy to keep up to date as most drivers do not change that often and even if they do, the manufacturer's website usually has the update first anyway.
I believe the "removal game" is to remove stuff without breaking other functionalities, and many older (and most current) hardware run fine on drivers provided by WU (some hardware like my Asrock Rack CW2018-S mainboard isn't even supported on 10 (no specific 10 drivers available at the official) support site) and the WU provided drivers work fine.
MSMG, could you make some sort of FAQ with a list of all known repercussions caused by deleting windows components? Everything that you know and what people from this thread have reported. That feature would be extremely useful!
Even if you want to use them you can do a preliminary install, grab the drivers, export them and then add those same drivers into your base image prior to toolkit removals and avoid the whole update issue outright.
I don't think that is true for everyone. Chopping an image down can be part of a greater strategy where the initial image is also the final image, no updates needed. Ever since I found this project I have been building images complete with drivers, updates and removals.
Why would you do that? Just do it with the installer, post deployment. Edit: And as I remember correctly, to install Office it is necessary to be logged on. You may be able to start the Office setup as a firstlogon.cmd specified in the answer file. Cheers.
Just found out that the problem was not with the .cab files but instead it is with the Windows 10 RS5 or RS5 DISM that it won't integrate the FOD cab files without their original filenames, for e.g: Windows Accessibility Braille integration works with the below filename : Microsoft-Windows-Accessibility-Braille-Package~31bf3856ad364e35~amd64~~.cab But not with the : Microsoft-Windows-Accessibility-Braille-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab Same is the case with other FODS like .NETFX 35
Creating a pack for Office is a huge task but as @Supern00b said you can use the firstlogon.cmd specified in the answer file. If you still insist to have Office to be integrated within the image then you can use the Office Desktop UWP Apps and the current ToolKit can integrate Office Desktop 2016 UWP Apps, When Office Desktop 2019 UWP Apps are available then the ToolKit will also add support for it too.