# Windows Explorer Goes AWOL, and Takes the Desktop With It

**URL:** <https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374>\
**Category:** Factual Questions\
**Created:** [February 25, 2023, 8:54pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374 "2023-02-25T20:54:22Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![OttoDaFe](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ottodafe/32/356_2.png) [@OttoDaFe](https://boards.straightdope.com/u/OttoDaFe)\
**Post date:** [February 25, 2023, 8:54pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/1 "2023-02-25T20:54:23Z")

</div>

Computer is an HP 15-gw0000 laptop running Windows 11 🥴. For the past week or so, whenever I do a cold start or restart the desktop and taskbar appear briefly, then either disappear completely or flash; either way I can’t proceed. If the former, Windows Explorer is missing from Task Manager (I can get there using Ctrl-Alt-Del, so the OS is running); if the latter, it comes and goes in approximately the same rhythm as the flashes. The only way to recover is to boot into Troubleshooting and either roll back to a previous restore point or run Start-up Repair, which I have a feeling is doing the same thing. Then I can start normally until the next time.

According to Microsoft, the culprit is either a bad video driver or a bad application. Since Task Manager doesn’t flash, it’s probably not a video issue; and as far as I know there have been no OS updates or new/updated applications. So I’m left in the dark, pretty much literally as far as the desktop is concerned.

I have a sneaking/sinking feeling my only way out is at least an OS reinstall or a system reset, and to that end I’ve been sucking everything I think is even slightly relevant off onto a thumb drive. But before I push the red button I figured it wouldn’t hurt to run the problem past the Dope. As always, thanks in advance for any suggestions/insights.

---

<div class="post-metadata">

**Author:** ![fordgt100](https://avatars.discourse-cdn.com/v4/letter/f/5daacb/32.png) [@fordgt100](https://boards.straightdope.com/u/fordgt100)\
**Post date:** [February 25, 2023, 9:12pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/2 "2023-02-25T21:12:51Z")

</div>

I think your plan is sound. Get everything file-wise off the computer and do a reinstall. Make sure you have an aux HD that is backing up whatever you have automatically (or do it at the end of each day yourself). Once it’s up and running, install programs one at a time and see if it triggers this again.

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [February 25, 2023, 9:13pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/3 "2023-02-25T21:13:27Z")

</div>

A few things I can think of to try.

First off, what happens if you just Run explorer.exe from Task Manager after it completely crashes? Does it do the same thing? I’m not sure this will help anything, but I’m curious if it’s something going on at boot that takes out Explorer, or if explorer itself fails.

The main thing I can think to try is to disable all startup apps before rebooting, and see if anything changes. Similarly, you could try this program and disable any shell extensions (mini-programs that run when you launch Explorer and add features).

> **[ShellExView - Shell Extension Manager For Windows](https://www.nirsoft.net/utils/shexview.html)**
>
> Shell Extensions Manager

And then, if any of this works, you would reenable things until you found the culprit.

---

<div class="post-metadata">

**Author:** ![scudsucker](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/scudsucker/32/14101_2.png) [@scudsucker](https://boards.straightdope.com/u/scudsucker)\
**Post date:** [February 25, 2023, 9:16pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/4 "2023-02-25T21:16:59Z")

</div>

It has been a long, long time since I ran Windows, but have you tried something in the terminal/console/cmd window (whatever it is called these days) like this:

> [@](#):
>
> taskkill /F /IM explorer.exe & start explorer

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [February 25, 2023, 9:20pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/5 "2023-02-25T21:20:53Z")

</div>

There are a lot of 3rd-party extensions meant to connect into Explorer that Explorer needs to defend itself carefully from. Buggy or version-incompatible examples can crash Explorer, and Windows gets the blame.

Since the Win95 days MS has gotten a lot better at detecting and defeating this stuff. Explorer is real well-armored against bad plug-ins, shell extensions, etc. But there’s always a chance of an as-yet unfixed crashing incompatibility.

I don’t know that I can give any specific advice unless you’re already a real windows administration guru. And if you were, you’d already be doing the techie things.

One bit f good news: If the problem is common, they’ll be getting lots of telemetry reports about this quickly. Failure to boot to desktop errors are real high priority for fixing.

---

<div class="post-metadata">

**Author:** ![Dr.Strangelove](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dr.strangelove/32/6613_2.png) [@Dr.Strangelove](https://boards.straightdope.com/u/Dr.Strangelove)\
**Post date:** [February 25, 2023, 10:38pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/6 "2023-02-25T22:38:22Z")

</div>

Try firing up Event Viewer by running eventvwr.exe from Task Manager. Open up Windows Logs-\>Application and check for “Error” entries. Exactly what shows up is hard to say, but you may find a clue (like, a shell extension of the kind that **BigT** and **LSLGuy** mentioned).

Here’s an example of one that I just spotted on my system:  
[![](https://i.imgur.com/9hhbvyo.png) ](https://i.imgur.com/9hhbvyo.png)

Didn’t cause any Explorer problems; this one just crashed itself. But I can easily see that it’s from the software included with my motherboard.

---

<div class="post-metadata">

**Author:** ![OttoDaFe](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ottodafe/32/356_2.png) [@OttoDaFe](https://boards.straightdope.com/u/OttoDaFe)\
**Post date:** [February 26, 2023, 4:07pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/7 "2023-02-26T16:07:43Z")

</div>

Well, I think\* I have the problem solved. Microsoft’s diagnostics said that it’s not a video issue if the Task Manager window isn’t flashing, but on the time-honored principle that “it couldn’t make things worse” I rolled back the display driver in Device Management — it was “updated” about six weeks ago — _et voilà_, after a restart the taskbar and desktop appeared normally. Multiple restarts and power cycles confirm that it’s working. For now.

Why the problem took a while to manifest, and why it crashed explorer, are among the mysteries of the universe, along with dark matter and the enduring popularity of {given the category, insert your target of choice here}. Or just blame it on Windows 11 — works for me.

(Side note: one of the first things I saw when going into Auto Repair was “Your PC did not start correctly.” Gee, thanks, I hadn’t noticed.)

I’ll probably have a bit more to say in response to the discussion, but for the moment I’m just going to enjoy having a functioning laptop. Until if/then, thanks(!) for the insights and suggestions: they are much appreciated.

\* Over 40 years in IT have made be a bit cynical about _any_ fix being permanent, especially where Windows is involved.

---

<div class="post-metadata">

**Author:** ![Isilder](https://avatars.discourse-cdn.com/v4/letter/i/cc9497/32.png) [@Isilder](https://boards.straightdope.com/u/Isilder)\
**Post date:** [February 26, 2023, 11:48pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/8 "2023-02-26T23:48:28Z")

</div>

A likely thing is that its caused by Nvidia Geforce User Experience _Driver_ Component

You could avoid that when you update driver

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [February 26, 2023, 11:58pm UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/9 "2023-02-26T23:58:02Z")

</div>

Did you update the driver manually, or did it autoupdate? If it autoupdated, I’d suggest you disable getting drivers from Windows update.

> **[How to Enable/Disable Automatic Driver Updates in Windows 11](https://www.minitool.com/news/enable-disable-automatic-driver-updates-windows-11.html)**
>
> Learn how to enable or disable automatic driver updates in Windows 11 in this tutorial. 3 ways with detailed guides are included.

---

<div class="post-metadata">

**Author:** ![OttoDaFe](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ottodafe/32/356_2.png) [@OttoDaFe](https://boards.straightdope.com/u/OttoDaFe)\
**Post date:** [February 27, 2023, 1:45am UTC](https://boards.straightdope.com/t/windows-explorer-goes-awol-and-takes-the-desktop-with-it/980374/10 "2023-02-27T01:45:18Z")

</div>

It’s actually an AMD adapter (Raedon Vega 3, if Device Manager is to be believed). It was a manual up(?)date based on a notification that there was a current release available. I’ll be filing a bug report in the soon future.

As I said (or at least implied), what I found perplexing is that several weeks passed before the driver started causing problems. And I can’t identify anything in the interim which would have triggered the failure
