10-28-2009 02:01 PM
I had this problem after installing Norton 360 v3.0. It was also affecting Windows Explorer. Finally found fix at http://kb.avanquestusa.com/al/12/1/article.aspx?ai
Never did find anything on Norton's tech support.
Hope this helps anyone else experiencing the problem.
10-28-2009 02:27 PM
Welcome to the Norton Community
Thank you for contacting us regarding your Norton Product.
Thanks for posting that solution to your PowerDesk issue, it is likely to be very useful for someone else.
We look forward to the time when the Power of Love will replace the Love of Power. Then will our world know the blessings of peace. ~William Ewart Gladstone
10-28-2009 02:29 PM
I have seen threads around here mentioning issues between PowerDesk and Norton, for example in this thread over here:
Thanks for posting the fix for people who might be experiencing such problems.
Ladies and Gentlemen, we are now ready for take-off. We would like to remind you that smoking and flaming are prohibited on all boards of this forum. We wish you an enjoyable flight with Norton Airlines.
10-28-2009 06:34 PM
There is a Symantec knowledge base article about this issue, which points you to the Avanquest website and the support article that you found there. Unfortunately, sometimes finding the correct information at the Symantec site requires a bit of local knowledge and some persistence. Sorry you were unable to find the Symantec document, but I'm glad you arrived at the solution by other means anyway.
10-28-2009 06:49 PM
Sorry not to have seen this sooner but I don't spend much time here in N360 now since I'm using NIS but I was involved in this when it first cropped up with the move from N360 V1 to V2 !
Everyone thought it was Norton's fault but actually it goes back to a changed protocol that Microsoft announced but did not immediately adopt themselves and when they did and there was a mix of applications that had adopted it and ones that had not there was a collision on the new one way street and it was not the fault of the one going in the right direction, even if it was a new model!
If you are intrested do a search here on PowerDesk and I'm sure you will find a lot of hits!
And some users found other applications that triggered the problem but unlike PowerDesk had not rewritten their software to comply.