Forum Discussion

alextorquatoc's avatar
alextorquatoc
Copper Contributor
Sep 18, 2023

The file manager doesn't open anymore! I can't open any folders.

Guys, please help me.

I've been facing an issue with my version since the last update!

 

The file explorer no longer opens; I can't open any folders on my Dell G3 3500 laptop.

Since the last update, I've been unable to access files on my laptop for two days because the file explorer won't open.

 

When I click on it, it simply appears as if it's going to load and open, no error messages appear, the screen blinks, the taskbar at the bottom disappears and then returns to normal, but the file explorer doesn't open.

 

My system version is Windows 11 23H2 Build 25951.10.10 (Build 25951.rs_prerelease.230908-1539).

I've tried various methods like restarting File Explorer, ending the task, using CMD, and even attempted some commands to scan for errors like SFC. I also tried to update video card drivers and cleaning the file explorer in the properties.

 

Even Microsoft support via chat accessed my machine through remote access and ran various tests, but nothing worked!

 

They said the only option left is to post here in the Windows 11 insider community to try and get help to resolve this.

 

Could someone please assist me?

10 Replies

  • Anonymous's avatar
    Anonymous
    Had the same problem as OP, I've just read somewhere that previous use of ViVeTool (as it was in my case to disable bing search and stuff) breaks some features that are needed for the new file explorer to work, what I did was:
    1. download latest vivetool (0.3.3 as of now command line version, not the GUI version)
    2. run terminal as admin
    2.1 terminal input: cd (wherever the vivetool zip was unzipped)
    2.2 terminal input: vivetool /dictupdate (maybe this step is optional)
    2.3 terminal input: vivetool /fullreset
    3. restart PC
    This works with all the updates applied, now my PC is running version 23H2 (stable channel) and the file explorer works again without issues
    • digitaljam's avatar
      digitaljam
      Copper Contributor
      Thank you very much! I forgot that I've used Vivetool to enable hidden explorer features.

      Also I want to add some useful info:

      1. in PowerShell or Terminal you have to prefix the commands with ".\"
      or you’ll get this error:

      vivetool : The term ‘vivetool’ is not recognized as the name of a cmdlet, function, script file, or operable program.

      2. Vivetool github link: https://github.com/thebookisclosed/ViVe
  • digitaljam's avatar
    digitaljam
    Copper Contributor

    alextorquatoc 

     

    I have the same problem. With the same description "When I click on it, it simply appears as if it's going to load and open, no error messages appear, the screen blinks, the taskbar at the bottom disappears and then returns to normal, but the file explorer doesn't open."

     

    It happened after updates on the screenshot:

     

    About: 

    • digitaljam's avatar
      digitaljam
      Copper Contributor
      uninstalling KB5031354 and KB5030651 updates helped
  • engalshwmi's avatar
    engalshwmi
    Copper Contributor
    I encountered a similar issue and attempted several internet-based solutions, but none of them worked. Eventually, I resolved the problem by uninstalling the latest update and pausing Windows updates.
    • Anonymous's avatar
      Anonymous

      I had today that same problem, but my pc is on the stable channel, even if this is a insiders´ forum I think this may be relevant/useful.
      In my case it was caused by the public release on windows update of the KB5030310 update that brings copilot and the new file explorer, the file explorer was completely unusable aside from the desktop and taskbar, whenever it attempted to open any folder the explorer.exe process just crashed and restarted by itself.
      After uninstalling that update the problem was solved, I would suggest reverting back the latest update if you did not try that already, then put a pause on the updates until someone at MS works on it.

       

      Edit:

      I don't know if it helps but event log shows this:

      - System

      - Provider

      [ Name] Application Error
      [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57}
      EventID 1000
      Version 0
      Level 2
      Task 100
      Opcode 0
      Keywords 0x8000000000000000
      - TimeCreated

      [ SystemTime] 2023-09-26T23:03:12.4177443Z
      EventRecordID 90761
      Correlation
      - Execution

      [ ProcessID] 12388
      [ ThreadID] 17584
      Channel Application
      Computer (omitted)
      - Security

      [ UserID] (omitted)

      - EventData

      AppName explorer.exe
      AppVersion 10.0.22621.2361
      AppTimeStamp 480de713
      ModuleName explorerframe.dll
      ModuleVersion 10.0.22621.2361
      ModuleTimeStamp 7b666dd1
      ExceptionCode c0000005
      FaultingOffset 000000000000877b
      ProcessId 0x40e4
      ProcessCreationTime 0x1d9f0cd9f951959
      AppPath C:\WINDOWS\explorer.exe
      ModulePath C:\WINDOWS\system32\explorerframe.dll
      IntegratorReportId c537ffcb-eaeb-43c2-8e12-a7afb0ded4c3

Resources