Recommended Posts

Ok, this might seem like a strange thing to worry about, but on my 64-bit Windows 8 Pro (clean) installation, the File Explorer takes about twice as long (1.38 seconds) to start when I click a shortcut on the taskbar than when I click a shortcut from the start screen or the desktop (0.76 seconds). Is there any reason for this? How could I speed of the opening of File Explorer (and probably other programs) when launching from the taskbar? I probably wouldn't care as much if it wasn't such a noticeable difference when waiting for it to open. Both cases (desktop and taskbar) opened instantly on Windows 7 Ultimate.

Anything over 0.3 seconds is easily noticeable to the average human brain. This difference is well over that threshold. For a task that I perform many times a day, it is an annoying regression and I'm simply looking for insight. If you have nothing constructive to say, please move along.

I think it takes longer for the application to start from the superbar, because of the little anination it does when you click the icon.

Try turning off all Windows animations. That should help your speeds a bit.

(Or just turn off "animations in the taskbar".)

Anything over 0.3 seconds is easily noticeable to the average human brain. This difference is well over that threshold. For a task that I perform many times a day, it is an annoying regression and I'm simply looking for insight. If you have nothing constructive to say, please move along.

Moving along

  • Like 3

I think it takes longer for the application to start from the superbar, because of the little anination it does when you click the icon.

Try turning off all Windows animations. That should help your speeds a bit.

(Or just turn off "animations in the taskbar".)

Disabling all animations and/or the taskbar animations made no difference. Thanks for the suggestion, though!

Do you have any other programs installed or just Windows itself?

If you have security software try disabling it. Same with startup/background processes.

I do have other software installed now. Just a few common programs (like Google Chrome). I was having this problem before I installed them, though. I disabled all of my security software and startup programs, rebooted, and still have the problem. Interestingly enough, if I right click the File Explorer icon on the taskbar and click on one of the jump list entries, it opens just as quickly as if I used the Start Screen. There's just something wrong with simply left clicking the taskbar icon. At this point, it's a puzzle to solve, not so much a necessity.

I do have other software installed now. Just a few common programs (like Google Chrome). I was having this problem before I installed them, though. I disabled all of my security software and startup programs, rebooted, and still have the problem. Interestingly enough, if I right click the File Explorer icon on the taskbar and click on one of the jump list entries, it opens just as quickly as if I used the Start Screen. There's just something wrong with simply left clicking the taskbar icon. At this point, it's a puzzle to solve, not so much a necessity.

That's weird. Have you tried to unpin it and pin it again? That's all I can think of right now.

@OP

Have you installed all the Microsoft Updates after clean install?

There are bunch of updates (above 500 MB) available from Microsoft which improve performance and stability.

I have all the updates applied and don't see any difference in launching File Explorer in my machine.

It's super quick. I see it as soon as I click.

I refuse to believe this. If you have disabled all window animations and you are indeed trying to run the same File Explorer from both locations then there should be no difference at all. Try one thing for me though. Hit up CMD and type


explorer
[/CODE]

and tell us how long that takes to start up.

That's weird. Have you tried to unpin it and pin it again? That's all I can think of right now.

That didn't help. Thanks, though.

@OP

Have you installed all the Microsoft Updates after clean install?

There are bunch of updates (above 500 MB) available from Microsoft which improve performance and stability.

I have all the updates applied and don't see any difference in launching File Explorer in my machine.

It's super quick. I see it as soon as I click.

Yeah, I updated the system as soon as the install finished. I obsessively update :p

I refuse to believe this. If you have disabled all window animations and you are indeed trying to run the same File Explorer from both locations then there should be no difference at all. Try one thing for me though. Hit up CMD and type


explorer
[/CODE]

and tell us how long that takes to start up.

Entering 'explorer' in the command prompt opens instantly, just like the Jump List entries, hitting windows + E, and shortcut on the start screen. I don't blame you for not believing it. I can assure you, however, that it is happening. It's not a huge deal, so whether or not I find a solution doesn't matter. I made this thread because I, too, see no reason for it and wanted to see if anyone else had heard of a similar issue. I guess not and that's fine.

  • 3 weeks later...

