The only thing you can do in situations such as this, is to try and do some debugging to find out where it is hanging, and what circumstances are occurring at the time. What operations are the users doing, and what does that cause the application to do? Is it perhaps getting stuck accessing the network drive?

What does Google show you when you type "caspol trust network location"[^] into it? A guide to posting questions on CodeProject Click this: Asking questions is a skill. Seriously, do it. Dave Kreskowiak

There is also an "UnhandledException" delegate in the Application class that you should assign your handler to. The difficult we do right away... ...the impossible takes slightly longer.

As Dave mentioned, you didn't give a lot of details so I'll take a stab in the dark and say that your "work" is probably being done on the UI thread rather than on a background worker or other type of thread. (If you have no idea what that means then you are definitely working on the UI thread.) That will kill UI performance if you start mixing long-running operations such as disk-based access or network-based access. Your UI will hang while it processes the work because there is only one guy in the room doing anything. If this is the case, you will want to change your worker method(s) to use an async pattern so you can decouple the long-running work operations from the UI. That will keep things responsive... at least on the UI.