Many thanks for all the years of replies to an issue Microsoft is clearly unwilling to address. Having tried most of them, and not using a joystick here is what I have found. I have three Windows 10 computers and each one is manufactured by a different firm: i.e. HP, Dell, and MS Surface. They all have one thing in common: every time there is a windows update from Microsoft, Screen Saver switches to "none" as my screen saver. This is what I find without exception at least for the past year. My solution is as follows: 1. Open Screen Saver. 2. Change the "new selection" from "none" to whatever you wish to choose by way of a screen saver.....bubbles, mystify, photos you may have chosen.) 3. Change the time duration setting by at least one minute in either direction. 4. Apply the "changes" and exit. This works for me but may not work for others, and I do make use of USB for my Microsoft Mouse and an external hard-drive. However, this only works until the next MS update comes through. Then I repeat the process and all is once again well. The nice thing with this is that I always know when I have received an update at night because in the morning my screen saver has been turned off ! No surprise that Microsoft has not fixed this problem....sadly, they have a long history of 1. Ignoring problems 2. Finding ways to "upgrade" a feature that once took only one simple step to complete, and turning it into a multi-step process. (e.g. the failed "windows 8" OS. I do hope the steps I outlined below will prove helpful for some but I suspect that this glitch behaves erratically across the user spectrum. Good luck.
Screensaver is not working after Windows update to 1903.
I have tried setting DISPLAY, SCREEN and all the other settings to enable the screensaver to come on at the set time but nothing happens? I have to close the lid when I leave my laptop alone for awhile
***Modified Title from: Screensaver doesn’t come on at set time Windows 10 ver 1903***
Windows for home | Windows 10 | Sleep and Power on, off
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
75 answers
Sort by: Most helpful
-
Anonymous
2020-10-22T15:17:01+00:00 -
Anonymous
2020-10-13T23:49:36+00:00 The problem could be from some hardware issues such as joystick, USB hub,.... and I removed most of anything that attached to my PC such as joystick, USB hub and even the mouse I was using! Nothing worked! And then I watched this video and it solved my problem (https://www.youtube.com/watch?v=b8f2DxqFE\_0&t=229s&ab\_channel=TooCrooked) Basically, what it said was that there could be some software, drivers,...... running in the background that prevent your PC from going to sleep (as for me, I had a software that was running from start up and as long as I removed this from start up, my screen saver works! :) Hope this helps someone out there!
-
Anonymous
2020-10-08T04:55:54+00:00 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.
-
Anonymous
2020-10-06T12:54:03+00:00 In my case, it was definitely photos.exe. I stopped only photos.exe and set my screen saver time to 15 minutes and ... voila ... screensaver works.
FYI: Gary-DJ, setting the timeout to 1 minute for troubleshooting is not a good idea in my case as timeout values of 2 minutes or less were always working. Any value higher than 2 minutes is what triggered the problem for me.
-
Anonymous
2020-10-05T21:22:10+00:00 Found that it is Microsoft Edge 44.19041.423.0 But the Microsoft.Edge.exe is version 11... something.
I have read that "In June 2020, Microsoft began automatic rollout of Chromium-based Edge via Windows Update for Windows 7, 8.1, and all Windows 10 versions from 1803 to 2004" and Windows Updates says everything is up to date.
I would rather uninstall it if I could, really.