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
  • Build 1903 – Intel Q45/Q43 driver conflict causes RDP black screen

    Posted on BATcher Comment on the AskWoody Lounge

    Home Forums AskWoody support Windows Windows 10 Windows 10 version 1903 – May 2019 Update Build 1903 – Intel Q45/Q43 driver conflict causes RDP black screen

    This topic contains 9 replies, has 6 voices, and was last updated by  woody 2 weeks, 3 days ago.

    • Author
      Posts
    • #1925720 Reply

      BATcher
      AskWoody_MVP

      This link refers, and precisely describes my problem with some HP Compaq 6000 Pro SFF PCs, which used the Intel Q45/Q43 Express display drivers.

      Currently, my only way out of the problem is to roll back the installed display driver to the Microsoft Basic Display Driver.

      Has anyone any suggestions of how I can ever find out if Microsoft has fixed the problem with a new Windows Update?

      Thanks!

      BATcher
    • #1925862 Reply

      steeviebops
      AskWoody Lounger

      The old Intel GMA video (pre i-series processors) was never officially supported in Windows 8 or 10, in fact Intel went out of their way to block their G45/Q45 drivers from installing on Windows 8 – IIRC they put an empty section in the INF to target Windows 8 and just do nothing. The driver you get from Windows Update is an extremely basic one so you could be stuck here unless you can pick up a cheap and cheerful AMD or NVidia card.

      A repeat of the Clover Trail graphics issues I wonder?

      • This reply was modified 1 month, 2 weeks ago by  steeviebops.
    • #1925885 Reply

      Microfix
      Da Boss

      @batcher, was the W10 1903 a forced seek, offered ‘feature update’ or even clean ISO install?
      This article over at borncity published 12th July seems to point that MS is aware of the issue..but wait, it’s now the end of august and still nothing official from OEM or MS!

      There is also reported workarounds within a link (at foot of the article) and contributed by poster Ho Ka Lok. Hope this helps

      ********** Win7 x64/x86 | Win8.1 x64 | Linux Hybrids x64 **********

    • #1927818 Reply

      cmptrgy
      AskWoody Plus

      This link refers, and precisely describes my problem with some HP Compaq 6000 Pro SFF PCs, which used the Intel Q45/Q43 Express display drivers.

      Currently, my only way out of the problem is to roll back the installed display driver to the Microsoft Basic Display Driver.

      Has anyone any suggestions of how I can ever find out if Microsoft has fixed the problem with a new Windows Update?

      Thanks!

      @batcher, I hope this becomes helpful

      JosephAlves1981 reply on June 14, 2019
      His workaround is “You have to have WinRM enabled.”

      SwissJay reply on June 23, 2019
      “Excellent idea!! Had to adapt it slightly as the devicename was different in my case but works like a charm. Well done!”

      JosephAlves1981 reply on June 23, 2019
      It’s involves different drive letters & G45 instead, but maybe there’s applicable information that can be helpful.

      BillMk reply on July 7, 2019
      “I missed a few updates so I’m unsure which one fixed the issue, but its appears to be fixed in build 18932.1000”

      GEOFFCKC reply on August 10, 2019
      “Which is an Insider build, it’s not yet fixed in the normal build eg. 18362.267 AFAIK.”

      HP EliteBook 8540w laptop Windows 10 Pro (x64)

    • #1936258 Reply

      BATcher
      AskWoody_MVP

      Thanks to everyone for their replies.  Again ploughing through the Replies in my original link, the final Reply (dated 1st September) now indicates that:

      “Now fixed in version 18362.329 ” 

      https://support.microsoft.com/en-gb/help/4512941/windows-10-update-kb4512941

      This link says, inter alia:

      This non-security update includes quality improvements. Key changes include:

      Addresses an issue that displays a black screen when you use Remote Desktop to connect to a machine running Windows 10, version 1903.

      https://support.microsoft.com/en-gb/help/4512941/windows-10-update-kb4512941

      I’ve applied this update, but won’t be able to test it works until Saturday.

      BATcher
      • This reply was modified 1 month, 1 week ago by  BATcher.
      • #1964288 Reply

        anonymous

        Hello,

        We have HP z2 g4 mini PCs – Windows 10 Pro 1903 – we have installed the updates above and we still get a black screen on remote desktop. We tried changing the systems we are remoting to to use the MS Basic Display Driver but that did not resolve the issue. Rebooting allows the system to work for an unknown amount of time before it stops working again until the next reboot. Any other ideas and or does anyone know if MS knows this is still an issue?

        W3

        • This reply was modified 2 weeks, 5 days ago by  PKCano.
        • This reply was modified 2 weeks, 5 days ago by  woody.
        1 user thanked author for this post.
        • #1964423 Reply

          woody
          Da Boss

          What build number? (Have you installed the latest patches?)

    • #1966420 Reply

      anonymous

      Same here.  Installed latest KB4512941 (OS Build 18362.329) update but still getting RDP black screen on HP EliteDesk 800 G4 SFF desktops.

      HTML removal – Please use the ‘Text’ tab in the post entry box when you copy/paste.

      • #1966443 Reply

        anonymous

        Edit to last Anon post:

        I installed KB4517211 (OS Build 18362.387) and still have the RDP black screen on HP EliteDesk 800 G5 SFF and HP 800 G3 Mini desktops. I ran HP SDM on both models to ensure all OEM drivers are current as of 9/27.

        • #1966525 Reply

          woody
          Da Boss

          Thanks for the reports, folks, but please… we have Anonymous 1, Anonymous 2 and Anonymous 3, with Anonymous 3 claiming to be Anonymous 2.

          Could I please convince you folks to register on the site? It’s free, easy, and you just have to respond to one email. You can even use a throwaway email address, if you like.

          We have some contributors who need to stay anonymous – usually because of their employer or their country. I really want to keep anonymous posts open. A little effort would go a long way, in this case.

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

    Reply To: Build 1903 – Intel Q45/Q43 driver conflict causes RDP black screen

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