print screen shortcut don't work on windows 11 - and cannot be configured to other keystroke.

[zurcacielos]

Flameshot Version

Flameshot v12.1.0 (96c2c82)
Compiled with Qt 5.15.2
winnt: 6.2.9200
windows: 8

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)

Operating System type and version

windows 11

Description

print screen shortcut don't work on windows 11 - and cannot be configured to other keystroke.
The printscreen shortcut continues to get assigned to windows regular screenshot tool.
And it cannot be configured to other key stroke, the shortcut for print screen is FIXED.

Steps to reproduce

1. run flameshot
2. press print screen
3. windows regular print screen appears.
4. flamshot should appear.

Screenshots or screen recordings

No response

System Information

windows 11
surface pro 9

[gamberoillecito]

I'm having the exact same issue, it worked at first but after a couple of minutes it stopped working

[mmahmoudian]

@zurcacielos @gamberoillecito

it worked at first but after a couple of minutes it stopped working

Please check our documentation. the answer is usually there: https://flameshot.org/docs/guide/windows-help/
Just to clarify, this is not a bug. This is Microsoft forcing their software (Snipping tool) to the user.

Also duplicate of:
#3506
#3325
#3259
#3234
#3147
#2887
#2261
#1961
#1551 <-- main thread

and cannot be configured to other keystroke.

No at the current state of Flameshot, this is not possible in Windows.
Duplicate of:
#3485
#3292
#3214
#2925
#2493
#2167
#1341 <-- main thread
#1861
#1054

Please always search among open and closed issued before creating a new one. This would primarily to save your own time.

[gamberoillecito]

@mmahmoudian thank you for your help, unfortunately I had already checked the documentation and tried the proposed solutions but none of them worked for me. I understand this has to do with Microsoft being Microsoft but being able to change the default shortcut instead of Print Screen could easily solve the issue. The fact that the CLI doesn't work in windows also prevents the use of alternatives such as autohotkey (mapping any key combination to PrintScreen doesn't solve the issue)

[mmahmoudian]

@gamberoillecito true, the lack of Windows CLI is an issue, but there is an open feature request about it. Please give it an upvote.