Aleksei Czukanov :
I am fully agree with your opinion regarding Windows Op system: a full shit. Apple does not allow to run their OS on other HW, since their system is: "1 HW - 1 firmware" (OS or IOS). O.K., there is 2-3 HW (2-3 iPhones) and 1 Firmware. However so they can guarantee the 95% "customization" of the Firmware for the given HW (even perhaps seems less "powerful/strong" in comparison with other HW configurations running Windows) and so they can ensure "smooth/flawless" operation (in iPhone "glacial movement"). All other OP System must "correspond" to "265.000 kind of iron" incl. no-name graphics cards, RAM-s, etc.
Apple puts together the things (I know, Steve Jobs also stole ideas from a lot of sources), but AS they put together, it is PERFECT: you should not always "restart" because of updates or because of "slowing down" of the machine. I switched off one of my Apple Macbook (I also have PC-s, laptops with Windows as well) JUST ONCE A YEAR. So I start to replace all my PC-s/laptops with Windows in my small firm with Apple OS.
Indeed... you must do what's best for your firm. Apple systems are most stable and they are top grade (used to be even more in the past) hardware. That doesn't mean they didn't have their failures here and there, from the antennagate of the iPhone 4 to swelling or exploding batteries, to macbook GPU failures (I personally fixed 2 units which apple refused to fix despite known recall failure...long story). But all in all I'd advise anyone to by an Apple computer if they can afford it and if they don't need to keep compatibility with specific software or hardware which would require a PC. Even then the solution might be to run Windows on a mac hardware using bootcamp although that too could be risky as I've personally experienced issues on mac pros where some windows features would not work as expected (like sleep/hybernate to name one).
That said, if window really wanted to keep compatibility it would be possible. Standards exists and any company that would produce hardware should have been required to receive certification from Microsoft before they could sell their product as being compatible with Windows. Microsoft appears to have started to go in that direction but then like most of what they've done recently, they lost their way... in fact when installing some drivers one would at time receive a warning about a driver not having a "certification" to be compatible with the current version of the system... but guess what, more often than not all the troubles I've had on Windows systems (my own and client's ones) it's not been caused by those "uncertified" drivers, but rather by OS updates.
I agree that as a system that is compatible with most of the hardware out there, there will be a high chance of experiencing issues... though what I do not accept as admissible is the releasing of major buggy updates that in more than one occasion required a complete fresh install of system, in other cases have caused loss of data. No commercial OS should ever cause either by careless release of half-assed updates. But the problems at Microsoft are much deeper than that albeit this isn't the right venue for such a debate.
Suffice to say that in my case the process I described earlier is what seem for some reason to have solved the issue with "Windows Update Not Showing Download Percentage" which is that this thread is about. If that helps others awesome... if it didn't help you, sorry to hear about that, hope you'll find a working solution that will allow you to move forward and finally stop wasting time on fixing OS issue and using that time to take care of business... it'd be nice if the OS one bought would prevent such time wasters in the first place, apparently that's never been a priority at Microsoft.