So I have worked out a basic path to force a particular lock screen image on Windows. I guess it won't be fixed before 1703 is released. Not to mention that Microsoft itself should have caught this before 1607 went live. This bug has been repeatedly reported to Microsoft for literal months, and no action has been taken. This change in behavior in 1607 has to be a bug because (a) it's a dumb change, (b) it would mean that the "Prevent changing lock screen and logon image" Group Policy no longer makes sense, and (c) the descriptions in Group Policy Editor still say that it should set only the default lock screen. The "Force a specific default lock screen and logon image" is supposed to set the default user lock screen for new users that's it. The "Prevent changing lock screen and logon image" Group Policy no longer makes any sense in 1607. Basically, in 1607, Microsoft incorrectly merged the "Force a specific default lock screen and logon image" and "Prevent changing lock screen and logon image" Group Policies. In 1607, the Group Policy "Force a specific default lock screen and logon image" still sets the system lock screen to an image, but it also forces the user lock screen to the same image without allowing the user to choose his/her own user lock screen. You could optionally use the Group Policy "Prevent changing lock screen and logon image" if you wanted to prevent users from choosing their own user lock screen. Set the default (but changeable by the user) user lock screen.In 15, you could set the Group Policy "Force a specific default lock screen and logon image." This would do two things: In 1607, the login screen just uses whatever lock screen you're at, so the login screen effectively no longer exists.
![best windows 10 lock screen wallpaper dino best windows 10 lock screen wallpaper dino](https://static1.makeuseofimages.com/wordpress/wp-content/uploads/2017/01/Lock-Screen-as-Wallpaper-Featured.jpg)
I'll just say what I know about this in regards to Enterprise (Pro has even less functionality): Problem is they are stuck on the same lockscreen that was originally pushed outĭeleting the cache in C:\Programdat\Microsoft\Windows\Systemdata does not seem to regenerate the lockscreen images where the cached lockscreen images are stored We also have SCCM update and push out the graphic to C:\Windows\Web\Screen as a simply copy to that location to all windows 10 clients Oh well, for now I have other fish to fry, I hope you all find a better solution.īTW I'm testing across Win 10 1511, 1607 with similar results.īig_Mark in a Win 10 Enterprise environment.īTW I'm testing across Win 10 1511, 1607 with similar results.You are having the exact same issue as me That seems like the best idea BUT WHAY CAN:T I POINT TO A LOCAL DIRECTORY FOR THE SLIDESHOW? While I was crawling around in this rabbit hole I read somewhere on a Microsoft page that if we enable Azure AD I can choose a web hosted slideshow. We have a pool of graphics used by the marketing department that I want to have rotating through all the PCs. "C:\Windows\Web\Screen\screensaver.jpg" DOES reflect the "weekly" graphic. It always takes the first graphic deployed (at least I have 2-5 different lock screens around the office) but never changes. It seems like we're doing the same thing, push out specific graphic to local machine, use GPO to se screensaver.Įvery week I have SCCM push out a new graphic with the same name as the previous one (overwrite old one with new one so I don't have to continuously change the GPO to switch images) the issue is the lock screen image doesn't change. Updating the lockscreen manually, then copying a new lockscreen via sccm breaks this and they just get a black empty lockscreenĪny suggestions would be in a Win 10 Enterprise environment. Problem is, we still allow users to update the lockscreen themselves for more freedom of their machines. Deleting the 2 SID folders (you'll have to use psexec as SYSTEM) seems to force windows to regenerate the folders and update the lockscreen There is a SID folder for the system account and also for the user account I have been troubleshooting this for a couple of days now and I found that Windows caches it here:Ĭ:\ProgramData\Microsoft\Windows\SystemData\"SID of account"\Readonly\Lockscreen_P\ We use SCCM to distribute a lockscreen every month or so showing events etc to copy the lockscreen.jpg to "C:\windows\web\screen\"ĭoing a gpupdate /force does not seem to do anything We have Force Specific Lockscreen set in GPO and I have done a GP Result and its there so the policy is working
![best windows 10 lock screen wallpaper dino best windows 10 lock screen wallpaper dino](https://i.redd.it/sggbgfyh9bm01.jpg)
I am having major annoying issues with this for our windows 10 only computers