1.38 seconds.... disgraceful

How would you even have noticed the difference between 0.76 seconds and 1.38 seconds?

When you have a high performing system, that's a lifetime to do something like open File Manager, one, one thousand, tw.......

There's clearly something wrong.

Perhaps the indexing service?

I recently had this problem after opening File Manager and waiting for it to enumerate all drives. Disabling defender eliminated the problem. So I disabled indexing, deleted the indexes, disabled Defender. Rebooted, re-enabled all, and all is well. Took a whole day to figure it out though, with several Google searches which lead to disabling Defender.

typing this from windows 8, and it works beautifully. (Dell Inspiron 1545)....opens as fast as I can click on it. (internal Intel drivers, generic MS drivers to be exact...dell won't release updated graphics drivers for this chipset for 8, frown)

  • 2 weeks later...

I have the same problem! It actually takes almost 2secs for the file explorer to open on my laptop when clicked from the taskbar.

and yes, 1.38 secs compared to milliseconds is a lot longer when you're always using your computer, so to the first person who replied to this thread, it is very noticeable.

and yeah, opening file explorer from the jump list is instant.

has anyone solved this problem? it is very annoying. can't work fast when you need to browse quick through your files.

right clicking file explorer on the taskbar and clicking any folder (jump list) is not very intuitive.

i just need for file explorer to appear immediately after clicking it on the taskbar.

anyone already has the solution for this? thanks!

  • 2 months later...

I had this problem too, but the solution is obvious! All other methods of opening explorer.exe are quick, but not the taskbar, so it must be using a different path. So it was! It goes to a directory (libraries by default), rather than opening explorer.exe.

THE FIX

Go to C:\Users\USERNAME\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar , where the taskbar shortcuts are stored. (The IE team developed the idea, hence the path)

Right click on File Explorer, and click properties.

Change the path to C:\Windows\explorer.exe .

Problem solved!

  • 3 weeks later...

I had this problem too, but the solution is obvious! All other methods of opening explorer.exe are quick, but not the taskbar, so it must be using a different path. So it was! It goes to a directory (libraries by default), rather than opening explorer.exe.

THE FIX

Go to C:\Users\USERNAME\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar , where the taskbar shortcuts are stored. (The IE team developed the idea, hence the path)

Right click on File Explorer, and click properties.

Change the path to C:\Windows\explorer.exe .

Problem solved!

 

Thank you! Good thing I came back to this thread I was hoping someone would have figured out the fix already.

 

Thanks again! :laugh: 

 

Now my Windows 8 experience is once again whole. :rofl:

  • 3 weeks later...

I had the same problem, but it is also slow when I click Windows-E. Anybody knows if there is an obscure shortcut for this as well? Opening Windows Explorer from the task bar is now immediate, but pressing Windows-E takes almost 3 seconds. That's 3 seconds to think about how much I love the improvements in Windows 8...

  • 3 months later...

I had this problem too, but the solution is obvious! All other methods of opening explorer.exe are quick, but not the taskbar, so it must be using a different path. So it was! It goes to a directory (libraries by default), rather than opening explorer.exe.

THE FIX

Go to C:\Users\USERNAME\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar , where the taskbar shortcuts are stored. (The IE team developed the idea, hence the path)

Right click on File Explorer, and click properties.

Change the path to C:\Windows\explorer.exe .

Problem solved!

 

Hi,

 

first off all, hi to everyone, and thank you PokeOracle for this solution...

 

it solved in windows 8, but now it happened again in windows 8.1 and the target is greyed out...

 

i'm trying to solve this by using same logic, but nothing solves...

 

does anyone solved this in windows 8.1?

 

regards...

Same here. It worked fine until I upgraded to Windows 8.1. Now it takes 4+ seconds to start Windows Explorer, even if I open explorer.exe under c:\Windows. It used to be a snap.Anyone with ideas on how to speed this up? I have a rather new i7 computer with 16GB ram, so the hardware shouldn't be the issue.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      591
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      75
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!