-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New+ not working on Windows 11 (French Canada version) #35210
Comments
Does it help if you restart Explorer? /needinfo |
Same issue for me. Windows 10, en-US, used powershell to completely reboot explorer. Have not tried a full system reboot though. Will try that, once I find a good stopping point. |
@GarThor , New+ doesn't work on Windows 10. There should be an infobar in Settings on Windows 10 informing of this. It's not appearing to you? |
I see it now. Is there a plan to get it working for win10? EDIT: I was able to upgrade one of my computers to win11, and it seems to be working now. I was a little disappointed that it doesn't seem to do anything for file contents... just file names... So I can't be like.. new+ -> new C++ class. |
Doesn't work for me either. Windows 11 Pro 23H2 |
I use Win 11 23H2 (22631.4169) enUS with PT-BR ABNT2 keyboard. Not sure if it has something to do with language support, though... |
Windows 11 23H2, not appearing in full context menu. Restarting the Explorer process does not help. This occurred on both 85.0 and 85.1, and has persisted through many reboots. |
#35420 is dup |
@jaimecbernardo Does this issue still need Author feedback after what @klueman said?
|
New+ is not showing in the contextual menu on Windows 11 23H2 on my side either with v0.85.0 and 0.85.1. Unlike PowerRename by example. Restarts and reboots of Explorer already done. |
It's now visible through the context menu after upgrading to v0.85.1. It's a separate 'New +' menu, not an extension of a system 'New' menu. |
I personally can't see it. I checked every submenu of the contextual menu after right clicking in an empty directory. |
Still not working for me, even on updated Windows 11 24H2 |
Please see the attached images to #35323 Can you tell us what is your windows language settings? Still trying to pin down if this bug has something to do with it. |
This is not needing feedback. We're having many threads opened on the issue closed as dup in favor of this one. Can some mod stop this auto closing? |
@pbargiona Can you run |
i have the same issue its not showing up in centext menu here is the output Get-AppxPackage -Name powertoysnewplus* RunspaceId : eb7e8dd0-d071-4d43-b62a-efaf1141c777 |
@nahid6970 Can you do the following:
Thanks In advance |
I'm using... Windows 11 Pro After setting it up and adding templates, I see no NEW+ menu entry for me anywhere :-( |
Remove-AppxPackage Microsoft.PowerToys.NewPlusContextMenu_0.85.0.0_neutral__8wekyb3d8bbwe nahid on Wednesday at 3:13 PM 0.062s MEM: 63% (8/13GB) there is no output now |
@stefansjfw ok now if i enable it in powertoys it appeared |
@stefansjfw i didnt even needed to kill explorer it just worked after running those commands and then enabling it in powertoys thanks a lot brother ❤️ |
I worked through #35210 (comment) although in my case, I already had v86.0 install so I removed that one. Still no NEW+ menu time, even after a Windows Explorer restart. |
@nahid6970 You're welcome! @SirClickALot Could you attach /bugreport here ? Thanks |
@SirClickALot i am also on v0.86 and its working after so long like 1 month ago it worked somehow and then stopped working and now running those commands probably fixed them but still i am thinking it will again not work after i restart the pc i am afraid of restarting my pc |
Ah, seems to eb working now after a complete Windows restart! |
Sounds good! thanks for checking! I'll look into why the package is sometimes not updated properly! Thanks for all the help and feedback! |
@nahid6970 Once you restart your pc eventually, let me know if it still works or not :) It might point out where the issue can be if it's not there after restart |
@stefansjfw ok restarted and its working ❤️ |
Working now after these steps 👍 |
No output.
Remove-AppxPackage: Deployment failed with HRESULT: 0x80073CF1, Package was not found. Windows cannot remove Microsoft.PowerToys.NewPlusContextMenu_0.85.0.0_neutral__8wekyb3d8bbwe because the current user does not have that package installed. Use Get-AppxPackage to see the list of packages installed. NOTE: For additional information, look for [ActivityId] 355a0321-257a-0009-e3f2-30367a25db01 in the Event Log or use the command line Get-AppPackageLog -ActivityID 355a0321-257a-0009-e3f2-30367a25db01 I noticed 0.85.0 in the command, but I'm using 0.86.0 now. Decided to fully uninstall and reinstall powertoys through winget. Still no output to I restarted the PC and the explorer.exe several times. Still no menu. For some reason, I'm unable to take a Screenshot with the tier1 context menu with Win+shift+s tool
Sure, here you are. |
@pbargiona Can you try enabling Developer mode from OS Settings -> For developers. After that disable/enable NewPlus, run Get-AppxPackage command again and let me know if you get any output? Thanks in advance! |
Also, do you have PowerRename, ImageResizer and FileLocksmith in Tier1 ctx menu? |
Why? All other powertoys tools that exist in the right context menu also appear in the full context menu. File Renamer, Locksmith, Image Resizer, etc. Combined with the fact there's no keyboard activation shortcut, this seems to imply the one and only way to use this tool is from the Windows 11, "tier 1" menu? This makes the tool unusable for users that bypass the Tier 1 menu entirely for the far more useful full one. But regardless, both this and the Windows 11 restriction should have been put somewhere in the documentation and/or release notes. There was no indication this tool was more restricted than the standard Powertoys tools, and there's no reason for a user to assume it would be any different. |
Now do I get an output
Also, and more importantly, New+ appears in the Tier 1 context menu now! I disabled Dev Mode and it kept appearing. I'm yet to restart the PC to see if it sticks.
No. Only in Tier 2. Also, I can't get any other program, as Winrar, to show on Tier 1. I kind of hate this in Win 11, just like @klueman I noticed you do have many programs showing at Tier 1, @stefansjfw. Do I have to Get-AppxPackage context menus for every program I want in Tier1 with Dev Mode on? Any clue on what might be happening or how could this be linked to language settings in windows, since most (if not all) people reporting this bug had other than enUS languages installed?
New+ now appears in Tier 2 for me also. Is this unwarranted? |
Very valid point! The author of New+ is already working on Win10 support #35832 so you can expect it soon. Stay tuned :) |
Yes, those packages are basically what bring context menu items for specific tools. So you should have a separate package for New+, PowerRename, ImageResizer, and FileLockmsith.
I'm not sure at the moment how it's linked to OS language. Will keep an eye on this.
No, this is expected. |
Windows 11 Enterprise 23H2 I am having the same issue and have tried the steps listed in this thread. It appears the package is failing to install at all. I am getting this error when I opened the logs from "Report a bug": [2024-11-14 16:27:50.866894] [p-13100] [t-13104] [error] Register C:\Users\userid\AppData\Local\PowerToys\WinUI3Apps\NewPlusPackage.msix package failed. |
Same Issue here, I use PowerToys on company laptop with pretty strict policy settings. But other features like File Locksmith or PowerRename are appearing regardless. |
This worked for me as well. |
Microsoft PowerToys version
0.85.0
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
New+
Steps to reproduce
Right-clicking on any folder doesn't bring up the New+ menu
✔️ Expected Behavior
New+ menu should be there (as saw in a video about this feature).
❌ Actual Behavior
Contextual menus are the same if New+ feature is turned ON and OFF
Other Software
No response
The text was updated successfully, but these errors were encountered: