[thomasmarton]

Wasn't Microsoft the "let's not break backwards compatibility for any reason" company?

Coming from software development, we do have tests that insert a screenshot into the report in case they fail, and I'm assuming we are not the only ones that found the PrtScr button to be useful for that

[smt88]

> I'm assuming we are not the only ones that found the PrtScr button to be useful for that

I can honestly say you might be the only ones. I've never heard or even conceived of such a thing.

There are a ton of ways to avoid this in the first place:

- use CLI to take the screenshot instead of simulating a key press

- don't test on Windows 11

- use reproducible test instances where you've turned this option off

- (if screenshotting text) use... logs?

I'm truly baffled by this complaint.

[Choco31415]

If they’re programmatically pressing the PrtScr button, then hopefully it’s not too difficult to write or find a library that takes a screenshot too.

[zerocrates]

You're saying you have tests that programmatically "press" PrtScr to take a screenshot?

I wouldn't put it past Microsoft to preserve the old behavior just for programmatic keypresses.

[sundvor]

Then disable the new default behaviour, by using the provided setting?

For 99.999% of the users, I reckon this is a good change. And for the rest they've thoughtfully provided an option to revert.

[pjmlp]

That ship has sailed with Windows 8 and .NET Core reboot.

[ArnoVW]

Oblig xkcd https://xkcd.com/1172/