New
#21
Hi Ken, unfortunately that workaround didn't resolve the issue, because it reverted back to doing the same thing again. So I then went back and disabled that change in the gpedit window (the ones I described in my last post), and switched back to normal mode of selecting a lockscreen image through the regular Windows settings. Since then, the same problem of the incorrect lockscreen image and slow start-up continued after a long shut-down.
But yesterday when I powered off my computer, I noticed that Windows said that it was installing updates during the process, which did not take long, but did not restart automatically to complete (maybe it didn't need to). I decided to just powerup the computer again anyway, and after logging in, it went to a 'Windows is preparing Features' message, or something like that, and then to my desktop like normal. Once my computer booted up totally, I then shut it down for the night again.
Today when I powered it up after several hours of it being off, which is when this lockscreen issue happens, it went right to the correct lockscreen image, which surprised me. In addition, there was no 'Please Wait' screen or slow startup like usual. What I'm starting to think is that small update yesterday during the shut-down process, was an update Windows made to correct this lockscreen image issue.
I hope I'm not speaking too soon, because I have not shut down my computer since, and experienced a long period between turning it back on, but it only seems logical because it has not selected the correct image after a long shut-down since the Fall Creators Update, which was all the way back on 11/15. The only time it selected the correct image is when I applied that gpedit change in my last post, but when the same issue resurfaced again, I went back and reversed those changes, like I said. I will definitely let you know either way, so I hope it was indeed a fix by Microsoft for this issue.
Quote