• Post Reply Bookmark Topic Watch Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Jj Roberts
  • Tim Holloway
  • Piet Souris
  • Himai Minh
  • Carey Brown
  • salvin francis

Has Microsoft Windows™ "jumped the shark"?

Saloon Keeper
Posts: 22784
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Disclaimer: I haven't used Microsoft Windows™ on a daily basis since about 2006. But my wife has to keep a Windows system running since her employer is a Big Company. And I get called in when things go wrong.

The number of Windows 10 updates with major breakage in them over the last 12 months has been legendary. I can't recall any product from any manufacturer breaking so routinely, and that includes earleir versions of Windows. Including the much-reviled Windows 8!

Aside from that, however, we have 2 long-standing issues of our own. First, and most annoyingly, the horrendous "thump" that the speakers emit periodically, especially when certain Windows events occur such as switching tabs in a browser window. Or, apparently, jat random times ust because it feels like it.

This is a known issue and can be affected by about 5 different systems settings. Most of them appear to be related to energy-saving features in the audio subsystem. Which in itself amazes me. The audio output for a PC isn't exactly high-power, and even the audio card itself would, I hope, not pull much power when it wasn't actually sending out sound. But there it is, and despite repeated fiddlings with the system settings, the cone-shattering thumps continue.

The second issue has been getting more frequent, and is also a reported issue. My back-end LAN uses fixed IP addresses. But now Windows keeps forgetting that, reverting to DHCP and thereby failing to join the network when it wakes up. If you run the network diagnostics, they won't even consider fixed IPs as acceptable, and they'll forcibly change to DHCP. This is really rude.

I could also mention various complaints I've heard about networking and printing in recent days, but they're coming in from channels where cheap employees are valued more than good ones, so I can't definitely blame Microsoft. But I've worked with Windows since version 3,0, and I'm not amused that it no longer seems to be possible to coax a semblance of professional quality from Windows.

I'm beginning to believe, in fact, that Microsoft doesn't love Windows any more.
Nothing up my sleeve ... and ... presto! A tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic
Similar Threads