Clickonce update takes 30 minutes?

Ok hopefully someone can help me out here. I've deployed my application throughout our office with success to 20+ stations. Then i reach a station when I try to install my application it just says checking for the latest updates. 30 minutes later the install screen finally appears, and I install my application. The application fires up run the program, then close it.

Next I re-open the application it does the checking for latest version and then proceeds to take 30 minutes again to check for the update. Basically happens each time the user re-opens the application?

Has anyone seen this before?

Thanks for any help!!

What is it attempting to update?

Its basically just trying to search for the latest update of the program. So using the click once i told it to check for updates at startup so the user has the latest and greatest at all times. But this one machine just hangs when looking for the update, then after 30 minutes or so it finds the update and prompts to install it.

Why would you want to update your packaged installation AFTER it has been deployed. That makes no sense.

Well the reason why I want it to check for updates each time is if bugs get introduced or people want additional features. What ever it is. The click once feature inside VS2005 I assume does just that to allow you to quickly update all the seats running your program.

I'm not a professional programmer by any means, so I'm constantly having to make small adjustments as our users are working with the new program.

So this is where I'm getting the delay time with this one machine checking for the update. I'm wondering if its maybe a .net framework problem on his machine or windows installer or who knows?

NEVER do an on-the-fly update to an installation already deployed. You have no idea of what will happen. Only do an update after you have tested that the new update will not affect your app. Expecially in the client's environment!!!!