Screensaver is not working after Windows update to 1903.

>> I Connected the DS4 

Thank you. My DS4 was just USB charging and I forgot about it. As soon as I took it out, the screensaver started working again.Microsoft should fix this.

From Power Shell, type:

get-appxpackage *Microsoft.Windows.Photos* | remove-appxpackage

Damn! You got it! I just unplugged my joystick and sure enough a minute later the dang bubbles screensaver that I put on out of desperation finally popped up. The silly joystick was causing it the whole time.

Thanks for taking the time to give your input mate, because you just solved one person's problem.

One more solved case over here!

I recently bought an LG CX 48" as my main monitor, and since yesterday i started activating some screen protections (activated the screensaver, bought Wallpaper Engine for live desktop wallpapers, etc).

The Screensaver was working just fine yesterday, but last night I Connected the DS4 to try a few HDR games (which, btw, look fabulous on the CX O_O) and i left it connected overnight, as usual. But this morning the screensaver refused to activate.

After a bit of searching and multiple tried solutions from this thread, I saw this post, unplugged the DS4 and voila! Working properly now.

Baffling really, as it didn't even have the lightbar lit up... i thought it was sleeping in preparation for tonight's next gaming session :)

Anyway, thanks a lot for posting this !

I had the same problem too (screen saver worked until updating Win10 to Win10 1903).

For me, Step #4 (Check 'On resume, display logon screen') helped "kickstart" the screen saver to work again. I unchecked it after it worked and the screen saver is still working as intended.

Previously I temporarily changed screen savers and the wait period, but that didn't help. But maybe doing that in combination with checking 'On resume, display logon screen' will help others get their screen saver to work again.

This is the only approach that worked right now after the 20H2 update and the version before this one. Strangely I did not have any screen saver issue with 1909.

I had recently increased the number of photos in the folder I use for both the background slideshow (Windows stock settings) and the screen saver (the amazing gPhotoShow) from 1,042 to 1,143 and I thought this may be related to the issues: in fact it wasn't at all. 

Thanks for suggesting this approach. I also added 2 restarts for good measure, and after the 2nd restart it worked again perfectly as originally.

1. change screen saver to 3d text or bubbles, or other stock windows; also change the timeout to something short like 3 minutes; tick the annoying "on resume display logon screen" -- restart and verify it works as expected (including the annoying log-on screen)
2. change screen saver back to gPhotoShow (in my case), change timeout to 20 minutes, untick the logon screen option -- restart and rejoice at the screensaver working again!

The background image "slideshow" (I set it at 10 minutes) always worked.

I also have screen power off after 2 hours (for completeness). So if I'm not using my PC, I enjoy a slideshow of my photos (with metadata display) for up to 1h40m, then screen off to save energy.

There's clearly a bug in the screen saver / lock screen settings pages which breaks the screen saver on windows updates (or perhaps this is done deliberatly by MS), and the above 2 steps seem to reliably nudge Windows back to behave properly again. Thanks so much for posting that.

Having a functioning screensaver is very important to me, i use my Sony bravia television as a monitor on my ryzen system, the "blank screen" one is the only one i want to use but it refuses to work, on bravia tvs the "blank screen" screensaver turns off the panels backlight, in turn reducing the power draw from 89watts to 6watts and also it stops the leds from burning out, i am using windows10 version 2004, and guess what, if you think an LCD panel cannot be damaged from image retention you are very wrong because they almost certainly can get damaged, and running an OLED panel without a screensaver is certain death for the display, so come on microsoft please sort this problem out.