When I try to search for a file on a "C:" drive, this happens and search effectively freezes:
The problem was a self-referencing shortcut "Application Data" inside "AllUsers" folder. I'm sure previous versions (like v13.9/v13.10) did not have this problem (but I'm not sure this "Application Data" shortcut was even here before either, maybe once again some stupid Windows update created it).
Could you detect circular junctions/shortcuts and ignore them?
They should already be detected.
What kind of search are you doing, and where is it being done from?
Could you please:
C:\ProgramDataAnd see what target is shown for the Application Data junction?
Sadly I've already removed the original junction since then. But now I've found another one that messes with the search inside C:\Users\%username%\AppData\Local:
And if I go deeper and deeper, only the path in the address bar changes, Target stays the same.
It seems like the problem happens only when the search goes via multiple junctions in a row. For example, it doesn't happen when I search inside the real C:\Users\%username%\AppData\Local, but it does happen when I do that inside C:\Users\%username%\Local Settings (which is a junction to C:\Users\%username%\AppData\Local folder) or C:\Documents and Settings (junction to C:\Users that in turn has "ways" to the faulty Application Data junctions in both C:\ProgramData and C:\Users\%username%\AppData\Local).
So to finalize, I think that to find circular junctions DOpus simply compares the current path (f.e. C:\Documents and Settings\%username%\AppData\Local) with the junction's Target path (literally C:\Users\%username%\AppData\Local). Since they differ, DOpus doesn't consider it a circular junction and goes deeper inside in an endless loop.
You should not remove that junction. It's put there by Windows for compatibility with older software.
How are you starting the search from that folder? Trying to double-click into the Local Settings junction in Opus will normally take you to the Local folder it points to.
If double-clicking it works and puts you under "Local Settings" instead of jumping you to "Local", the permissions on that drive are probably messed up and no longer the Windows defaults.
Those junctions are usually permissoned to stop things recursing through them, which is one of the ways Windows protects against infinite loops here. (Opus also tries to detect infinite loops even if the permissions don't, so I'm still not sure what is happening here, but either way those permissions should be fixed or it'll cause problems in other tools as well.)
Which permissions are we talking about? It could be so they are messed up indeed. And by the way, the system is encrypted via VeraCrypt, it could also matter.
Tried to go into the junctions in Explorer itself, and this happens:
But in DOpus it's perfectly okay to go into. Another thing to note is that UAC is disabled completely, so everything, including DOpus, is running as admin.
Which path are you in after going into it? What does the location bar say?
So the permissions on DnS are the following:
The location bar tells it's inside DnS:
And I can go all the way down to the circular AppData junction in UserLocalAppData, and endless times deeper inside it:
And the permissions for it are the following:
Funny. DOpus crashed on N-th view of junctions permissions and after that everything works normally. I can no longer enter any junction, DOpus redirects me to the real folders. Not sure what it was previously.
So the Properties dialog crashed? That's part of Windows, not Opus itself.
I can't explain what you've been seeing but, especially if it has just started working again by itself, it seems like an OS-level issue somewhere.
