News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Why can’t Microsoft reliably patch its own hardware?

    Posted on Tracey Capen Comment on the AskWoody Lounge

    Home Forums AskWoody blog Why can’t Microsoft reliably patch its own hardware?

    This topic contains 4 replies, has 5 voices, and was last updated by  rc primak 3 weeks, 5 days ago.

    • Author
    • #1879399 Reply

      Tracey Capen
      AskWoody MVP

      WOODY’S WINDOWS WATCH By Woody Leonhard You don’t need me to tell you that Windows patches are too often of, uh, questionable quality. But the latest
      [See the full post at: Why can’t Microsoft reliably patch its own hardware?]

      2 users thanked author for this post.
    • #1881269 Reply


      Windows 10 1903 renders ‘Client Hyper-V’ useless as well. The problem is a new graphics driver handling enhanced session mode RDP causing VMConnect windows to freeze when the host moves the monitor into sleep mode. Even worse, the new graphics driver leaks quite a bit of memory (25+ MB) each time a VMConnect window is resized or flipped between full-screen and normal mode. Microsoft is aware of this for months (see feedback hub), but a fix is not in sight.

    • #1881296 Reply

      AskWoody Lounger

      because Microsoft is a software company that is good at OS but not so much of anything else


      • #1881496 Reply

        AskWoody Plus

        MS does not impress me as being that great at software either. For the highest stock-market valued company of them all, one would thing they could well afford to use just a few of their billions to employ and equip adequately some competent engineers to manage and staff the software and hardware divisions, or whatever these are called in their company’s organigram.

        In exchange for that tiny expense, they could save themselves tons and tons of continuous embarrassment.

    • #1882420 Reply

      rc primak

      I posted much the same thing about the third party antivirus issue that I am about to post about this issue:

      In spite of being Microsoft branded, the dGPUs are NVidia products with NVidia drivers. (Although, these drivers may be Microsoft branded.)

      As a graphics card manufacturer, NVidia has a long history of making proprietary drivers with specialized capabilities. This is a strength and a weakness. These proprietary NVidia drivers are notoriously fragile. Any change in a Graphics Stack will break them and cause issues. Microsoft Windows and their Surface devices are by no means the only instance of such fragility in NVidia drivers.

      Every OS NVidia runs on has had similar issues. Linux has had plenty. MacOs has had some. And Windows has a long history before Windows 10 of updates and upgrades borking NVidia drivers, or failing to install due to issues with NVidia drivers.

      This is nothing new, and it is not Microsoft’s fault. NVidia’s driver writers (outsourced last I knew to somewhere on Taiwan) have no respect for the requirements of or changes in graphics stacks. None whatsoever. It’s almost as if they live and work in a vacuum.


      -- rc primak

      • This reply was modified 3 weeks, 5 days ago by  rc primak.
      • This reply was modified 3 weeks, 5 days ago by  rc primak.
      • This reply was modified 3 weeks, 5 days ago by  rc primak.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Why can’t Microsoft reliably patch its own hardware?

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.