If you want to get to the bottom of it, you can use the tools and techniques that Mark Russinovich demonstrates in his blog (such as here
) -- though you may need admin privs to do some of that. But honestly, if this is an IT-supported machine and it is not performing correctly, it's their problem and they should fix it.
computron9000 wrote:As an aside lots of programs and things try to get added to the context menus in Windows. If even one of those is trying to hit a network-resource, that could explain the issues... if the client has no connection, just load the menu normally, but if the client is attached to a network, go try to grab it. And each could have their own time-outs.
Well, the context menu handlers are in
as well as various other spots (search the registry for ShellEx
You can see all of them at once using a tool like AutoRuns from the afore-mentioned Russinovich / SysInternals
But it's not clear if this only happens from explorer, or whenever "accessing a file" from any program (without bringing up a file open dialog).
computron9000 wrote:What surprised me was the idea of the consistency of the times. That seems registry related if accurate: why? because it would take roughly the same time to process the mess in there.
The registry is cached; you wouldn't see consistent times between the first and second case, and it wouldn't take that long no matter what the "mess." Multi-second delays with consistent duration like that screams "hardware time-out" to me.