It takes Windows 2 seconds to see files in a folder, sometimes

Hello

It sometimes takes 1-2 seconds before the files in a folder appear. This means that I can no longer be certain that a folder empty unless I wait 2 seconds to see if Windows is going to realise that there are files in the folder and display them, or I have to glance at the status bar, because the status bar shows the file count correctly in those 1-2 seconds. This happens mostly with folders that I haven't visited yet. In other words, if I have visited a folder before, the files appear immediately.

Is there a way to make Windows not *wait* before it shows the files in the folder, or trick Windows into thinking that it had visited all folders before?

Thanks
Samuel

Sounds like it's caching the files. If you have a slow or full hard drive there will a small delay.

1-2 seconds is not the end of the world.

farrellart said:

Sounds like it's caching the files. If you have a slow or full hard drive there will a small delay.

Thanks. I'm afraid I don't understand this "caching" but I'll look into it.

It's a 250 GB M.2 SSD (NVM Express, PCIe 3.0 x 4), and I never fill the last 50 GB.

1-2 seconds is not the end of the world.

It definitely is the end of the world.

NVM Express should be fast enough. Do you have all the drivers installed?

With mechanical drives it is recommended to never go above 75% capacity - SSD's you can use the lot.

For what it's worth, on my ssd system there is a slight delay ( about 1 sec ) between the click and seeing the content of a folder. Never really thought about the speed and it doesn't bother me.....if the delay was longer I would be agitated.

You have posted a similar post in Faster folder access, please

Is this post related to same computer?

When you open a folder the antivirus scans the files before allowing it to be seen. What antivirus you have?
Did you do a check disk (chkdsk c: /f)?

How large is your page file?

Thanks everyone, but after a few days something else broke, and I had to reinstall Windows entirely. The issue seems to be gone.