Screenshots appear blank

from Stardock Forums

I don't know if anyone else gets this - and I've been unable to find the cause.

If I screenshot, or use the snipping tool or snip and sketch, anything that does a screenshot partial or full. It simply shows a blank grey screen.

I don't know if this is an app setting, a conflict or something I can alter.

I have an Nvida 1080ti,(With GSynch running) Windows 10 Pro, VMWare Workstation running And numerous other apps/programs but none related to the desktop/screen or things like that.

Is there anything I can set/change to resolve this? Do you require more information? I keep my drivers up to date

fences
6,255 views 7 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. But,how is this related to Fences?

Thanks

Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

The problem has occured since Fences was installed - I guess I can confirm this by disabling Fences, But Fences is the only thing affecting my desktop unless Microsoft have done something 'helpful' again. I'll get back to you,  The fact it overscrolls beyond my desktop resolution I assumed might have been part of the issue but I will check.

 

DeskScapes - Bring your desktop background to life.
Reply #3 from Stardock Forums Top

Ok I killed Fences and screenshots is working, though - Fences is still running so I'm not convinced to be fair that it is necessarily the cause. Is there a reason there is two fence.exe processes in the startup - I presume there should only be one? I don't know if running two was part of the issue. Atm I'm not sure (still) the cause of the issue. I couldn't screenshot earlier, I can now.  I'll see if its the same after rebooting again - not had a chance to do that.

 

Reply #4 from Stardock Forums Top

Yes , both Fences should be running .

Reply #5 from Stardock Forums Top

Ok I'm at a lost what caused the screenshot issue, a reboot and its still working. It appears I must be wrong that Fences is the cause but not a clue what is - it's stange - it started after the install. At least I thought it did. Never mind. Thread ended :-)

Reply #6 from Stardock Forums Top

Great, glad it get solved.

Thanks for informing.

 

Basj
Stardock Community Assistant.