"An operation is taking longer than expected." Getting this error message quite often

I am getting this message very often. Started within the last month or so.
Tried to research the message and not finding any explanation.

Message:
"An operation is taking longer than expected."
"Operarion: SHGetFileInfo"
"{679F85CB-0220-4080-B29B-5540CC05AAB6}"

image

I'm using Version 13.7 x64 Build 8944

The only possible cause I can mention is that I have a USB Drive plugged in. If I unplug it, the error goes away. When I replug it in, seems back to normal.

Can someone help me to find the trigger and the fix? Thank you in advance

{679F85CB-0220-4080-B29B-5540CC05AAB6} is the Windows shell's internal name for the Quick Access folder (renamed "Home" in later Win11 updates).

Maybe something in that is pointing to something that cannot be resolved. For example, paths on a network server that is not accessible.

Check what's in the folder in File Explorer if Opus is having trouble displaying it. It's also possible something is wrong with the folder itself, which might affect File Explorer as well.

Iā€™m experiencing the same issue.

I have a connected network drive at home, but when I'm away, the path to that drive becomes inaccessible.

What can I do to resolve this problem while I'm away? I keep getting this error message, and it causes Directory Opus to freeze constantly.

P.S. I have the latest version installed.

Unmap the drive. Windows will cause long delays if it tries to access a network drive that isn't there, and having it mapped as a drive letter will cause things to access it (e.g. just asking the OS for the drive's icon when showing a list of drives can cause a 30 second delay).

Using UNC paths (the \\server\share\dir... type paths that you map drive letters to) directly is often a good solution to the problem, as it avoids the drive letter which is the cause of many problems. Of course, you still need to ensure nothing tries to access a UNC path that isn't available, but that's easier than with a drive letter where it can happen implicitly rather than via explicit actions. Drive letters for network drives aren't really needed, and personally I haven't used them in about 15 years.

I second that : I used to have so many mapped drives, but that brought me more annoyance in the end.
I had to change because I had then too many internal/external drives connected, and went on the UNC paths route.
To ease everyday use, you can :

  • assign aliases to these UNC paths to make them available more easily
  • if you're more a mouse guy than a keyboard guy : make a button (command GO /myNetworkDriveAlias if you made an alias or GO \\server\share\dir1\dir2) or a menu button with several entries (each one with a GO command to access either multiple drives or multiple common paths on this network drive).
2 Likes

Thanks for the reply.

I deleted the mapped network drive.

I created a new shortcut on my desktop, assigned the UNC path to it and then added it as a favourite in DOPUS.