KB5026361 Windows 10 Update 19042.2965, 19044.2965, and 19045.2965 Win Update
-
I am at 19045.2846 and Windows Updates says "your up to date", but checking on Update Catalog, I am behind by one preview update KB5025297 (25APR2023 19045.2913) and this cumulative one KB5026361 (09MAY2023 19045.2965). Guess I'll do the manual thing and see if anything 'assplodes'.
Edit: Manual update went smooth. I run a heavily modified Windows 10 (all telemetry/apps/Edge, etc. pre-stripped from ISO) so probably whatever components that "trigger" the update don't even exist on my rig.
Last edited by Quexos; 10 May 2023 at 21:48.
-
-
Last edited by Brink; 11 May 2023 at 08:20.
-
done deal.
-
No Malicious Software Removal Tool for me this month, just KB5026361 and another .NET update 'preview' forced on me.
Done a manual update check several times, and no sign of MST.
-
-
Any idea why I've lost about 3Gb with both this cumulative update and april's? This is after even all the regular cleaning I do after each monthly cumulative update, I start with the classic disk cleanup which finds 300Mb on average, then I run DISM component cleanup and finally I manually clean SoftwareDistribution/Download of all previous update packages except for the latest.
Where did those six gigabytes go, Is Microsoft deliberately filling our Windows 10 system drives to slow them down?
Last edited by i486; 11 May 2023 at 19:54.
-
Any idea why I've lost about 3Gb with both this cumulative update and april's? This is after even all the regular cleaning I do after each monthly cumulative update, I start with the classic disk cleanup which finds 300Mb on average, then I run DISM component cleanup and finally I manually clean SoftwareDistribution/Download from all previous update packages except for the latest.
Where did those six gigabytes go, Is Microsoft deliberately filling our Windows 10 system drives to slow them down?
Look in C:\Windows\Servicing\LCU
LCU folder is LARGE-But what is it?
-
-
Windows Update keeps copies of up to three of the latest CUs there. DISM's cleanupimage deletes all but the most recent. I routinely delete that last one myself. The only effect this has is that you will not be able to uninstall the latest CU if you do so.
-
Windows Update keeps copies of up to three of the latest CUs there. DISM's cleanupimage deletes all but the most recent. I routinely delete that last one myself. The only effect this has is that you will not be able to uninstall the latest CU if you do so.
The LCU folder only amounts to about one gigabyte, if its size is calculated correctly. It doesn't explain the lost space when the size of that folder is kept in check with the component store cleanup routine. That's why I assume there was only one subfolder, with only very recent files inside.
- - - Updated - - -
Alright, the lost space is no mystery anymore - the april cumulative update had re-enabled system protection for the C drive. I guess this is pretty common. I disabled it to reduce drive wear because the system protection seems to create a new restore point during daily idle maintenance, in addition to those created during update installs, including store app updates.
-
-
Quote
