I frequently encounter an issue where I click on a stored location from a network or virtual drive that’s no longer available, and Directory Opus either freezes or crashes as a result. More recently, I’ve noticed a new smaller window (pictured) appearing, indicating that Opus is trying to recover or locate the missing path. This window seems to show up more often with the latest updates.
Given this recurring problem, I’m wondering if there’s a smarter or more reliable way to manage stored locations that aren’t always accessible—especially for drives that may be offline or disconnected at times.
I also encountered a similar situation. When I navigate to the target file, if the target folder and its subfolders contain offline network folder links, then this interface will appear.
It usually lasts 10 seconds or more.
Click Abort to return to the previous directory.
This will not happen if you perform the same operation in the resource manager
Is there a better way to make this interface pop up only when I try to navigate to a network folder link that contains offline?
Also, when I navigated to a network folder link that contained offline content, it failed to load properly and caused the entire process to fail or crash.
Is there any way to put the parsed network folder into another process to separate it from the main process to avoid the process from crashing and not affecting the operation of the main process?
