Thanks for sending the snapshots.
They show Opus itself is idle and waiting for user input, so if the snapshots were taken while the delay was happening (i.e. between a double-click and something happening, and not after it had happened) then it means something outside of Opus itself is causing the delay.
Things that may help track down the cause:
-
C:\Program Files\Microsoft Office\root\Office16\JitV.dll(which seems to be related to Outlook, although it's not completely clear what it does) seems to be hooking the DispatchMessage API which is a key part of all input and window message processing. If their hook is taking a long time sometimes then it could cause all sorts of strange delays. I've never noticed it doing this before on my machine or in other snapshots people have sent, so it seems unusual.
-
HP ProtectTools Security Manager is loaded in the process. There are some threads on the web about it slowing things down, but they could be a coincidence.
-
McAfee is also there, and could be involved in slow-downs. Antivirus may also treat dopus.exe with more suspicion, and do deeper tests, than it does with explorer.exe. But I'd still expect to see an operation in progress in the snapshots, if antivirus was slowing things down, so I'm not sure it's this.
The JitV.dll thing is the most strange, and the only thing I can see that's actively involved in what's happening in 2 of the 5 snapshots.
Other DLLs/shell extensions in the process, but without anything particular pointing in their direction as a potential cause:
- Adobe CoreSync
- DropBox
- OneDrive
- EditPlus
- Lots of other Office/Outlook components.
If there's a pattern, like the problem only happening after visiting a folder containing Outlook messages, then that would point further in the direction of Outlook / JitV.dll. But there's nothing absolutely conclusive, unfortunately.
It happening after opening a document may also suggest the antivirus/privacy side of things, since that software will kick in when documents are opened in some cases.
A Process Monitor log might also be worth a try, if you tell us what was double-clicked and delayed while making the log.