W10 holding onto cached lock screen images?

[Sheridan]

Another bug for the list. We pushed out a default lock screen which seemed to work ok, however a week or so later we needed to change this screen and rolled out the new image. However, only half of the PCs show the new lock screen, the other half show the old lock screen.

 

But, on every machine the \windows\web\screen folder shows the correct new lock screen - I know this is cached somewhere and has to be manually deleted after permissions are reset but thats a massive pain in a room full of computers.

 

I guess I'm waiting for another update, unless theres a way to force the cache to clear?

[jtotheb]

I know this is cached somewhere and has to be manually deleted after permissions are reset but thats a massive pain in a room full of computers.

ProgramData\Microsoft\Windows\SystemData\S-xxxx\LockScreen_xxx

 

Fun permissions too!

 

Does the new image have the same filename? I've had a similar issue where I've overwritten the original image with a file of the same name (the original file, not LockScreen.jpg). I'm yet to try one with a different name and new lockscreen setting to see if this makes the alteration go more smoothly.

[Sheridan]

It did have the same filename, so I tried with a new filename and it makes no difference - it simply hangs on to the first lock screen that was deployed by GPO.

 

Can't be faffed manually changing permissions on all of them, its anothe reason I feel justified in the impending roll back to 7!