Win 10 screen saver won't (usually) trigger w/ WE running

[Psychor]

Hi,

I have Win 10 Pro set to enable a screen saver and lock the PC after 10 min. of inactivity. This is a Win 10 setting. I've found that Win 10 won't trigger the screen saver with WE running. My guess is because the animated wallpaper makes Windows think there is activity - I don't know for sure.

Is there any way to have WE honor Window's screen saver settings? This is a security concern for me.

Thank you and keep up the great work!

[Tim]

Hey, check out our FAQ on this issue, it talks about hibernation but it's essentially the same issue:

https://steamcommunity.com/app/431960/discussions/2/1354868867716398763/

Try to disable audio output in the Wallpaper Engine settings for starters, for example.

[Psychor]

Originally posted by ultio:

Hey, check out our FAQ on this issue, it talks about hibernation but it's essentially the same issue:

https://steamcommunity.com/app/431960/discussions/2/1354868867716398763/

Try to disable audio output in the Wallpaper Engine settings for starters, for example.

When I run "powercfg /requests" the only thing that shows up is:

SYSTEM:
[DRIVER] High Definition Audio Device (HDAUDIO\FUNC_01&VEN_10EC&DEV_0900&SUBSYS_104386FE&REV_1000\4&1ab1d9e6&0&0001) An audio stream is currently in use.

I have "Audio output" disabled in Wallpaper Engine. I never had this sleep issue with WE builds from mid-2018+. I suppose something in a recent Windows update could have caused this issue though. Any further ideas?

Thanks.

[Tim]

Are you absolutely sure that this is caused by Wallpaper Engine. If you kill Wallpaper Engine and all its processes (wallpaper32.exe, wallpaper64.exe, webwallpaper32.exe), does this still appear when you run the command?

What wallpaper(s) are you using exactly when you receive this output? Wallpaper Engine cannot control the audio output for web-based and application-based wallpapers, so these could potentially still be the source of the open audio stream.

[Psychor]

Originally posted by ultio:

Are you absolutely sure that this is caused by Wallpaper Engine. If you kill Wallpaper Engine and all its processes (wallpaper32.exe, wallpaper64.exe, webwallpaper32.exe), does this still appear when you run the command?

What wallpaper(s) are you using exactly when you receive this output? Wallpaper Engine cannot control the audio output for web-based and application-based wallpapers, so these could potentially still be the source of the open audio stream.

Ok. So I finally found out what was causing "An audio stream is currently in use." I completely killed the application causing that and made sure there were no audio streams in use. See here: https://imgur.com/g5OxF1H.

I then left my PC alone with a 15 min. timeout and even after 20 min. my screensaver didn't trigger. As I said above this wasn't the behave many months ago, but I can't say exactly when.

Any ideas? Thanks.

[Tim]

What type of wallpaper are you using? Or even better: Which wallpaper are you seeing this behavior with exactly? You can find the link to the wallpaper by clicking on the little Steam icon below the preview image when you select a wallpaper in the app.