Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SimonT]

Hi - the issue mentioned here (http://yabb.jriver.com/interact/index.php?topic=96682.0) has resurfaced for me with the latest Windows 10 update.  The only way to get the context menu of Windows Start working again was to disable the JRiver shell extension.  Nirsoft ShellExView details :

Media Center x64   Yes   Context Menu   Shell Extensions   21.0.23.0   Media Center 21   JRiver, Inc.   No   No   No   No   No   No   C:\Program Files (x86)\J River\Media Center 21\x64\JRShellExt.dll   {6C954710-1CD0-46F0-B45D-1824231244C6}   04/12/2015 20:33:17   03/12/2015 03:18:50   No   *, Directory, Drive, Folder, opensearchfilefolderresult   A   612,864   No      No   

Seems to be an incompatibility with the latest W10 update therefore?

[Wildcat]

Same problem here.

[Matt]

I'm running the latest Windows 10 and shell extensions work great for me.  The start menu also seems to work fine.

[SimonT]

Indeed - doesn't affect all PC's in the same way it would seem.  The version of windows I have is 10.0.10586.  I have one PC that doesn't show this issue and one that does.  The only difference is that the affected PC has the JRiver sound driver installed, the other one doesn't - can't imagine that this is related however.

[stewart_pk]

I've had this problem after each Windows upgrade after Windows 7.

[Mike48]

I just updated my laptop to Windows 10/64 Pro, and now I have this problem. Context menus for the start button and computer icon can be brought up, but the clicked actions don't work if the MC shell extensions are enabled. This is terribly frustrating, and I hope an answer can be found. I understant that might be difficult if the problem is not replicable, but I'd hope some solution can be found for these two functions to coexist.

Is anyone at JRiver running Windows 10, and if so, haven't you had this problem?

[JimH]

Most of us use Win10.  I don't think we've seen the problem you describe.

These kinds of things often turn out to be caused by antivirus or other security software.

[Mike48]

Most of us use Win10.  I don't think we've seen the problem you describe.

These kinds of things often turn out to be caused by antivirus or other security software.

Jim, Thanks for the response. The only security software in use is Microsoft's own. If that's really the problem, it doesn't change the picture.

There are many similar problem reports on the Web, with the common thread that W10's own shell extensions don't work for some people, on some installations unless other shell extensions are disabled. I don't think anyone has found the root cause of this yet, nor a good solution, not why it only happens in some cases.

In my case, it's now moot, as I rolled the laptop back to Windows 7, which runs considerably faster and doesn't have this issue.

[wwlearp]

Problem located as defined- disable JRiver 21 context shell, get Win 10's Start context links to work again, both pre & post Win 10 anniversary upgrade. p.s. It appears to be the x64 shell extension, as the 32 bit one is still enabled.