Indeed, there are some bugs that have persisted since 1607. And the two feature updates per year didn't help. Hopefully the 19H1 and 20H1 releases mean MS has moved to a slower annual release cycle. As to the script - It's very personal, and whilst I do have some coding experience I'm not a programmer by trade so it's not very elegant. The services, tasks, firewall rules, telemetry and registry tweaks mostly came from here. Its a generic script that customizes the dozen or so systems I am continually working with - installing the applications that they use. You couldn't use it as is, but maybe you can get some ideas from it. It is far from perfect, is a work in progress and still contains some bugs so if it breaks my PCs that's my fault - but if you or anyone use it and it breaks your PC(s) please don't get angry with me. Anywhere you see XXXXXXXX something has been removed for privacy/security reasons.
Well to me it doesn't matter if it's perfect. It's the thought you put into making it. I like to see users make their own tweaks and scripts, it's fun to see and test. Although I might not be using it because I already have my system set, I will be testing it out
You answered your own question... Yes that is what i said. The (integrated/updated) version of LTSC is v17763.107 and up...
W10 v1809 LTSC already have Win32Calc packages and integrating the Win32Calc (v1609) pack present in the ToolKit will overwrite the original ones and thus causes the SFC to give errors. Note: The Win32Calc packages post v1609 is broken in terms of functionality.
Short repost and results: Yep, I also report success. @MSMG, here is the feedback after making a x64 image: Source OS: LTSC x64 English Target OS: LTSC x64 Spanish Image version used: 17763.1 <--- important, clean image without any pre-integrated updates Integrated: Edge, Store, Alarms and clock, camera app, dart, dx9, WHD updates. Removed: AAD.BrokerPlugin Microsoft.Windows.ContentDeliveryManager Microsoft.Windows.ParentalControls Microsoft.Windows.PeopleExperienceHost App.Support.QuickAssist Retail demo content Customer Experience Improvement program Microsoft.Windows.Cortana First logon animation smartscreen app Windows Defender Microsoft.XboxGameCallableUI Cleanup + Restbase Rebuild image Make ISO Done. The build process was flawless, but I have two comments: 1. The WHD updates offers TWO .net updates, one cumulative and one security. However, the toolkit only processes ONE of them. Should we use another folder ("dynamic update") for the .net security update? It seems that the toolkit only processes one file from each folder. 2. The desktop app installer metro app: At this time the adguard site offers the neutral appx bundle single file. But the toolkit insists on having the older files that are separated (x64 and x86). It would be nice if we can integrate the neutral appx bundle as it is updated. Edit: Deployed and SFC came up clean, all is working. The modern apps worked after updating the app installer package. So far the best result I have obtained since using MSMG toolkit. Cheers.
1) The ToolKit extracts the update to temporary folder and integrates them using the update.mum file. There was only one .NET cumulative update present when I released the last version, Now I have made changes to the next version to integrate all .NET framework cumulative updates present in the .NETCumulative folder. 2) I used the files from the original MSDN v1809 AppX ISO where the DesktopAppInstaller Appx and License files are different for (x86, amd64 and arm64). Don't know whether the Adguard site is giving the DesktopAppInstaller common appx files for all Windows 10 versions.
I also script most of my settings, saves a huge amount of time. Yeah Windows is determined to phone home and do all kinds of activity you don't want. One thing you can do to make Windows less "phone homey" on install is to disable things in the registry while you have the .wim mounted for install servicing. I have a file of reg tweaks I apply to the offline image to keep Windows in check. The file includes tweaks to disable Windows Update and driver servicing. You can modify the registry in the offline image with these commands; Code: reg load HKLM\temp <mount point>\windows\system32\config\software regedit /s <reg file with items using path to temp reg mount> reg unload HKLM\temp You can go a step further by using an autounattend script telling windows not to configure any network interfaces during install. On my install Windows does not connect to the network until I tell it to, then once it does it's idle other than grabbing some certificates which are needed.
I export my drivers, then install them offline. I never have a problem with WU installing drivers which are older than the ones I have integrated.
@MSMG Do we still need to do step "[F] - Integrate Windows Setup Media Updates " if not integrating updates to iso?I skipped it when I made that .iso that came up with no sfc scan error also, what does windows manual setup do in component removal?
When you remove manual setup, it will clean the iso of all unneeded files and it can only be used to install from boot.
I start to repeat myself. The option removes all unneeded files, so it can only be used by booting from the iso/usb or dvd.