30-60 second delay on right clicking Context Menu- how to fix it?

Right click context menu problem.  Same as in this link

 

http://community.norton.com/t5/Norton-Internet-Security-Norton/NavShExt-dll-breaks-the-Windows-7-64bit-Windows-Explorer-Context/m-p/1053671#M249187

 

30-60 second delay when you right click on anything.  I've been able to disable all items except those relating to Norton/Symantec.  They don't allow any changes.  I've even tried deleting the key in the Registry and that wasn't allowed either.

 

How do you fix this?  It's driving me crazy!

Right click context menu problem.  Same as in this link

 

http://community.norton.com/t5/Norton-Internet-Security-Norton/NavShExt-dll-breaks-the-Windows-7-64bit-Windows-Explorer-Context/m-p/1053671#M249187

 

30-60 second delay when you right click on anything.  I've been able to disable all items except those relating to Norton/Symantec.  They don't allow any changes.  I've even tried deleting the key in the Registry and that wasn't allowed either.

 

How do you fix this?  It's driving me crazy!

This may be grasping at straws -- I had the same problem on my Windows 8 computer.  Right clicking took forever.  I was determined to figure out what was causing the problem.  Go to tools - manage add ons - and see if you see anything from Qualcomm running.  If so, disable it and try right clicking.  It seems there was a Qualcomm bluetooth suite that I also disabled, but I can't remember the details.  After this, right clicking worked as expected.  I had actually forgotten about the whole thing until I saw your post.

Windows 7

Norton 360 20.4.0.40

 

Essa, nothing from Qualcomm is running

 

 

 

 

 

Hi,

 

Do you have by chance Roxio virtual CD drive?? . 

You can also download shellexview from nirsoft.net

It will scan your system for corrupted shell extensions.

Backup everything before applying anything.

Other thing to try, from an elevated cmd, (Run as admin), type:  sfc /verifyonly

See what happens.

Post back the results.

 

Regards,

I ran the sfc (I wish you had told me how long it would take) and reported "did not find any integrity violations"   I haven't done the other yet.

" I wish you had told me how long it would take"

 

It's strange, on both my w7 x64 pc's the sfc finishes in about 8 minutes with NIS uninstalled, and in about 13 minutes with NIS installed.

How long did it take??

If no problems found, you are good so far.

Try the other suggestion and see if it helps.

(I suspect an Adobe Reader problem or another app).

Please post back.

 

Regards,

Apostolos,

 

<< on both my w7 x64 pc's the sfc finishes in about 8 minutes with NIS uninstalled, and in about 13 minutes with NIS installed. >>

 

When I'm sure of what "tool" I'm using I have found great benefit in temporarily disabling Norton's Autoprotect by right mouse clicking on the little icon.

 

CCleaner runs like lightning when analysing if you disable Norton that way but crawls if left enabled.

 

At least it shows that Norton does check what is accessing the system!

Hi Hugh,

 

Good point there, just wanted to show to the OP, who complained about sfc taking too long, that even with NIS Auto-protect enabled, 13 mins is not that long... (at least on my systems).

 

 

"CCleaner runs like lightning when analysing if you disable Norton that way but crawls if left enabled."

 

I never use CCleaner, and never will, I prefer doing "housekeeping" myself as I have the skills & the knowledge...  never had a problem so far.

 

Hope it helps,

 

Regards,

<< I never use CCleaner, and never will, I prefer doing "housekeeping" myself as I have the skills & the knowledge...  never had a problem so far.  >>

 

If you have never tried it you will not be aware that it's great virtue that it does nothing but list items -- the decisions on what to do are entirely yours so it is you who does the housecleaning..

 

Identifying temp files etc that are candidates for deletion and registry cleaning are completely separate and while I rarely even consider registry cleaning CCleaner again lists precisely what it is concerned about shows where it is in the registry and makes you check it for deletion if you want to PLUS it makes a backup of the registry first.

 

It's actually very educational and I'd love to have you look at it. But let's not distract anyone ....

Hi Hugh,

 

It's my fault, I didn't explain in detail, when I said I never used it, I meant that it is not installed on my home pc's.

Of course, I have tested in the past at work, I know more or less, what it is designed to do but most of the it's functions I can properly manage by myself.

On my home pc's, I have different third party utilities installed like Autoruns, Process Explorer, TCPView and that kind of stuff, although nothing to do with CCleaner.

 

Regards,

 

It's a personal choice. I don't regard it as doing housecleaning for me; just opening the book at the right page, to mix a metaphor.

I've been running SHELLEXVIEW and like the instructions said, disabling the entries one at a time.  This is very time consuming because you have to reboot ever time.  The first time I did it, the restart failed and I had to go back to a system restore point (I did take your advice and created a backup and system restore point before changing everything).

 

I'll keep plugging away, I only have five entries and I can't hang around the machine while it reboots, so I'll let you know.

Windows has 3 different main context menus.

 

Right clicking a empty spot on the desktop

Right clicking a file

Right clicking a folder

 

(I'm not counting the specialized ones like recycle bin, computer, network, etc)

 

On your screenshot it shows "Open with Adobe Reader" on top, that shows your right clicking on a PDF file.

So in addition to the seperate screens between files and folders, the file context menu also changes a little bit between flle types.

 

If you happen to find a situation where the context menu works without problems it really helps narrow down the search.

For instance if it works fine for folders but not for files, or if it only has a problem with certain filetypes.

It's almost never a microsoft program causing the problem.

It also sometimes happens only when a system is online or offline.

 

Best of luck,

Dave