-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Bug report tool not generating the zip file on desktop #12707
Comments
@franky920920 thanks for reporting this! Can you verify that this only happens with v0.43.0? If you re-install v0.41.4, is the issue still there? |
@dedavis6797 Nope. v0.41.4 get the same issue. Screenshot attached. |
I've just tested it out on Windows 11 and it generated the zip file. It's named something like |
@jaimecbernardo Sure, this is my full desktop path: |
I believe it is a known issue. We created an issue https://github.com/kuba--/zip/issues/156 to address it.
|
@mykhailopylyp Here you go! |
@franky920920
Let us know if it works for you |
@mykhailopylyp Yes. This workaround works! See screenshot below: |
@mykhailopylyp According to https://github.com/kuba--/zip/issues/156#issuecomment-907109766 the blocked issue has been resolved so I believe this issue could be processed. |
Fixed in 0.47 |
I was having the problem with the Bug reporter tool not running in v0.49.1. Bug ID #14270 is mine. I tried running the tool manually from the installation folders as recommended above, and it works correctly. Note- On this machine I have PT installed in |
I still have this same problem. It works if I run the actual tool in the installation folder, but not if I use the icon in the system tray menu. |
Microsoft PowerToys version
0.43.0
Running as admin
Area(s) with issue?
General
Steps to reproduce
Report Bug
.OK
button clicked.✔️ Expected Behavior
The bug report .zip file should be created on the desktop.
❌ Actual Behavior
There is no file created on the desktop. (Shell location:
shell:desktop
)Other Software
Windows version: Windows 11 build 22000.120
The text was updated successfully, but these errors were encountered: