Device fails to start upon turning on after being off.
Device fails to start upon turning on after being off.
Here’s a rephrased version of your text:
So, there isn’t much to describe in this situation—it’s quite strange. I’d step outside for a while, so I turned off my dual monitors and kept the desktop active. Then, when I came back, the system that manages the desktop GUI (Explorer.exe) seemed to stop working around 2k or later. I can’t click anywhere, whether it’s right or left. The cursor moves, but everything keeps refreshing. In Task Manager, I can still interact with threads and manage them, yet nothing feels right. Telegram loads new chats, Firefox refreshes, etc., but I can’t actually click anything. The only solution I found was to give the three-finger salute and log out. After logging back in, everything works properly. I’m sharing screenshots, though I’m not sure how they’d help. I enclosed my dxdiag file for reference. In the Event Viewer, I noticed a few errors; Windows Hello for Business isn’t launching. The device is AAD joined (AADJ or DJ++ Not Tested), and a user logged in with AAD credentials didn’t trigger Windows Hello. No policy was enabled for Windows Hello after logging on. Local computer meets Windows Hello hardware requirements? Not tested. User isn’t connected via Remote Desktop. Yes, the machine has an Active Directory join. The certificate for local authentication is active. Machine follows no specific policy. Cloud trust for on-premise authentication is enabled. The user account has a Cloud TGT that isn’t being used. The application-specific permissions don’t allow Local Activation for this COM Server. I’m unsure if this will work. Please let me know if you have more details. Thanks! By the way, just a note—my motherboard is an Asus TUF Gaming x570; I didn’t need WiFi or a GPU. DxDiag.txt edited on May 14, 2023 by HazyDurg for clarity.