KB4456655 Servicing stack update for Windows 10 v1803 - September 11
-
So to really dumb it down this makes KB4457128 possible?
Windows update downloads the files to C:\Windows\SoftwareDistribution\Download and servicing stack copies the data to WinSxS and tries to create the hardlinks, if this fails (when the files are still used), the operation is pending and the update gets installed at next boot (the configure Windows updates screen at shutdown and boot).
(they lost me at "hardlinks")
Sidenote: Maybe this is why people are confused by having to reboot twice even after rechecking for updates or have a (2) next to KB4457128 after it is installed. You do state no restart required but just for SSU so LCU kicks the required dual restarts into gear.
-
-
Hello @andyouf,
LCU stands for Latest Cumulative Update.
-
Thanks I just realized that, said duh, and went to edit out my question but see you replied.
(I have no idea what an 092 emoji is and just looked it up and got nothing).
So this does enable the LCU?
-
-
Correct.
It's required to install this KB4456655 first to be able to have KB4457128 available via Windows Update to install.
Prerequisite: The servicing stack update (SSU) (KB4456655) must be installed before installing the latest cumulative update (LCU) (KB4457128). The LCU will not be reported as applicable until the SSU is installed.
-
You guys ever look at C:\Windows\WinSxS\Temp ... InFlight, PendingDeletes and PendingRename folders. Seems there's always files/folders left in those folders, even after running ... Dism /Online /Cleanup-Image /StartComponentCleanup or Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
-
You guys ever look at C:\Windows\WinSxS\Temp ... InFlight, PendingDeletes and PendingRename folders. Seems there's always files/folders left in those folders, even after running ... Dism /Online /Cleanup-Image /StartComponentCleanup or Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
Way above my head. I went there and just saw a bunch of amd64, wow64, and x86 files (no Temp folder). I take it amd64 is amd machines, wow64 is me, and x86 is legacy. If they were in a temp folder I may be more comfortable just deleting them but I'm guessing I should leave them alone. Also, are all those DISM commands okay to run? Only one I've ever used is the RestoreHealth one I believe.
I love how I through your question back at you with more questions.
-
Eagle51 C:\Windows\WinSxS\Temp ... InFlight, PendingDeletes and PendingRename folders.
Do you delete those files?