Why does it take so long to open a folder?

[Ztruker]

Why does it take so long to open a folder the first time after a boot? For instance, D:\Temp which is my generic work area only has 25 items in it yet after booting, it takes 10 to 15 seconds to open in Windows Explorer. 2nd and all subsequent times it opens almost instantly.

The same is true of Toolbars I've added to the Taskbar. I have System Tools there and the first time I hover over any of the sub folders, it takes the same 10 to 15 seconds before I see what is in those folders.



I've tried deleting Iconcache.db in various places but that did not make any difference. This is where I've found them:

 

[Mike Connor]

Because all the icons and information are loaded the first time the program runs after a boot. On subsequent runs they are already loaded.

On large directories with lots of header information checked this can take quite a long time. Even on small directories in other drives the time lag is noticeable.

If you have set explorer to display thumbnails it takes even longer.

This also depends to some extent on other system settings, and if you have used cleaners etc to delete various things. If you delete the page file on shutdown, ( invariably a bad idea, but it seems various programs reset this now and then), then it will take ages to shut the machine down, and also longer to boot.

Regards....Mike Connor

 

[Ztruker]

Mike, the folder I mentioned has 25 items in it. I have the view set to Details. I run CCleaner every night before I shutdown and I never delete the page file. I just booted a few minutes ago and when I opened D:\temp, the folder with 25 files in it, it took 11 seconds after the Explorer window opened before the files were listed. During that time the green bar crawled across the address bar as if it was looking for something.

This slowness was not the case for the first year or more, only the last 6 months or so has it become slow like this.

I've installed lot of software over that time and uninstalled a lot as well. I'm wondering if any of that is causing this.

For instance, I have a program called Everything installed which gives me instant access when I want to know where a file or files containing certain characters, are located. It has to generate and maintain an Index, but I think this slowness was happening before I installed everything.

I also have Acronis TI Home 2010 running but that has also been true since I installed Pro X64.

When you say Icons and Info are loaded the first time, I don't understand. Is this data cached in RAM? I don't delete Iconcache.db so it doesn't have to be rebuilt.

If you look at my specs you'll see this is not a slow computer and it has plenty of RAM.

There has to be something else going on here but I don't know how to figure out what it is. I don't have the knowledge to use a Kernel debugger and I don't know of any other way to figure this out. I'm hoping one of the wizards here has some ideas.

This is just an annoyance, not a real problem.

 

[Mike Connor]

There is always some delay when loading directories you open for the first time. The larger the directory, and the more information that has to be loaded, the longer it takes. I have a directory with a few thousand PDF's in it, and when I load it, or switch views to thumbnails for instance, it can take quite a while for everything to load.

I also routinely operate with up to twenty or more Explorer folders open at start, and it takes a moment for them all to load. Once loaded, I can switch back and forth between them about as fast as I can click.

I also run Everything, and I used to let it run at boot, but now I only start it when I need it. I have also reduced the number of items in my startup very considerably because it makes the machine sluggish. I also check immediately if I notice my machine slowing down appreciably on various tasks. There is always some reason for it.

If you want to see what is happening when you start, then load "Process Explorer" to start and run in an open window at startup.

Process Explorer

One other point I almost forgot. If you set explorer to default settings in all folders etc, then it loads a lot faster even on more or less "empty" directories.

Get this, ( I only use it for this sort of demo because I have the functionality built in to my explorer) "Get Folder Size" and see how long it takes to retrieve the information. Explorer has to do this every time it starts. The more directories and files you have, and the more information you are trying to retrieve, ( Header info, thumbnails etc),the longer it takes.

Even on "empty" directories, because it loads all the information concerning those directories, not just the contents.

Keeping the number of directories etc on your system drive to a minimum also speeds everything up considerably. Most of my stuff is on a separate drive. If it was all in the system drive, ( or even any appreciable portion of it), the system slows to a crawl when loading directories.

Regards....Mike Connor

 

[SillySod]

Nah, it should only take a few seconds to open a folder of that size at the most. Its probably due to so much other stuff going on at start up. For instance if you have spotify or a virus checker installed, all these programs try to start up together and it all contributes to making your PC run like a two legged dog. Try to reduce the amount of programs that startup automatically. If you press the window key and the R key at the same time then type msconfig in the box that appears, it will open a program where you can see all the startup up programs listed in the tab called "startup". You can remove ones that arent absolutely necessary. (like adobe updates, old camera or wifi startups, scanner software etc etc.)

Another thing to try, which helped me just now, is to stop the explorer.exe program and re-start it. For some reason this program can get really slow some times. This meant that a folder that was taking several minutes to open, only took a second to open. Not sure what windows was doing, but it seemed to be a good fix.

 

[bigmck]

Ztrucker -- Did you solve the problem from 3 years ago.

 

[AddRAM]

OMG