You're completely wrong, no way download the same lcu and unpack by itself. Every new CUs I download it manually and install/integrate by dism or wsus whatever, then run dism with two arguments '/StartComponentCleanup /ResetBase' After this run this script by nsudo. Code: @echo off set "LCU=%SystemRoot%\servicing\LCU" if exist "%LCU%" ( echo.Deleting '%LCU%'. rmdir /s /q "%LCU%" echo.Folder '%LCU%' has been deleted. ) else ( echo.Folder '%LCU%' not found. ) pause exit Everything is OK.
This doesn't seem to happen for all, i showed one probable cause but seems for that situation the lcu was not needed. Here you caused it yourself and then there is no mystery about it why it's occurring. Yes, the deleting of the LCU folder can cause the need for redownloading it when it's needed for updating changed components.
This is an interesting observation, but generally speaking, if things are properly done and the cleanup is performed using supported methods, there should be no need for manual cleanup of the LCU folder. At least in theory although we all know things are not always as smooth as they are supposed to be.
Actually sometimes the LCU folder is not getting updated correctly for some reason. It is in fact a symptom of a problem and not the root cause, but the problem may also be created artificially by deleting the contents of the LCU folder?
Retired, its just a hobby now. Finding corner case issues is kind of fun actually. Either way its not just me reporting this CU re-offer so by definition, its not just me. This strange glitch quite literally just unpacks the current CU into the LCU folder so other than taking up disk space, it is completely harmless. Since this glitch does not require a reboot, the vast majority of people that experience it would never even know that it happened. The other glitch I am observing is that some of you guys care a heck of a lot about certain ithings, not sure that one will ever get patched though.
You can definitely create it artificially. There was a debate about deleting that folder to save space and MS reps were claiming that it might break things so I tested it out to see what broke. The only thing that I observed was that sometimes the latest CU was re-offered and unpacked into LCU. If I am not mistaken, doing a Windows updates cleanup will delete all but the last CU from LCU so it makes sense that you are not supposed to actually delete all of them, certainly not manually.
So from *insert upcoming moment* forward, Windows 10 2xHx will be like 1809 with 4.8? Two netfx CUs depending on whether 481 is integrated or not?
Wait, nevermind, I just re-checked that post and there's a DBX update for 2xHx now too... Anyway, I don't recall that update showing up in control panel at all, even on v1809. Might be wrong.