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
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.
more accurately, average person has a higher tolerance for bullshit than for spending many hours learning something new or spending potentially years applying for citizenship in another country
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.
I don't think it counts percentages. It has to be more like : do this; display 30% ; do this ; display 70% ; do this ; display 100% ; do this; done (maybe);
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.
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...
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.
Last week I had the lovely experience of it also pushing a bios update that enabled bitlocker and locked me out of my drive. I had to completely wipe the laptop and lose the data.
Exactly. After reading through some forums it sounds like BitLocker may have been enabled at the factory initially but I had never noticed and since I didn't set it up myself I had no key. So anyone reading this and running windows: right click your C: drive and see if BitLocker is enabled. If it's enabled and you didn't enable it or don't have the key then disable the encryption. You can re-enable it afterwords and safely backup your new key so you never find yourself in this situation.
When I updated to Windows 11, it detected TPM 2.0 but failed to notice my drive had an MBR partition table and therefore couldn't use Secure Boot. It happily updated anyway and rendered my drive unbootable.
It used to be convenience, but, by some foul magics, they have made Windows both dumber and less user friendly, like the inbred cousin of Apple with more privacy violations.
Like Linux doesn't have its annoying quirks that linux users will endure ...
Just installing an audio device or Nvidio GPU is a pain. You guys are reinstalling your OS every couple of days because yet something else broke and you don't know how to fix it. Repositories needing repositories needing repositories for things to work.
Not to mention the limited amount of programs that are compatible compared to Windows.
It's all about familiarity. People feel comfortable with Windows because they always used it and it has all the programs they always used. Most people just want to get their shit done and don't care about operating systems at all.
The original Azure progress bar was Microsoft’s crowning masterpiece of progress bars. It would very slowly fill up, and then wrap around and start to fill up again. To be fair, all of the animations in that early KnockoutJs version of the Azure portal were just incredible to watch, and someone must have put a lot more effort into them than they did adding features.
Time to upgrade to a faster NVME (and possibly a better CPU too). Windows updates install so fast on a modern system that they don't even bother me anymore.
The solution here isn't to upgrade your PC for Microsoft's sake. The solution is to use an OS that actually respects you and your time. Use Linux, or FreeBSD, or even macOS. Alternatively install Gentoo and spend even more time updating, but with spectacular performance and customizability when you're not updating.