Thanks abbodi, I see the logic.. but would this be a Windows 10 thing? It is directly the opposite to the way Komms KUC tool works with previous versions of windows.
abbodi.... you are revered in this forum, but in this instance, question not answered... is this a personal choice, or as M$ suggests that each update only installs what is missing from previous updates.. as a consequence, surely it must be advantageous to remove all superseded updates and inntall the (Presumably) new components.
I'm not sure what you mean, but like you said.. it's logic for Windows 10 cumulative updates (rollups in Windows 8.1), most components in the update are shared with previous cumulative (shared = same version) when you uninstall superseded one after installing new one, those components remain tied with new one, and only superseded components removed
so far ive wrote my win10 dism/offline integrate script to do this: extract msu -> extract cab -> integrate update.mum Is this method ok still for win10?
Yes, it's still valid but be aware that some (or most) updates .cab files cannot be extracted unless the host OS is Windows 8.1 or 10 Windows 8 or 7 will fail upon extraction i mean the manual extraction (using expand.exe tool) using dism directly with .cab (or .msu) is OK of course
It's not an actual bug, it's a typical msft behavior currently, only 3 updates are really required, other 4 are just to shut up WU
3 Required are: KB3097617 Cumulative KB3099406 Flash Security KB3081452 Servicing Stack + that KB890830 "Malicious" thingie and LPs 4 Redundant are: KB3093266 Cumulative KB3081449 KB3074686 KB3074678 right?
Yes, except you don't need the previous cumulative update. Edit: 3093266 is currently still being downloaded by Windows Update, but it's likely an mistake.
I wanted to mention that on these new 16393 builds, you can add-package the 3097617 cumulative update and resetbase it. It doesn't set pending flag. Code: C:\>dism /image:c:\mount /add-package /packagepath:E:\win10slipstream\kbfiles\x64\Pending /preventpending Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 Processing 1 of 2 - Adding package Package_for_KB3097617~31bf3856ad364e35~amd64~~10.0.1.5 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_KB3099406~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. C:\>
May I ask what you mean by "These new 16393 builds"? Edit: Never mind: Build 10240.16393 = Build 10240.16384 + KB3081452 + Cumulative Update KB3081455 (has been superseded by now) (i.e. NOT full 16393)
Code: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>Dism /Image:e:\Mount /Add-Package /PackagePath:d:\Windows10\Project\Integratiemap\10.Updates.12-8-2015\Index.x64.1.resetbase\ /preventpending Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 Processing 1 of 7 - Adding package Package_for_KB3074678~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 2 of 7 - Adding package Package_for_KB3074686~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 3 of 7 - Adding package Package_for_KB3081449~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 4 of 7 - Adding package Package_for_KB3081452~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 5 of 7 - Adding package Package_for_KB3093266~31bf3856ad364e35~amd64~~10.0.1.4 [==========================100.0%==========================] The package was not added because the specified Windows image or package has pending online actions. For more information about the /PreventPending option, refer to the help. Processing 6 of 7 - Adding package Package_for_KB3097617~31bf3856ad364e35~amd64~~10.0.1.5 [==========================100.0%==========================] The package was not added because the specified Windows image or package has pending online actions. For more information about the /PreventPending option, refer to the help. Processing 7 of 7 - Adding package Package_for_KB3099406~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. Hmmm, why do I get this result? KB3093266 sets the install pending flag, i know, but KB3097617 shouldn't, right?