Somebody convince me I’m wrong.
There is no reason to display “100%” in your UI for more than a single second. Either show 99% and then finish, or show 100% only when you are ACTUALLY done and only show it for a little.
If you’re still doing ANYTHING AT ALL don’t say you’re 100% complete. How is it still like this
How is it still like this
Because Microsoft knows no one is going to stop using Windows even if it sucks. It’s same way no one actually moves to Canada when a shitty US president is elected. The average person has a high tolerance for bullshit.
I imagine it started with some sub-installations actually giving approximations that were acceptable and summed up, but then some finalizing was not taken into account or something needed to be added after the other processes are finished, and the deadline was close. That last part builds up over time with other quick additions and some annoying stuff that is actually quite performance heavy and not easy to incorporate through the whole installation. “Let’s do it at the end as well.”
No time / budget to change the 100% to 99% as they have to adjust calculations based on the processes that actually do a good job. Although a display change could fake it, priorities are elsewhere.
It’s especially bad when it’s stuck like that for hours, and you have to make a gamble with a force restart.
Spinners must die. I don’t care if I don’t understand what exactly you’re doing, Windows, (I’d be surprised if you knew), but show me something, anything about the steps you’re currently doing, so I can guess if you’re doing something at all.
They could actually show you a command prompt / terminal readout, which shows warnings and errors when things just outright fail and the process is borked… but that would scare people, apparently.
LOL, yup! I was just going to reply that people find that scary, and then got to your last sentence. Idk why it scares people. I love seeing the output.
It must be a really deeply integrated part of the Windows kernel because it has never been able to show progress properly.
Back in the days of floppy disks it always felt that actual copying started when the progress showed 100%.
While we’re on this topic, why does “update and shutdown” reboot the PC after updating? Just had this the other day. Was in my bed when I heard the PC running and when I got up to check, lo and behold, the login screen…
I thought that it restarted the pc, finished its whatever and then shut it down.
(Disclaimer: I don’t really use windows, so I’m not super familiar with its latest shenanigans)
This is what is supposed to happen with that option, in reality there is a very good chance that it just doesn’t shut itself off afterward. Back when I used the OS I would have it set to auto update and since I shut my computer off nightly I didn’t have a problem with it, but I found that it had a fairly good chance that if it updated when I shut it down my computer would still be running when I woke up in the morning. My work around that I put for it is I put a scheduled shutdown in task scheduler for early in the morning when I knew I was never up so if the system had restarted but failed to power itself back off again it would turn itself off.
The best is when this starts on battery power on an old machine. It’s always a race to see who wins.
