FSLogix black screen at login

[tylital520]

Environment:

CVAD 1912 CU1

VDA version: 1912 CU1

VDA client OS: Windows 10 v1909 (OS build: 18363.1256)

FSLogix version: 2.9.7621.30127

Citrix UPM used.

MCS used

 

We are using FSLogix Office365 containers with our Citrix CVAD Windows 10 desktops. The idea is to use the container mainly for OneDrive data. We're not using it for Outlook (it is not even installed). When our users login they are getting a black screen for 10-40 seconds before desktop with icons is shown:

 

 

Here are the troubleshooting steps I have tried so far:

 

• Removed VDA client with VDA Cleanup utility and reinstalled the client -> no change
• Updated FSLogix to the latest version -> no change
• Removed our antivirus client -> no change
• Made sure Windows Defender is disabled -> true, disabled with GPO
• Disabled App Readiness Service -> no change
• Enabled/Disabled Windows Search Service -> no change
• Removed Office and FSLogix, installed everything back in order which was suggested over here: https://virtualwarlock.net/how-to-install-the-fslogix-apps-agent/  -> no change
• Removed FSLogix -> black screen disappears and login time goes from 60-70 seconds to ~30 seconds.

 

On the first login we see the following warnings in Windows Application log:

The winlogon notification subscriber <frxsvc> is taking long time to handle the notification event (StartShell).
The winlogon notification subscriber <frxsvc> took 282 second(s) to handle the notification event (StartShell).

 

Here's the FSLogix log from C:\ProgramData\FSLogix\Logs\ODFC for the first login which took 329.03 sec according to Citrix Director:

 

edit: log removed

 

Here's the FSLogix log for the second login which took 66.66 sec according to Citrix Director:

 

edit: log removed

 

I've found the following discussions about the topic, but none of the solutions provided have solved the issue: 

https://social.msdn.microsoft.com/Forums/en-US/c3004697-ed02-4c81-9ef0-d082f52911b5/fslogix-slow-login-issues?forum=FSLogix
https://social.msdn.microsoft.com/Forums/office/en-US/fa008c11-b70c-4da9-9fb8-de90729fd229/black-screen-after-login-takes-over-a-minute-to-login?forum=FSLogix&prof=required

 

I am all out of ideas. Has anyone else experienced this and have you been able to solve this?

Edited December 17, 2020 by tylital520
removed logs for security reasons

[tylital520]

This seems to be a file server issue. When I moved the vmdx location to the local disk I am not seeing the black screen. 

[Salim Hurjuk]

Try VDA 1912 CU2

[tylital520]

13 hours ago, Salim Hurjuk said:

Try VDA 1912 CU2

Unfortunately that didn't help.

[tylital520]

Ok, so the root cause was the file server where we stored the VHD(x) files. Here's my troubleshooting steps in case someone else faces something similar:

 

The logs from C:\ProgramData\FSLogix\Logs\ showed that attaching the VHD(x) took a long time:

Quote

VHD(x) attach request returning after 4359 milliseconds

 

• Changed the VHD Location Group Policy setting to point C:\Temp
• Made sure the MCS allocated random non-persistent desktops don't turn off after logoff by running the following PowerShell command on Delivery Controller:

Set-BrokerDesktopGroup -Name "delivery group name" -ShutdownDesktopsAfterUse $false

• Set all but one desktop to maintenance mode.
• Launched the desktop after changing the VHD Location and didn't notice the black screen. The delay when attaching the VHD(x) also went down and logon time went from ~70 seconds to 25 seconds.

We've now fixed the file server and everything seems to be working again.

[Stefan Wendrich1709160263]

What was the issue on the fileserver?

[Vijeesh Kumar]

On 12/17/2020 at 12:01 PM, tylital520 said:

Ok, so the root cause was the file server where we stored the VHD(x) files. Here's my troubleshooting steps in case someone else faces something similar:

 

The logs from C:\ProgramData\FSLogix\Logs\ showed that attaching the VHD(x) took a long time:

 

• Changed the VHD Location Group Policy setting to point C:\Temp
• Made sure the MCS allocated random non-persistent desktops don't turn off after logoff by running the following PowerShell command on Delivery Controller:

Set-BrokerDesktopGroup -Name "delivery group name" -ShutdownDesktopsAfterUse $false

• Set all but one desktop to maintenance mode.
• Launched the desktop after changing the VHD Location and didn't notice the black screen. The delay when attaching the VHD(x) also went down and logon time went from ~70 seconds to 25 seconds.

We've now fixed the file server and everything seems to be working again.

What was the issue you fixed in file server ?

[tylital520]

On 6/24/2021 at 1:13 PM, Vijeesh Kumar said:

What was the issue you fixed in file server ?

Well we actually installed a new file server, so the root cause ended up being a mystery.

[lei zhang1709161436]

我有相同的问题，使用旧版本的fslogix后正常，但同时带来了explorer.exe高cpu的问题