BillN wrote:
Thanks for your help with the context menu issue. Do you have nay repsonse to the backup issues that I described in my posting?
Thanks.
I am getting almost exactly the same problem except I installed 360 v2 rather than upgrade. I believe, but I can't prove that 360 v2 was working fine until Vista SP1 was installed and then I was unable to open the main window. 5 support staff have been unable to get either v1 or v2 working despite many uses of the uninstall tool and reinstalling.
v1 - The main window starts but the subscription is expired (not surprising - I haven't entered any details yet) but pressing the "Continue" button does nothing.
v2 - The main window won't start at all.
In both cases there are no error mesages to investigate.
hi bjaston - point of clarification - what is the title of the dialog box where pressing "Continue" do nothing? i suspect that the migration to Vista torqued the XP install of 360... on any of the uninstalls or reinstalls, were there any errors? or are you always left at the frozen "Continue" dialog?
also recommend if you haven't already to try the utility in this document if you believe your subscription should reflect an license with days left on it.
mel
Hi bjashton,
You are writing
"I believe, but I can't prove that 360 v2 was working fine until Vista SP1 was installed and then I was unable to open the main window."
I have installed N360 v2 and installed Vista SP1 standalone-package on top of it, without any issues at all but a rather unstable setup.
The situation of not opening main windows happends all the time when you have this kind of instabillity.
I use to shut down the system over night, and the next morning it use to work much better.
You also write
"In both cases there are no error mesages to investigate."
The none existing error messages says there are no errors present.
Instabillity is not a real error.
Kurt
Message moved to a new thread for better exposure
Hi,
I understood Symantec is working together with the powerdesk engineers in order to solve the context menu thing. Is there already a solution insight? Will we be informed thru this thread of progress and /or a solution? Feel like left in the dark since last messages.
Thx in advance
Hello Grumpster,
We are working with PowerDesk on this problem and expect a resolution shortly. We will announce that resolution here when it becomes available.
In the meantime, the problem can be resolved using the steps listed by Matt Boucher listed on page two of this thread, repeated here for your convience:
Here are the steps to work around the current issue (this is a temporary solution)
NOTE: Using the Registry Editor incorrectly can cause serious problems with your system, proceed at your own risk and ensure you have backed up your registry prior to editing.
- Run regedit
- HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\PowerDesk Menu
- Right click on "PowerDesk Menu" and rename to "zPowerDesk Menu" (this will force it to load last)
- Exit regedit
Thanks,
Matt
<< We are working with PowerDesk on this problem and expect a resolution shortly. We will announce that resolution here when it becomes available. >>
That is good news! Look forward to bringing PD back into my fold <s>
Hi All,
We're still awaiting word on the fix release. In the meantime, we're providing this document for customer experiencing the problem:
Windows Explorer stops responding when you right-click on a file, folder, or drive after installing Norton 360 2.0 with Avantquest PowerDesk installed
http://solutions.symantec.com/sdccommon/asp/symcu_contentredirect.asp?docid=20080430093320EN
Matt
matt_phillips wrote:Hi All,
[ ... ]
Windows Explorer stops responding when you right-click on a file, folder, or drive after installing Norton 360 2.0 with Avantquest PowerDesk installed
http://solutions.symantec.com/sdccommon/asp/symcu_contentredirect.asp?docid=20080430093320EN
Matt
Many thanks for the update and the pointer. I've printed out the document and will switch over into VISTA to apply it.
Finally got the time to reinstall PowerDesk7, check that the Context menu is still there (no update from Avantquest yet) and make the registry change you have given.
Works fine now -- such a small change and yet .... <g>
The registry change works fine on file level however right clicking on folders will still produce the well known error. This goes for XP Sp 3 as well as Vista SP1 on my pc"s
Grumpster wrote:
The registry change works fine on file level however right clicking on folders will still produce the well known error. This goes for XP Sp 3 as well as Vista SP1 on my pc"s
Thanks for the warning. I can't remember RMCing on a folder. Normally I'm after a file properties, drag and drop copy or in VISTA Run as Administrator.
Matt said they are working on a more complete solution.
I don't get it on XP SP3 where I've been using PPD7 for ages because I use NIS2008 there.
Message moved for better exposure.
Sorry -- no knowledge or ideas on "external control" .....
I'm sure you'll hear from someone who can help.
Hi All,
The fix has been released by Avantquest. Here are their instructions for obtaining the patch:
To access the article, go to the main KB page: http://kb.avanquestusa.com/ Once there, search for the article number, which is 4030. Searching for this article number will take them directly to the correct article.
Thanks,
Matt
matt_phillips wrote:Hi All,
The fix has been released by Avantquest. Here are their instructions for obtaining the patch:
To access the article, go to the main KB page: http://kb.avanquestusa.com/ Once there, search for the article number, which is 4030. Searching for this article number will take them directly to the correct article.
Thanks,
Matt
Great news -- downloaded and over to VISTA shortly to install.
great news. tested it on xp sp3 and works fine. Just be reminded when you used the workaround it might be a good idea to undo the added z in the registry.
I think a thank you to all concerned is in its place so thx a lot
btw may be my additional question about the network thing in message 34 in this thread should be moved to another (new) thread
Grumpster wrote:great news. tested it on xp sp3 and works fine. Just be reminded when you used the workaround it might be a good idea to undo the added z in the registry.
I think a thank you to all concerned is in its place so thx a lot
Agreed -- I've installed it on XP SP3, although there I have NIS2008, but I didn't have the problem there. I'm about to switch over to VISTA and run it there.
I thought I might leave the z in place just to see if that broke anything -- then people would know they must remove it.
One niggle -- Avantquest changed the file and changed the date but not the version number, not even a special build number ...
More later.