New+ not in context menu

[atomicgeek]

Microsoft PowerToys version

0.86.0

Installation method

Microsoft Store

Running as admin

Yes

Area(s) with issue?

New+

Steps to reproduce

Right-clicking inside a folder--New+ is not in the context menu.

✔️ Expected Behavior

Before yesterday's update, I could right-click inside a folder and New+ showed up in the context menu as expected.

❌ Actual Behavior

Today, after the update, New+ does not show up in the context menu. I've rebooted my system, elevated PowerToys to administrator privileges, turned New+ off and on, and verified that the template folder still exists in the place the program expects it and contains my templates. Since it never appears, I cannot actually use it to create new files.

Other Software

No response

[similar-issues-ai]

We've found some similar issues:

• New+ is NOT working #35328 , similarity score: 88%
• New+ isn't coming in right-click Context menu #35312 , similarity score: 87%
• New+ no longer appears in the context menu #35482 , similarity score: 86%
• New+ not working on Windows 11 24H2 #35531 , similarity score: 85%
• New+ not showing on context (right-click) menu, even under "show more options" #35323 , similarity score: 84%
• New+ not working on Windows 11 (French Canada version) #35210 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[pbargiona]

Do you have any language other than enUS active in your OS?

This is probably a dup to #35210

[atomicgeek]

I do not, enUS only.

Thanks for your link! I was finally able to get it to work by going through the steps in this post: #35210 (comment) (I did have to query the package name first with the get-appxpackage command, because I have a different version from the one listed in the instructions.)

[cinnamon-msft]

/dup #35210

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!