-
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
Upgrade to 0.60 the PowerRename context menu is disappeared #19219
Comments
Do you have Windows 11? /bugreport |
Yes,It's Windows 11 v22622,this is bug reports file: |
On Windows 11 there's the known issue of having to restart the computer before it recognizes the tier 1 context menus. Have you tried restarting the computer yet? Restarting explorer.exe should work too. /needinfo |
I have restart computer but it still doesn't works! |
According to the logs, the package has installed successfully, so it's not a package install error. Did you restart with PowerRename enabled? Not sure what might be causing this. |
@jaimecbernardo @ldqk |
Yes, that's beta channel. I've tested there and it worked. |
@ldqk , what file are you trying to select to rename? We saw some issues where some files are not being detected as rename-able, such as the "Recent" files. |
I want to try rename some regular folders, the path such as E:\Downloads\xxx ,but it works on version 0.59.1. |
If you select in Settings to "only show on extended context menu" and shift right-click the file, does it still work? |
I've try to switch "only show on extended context menu" option,and try to rename other folders but it still doesn't works. |
You have to Shift+Right click to show the extended context menu. You're doing this, right? |
Yes,Shift+Right click,I make sure I doing correctly. |
Manually or if there was any way I can add power rename to the context menu,regedit? because I really need this function! |
What does your right click menu look like? (Before clicking show extra options) |
My right-click menu has been modified to look like windows10 by third tools |
What you can do while we figure this out is perhaps remove the appxpackage for the context menu, so that a fallback kicks in.
|
I have executed this command succeed |
Which tools are that? I think it might be some incompatibility there. |
I guess we can try to always show the old controls alongside the new Windows 11 tier 1 ones 🤷 |
I modified to classic context menu use by a tool named "StartAllBack",but I don't think it caused by incompatibility, In a word,this issue has been solved by executed Remove-AppXPackage command,thank you very much! |
That's because there's a fallback to call the older context menu when the package is not installed ;) |
Isn't that what most apps do? |
Restarting Windows makes it show up in the extended context menu - if you enable that option before the restart - but not in the regular one. Restarting explorer.exe doesn't seem to work. |
Related so posting here, but let me know if I should file a new bug: Just installed PowerTools. PowerRename shows up in the context menu when "Default and extended context menu" is selected in settings, but not when "Extended context menu only" is selected. Running version 0.60 on Windows 11 and restarted the computer as well as explorer. PowerToysReport_2022-07-13-17-45-56.zip Edit: fixed a link |
This is fixed on https://github.com/microsoft/PowerToys/releases/tag/v0.60.1 |
@anksingla The extended context menu is for pressing shift+right click |
Thanks! I'll try the new version |
Microsoft PowerToys version
0.60
Running as admin
Area(s) with issue?
PowerRename
Steps to reproduce
When I upgrade from 0.59.1 to 0.60,the PowerRename context menu is disappeared but the enable state is enabled in PowerRename Settings page as show in screenshot:
I was try to switch enable/disable PowerRename switch however the context menu still have not appear.
When I downgrade to 0.59.1 the PowerRename context menu is works normal.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response
The text was updated successfully, but these errors were encountered: