Read many posts on this issue and we are also experiencing this at our customer computers as well. Is there any kind of status in the latest release of this software that corrects this issue and honors .NET Framework - Click Once security mechanisms?
Thanks