I realize that bugs happen, but to me this feels like another point on a pattern of Microsoft being too cavalier with my hard drive space. Sure it was a mistake in this case, but it hints at what Microsoft prioritizes internally.
That reminded me of how Windows abuses my HDD by regularly writing dozens of logs I won't ever need unless I'm both knowledgeable enough and debug for specific errors.
And also about WinSxS/Temp/InFlight folder that gets filled with an undeleted garbage of unknown purposes. You can't safely delete files there (with elevated System privileges) even after finishing delayed patching and dism cleanup operations because some of them are still used by the system somehow despite it being a "temp" folder. While thousands of empty subfolders there slow dism/TrustedInstaller runs to a crawl on their enumeration.
I presume that's what deletes the cache... but I see this from the article:
> Microsoft is preparing a patch to solve the problem, which should be rolled out as part of an upcoming update. Until then, you should leave the Windows Update cache untouched. It really isn’t worth the hassle of reinstalling Windows just to clear those files.
It's not just modern devs, this has been an issue on Windows for a long as I can remember. There have been cache cleaners, registry cleaners, etc for as long as I can remember. Devs installing shit in the root of my C drive since the Win3.1 days and I'm sure earlier than that.
But it will soon be deletable. And coming from 5¼ floppy disks I expect you also consider Linux distros to be extravagant and wasteful. You must be gobsmacked every time you take a picture with your phone.
But they are still way more than 360 KB. I assume that's why you brought that up, as that's the point of reference - 360 KB per disk, making anything on a modern PC monstrous.
And I wish it was only the data I want in my photos. They keep adding more things to each photo, and you end up with HDR and a little video file if you're not careful.
There is a way to fit the kernel in 360 KB, but that's the most you'll get. Whole distros have been fit on a floppy disc. The kernel with ancillary embedded software in half a megabyte of flash easily.
However, this kernel does much more than, say, C64 ever did. BPF and ACPI parser alone is bigger than BASIC, there's a network stack, multitasking etc.
Multiple people have claimed you cannot do it with new kernels. They are wrong. (E.g. Floppinux by Jankowski.)
Remember that a lot of the software back then took more than one disk. Amiga Workbench for example used 3 for 1.0 I believe... And that built off Kickstart, which is the true kernel and was extra 256 KB.
My work laptop has only a 256GB disk for the OS. Now it's 4% of the entire disk.
In contrast, my Linux desktop only uses 13GB of the 24GB allocated to the OS partition (excluding /opt and /home). Now that 8.6GB is 35% of the OS partition.
Goody for you - but I am stuck with a 512GB drive on a 2024 issued laptop (small capacity due to dAtA s3curiTy or some silliness, the defense industry is full of nonsense like that). I currently have 90.4 GB available, so this update would be consuming 10% of my available storage.
The BestBuy near me still sells laptops with 128GB SSDs. I can’t imagine the people who can’t machines like that are doing much, but 9GB is a big chunk of that.
Well, that sounds like a work laptop, so you shouldn't really be doing much of anything personal on it except for work. If you have drive space problems, then talk to your work.
And your OS partition is how much of that? Mine is like 100GB and this would easily consume the majority of the free space it has left. And no, the rest of the space on the disk isn't just unallocated space sitting there for the OS to bloat into.
>Microsoft is preparing a patch to solve the problem
Very not interesting.