microsoft / microsoft/PowerToys

PowerRename and File Locksmith context menu entries missing in v0.94.0 and later

Open
#48,951 2 comments 0 reactions 0 assignees View on GitHub
Issue-Bug Needs-Triage Product-File Locksmith Product-PowerRename
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

### Microsoft PowerToys version

0.94.0

### Installation method

GitHub

### Area(s) with issue?

File Locksmith, PowerRename

### Steps to reproduce

Install PowerToys v0.94.0 or later (including v0.95.0 and the latest version).

Ensure both PowerRename and File Locksmith are enabled in Settings.

Right-click on any file or folder in File Explorer.

### ✔️ Expected Behavior

The "PowerRename" and "File Locksmith" options should appear in the context menu.

### ❌ Actual Behavior

OS: Windows 10 22H2

Affected versions: v0.94.0 and above

Last working version: v0.93.0

Installation method: Tried both .exe installer and Microsoft Store version — same issueBoth options are completely missing from the context menu.

### Upload Bug Report ZIP-file

[PowerToysReport_2026-06-27-18-32-32.zip](https://github.com/user-attachments/files/29407385/PowerToysReport_2026-06-27-18-32-32.zip)

### Additional Information

Already checked and deleted the corresponding CLSIDs in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked (PowerRename: {0440049F-D1DC-4E46-B27B-98393D79486B}, File Locksmith: {E5235BAE-8628-4E57-9694-D1F3780D21B7}) — issue persists.

Already tried enabling via Context Menu Manager Plus — no effect.

Already tried installing .NET 8 Desktop Runtime — no effect.

According to the v0.94.0 release notes, Win10 context menu modules were switched to runtime registration. This change might be related — it appears to have compatibility issues on certain Windows 10 environments, preventing the context menu extensions from loading correctly.
Additionally, please do not repeatedly close existing bug reports without actually fixing the issue. This bug has been present since v0.94.0, which is over a year ago, and it severely affects the usability for a large number of users.

### Other Software

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the v0.94.0 release notes and the Win10 context-menu modules' runtime-registration path, focusing on the PowerRename and File Locksmith CLSIDs listed in the report. Reproduce on Windows 10 22H2 with both utilities enabled, then verify that both entries appear in File Explorer's context menu without registry or runtime workarounds.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
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.