Try gpupdate /force command and see if the problem persist?
Open start and search for feedback and open the Feedback Hub app and report this issue.
20H2 screensaver not working via GPO
Hi All,
Has anyone else experienced issues with screensavers on new builds or upgrades to version 20H2. We have the following policies set via GPO (User) and these work on 1909.
Enable screen saver
Password protect the screensave
Screen saver timeout
Force specific screen saver
On 20H2 the screen saver shows as a black screen, likely the blank.scr in system32 rather than the specified screen saver in the GPO. Have also found that the registry settings are missing for these apart from 'Enable screen saver'. This is happening on all 20H2 builds, wondering if something has changed in 20H2 build?
Windows for business | Windows Client for IT Pros | User experience | Other
4 answers
Sort by: Most helpful
-
Reza-Ameri 17,341 Reputation points Volunteer Moderator
2021-06-04T17:16:17.113+00:00 -
Andy YOU 3,076 Reputation points
2021-06-07T06:43:16.113+00:00 HI AlistairRussell-5043,
Did you try to fresh install win10(20H2) and set local screen saver policy and set local blank.scr on this win10(20H2)?
there is other thread for your reference
https://www.reddit.com/r/sysadmin/comments/lp39nd/screen_savers_windows_10_20h2_should_be_simple/ -
Jeremy Beaulieu 1 Reputation point
2021-06-09T17:50:45.647+00:00 Yes, I've experienced this at 2 clients. These were not fresh installs though. We use the screensaver to lock the screens and people have been noticing that screens are not locking on time.
-
Jeremy Beaulieu 1 Reputation point
2021-06-22T13:47:17.213+00:00 I did and I don't believe it helped. I haven't heard any complaints from anyone since so I'm not sure if it was fixed with an update or if it's just not something that's really noticed/complained about much. When I checked, the PC the GPO was applied.