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

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • 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
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!