The Windows 3.1 "goth theme" call
Chen published the story as a tale from the Windows development trenches. The setup is simple. Back in the Windows 3.1 era, a customer called product support. It turned out the customer liked black a little too much and had built a Goth theme for themselves. The customer said Windows started, but once the logo went away, all they saw was a blank screen.
After some questioning, the support engineer worked out what had happened. According to Chen, the customer had set the wallpaper, title bar, button, window background and window text colors to black. Chen's account says that every color in the Colors control panel was set to black, window text included. His verdict on the trap: once you get into this situation, it's hard to get out because you can't see anything.
How it was fixed (Chen's guess)
Chen says he doesn't know how the support engineer fixed it. His guess is that they booted into MS-DOS, ran EDIT.COM and deleted the [colors] section from win.ini. That would put all the system colors back to their defaults. This is a guess about a Windows 3.1 configuration file. It isn't a procedure for any modern version of Windows, so don't try it on current systems.
Was the screen really all black?
Chen's post says nothing about the mouse pointer, the icons, or the exact appearance of the screen. Some embellishments in aggregator rewrites of the story, such as the pointer surviving or the icons vanishing, are speculation, not part of his account.
Commenters on Chen's post also questioned whether the screen could have been literally black. Some said Windows 3.1 couldn't recolor everything, and that icons and some controls would likely still have been visible. Those are reader comments, not verified findings, and Chen didn't claim every pixel was black. The reported symptom was "all I see is a blank screen", and the story ends there.
The lesson stands either way. The same "black screen" complaint can be self-inflicted, and the support engineer only found out by asking questions.
The modern power-button behavior
Chen uses the story to tie off a post about forced shutdowns. As he describes it:
- 12 seconds: holding a PC's power button this long turns it off at the hardware level, without telling the operating system. This is a safety net for when the normal Shut down command doesn't work.
- 8 seconds: the Windows kernel realizes the user is trying to force a power-off, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on.
- Incomplete dumps: Chen says four seconds isn't always enough to capture the information, so the dump can be incomplete. He believes Windows Insider builds show a message, worded something like "please let go of the power button", so the kernel has more time. That is his recollection, not a documented UI string.
Not everyone accepts the timing. A reader commenting on Chen's post said that every desktop PC they've used shuts off after about five seconds of holding the button. If so, the 8-second dump would never get a chance to run. Chen's post doesn't address hardware or firmware differences, so treat the timings as a description of Windows behavior, not a guarantee for every machine.
OSNews raised a related worry. The dumps made after the 8-second hold do get sent to Microsoft once the computer starts again. Windows Latest noted that Microsoft's own diagnostic-data documentation says a crash's memory state may unintentionally include parts of a file you were using, and that Microsoft hasn't said what an LPBH dump contains. That is a fair privacy question for admins to keep in mind.
What "black screen LPBH" means
Chen says these emergency kernel dumps are internally classified as "long power button hold" (LPBH) failures, and one recorded item is whether the screen consists entirely of black pixels. Those cases are sub-classified as "black screen LPBH" and go to a special virtual team, which Chen says he belongs to.
He lists several possible situations:
- A broken video driver.
- A working video driver that the desktop compositor is feeding black pixels.
- A working compositor with nothing drawing to the screen. That splits further into "nobody around to draw" and "the process that normally draws is hung".
So the black-pixel flag is a triage clue, not a diagnosis. Chen doesn't say how often these dumps lead to fixes, and he gives no user-facing checklist. Windows Latest summed up the Windows 3.1 anecdote this way: it's hardly a job for the black screen LPBH team.
What this means for Windows users and admins
- A black screen has more than one cause. In the 3.1 story it was a deliberate color choice. On modern PCs it can be a driver, compositor or drawing-process problem.
- Hold-to-power-off may do more than cut power. If Windows has time, it may capture a kernel dump that goes to Windows Error Reporting on the next boot. Admins who care about diagnostic data policy should know this.
- If you hold the button, hold it all the way. Chen's description implies that letting go early may mean the dump isn't taken, or is incomplete. The post doesn't state this outright.
- Dark mode is the safe version. Today's dark themes keep text and controls readable, which the all-black 3.1 setup did not.
Chen's recovery guess is a historical curiosity. The post's main practical value is the explanation of what the 8-second and 12-second marks mean, and why Microsoft engineers keep a dedicated team on black screens.
References
- Windows 3.1 user turned every pixel black with a 'Goth mode' theme - news.lavx.hu news.lavx.hu · 2026-10-31T12:32:24.816000+00:00
- The support case of a customer who said that all they could see was a black screen - The Old New Thing devblogs.microsoft.com
- How long do you need to hold down the power button to turn off a PC? osnews.com