none
Black Screen of death on a 2016 RD Session Host RRS feed

  • Question

  • Hi

    I have received a call from a customer telling me that he is experiencing the black-screen-of-death issue on a newly installed 2016 RD session Host server. I know there was a fix for that issue in RDS 2012 R2, but I have yet to come across information about this issue in 2016.

    Has anyone else seen this issue in 2016?


    Monday, January 2, 2017 11:15 AM

Answers

All replies

  • Hi

    I have the same problem and i create an other topic

    https://social.technet.microsoft.com/Forums/en-US/c2dfe59a-3aa1-40b9-b1ff-65e57e12793c/rds-2016-blue-screen-and-issue-with-umrdpservice?forum=winserverTS

    Monday, January 2, 2017 2:38 PM
  • Hi

    Have you opened a support case at Microsoft about this issue?

    Monday, January 2, 2017 2:45 PM
  • Hi

    No for me and you ?

    Best Regards

    Monday, January 2, 2017 2:48 PM
  • Well we are considering it.

    My customer is currently migrating their RDS 2012 R2 setup to 2016, but this is a show stopper.

    Monday, January 2, 2017 2:51 PM
  • Hi

    I just create a support case (#117010215122970).

    Best Regards

    Monday, January 2, 2017 3:11 PM
  • Since the installation of the KB3213986 https://support.microsoft.com/en-gb/help/4009938/windows-10-update-kb3213986 the problem is disappeared


    Friday, February 17, 2017 8:02 AM
  • Hi Kasper,

    In my experience this issue should be resolved as of the January 10, 2017 (KB3213986) update to Server 2016.  If you have installed all the latest updates on the customer's server and they are still seeing this issue please reply back.

    Thanks.

    -TP

    Sunday, March 19, 2017 10:43 PM
    Moderator
  • Hi TP

    I have notified my customer of this fix, I have however not heard from him, so I am unable to confirm it.

    Monday, March 20, 2017 5:16 AM
  • I've got a 2016 Server installation with the same issue. I attempted to apply KB3213986 and it tells me it's not applicable for my 2016 Server. Between this, the update-nag-screen-from-hell, and Edge constantly taking over as the default .pdf viewer I'm really looking forward to having more Linux and Less Windows in my life.
    Thursday, June 22, 2017 1:02 PM
  • hi,

    i can confirm that the "black screen on rds login on server 2016" is not resolved. our farm is fully patched and i get this issue regularely on my session hosts ...

    best regards

    Tuesday, July 4, 2017 9:43 AM
  • same issue with RDP Blank screen on Windows server 2016.

    tired with all users with the same problem. User sucessfully logs in but the after 5 minutes it throws a blank screen. cannot open anything like explorer or task manager etc..

    Completely unresponsive.

    Thursday, August 10, 2017 9:14 AM
  • This issue is still happening. I have using a farm of WS2016 and it happens in all of them
    Wednesday, October 4, 2017 2:11 PM
  • if the problem is still relevant
    stop the AppReadiness service
    Wednesday, November 8, 2017 8:52 AM
  • Can confirm this is still happening here. Windows 2016 Standard with GUI on HPE DL380 Gen9 servers. Have had 3 occurrences of this issue. Tried restarting the Winlogon and Explorer processes and also the AppReadiness service. None of which have solved the problem
    Tuesday, January 9, 2018 10:08 AM
  • it's the "audiodg.exe". kill the process and in most cases the gui will pop instantly, allowing users to login again.

    source:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/f18fa9e9-2f5b-42ad-9248-38685542134c/remote-desktop-into-server-2016-gives-black-screen-same-issue-as-bug-recently-foundfixed-in-2012?

    Thursday, February 1, 2018 12:59 PM
  • it's the "audiodg.exe". kill the process and in most cases the gui will pop instantly, allowing users to login again.

    source:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/f18fa9e9-2f5b-42ad-9248-38685542134c/remote-desktop-into-server-2016-gives-black-screen-same-issue-as-bug-recently-foundfixed-in-2012?

    There are several black screen causes with 2016:

    • Audiodg.exe (related to an endless loop within audiodg.exe created by Firefox) If you problem relates to audiodg.exe, where terminating audiodg.exe allows the user to get to desktop then read this fix:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/4e3ff4ea-ad23-4dda-b1e9-022f8d76c8e6/remote-desktop-rds-2016-gives-back-screen-on-logon-and-prevents-progression-to-desktop-audiodgexe?forum=winserverTS#5b3597fb-898d-4817-90c6-8520bcfd1016

    • Nvidia Quardo issue If you are running a nvidia quadro graphicas card  and only get 6 -7 users on a host on bare metal then read this (you need a later graphics driver 385.08 or later, a bug existed in the old one) In the event logs you will see dwm.exe crashing when the users try to connect :

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/6779b586-c158-491c-b76b-353d5a490642/server-2016-rds-connections-maxing-out-and-crashing-dwmexe?forum=winserverTS#0f413770-5da6-4829-983b-8f6917f3a148

    • Nvidia quadro blue screen issue exists with 391.33
    • The patch mentioned above
    • Other things to check: Anything else you have in run registry

    hklm\software\microsoft\windows\currentversion\run

    hklm\software\wow6432node\microsoft\windows\currentversion\run

    Active Setup items, A few app developers are adding stuff in here now. Do not delete all of these, they are small installer type apps. This is where the small app windows (you see them flash past just before desktop setting up IE etc).  They launched on your first logon to a new host to setup IE. 3rd party apps here are bad and likely delay logons and could be causing your issue. The key "IsInstalled" controls if it needs to be run or not.

    Suggest you backup the keys then test:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Active Setup\Installed Components

    Here is an example of a Google chrome active setup item that can be safely backed up and removed

    •  Startup C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp, or via scripts GPO) could also be causing the issue
    • Disable windows error reporting user prompt, you may have an app crashing during logon this will cause the (default) windows error reporting window to activate.  The problem is the users do not see the pop up via rdp becuase the session is not interactive enough at that stage. They can't see to click the buttons so the session does not progress to desktop.

    Disable the prompt only:

    Group policy method for the prompt behavior (I found WER Prompt was set as default action, used the policy to reverse it):

    You can also set the windows erorr reporting component not to prompt the user, but do it silently.

    1. Open the Local Group Policy Editor.

    2. In the left pane of the Local Group Policy Editor, click/tap on to expand Computer Configuration, Administrative Templates, Windows Components, Windows Error Reporting









    Thursday, July 19, 2018 12:46 AM