@KedarWolf The "feature updade to windows 10, version 1709" suggests you're on a previous build. How do you install the newly created iso (Win10_16299.309_2018-03-13.iso)? It doesn't matter from what source the files come from (UUP>ISO, ISO, ESD>ISO), as long as they're not corrupted or created with errors, during the conversion process.
I posted the output as well. It was a 16299.15 ISO as I used made from the OEM 16299.15 OEMRET CONSUMER CLIENT ESD
That's how you created the install media, i asked how you install it, do you boot from the USB (clean install) and delete/format all existing system partitions or do you run setup from a running windows (inplace upgrade)
Yes, clean install, deleted the four GPT partitions and created them again in the Windows installer. And after making the ISO I checked to see all the updates were installed and they were.when only the EN-GB language pack as I used that ESD file.
Right after installing run this command in an elevated cmd: Code: dism /online /get-Packages /format:table >"%userprofile%\Desktop\Packages.txt" And post the output here in code tags
Last part is hard to understand . Did you install a lang pack after the update integration (that would explain the offered updates)?
If it's installed after the update integration, the new lang resources need to be updated (this will at least trigger a partial re-install of CU components).
@abbodi1406 What is happening here at @KedarWolf's integration progress (on winpe images only): Code: ============================================================ Resetting WinPE image base ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.309 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.309 [=========== 20.0% ] The operation completed successfully. ============================================================ Unmounting boot.wim - index 2/2 ============================================================ It doesn't happen on my integrations. I just noticed, it also happens on my integrations, it shows resetting the image and next another progress line without header. It seems it runs resetbase twice on winpe images?
Nothing weird, percentage doesn't matter rebasing 16299 images require two StartComponentCleanup commands, the first do the resetbase and remove components, the second merely permanize updates and delete sessions*.xml files
Is it because of the "workaround" you've implemented to still be able to do a full resetbase on winpe images? ps, i know about why the progress bar not completing, it was the showing it ran twice that made me wonder
I don't get where the en-ca package comes from, and you said you've used the en-GB ESD? This is on one of my VM's, direct ESD upgrade from 14393 > 16299.125 (en-US): Code: --------------------------------------------------------------------------------------------------- | --------- | --------------- | ------------------ Package Identity | State | Release Type | Install Time --------------------------------------------------------------------------------------------------- | --------- | --------------- | ------------------ Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15 | Installed | Language Pack | 9/29/2017 2:41 PM Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | Foundation | 9/29/2017 1:49 PM Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.16299.15 | Installed | OnDemand Pack | 9/29/2017 2:41 PM Package_for_KB4053577~31bf3856ad364e35~amd64~~10.0.1.0 | Installed | Security Update | 12/14/2017 1:40 AM Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 | Installed | Security Update | 12/14/2017 1:40 AM The operation completed successfully. But it seems the en-CA LP is integrated after the updates (lp = 2AM and the updates 12AM), so @s1ave77 was correct with his conclusion, when a LP is integrated after the updates, some of the updates will be (partially) re-installed by WU. Why do you integrate LP's and not just use the correct ESD?
No, never installed a language pack. I've tried an ISO from both the EN-US Full Consumer ESD and the EN-GB Full Consumer ESD. Last one I did I used the EN-US ESD. hence the US language pack. Oh wait, in the Windows install I choose EN-CA Time and Currency. I'm sure that's the problem!! Edit: But won't that mean if I enable EN-CA in Windows after the install it'll install those updates again?
Prolly is, but that still doesn't explain the redownload/install of the "Feature update.... version 1709", although....