microsoft / microsoft/PowerToys

[Feature Request] Please allow for New+ compatibility with the classic context menu in Windows 11

Open
#48,512 0 comments 0 reactions 0 assignees View on GitHub
Needs-Triage Product-New+
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

### Description of the new feature / enhancement

The only way to use the PowerToys New+ shell extension is to use the default "new" Windows 11 context menu.

To reproduce:

1. Enable the classic context menu with this registry addition:

```
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}]

[HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32]
@=""
```

2. Enable New+ in PowerToys
3. Right click on the background of a directory and observe the New+ menu doesn't appear.

## More detailed information

- The NewPlus logger is initialized and fires repeatedly in the log file at `C:\Users\username\AppData\Local\Microsoft\PowerToys\NewPlus\NewPlus.ShellExtension\Logs\v0.100.0\log_2026-06-10.log`

- That's the handler DLL (`PowerToys.NewPlus.ShellExtension.win10.dll`) being loaded by Explorer every time Windows builds a context menu. Explorer is invoking New+; it's getting loaded but producing no visible entry.

- `HKCR\Directory\Background\shellex\ContextMenuHandlers\` contains `NewPlusShellExtensionWin10`, with a correct default of `{FF90D477-E32A-4BE8-8CC5-A502A97F5401}`. That should be the New+ classic-menu handler (.win10.dll variant, purpose-built for the classic context menu).

- Its COM server resolves to `…\WinUI3Apps\PowerToys.NewPlus.ShellExtension.win10.dll`, So registration is fine, the handler loads (logs prove it), and it's hooked into the folder-background menu — yet draws nothing.

- This means the .win10.dll handler's `QueryContextMenu` is erroring at runtime.

Finally, if I re-enable the modern "new" Windows 11 context menu and then restart explorer, New+ appears. However I don't *want* the new context menu, and there should be no reason why the shell extension can't work with the classic menu.

### Scenario when this would be used?

The scenario is daily usage of New+ with the classic menu enabled.

### Supporting information

From what I understand, classic menu items are in-process `IContextMenu` (loaded into explorer.exe, stable PID). The New+ menu's `IExplorerCommand` runs out-of-process (fresh DllHost PID each time).

## Incorrectly Reported Solution: Removing `Microsoft.PowerToys.NewPlusContextMenu_...` Appx Package

There was an issue in this repository where a user reported that they fixed this by:

1. Turning off New+ in PowerToys
2. Removing the `NewPlusContextMenu` Appx Package (`Microsoft.PowerToys.NewPlusContextMenu_0.100.0.0_neutral__8wekyb3d8bbwe` on my system)
3. Toggling New+ back on to re-register the package.
4. Finally, restarting `explorer.exe`

This can be done via powershell:

```powershell
# 1. In PowerToys Settings → New+ : toggle it OFF (keep Settings open)

# 2. Remove the stale package (PowerShell):
Remove-AppxPackage Microsoft.PowerToys.NewPlusContextMenu_0.100.0.0_neutral__8wekyb3d8bbwe

# 3. Confirm it's gone (should print nothing):
Get-AppxPackage -Name *powertoys*newplus*

# 4. In PowerToys Settings → New+ : toggle it back ON (this re-registers the package)

# 5. Restart Explorer:
Stop-Process -Name explorer -Force # Explorer auto-restarts

# 6. Right-click empty space inside a folder. Spoiler: It still doesn't work.
```

So, this does not fix the issue.

New+ simply refuses to appear in the classic menu.

I know it IS possible for PowerToys to add a context menu shell extension to the classic menu, because if I turn on PowerRename, it appears fine.

**PLEASE, update PowerToys to allow for New+ usage with the classic context menu in Windows 11.**

Contributor guide

Open the contributing guide

Research direction

Start at the PowerToys.NewPlus.ShellExtension.win10.dll handler and its QueryContextMenu path, then reproduce the classic-menu registry configuration while reviewing the NewPlus logger output. Compare the handler registration with the working PowerRename classic-menu behavior. Done means New+ appears in Explorer's classic background context menu while remaining available in the modern menu.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
desktop, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.