From researching further, and attempting various things, I've found what was causing my own problem. For me, the problem was my computer had a drive mapped to a NAS/network location that I don't have turned on 24 hours a day. I mostly use my NAS for some backups and storage of old files.
When I turned the NAS back on, File Explorer appeared instantaneously when I clicked it. When I turned the NAS off, the delayed and sometimes erratic File Explorer behavior began. I then turned the NAS on, and no delays in File Explorer once again. I turned the NAS off, and the delayed behavior was back.
One of two possible solutions for now based upon what's causing it from reading others' solutions :
- In my case, I removed the drive letter mapping to the NAS and normal behavior was back for File Explorer again. I've repeatedly tested these on dozens of clicks and File Explorer starts, and it appears to be related to the mapped drive that wasn't available. So I just deleted the drive letter mapped to that location and created a shortcut on my desktop to that drive instead of mapping a letter to it in File Explorer. I also tested creating a shortcut to the network location *within* File Explorer and that, too, seems to work. So the functionality I seem to lose with this is referencing that network location/NAS by drive letter - I'll have to use UNC paths to create these shortcuts to network locations that aren't reachable 24 hours a day.
- On a side note, after reading other users having similar issues, in almost all other cases (ie, not related to a drive mapping), it was due to some form of a drive or file that was being referenced that File Explorer or the pc no longer had access to or very slow access. For example, some people saw the issue when they mapped to a location using Quick Access (or Windows referenced that location for them in Quick Access), so when they removed that location from Quick Access (or just turned off Quick Access altogether), File Explorer performed normally. I didn't test this specific issue out, but like I said, disabling Quick Access altogether (or removing that particular location from Quick Access) fixed it for them. Losing Quick Access wouldn't be a big deal to me if it came down to it.
