Pressing Print Screen results in a black display


After pressing the "print screen" key, the entire screen goes black except for the cross-hairs of the cursor, which can be moved around like normal.

The resulting capture is only black, with no indication of what was originally on the screen, save for the mouse cursor.

The same issue occurs if "Shift + Print" or "Alt + Print" is pressed; the resulting capture is nothing but black.

The graphics card driver is updated to its latest version. The only obvious change I can think of is that Windows 10 recently installed its "Creators Update". Previously the screenshots would be taken without issue.



  • Windows 10 Home edition

  • version 1703

  • OS Build 15063.138

Graphics Card:

  • NVIDIA GeForce GTX 980M

  • Driver Version


Robin Krom
April 29, 2017, 6:01 PM

Hi, thanks for reporting this.

It's not the creators update, using this myself without issues.

We have had a few similar reports before, in every single case the issue was the graphics driver.
People reinstalled it, updated or else, and the problem suddenly was gone.
Some had to wait for a driver upgrade, than it worked again.

If you can't get the problem away, I am sorry but this is something I will not be able to fix from our side.
We have millions of Greenshot installs on the whole world, if it would have been a Greenshot bug or an issue with a normal setup, we would have had a really huge load of bug reports.

Best wishes,

Alex Certa
April 29, 2017, 7:14 PM

Fair enough; I'll see if I can figure something out. I appreciate the quick response.

Robin Krom
June 21, 2017, 7:23 AM

Hi Alex, did you find something?

Alex Certa
June 23, 2017, 7:57 AM

Hi Robin, the issue is resolved. I don't have an explanation as to how; I tried uninstalling and reinstalling various software and drivers without any luck. But one day I turned on my PC and noticed the issue no longer existed. I'm inclined to believe that you were correct and the cause was the graphics driver, though I wish I had some shred of evidence or an explanation of what happened.

Regardless, I no longer have an issue, so this bug can be closed/rejected as far as I'm concerned.

Robin Krom
June 23, 2017, 8:29 AM

Maybe there is something in the update history which explains it... thank for the feedback, closing this.




Alex Certa

Affects versions