moudey / Shell

Powerful context menu manager for Windows File Explorer
https://nilesoft.org
MIT License
3.45k stars 117 forks source link

no effect #1

Closed twonth closed 2 years ago

twonth commented 2 years ago

I love the idea behind this software but I can't seem to get it to run

I downloaded Shell (the 64-bit version), ran the exe as an admin and hit the Register button. The registration was reported as successful and I restarted Explorer. But my context menu is unchanged. I also tried replacing the shell.shl file with the Hello World example and redid all the steps: still no result. Any idea what I could be doing wrong?

I'm on Windows 11 22000.376.

moudey commented 2 years ago

Please give me the value of the registry key after Shell registration

HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32
asakurato commented 2 years ago

So it seems like I have this problem too. When I check that path in regedit, there is no folder with that name, so that's probably why shell doesn't work. The screenshot is after registering and restarting the explorer. image

moudey commented 2 years ago

So it seems like I have this problem too. When I check that path in regedit, there is no folder with that name, so that's probably why shell doesn't work. The screenshot is after registering and restarting the explorer. image

Is it the modern context menu that appears or legacy?

asakurato commented 2 years ago

So it seems like I have this problem too. When I check that path in regedit, there is no folder with that name, so that's probably why shell doesn't work. The screenshot is after registering and restarting the explorer. image

Is it the modern context menu that appears or legacy?

It's modern, like nothing has changed after registering. Old context menu also doesn't have anything new.

moudey commented 2 years ago

It works fine on version 22000.318

w11 22000 318

We will review those keys in the system registry to see if Shell is registered correctly

HKEY_CLASSES_ROOT\CLSID\{47535343-0064-434D-0000-000000000046}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved
{47535343-0064-434D-0000-000000000046}

HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers\nilesoft.shell
{47535343-0064-434D-0000-000000000046}

HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers\nilesoft.shell
{47535343-0064-434D-0000-000000000046}

HKEY_CLASSES_ROOT\CLSID\{47535343-0064-494F-0000-000000000046}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers\nilesoft.shell
{47535343-0064-494F-0000-000000000046}
twonth commented 2 years ago

Just like asakurato, I don't have {{86ca1aa0-34aa-4e8b-a509-50c905bae2a2} under HKEY_CURRENT_USER\Software\Classes\CLSID\

The registry keys mentioned in the last message do exist and (as far as I can tell) seem configured correctly, in that I see entries for shell where I would expect.

Thanks for looking into this !

moudey commented 2 years ago

Hi everyone,

This issue is resolved by changing the following Windows registry values by putting a minus sign in the first file path or deleting the value as you like as shown below.

Tested on Windows 11 build 22000.434

[HKEY_CLASSES_ROOT\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32]
@="-C:\\Windows\\System32\\Windows.UI.FileExplorer.dll"

[HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InProcServer32]
@="-C:\\Windows\\SysWOW64\\Windows.UI.FileExplorer.dll"

[HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32]
@="-C:\\Windows\\System32\\Windows.UI.FileExplorer.dll"
moudey commented 2 years ago

After applying the change of Registry values, you must restart the File Explorer by pressing Restart Explorer button