Creative Cloud prevents the display from automatically entering a low-power mode

Forum|Forum|6 years ago
October 16, 2019
3 replies
715 views

Lately, I noticed that my display does not shut off, e.g., when I lock the screen (<Windows> + L).

"powercfg /energy" shows

The program has made a request to prevent the display from automatically entering a low-power mode.

Requesting Process

\Device\HarddiskVolume2\Program Files\Adobe\Adobe Creative Cloud\ACC\Creative Cloud.exe

I stopped the "Adobe Creative Cloud", and everything is back to normal.

But, the question is why is it doing this.

This topic has been closed for replies.

Correct answer tsmith35x

So just an update with regard to the whole issue with Creative Cloud preventing my monitors from going to sleep while my computer is powered up and at the lock screen... this one, specific fix worked and is continuing to work, even though I have CC running 24/7 in my tray:

From CMD prompt, enter this one line:
POWERCFG -REQUESTSOVERRIDE PROCESS "Creative Cloud.exe" DISPLAY

This has been working great on my two PCs, and I have seen no reoccurrence of my monitors staying awake when they should go to sleep. Looks like this fix (based on a post from @MRMAdmin) is a permanent solution.

kglad

Community Expert

also, reports are coming in from users that had this monitor lock problem that the latest adobe cc desktop app (5.9.0.372) appears to be better behaved than previous versions and does not trigger the monitor lock.

tsmith35xCorrect answer

Participating Frequently

So just an update with regard to the whole issue with Creative Cloud preventing my monitors from going to sleep while my computer is powered up and at the lock screen... this one, specific fix worked and is continuing to work, even though I have CC running 24/7 in my tray:

From CMD prompt, enter this one line:
POWERCFG -REQUESTSOVERRIDE PROCESS "Creative Cloud.exe" DISPLAY

This has been working great on my two PCs, and I have seen no reoccurrence of my monitors staying awake when they should go to sleep. Looks like this fix (based on a post from @MRMAdmin) is a permanent solution.