Clean MSDN iso gives me the updates from my list, abbodi's w10 list (follow his sig) gives me also the same updates so you should be missing a few. As i showed, 1454 is for unpakking to iso:\sources folder not for integrating
My observation is this. KB3081452 - Needed, Servicing stack KB3074678 - Not needed, OOBE KB3074686 - Not needed, OOBE for pre-GA ?, came out 6 days before Win10 release KB3081449 - Needed, OOBE KB3087916 - Not needed, I dont use Windows built in flash. and Cumulative: KB3081455 - Needed and for \sources: KB3081454 - Not needed, its for Upgrade process
I'm talking about the updates offered by ms and that's my list (+ the sources update for complete iso use )
I understand, But in my opinion those above you listed in Red aren't needed, well for me anyway. Ahh ok KB3081449 replaced KB3074678, I just read this over on the Article page. As for KB3074686 It only updates one file and is listed as OOBE, the file is Rdxservice.dll, Dont think i need that.
My list was for normal use, normally windows installs the updates from my list and that's considered an updated windows. So 1455 replaces 1448 (to be short)
I integrated the following into Build 10532 via NTLite: - microsoft-onecore-graphics-tools-package_2e021749327e09e4406c340a29c0fabaaf2bbae2.cab - microsoft-windows-insiderhub-package_f5c0f374a50c32f77b124eac148e50a769b013df.cab - microsoft-windows-netfx3-ondemand-package_1c89e2ded9ddd050dde8e723c5806704416dd363.cab - Windows10.0-KB3074682-x64_567f3e88d08fbfaf16b3b9d60387b83c5a665d5c.msu - Windows10.0-KB3081424-x64_166daaea0dfeb06b34f39d7aebf03ff93a7bf99e.msu - Windows10.0-KB3081438-x64.msu - Windows10.0-KB3081441-x64.msu - windows10.0-kb3081448-x64_791bde45376041ecf6791fb2e594d8ca9beab48a.msu - windows10.0-kb3081449-x64_df1c4d6c972038cab1f388a57b5f1140f4ca6ebb.msu - windows10.0-kb3081450-x64_9ac558fda13caccf5758a3df6b955666281eef4d.msu - windows10.0-kb3081452-x64_3163f6a4522049a3cf72586ce1d71db1b820646d.msu - Windows10.0-KB3087916-x64.msu - WindowsTH-KB2693643-x64.msu
This has been my experience as well. What I did is just integrate all the non-cumulative into base image and resetbase it. Then use that base as a starting point.
Does anybody know what the DisableResetbase nonsense in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Configuration is?
It's probably a way to prevent resetbase operation. There's not really a point as you have to have admin permissions, but maybe admins don't want to get requests for that?
Any idea why WU offers me KB3081455 again? Fresh installation, KB3081455 installed successfully, yet it offers me this update again for download and install.
Not much at all changed in KB3095020, compared to the previous KB3081455. These are the new additions (x64): Code: amd64_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_10.0.10240.16500 wow64_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_10.0.10240.16500 And these are the only ones that have been updated from older versions: Code: amd64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.10240.16500 amd64_microsoft-windows-setup360-media-base_31bf3856ad364e35_10.0.10240.16498 amd64_microsoft-windows-u..access-unifiedstore_31bf3856ad364e35_10.0.10240.16500 amd64_microsoft-windows-win32k_31bf3856ad364e35_10.0.10240.16498 wow64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.10240.16500 wow64_microsoft-windows-u..access-unifiedstore_31bf3856ad364e35_10.0.10240.16500