Fight for the Internet 1!

Sunday, February 7, 2010

Microsoft Windows bugs that could be fixed, but won't be

This is just a list of the bugs I observe in Microsoft Windows that are still popping up, more than 10 years after viable solutions having been discovered. (In the case of some bugs, the time is even longer). The list is short right now but I will update it as I find more, which shall doubtless occur in time.

The follow Microsoft Windows bugs that still exist because they don't care enough about you as customers to fix them. Instead they'd rather kowtow to the RIAA and MPAA with useful system performance leeching software you never wanted and will ONLY inconvenience you. Yeah, way to go guys. Give the people stuff they'd riot about if most people knew or understood it, but never fix real problems for them.
  • Virtual Memory running low / running out. [Confirmed since Windows XP, until currently today (2010-02-06) with Windows 7]. It should be noted this still occurs on machines equipped with tons of memory.
  • File System Fragmentation (with NTFS and/or FAT32). [Confirmed since Windows 2000 until Windows 7]. Let's not even start on the abysmal performance of Microsoft File Systems.
  • Rebooting (still too frequently). Need I say more? Every single update that is security related requires an update, and not just those. Too much I tell you, especially for a system that is so horribly insecure.
This List is not necessarily Bugs, though they are still problems that COULD and SHOULD have been fixed decade(s) ago.
  • Slow Windows Update Downloads. There is no excuse for this. Honestly, none. Not anymore anyway.
  • Slow Windows Update Execution. I really forget how long these can take sometimes and just accept this as normal. It's pretty ridiculous when I take a moment to notice it.

No comments:

Post a Comment