I'm dual booted XP Pro SP3 and VISTA Ultimate SP1 on two separate drives and I had the problem in VISTA between Norton 360 ver 2 and PowerDesk 7.
I followed up the instructions on the Avantquest KB4030 while I was in XP SP3 and it all ran smoothly as described.
I then copied over the downloaded exe file to my VISTA Internet Downoads folder and switched over into VISTA.
I decided to leave the "z" workaround in place just to see if it inhibited the update although I could not see why the sequence in the Registry should matter when a different file is in place to cure the problem.
I ran the exe file under VISTA using Run as Administrator and it and it appeared to run through to completion including the brief flash of the command screen that I imagine shows that the BAT file did indeed run.
However when I checked the Powerdesk folder as described at the end of the KB4030 it showed the addition of the PDShExt.new but the old file had not been renamed to PDShExt.orig and the PDShExt.dll was still the old one.
I ran the bat file manually using Run as Adminisxtrator with no change so in the end I renamed them manually without any objection from UAC or anything in VISTA.
I have now removed the ""z" from the Registry and rebooted again and PD7 does not crash so the fix must be in.
Can you pass this one to Avantquest please.
Nagging at the back of my mind is that there is something in VISTA that protects system files and as soon as you rename them it names them back again .... Does that ring any bells?
I'll ask over in my sources .... or am I thinking of GoBack which I presume I do not have with N360?
While I was doing all of this N360 was busy updating itself and I now have N360 2.3.0.9 with Add-on 2.1.0.55 -- are these the current ones?
Yep - you do have the latest versions of NIS and AOP.
I was unable to get the fix to work from Avanquest because the instructions included a right-click option that immediately crashed Explorer. How did you overcome that?
I did update Avanquest with your details although I believe that since we identified the "workaround", it may be for us to resolve for the limited number of folks we touched. That said, I haven't identified any deleterious affects from leaving the "z" - have you?
I was unable to get the fix to work from Avanquest because the instructions included a right-click option that immediately crashed Explorer. How did you overcome that?
I did not encounter that perhaps because I had the "z" fix in.
<< I decided to leave the "z" workaround in place just to see if it inhibited the update >>
I did update Avanquest with your details although I believe that since we identified the "workaround", it may be for us to resolve for the limited number of folks we touched. That said, I haven't identified any deleterious affects from leaving the "z" - have you?
Well -- they offered the fix for a named product, Norton 360, and I could not install it so I guess it's up to them to fix their install procedure, or to say to remove that "z" if that is the cause.
I'm not in VISTA at the moment so I can't check if after installing their fixed files by manually editing them to old and dll
<< I have now removed the ""z" from the Registry and rebooted again and PD7 does not crash so the fix must be in. >>
I suppose I could go back and switch the files back to the original versions and then see if their install works without the "z"
I just installed 360 V2 on my desktop computer since my 360 has expired on that machine. That machine has Windows XP. Unfortunately, the workaround that you suggested: to rename "Power Desk Menu" to "zPowerDesk Menu" has not worked. I am getting the same crash with Power Desk and WIndows Explorer when I right click on anything. I am getting ready to disable the 2 Norton 360 shell extensions that I found had caused the right click problem on my Vista notebook - TP Context Menu Class and BU Context Menu class. With these disabled, no right click problems. Have the engineers at Symantec come up with any other solution? My 360 v2 software is up to date. If not, what do I lose from 360 if I disable these 2 shell extensions? (I hope that I don't have to make a choice between 360 and Power Desk because Power Desk will win!)
I just installed 360 V2 on my desktop computer since my 360 has expired on that machine. That machine has Windows XP. Unfortunately, the workaround that you suggested: to rename "Power Desk Menu" to "zPowerDesk Menu" has not worked. I am getting the same crash with Power Desk and WIndows Explorer when I right click on anything. I am getting ready to disable the 2 Norton 360 shell extensions that I found had caused the right click problem on my Vista notebook - TP Context Menu Class and BU Context Menu class. With these disabled, no right click problems. Have the engineers at Symantec come up with any other solution? My 360 v2 software is up to date. If not, what do I lose from 360 if I disable these 2 shell extensions? (I hope that I don't have to make a choice between 360 and Power Desk because Power Desk will win!)
I have installed the Avanquest patch on my desktop with Windows XP SP2. The patch functioned properly and installed the file as indicated in the instructions. However, I still have a problem. When I right click on a folder I either get a blank pop-up window, or else PowerDesk (or Explorer) crashes. I have run Norton Live Update and my product is up to date. I plan to uninstall both PowerDesk an Norton 360 V2 and to start again from scratch. Any other ideas?
I uninstalled and then re-installed Power Desk. I applied the patch as directed. Everything now appears to be working OK. Norton 360 v2 is running as are Power Desk and Windows Explorer, all in Windows XP sp2.
Tomorrow or the next day I will try installing V2 with Windows Vista SP1.