So I got a new machine. Windows 11. Brand new. It's stuck updating. It is taking ages. Why? Well, I don't have any definitive answers but my most basic instinct is to always attach a profiler -- I recommend the excellent @superluminal .
It turns out that there is this thing in the background, TiWorker.exe, and it's taking its dear time while burning through CPU cycles. This is part of the "Windows Module Installer" service, which handles updates.
I have no idea whom to tell that at Microsoft. Is this a known problem? Are there good reasons for this? Am I holding it wrong?
But I have done some back-of-the-napkin math: At roughly 19s per package, and assuming I have 10000 packages installed, and assuming there are no additional such steps, the update will hopefully finish in 53 hours.
I'll add a post when the update has finished.
It finished! I had already waited for a day when I started to look into what went wrong (with some restarts). Not sure what the precise walltime then is, but it's somewhere in the 30h range.
In a cruel twist, there are now two more updates, and they just fail immediately :)
@aras I actually prefer this to waiting for two days while something assures me that they "are definitely still doing important work so please don't kill the process."
It's scary to think how many times I just kill stuff because I don't think that it can possibly be doing meaningful work for so long, haha.
@sschoener possible some of this is recently improved: https://www.theverge.com/2024/10/23/24277844/microsoft-windows-11-24h2-windows-update-improvements
But, still, Fucking Yikes 😬
Thanks for posting, it was good for a hearty IRL laugh.
@gorlak Thank you. But I have bad news (see picture below) 😛.
Also, "big scary update" sounds like something that might be... extra... slow to update to, haha.
Otherwise it's of course great to hear that they are apparently looking at update performance.
Sebastian Schöner
Aras Pranckevičius
Simon Felix
Stefan Reinalter
Sylvain Meunier
Geoff Evans