Black Screen Gif ((BETTER)) Download
Manuel Sohne
Hello,
I am creating my Citrix Worker image via MECM, using a task sequence. In the task sequence I can choose between Server 2016/2019/2022, so the window-side settings are all identical. If I create a worker with Server 2019 and VDA 2203CU2 this way and deploy it via PVS, it works fine. A desktop login on the worker is possible without any problems. When I create the same worker with Server 2022 and VDA 2203CU2, I get a black screen when logging in. If I then log in locally to the console of the server, the black screen disappears and the desktop appears. But I still can not make any interactions in the session?! When I log out of the local session, the black screen appears again in the session. How can this problem be solved?
I have tried the cleanup script ( -cvad-connectionfailure-after-install-ltsr-2203-cu2-on-server-2022/page/3/), as well as disabling the WDDM driver ( -session-goes-to-black-screen-after-launch-when-using-windows-21h2-multisession). I did not disable the WDDM driver via GPO but via RegKey:
This is positively bananas to me. I wrestled with this problem through the summer and could never figure it out. Citrix support was not helpful either. I just had the black screen issue again after upgrading to 2203 CU4. I uninstalled CWA, rebooted the VM, and was able to log in like nothing happened. This revelation is priceless.
I am dealing with an internmitent issue where randoms users, across random servers logon and post windows logon screen (processing/apply policies etc) they are presented with a black screen varying from 0-3 minutes.
There is no correlation in users and black screen length, the same user can have it for as little as 15 seconds upon logon and then next logon it can last up to 3 minutes. When it does not happens the logon process completes within 15 seconds. On average it happens once per 3x logons.
I am facing this problem with Doorbell 2. I see black screen with ring logo when playing motion video both on app and PC. Live view recording and playing is fine. Called ring help 3-4 times, tried all the remidies they suggested. No issue with the router speed, using same router for many years . They though it could be a hardware issue. They sent me a new door bell 2.
Hey @piotrr ,
The black screen issue is happening when Connect is not yet on 2.27 version, but we already updated the macOS version or if we erase & reinstall, but do not deploy Connect 2.27.
As soon as the package is updated in your Jamf Pro instance and use the updated package in PreStage too, you will not see the black screen issue anymore.
I replicated things, but now I'm getting a black screen after the disk check (when sddm is supposed to start). I can login to tty2 and disable sddm.service. When it's disabled I can login at tty1 and use "startx" to start my Plasma session (everything in it is working as expected).
So the most interesting part is that on boot the screen freezes at the output of fsck. If I go to tty2 (without logging in) and then go back to tty1 the screen is now black. If I just enter my password the system is starting. Also (just tried) - if I enter my password on the "stuck" output of fsck, I'm again logged in. So the greeter is there, but I can't see it for some reason - the screen is not refreshing from the console output to the greeter.
After the fsck output the screen blinks (through black) and freezes on the text output. When I type my password on this "screen", I get logged in and the session starts as expected. So the screen is not refreshing to show the greeter.
After logging in with my password at the initial sign-in before we reach the desktop screen, there is around a 5 minute black screen with only a mouse cursor showing. After 5 minutes the desktop shows up as usual. Restarting with Safe Mode doesn't have the black screen issue.
Formerly it was only black screens and everything else kept working (aircraft kept route and altitude for example). This time 787 lost altitude (only at 100-200 fpm, but continously). So I think it is a different issue and something with the plane (no general bug like the formerly black screens that happened for every plane).
Whenever I start my HP Envy I am given a black screen which after trying about everything you possibly can without seeing a thing I have had no luck fixing this. Basically I press the power button to boot it up, it begins it's bootup(judging by sounds) but shuts back down after a couple of seconds, after about 5 more seconds pass it begins to start back up again sounding like it used to sound when starting it up, However I am left with a black screen which I am unable to fix. Please help
df19127ead