Open lister

When open a lister first I see a screen searching folders ( see atachments ).
This is an issue that I already had with Dopus 11 in Windows 10 the latest build I now use Dopus 12.
Why is this happening or what is wrong?

Does the drive simply take a long time to read the folder? e.g. If it is a mechanical HDD which has spun-down and gone to sleep, it may take a few seconds to spin back up again.

Does it happen for all folders or just some, or just ones on a certain drive, or containing certain types of files?

I have an ssd and it happens for all the folders and drives.
This problem happened only in Windows 10 64 bit not in Windows 7 64 bit with version 11

Does it still happen if you only have the Name column turned on and not all the others?

I just opened one lister and it did not happen but now I tested it ones more it does happen.
But what did you mean with Name column turned on?
I doe not understand exactly!

All the columns you've added:

Try turning them all off except for the Name column, in case the slowdown is caused by one of them.

Another thing to try is disabling all script add-ins under Preferences / Toolbars / Scripts.

That does not help either

If you open a second window for the same folder, is that also affected, or just the first one?

And what happens if you open the same folder in Windows Explorer?

If the problem does not affect Explorer, please do this while the folder is still loading in Opus:

[ul][li]Open Task Manager and click on its Details tab.[/li]
[li]Find dopus.exe and right-click it.[/li]
[li]Select Create dump file. (It should then tell you where the file has been created.)[/li]
[li]Zip the dump file and email it to[/li][/ul]

That may reveal which operation or component Opus is waiting on.

Thanks for emailing the dump file. Re the email:

If it's affecting both Opus and Explorer, then it's almost certainly an issue coming from outside of Opus. We can still try to help, but only to a limited extent.

The dump file shows lots of threads stuck in the startup phase, which usually means an improperly written DLL has been loaded into the process and is blocking thread startup/shutdown.

The dump also shows that .Net has been loaded into the process (already dubious and indicating a shell extension written by someone who may not know what they are doing) and has more threads going on than what I'd usually see with .Net shell extensions, including one that looks like something to do with a .Net debugger.

My advice is to use ShellExView to disable all non-Microsoft / non-Opus shell extensions, then reboot and see if things improve.

If that fixes things in Explorer and/or in Opus, re-enable a few things at a time, reboot, and see when the problem comes back. That will usually indicate which component was causing it.

All of the programs below have DLLs loaded into the Opus process. It's likely one of them is causing the problems (or perhaps a combination of two of them). This isn't a list of guilty software, as they may all be innocent and at most one is probably causing problems, but it is a list of things to try uninstalling if using ShellExView on its own does not help. The order is just by path/filename of the DLLs, not in any particular order of likelihood:

[ul][li]Internet Download Manager[/li]
[li]NZXT CAM[/li]
[li]Razer Cortex[/li]
[li]RivaTuner (Statistics Server)[/li]
[li]"Stack" (Not sure if that's the right name. It's under "C:\Program Files (x86)\stack" and looks like an overclocking overlay from the filenames)[/li]
[li]WinSCP (drag & drop extension; unlikely to be involved with anything, but not impossible)[/li]
[li]LibreOffice 5 (property handler DLL; that has caused other problems in the past, FWIW)[/li]

Components of these are also loaded into the process, but unlikely to be the problem, and difficult to uninstall as they're part of the OS. Just mentioning for completeness:

[ul][li]Windows Photo Viewer[/li]

It's also possible the problematic component was no longer loaded into the process when the dump was taken, so it could be something that isn't listed above, but that's less likely.

I think it is solved it is as far know it is "illustrate" in context menu.
It is not affecting Explorer, I see I had written that it does affect explorer but it is not!
You can close this item now.
Thank you for all your help!
Best regards
Albert Drewes