Is it I let it find the Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.16299.15 package in my updated Windows?
Not as far as i know, but i can't sleep anyway (my wife is sick and coughs so much, i can't sleep). My W10UI script needs to run on the last 2/10 indices and the boot.wim, when it's finished i will do a test. I conclude you're in canada, according to the time and currency settings?
Yes, I installed all the updates in W10UI, checked the WIM with NLite, all the updates are integrated with EN-GB langage pack. I used the Consumer Client Full ESD and only saved the Windows 10 Pro indice and the boot.wim were kept etc. of course with the ESD to ISO converter. Only change I made this last install was to US keyboard. Kept the region as GB during the Windows install. I also checked the updates WIM file in the ISO BEFORE I used W10UI with NLite and only the EN-GB language pack was installed. KB4088776 and the Feature Update installed again on a clean install. Now I'm going to try the Official 16299.15 EN-US ISO from Asguard's TechBench without making any changes in the install with language or keyboard or anything. Only thing I'm going to do is delete all the indices except Windows 10 Pro and the boot.wim indices. Can deleting indices cause these issues?
Based on your info you didn't use any en-GB source, it was en-US. So, did you or didn't you manually integrate any LP? You seem to be very vague about that, and why would you use ntlite for this straightforward stuff?? How do you think you are going to boot without boot.wim? After the feature update to version 1709 was installed, can you run the get-packages command again, and post it here, in normal colors? And a sshot of update history?
I said I never touched the boot.wim. Sorry, clean install, was using Edge, it messed up the colours. I know it's confusing but last install I used the EN-GB full ESD file with the ESD to ISO converter. And no, I never installed any language packs. Only thing I did was change it to a US keyboard. I use NLite to delete the indices because when i try it with DISM it never updates after I delete an indice and I can't tell what I am deleting or not. I even closed the admin command prompt and reopened it after deleting an indice and they were still all there. But when I tried to make the ISO the indices were deleted even though DISM said they weren't. Edit: Right now I'm painfully using W10UI to integrate the updates without deleting any indices with reset base disabled.
But with ESD to ISO I only chose to keep Windows Pro. It keeps the boot-wim indices as you know and I never used NLite at all.
Here you select en-CA time and currency: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-280#post-1418324 Here you select en-US keyboard. It's getting a bit confusing to follow what you did and didn't do. The output of get-packages didn't show you've used en-GB at any time. So, i will take an en-GB full ESD, create a Pro only ISO, run w10ui_4.4 with resetbase enabled and one with resetbase disabled and install it with en-CA time and currency, with en-US keyboard.
Yes, that is what i did with the output I provided. I made other ISOs that were EN-GB since then to test. I've used: 16299.15.170928-1534.rs3_release_clientconsumer_ret_x64fre_en-gb_698670fa66d071b531ed9308091176da4c2384e4.esd and 16299.15.170928-1534.rs3_release_clientconsumer_ret_x64fre_en-us_f6df8c19358335bc05e638b45bb6c6f8078480a4.esd files and made Windows 10 Pro only ISOs with ESD To ISO and integrated the same updates you did with W10UI_4.4. And I just used 16299.15 Asguard TechBench Win10_1709_English_x64.iso, never changed the Time and Currency or keyboard or anything. Kept it all EN-US. Here's the results. Code: Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.309 Packages listing: --------------------------------------------------------------------------------------------------- | --------- | --------------- | ------------------- Package Identity | State | Release Type | Install Time --------------------------------------------------------------------------------------------------- | --------- | --------------- | ------------------- Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15 | Installed | Language Pack | 2017-09-29 2:41 PM Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | Foundation | 2017-09-29 1:49 PM Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-LanguageFeatures-Speech-en-ca-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2018-03-15 7:32 AM Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-LanguageFeatures-TextToSpeech-en-ca-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2018-03-15 7:32 AM Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2018-03-15 10:27 AM Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 2017-09-29 2:41 PM Package_for_KB4088785~31bf3856ad364e35~amd64~~10.0.1.0 | Installed | Security Update | 2018-03-15 6:10 AM Package_for_KB4090007~31bf3856ad364e35~amd64~~10.0.1.3 | Installed | Update | 2018-03-15 6:10 AM Package_for_KB4090914~31bf3856ad364e35~amd64~~16299.251.1.0 | Installed | Update | 2018-03-15 6:10 AM Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.309.1.3 | Installed | Security Update | 2018-03-15 6:13 AM The operation completed successfully. It seems it's installing the Microsoft-Windows-LanguageFeatures-Speech-en-ca-Package~31bf3856ad364e35~amd64~~10.0.16299.15 likely because I Sync my Windows settings and it adds the language pack when I log into my Windows Hotmail account during Windows setup when i first boot into Windows. What I need to do is either turn Sync off and reinstall, or log into a local account instead of my Hotmail during Windows setup.
Is there any way I can integrate the EN-CA language pack with all the updates and not trigger Feature Update and CU reinstall?
I belive Speech and texttospeech packages are for cortana only and not actual OS language. could be wrong about that.... . try skipping the cortana setup.
I got this "Feature update to windows version 1709" first time I installed 1709(version 16299.125 Official iso), it went away after I updated SSU.