Windows 11 Blinking Black Screen? Here's What I Did — And What Finally Fixed It

Photo for illustration only.

It was a regular morning at the office.

I was at my desk, minding my own business, when my officemate appeared beside me.

"Kuys, yung laptop ko kasi..."

I looked up. He had that specific expression. The one that says: something is wrong and I don't know what it is and I'm hoping you do.

I said yes. I always say yes. That's what happens when you become the unofficial IT guy in a government office. 😄

The Patient

His personal laptop. Windows 11. He brought it to work that day for whatever reason — personal stuff, side work, the usual. He powered it on in the morning, entered his login password, and then —

Blink.

Black screen. Seven seconds. Back. Black again. Seven seconds. Back.

The taskbar was gone. The desktop icons were gone. Everything just... blinked. In and out. Rhythmically. Like the laptop was trying to send an SOS in Morse code.

I sat down in front of it and watched it for a moment.

Blink. Seven seconds. Blink. Seven seconds.

I asked the standard first question: "Ano ginawa mo bago nangyari ito?"

He looked at me with complete sincerity and said: "Wala, Normal lang."

Which in IT support language means: "I have absolutely no idea."

Noted. Let's begin.

What Was Actually Happening Under the Hood

Before I walk you through the steps — here's what the research and the symptoms point to as the real cause.

Windows 11 has a known bug where explorer.exe — the process that runs your taskbar, desktop icons, and basically everything you see on screen — crashes, attempts to reload, and crashes again on a loop. Every time it tries to restart and fails, the screen blinks. Seven seconds. Blink. Seven seconds. Blink. That rhythm isn't random. That's explorer.exe dying and trying to come back to life over and over.

Microsoft confirmed this bug and released a fix in Windows 11 update KB5074105 in January 2026. If the laptop hadn't applied that update, and the corruption had already set in — the damage was done.

And in this case, it had gone even deeper than that. Not just the display layer. Not just explorer.exe. The user account profile itself was corrupted. Which is why what happened in Safe Mode made perfect sense — but I'll get to that in a moment.

This kind of deep system corruption reminds me of another case I wrote about — a USB flash drive that turned all its files into shortcuts. Different symptom, same root idea: Windows failing silently underneath while the surface still partially works.

Step 1 — Task Manager

First thing I always check when Windows is behaving strangely: Task Manager.

Pressed Ctrl + Shift + Esc.

Task Manager opened. And here's the interesting part — it was completely fine. Not blinking. Not affected. Running normally. CPU, memory, disk — all within normal ranges. No rogue process consuming everything.

But if you look closely in Task Manager during this kind of issue, you'll sometimes catch explorer.exe restarting repeatedly in the process list. That's the confirmation. That's the bug showing itself.

So whatever was causing the blink, it wasn't a runaway application eating system resources. The problem was somewhere deeper — in the display layer itself.

Step 2 — Device Manager, Display Driver

If Task Manager is fine but the screen is misbehaving — the display driver is the natural next suspect.

Opened Device Manager. Navigated to Display Adapters. Found the graphics driver. Right-clicked → Update Driver.

Windows searched. Found something. Installed it. Restarted.

Opened the laptop back up. Entered the password.

Blink. Seven seconds. Blink.

Still blinking. Driver update didn't fix it. Okay. Moving on.

Step 3 — Command Prompt, SFC and CHKDSK

When driver updates don't work, the next step is checking whether the Windows system files themselves are corrupted.

Opened CMD as administrator. Ran two commands.

First:

sfc /scannow

for illustration only. I forgot to took a photo on the laptop :D

System File Checker scans all protected Windows system files and attempts to repair any that are corrupted. It ran. Completed. Found some things, said it fixed them.

Restarted. Entered password.

Blink. Seven seconds. Blink.

Still blinking.

Second:

chkdsk /f /r

Check Disk scans the storage drive for errors — bad sectors, file system issues. Scheduled the scan for the next restart. Restarted. Let it run through the full scan on boot.

Completed. Restarted again. Entered password.

Blink. Seven seconds. Blink.

Still. Blinking.

At this point — between the driver update, the SFC scan, the CHKDSK scan, and the multiple restarts — we had burned through a significant chunk of the morning. And the laptop was still sending its seven-second SOS.

What I Also Tried — And Why Safe Mode Didn't Save Me

Before I hit reset, I tried one more thing.

Safe Mode.

The logic was sound — boot into Safe Mode, create a new admin account, transfer the files, fix the profile without wiping everything. Clean surgical fix. I've done it before on other machines.

Except this time, Safe Mode asked for the password.

I entered it. Incorrect.

I entered it again, carefully. Incorrect.

Same password that worked fine on the normal login screen — the one that got him past the blinking and into the broken desktop. But Safe Mode wouldn't accept it. I tried a few more times. Same result every time.

That's when I realized the problem was deeper than a software glitch or a bad driver update.

The user account profile itself was corrupted. Not just the display layer, not just explorer.exe — the profile that Windows uses to verify who you are was already broken. Correct password, broken profile behind it. The system couldn't match them anymore.

Safe Mode had nothing clean to boot into. There was no ladder back in.

That's when the reset stopped being the lazy option and became the only option.

Sometimes the nuclear option isn't impatience. It's the honest conclusion after everything else has been ruled out.

Step 4 — The Last Resort

There's a phrase in IT support that experienced people recognize immediately:

"I've tried everything reasonable. It's time for the nuclear option."😂

Reset PC.

I looked at my officemate. "i-reset na natin? Lahat mabubura, ano ayos lang?"

He looked at the laptop for approximately two seconds.

"Sige lang Kuys. Wala namang important file na eh"

I want to describe the feeling of hearing those words. It's relief. Pure, uncomplicated relief. No backup drama. No "wait, may files pa ako." No twenty minutes of transferring folders to a USB drive. Just: go ahead.

