I work for an MSP and we've been seeing an intermittent issue on client workstations after Windows updates. The sign-in screen appears normal, but after the user logs in, Windows shows a black screen while the mouse cursor remains visible and responsive. This has mainly affected end-user PCs rather than servers or remote sessions, and it has occurred across different clients and hardware configurations.
We haven't identified the specific update responsible. Reinstalling graphics drivers helped temporarily in some cases, but the problem returned. The workaround that currently seems reliable is to open Task Manager with Ctrl+Shift+Esc, run an elevated Command Prompt, execute `powercfg /h off`, and reboot. This disables Fast Startup, which may be involved.
Has anyone seen this behavior or identified a particular update, driver, service, or configuration that causes it? We need to maintain update compliance, so simply blocking all updates isn't a practical solution.
4 Answers
I'd start by preventing Windows Update from installing display drivers and use the manufacturer's driver packages instead. Also check firmware and chipset updates. Microsoft-provided graphics drivers can occasionally cause problems even when the update itself looks unrelated.
There are several possible causes besides the update: antivirus or application-control software blocking Explorer, inaccessible mapped drives or DFS paths, printer-driver installation delays, or policies waiting on a network resource. Collecting event logs and comparing affected machines would help narrow it down, since the issue doesn't appear tied to one known update.
The fact that the cursor still works and Task Manager opens makes a basic display failure less likely. On some affected systems, restarting or terminating State Repository Service or WSAIfabric allows Explorer to load, although that isn't a guaranteed fix. It may be a shell or service startup issue rather than the graphics hardware itself.
The workaround is worth testing proactively. Running `powercfg /h off` disables hibernation and Fast Startup, so it can prevent problems caused by a bad hybrid-shutdown state. It isn't proof that a particular Windows update is responsible, but deploying that setting before patching may be a reasonable pilot test while you continue identifying the trigger.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures