Step 1: Pressing "Windows" key and "X" key to open Control Panel on your Windows 10 computer. This content menu handler can load from many different areas in the registry, and it can be a difficult task for a end-user to pinpoint which extension is causing the problem. Content menu handler would add commands to your right-click menu. But the diagnostics would have to be logged all the time when I use it, as it doesn't happen on any regular basis (or enough to get me to stop using it altogether), and I can't afford to replace my file manager with something that might freeze for daily use, so it would probably take a while to get you anything.In most of the case, this problem would be caused by a poorly coded content menu handler which is added by some third party program.
Various OSes (from Windows Server 2003/Windows 7/Windows 8/Windows Server 2012/Windows 10) at sometime when I use the portable version, it does it, and it's when accessing local or network resources. If you have a way that I could give you some more info, I'd love to help. But without some diagnostic way of getting information, there's no way for me to give you something useful. I bought a true lifetime sub sight unseen, so I'd love to be able to use it rather than re-upping DOpus every few years, so I'd love to be able to help you.
Unfortunately applications get the blame for something that (the TCP implementation) Windows itself should be blamed for, because the software author has no control over it. If you are interested in such things, of course. More info about the behavior of the library being used by XYplorer should be asked to the person(s) that wrote XYplorer. For all I know, the used library can be more strict (as in: crappy connection = untrustworthy connection = no connection) than the library Windows Explorer uses. And that library can treat network mishaps very differently than the one Windows Explorer uses. More often than not they make use of a commonly used library for the language they wrote the application in. Not all file managers treat such problems in the network in the same way. Run it on the computer experiencing the problem and when you see a lot of black lines passing through the capture session, while you do your thing on your LAN, your connection is (much) crappier than you think. Several modems later the problem still wasn't fixed, so at the end the company inspected their cable to the server that managed the traffic for my barrio and now the connection really works as advertised. A tool like WireShark helped me to prove to several field techs that their connection appeared to be as promised, but in practice wasn't. Existing connections acted as expected, but whenever a new connection had to be made, a lot of TCP packets not arriving, improperly transmitted etc. I kept complaining about a shitty connection that I got from the cable provider. WiFi connections can introduce high(er) latencies between network nodes at any given moment, which in turn can make Windows wait for the TCP protocol to get things straight again. Of course, if you more than 2 computers/devices in your LAN and this problem occurs on any device while accessing the same shared folder, you better take a look at the device with the share that gives problems. The TCP protocol is responsible for actual communication over the network and can make Windows wait, giving the user the impression the currently application is doing something badly, while it just waiting for the TCP implementation in Windows before it is allowed to continue. If so, you better take a look at the network configuration of the system you experience this problem on.
That sounds like a familiar problem, which usually happens when you access folders on your LAN.