So I went ahead.

Settings → System → Recovery → Reset this PC → Remove everything.

The Part They Don't Tell You in the Tutorial

Here's where I added one extra step — and if you're doing this yourself someday, write this down.

During the Windows reset process, when it gets to the screen asking you to sign in with a Microsoft account, I bypassed it completely and set it up as a local account instead.

Here's how:

When the Microsoft login screen appears — before you type anything — press Shift + F10.

A Command Prompt window will open. Type this exactly:

start ms-cxh:localonly

Press Enter. Windows will immediately open the local account setup screen — no restart, no looping back through setup. Just fill in a username and password and you're done.

This works on both Windows 10 and Windows 11.

Why does this matter? A local account means the laptop runs independently — no Microsoft account required to log in, no syncing you didn't ask for, no "your settings are being restored from the cloud" surprises. For a personal laptop that one person uses, a local account is cleaner and simpler.

My officemate didn't need his Microsoft account tied to that machine. So we skipped it entirely.

Fresh install. Local account. Clean desktop. No blinking.

Fixed.

What Actually Caused It?

Corrupted user profile — that's the most accurate answer based on everything I observed.

The explorer.exe loop caused the blinking screen. But the fact that Safe Mode rejected a correct password tells the deeper story — the account data itself had broken down. A corrupted profile doesn't just affect what you see on screen. It can corrupt the credentials stored against that account, making it impossible to authenticate even in recovery environments.

What triggered the profile corruption in the first place? Most likely one of these:

A Windows update gone wrong — partially completed or conflicting updates are one of the most common causes of explorer.exe instability and profile corruption in Windows 11. Microsoft itself confirmed this bug and patched it in January 2026.

Corrupted system files — the SFC scan found issues and said it fixed them. What it couldn't fix was the deeper account-level damage already done.

Third-party software conflict — something installed recently, that he may not even remember installing, may have started the chain reaction. Without knowing his full install history, impossible to trace.

The reset resolved all causes simultaneously. That's both the beauty and the frustration of the nuclear option — it works, but it doesn't always tell you exactly why.

What I Learned (Again)

This is not the first time I've gone through the full diagnostic sequence — Task Manager, Device Manager, SFC, CHKDSK, Safe Mode — and ended up at reset anyway. It probably won't be the last.

The lesson isn't that diagnostics are useless. Each step rules out a category of problem and gives you real information. The SFC scan told me there was system file corruption. The CHKDSK told me the physical drive was intact. The Task Manager told me it wasn't a runaway process. Safe Mode told me the profile itself was gone.

Each piece mattered. Each step narrowed the diagnosis.

But sometimes the corruption is deep enough that repair tools can't fully reach it. When Safe Mode rejects a correct password — the profile is too far gone. At that point, the cleanest solution is the most complete one.

Reset. Fresh start. Move on.

The Decision Point Worth Knowing

If you're in the same situation someday, here's the clearest signal I can give you:

If Safe Mode accepts your password — you still have options. Create a new admin account, transfer your files, repair the profile. You don't have to reset.

If Safe Mode rejects your correct password — stop troubleshooting. The account data is corrupted beyond repair tools. Go straight to Reset PC. You're not doing anything wrong. The reset is the fix.

That one test — can Safe Mode authenticate you or not — tells you which road you're on.

The Backup Conversation Worth Having

My officemate said "Okay lang Kuys, burahin mo na lahat" and meant it. For him, that was genuinely true — his important files were elsewhere, the laptop was relatively clean, and a reset was no big deal.

But I want to say this clearly for anyone reading who might face the same situation someday:

Most people do have something worth saving. They just don't think about it until it's gone.

Photos. Documents. Browser bookmarks and saved passwords. Downloaded files. That one spreadsheet they've been quietly updating for six months.

Before any reset — even if the user says "just go" — ask twice. Check the Desktop, the Documents folder, the Downloads folder, and any browser-saved passwords. Thirty seconds of checking is worth more than three months of regret.

Luckily my officemate was right. Nothing important was lost. But the habit of checking first — that's worth keeping. 😄

Before I Close This Tab

Another officemate back to work.

This is government office IT support. Unofficial, unscheduled, and always exactly when you were about to do something else.

I don't mind. This is what I do. And the "Okay lang Kuys, burahin mo na lahat" response might be the most satisfying thing a user has ever said to me in ten years of being the office IT guy. 🤣

If your Windows 11 laptop is doing the same thing — blinking black screen every few seconds, taskbar missing — try the steps in order:

1. Task Manager (Ctrl + Shift + Esc) — check if explorer.exe is restarting on loop
2. Device Manager — update the display driver
3. CMD as Admin — run sfc /scannow then chkdsk /f /r
4. Check for pending Windows updates — look for KB5074105 or later in Windows Update
5. Safe Mode — if it accepts your password, create a new admin account and repair the profile
6. If Safe Mode rejects your correct password — the profile is gone; go straight to Reset PC
7. During reset setup — press Shift + F10, type start ms-cxh:localonly, skip the Microsoft account, set up local

And if your officemate says "just go" — count yourself lucky. 😄

Disclaimer: The steps in this post are based on personal experience and general IT troubleshooting practice. Results may vary depending on your specific Windows version and hardware. When in doubt, consult a licensed technician — especially for work or business laptops.

Have you experienced a blinking black screen on Windows 10 or 11? Did Safe Mode work for you — or did you end up going straight to reset? Drop it in the comments.

-Mavs

Source:

Microsoft — explorer.exe bug KB5074105  windowslatest.com/2026/01/31/microsoft-says-latest-windows-11-issue-crashes-explorer-exe-makes-taskbar-disappear-but-a-fix-is-rolling-out