12 thoughts on “Fixing the Windows 10 Pre-Login Background Screen

  1. Finally, just about the only person on the internet who actually understands the difference between the login screen and the *pre-login* screen. Awesome work figuring this out.

    Notes from my experience (for anyone else trying this):
    – In order for this to work for me, I first had to remove the img100.jpg file in C:\Windows\Web\Screen (I just renamed it img106.jpg) and then follow the steps described above. Failure to do so would cause the LockScreen_Z folder and its contents to be recreated on reboot and the sea cave image to return.
    – With no img100.jpg in C:\Windows\Web\Screen at reboot, a light blue background is all that is shown on the pre-login screen. Saving a different image as img100.jpg in this folder and rebooting would cause that image to be copied to the LockScreen_Z folder and applied to the pre-login screen (only the first time, there-after, all the steps unfortunately have to be repeated)
    – I found another copy of img100.jpg in the following folder: C:\Windows\WinSxS\amd64_microsoft-windows-t..nbackgrounds-client_31bf3856ad364e35_10.0.10586.0_none_699c5beca3c8f021. I imagine the folder name may be different on other Windows 10 installations. Manipulating the img100.jpg file in this folder appeared to have no effect on the pre-login screen.
    – The ownership settings and permissions on the C:\ProgramData\Microsoft\Windows\SystemData folder appear to be reset on each reboot. Use “Replace owner on subcontainers and objects” when modifying them to save time and hassle.

    Thanks again!

  2. Great help on the latest and greatest clean install of “Anniversary” garbage. How Microsoft is still in business is beyond me. Good Grief!

  3. Just wanted to thank you and Scott for your insight on this very annoying issue.
    So I did some addition experimenting and found that if you pre-populate the “C:\Windows\Web\Screen” folder with your own images the image named img100.jpg will get “assigned” to the pre-login screen on reboot. So now instead of eliminating that image I can use my own.
    So I made a little batch file ( must be run in an administrative command window) and will pass it on for what it is worth.
    Now if someone can get this to work at startup we can autorotate the image.
    ————– cmd script follows ———–
    C:
    CD \Windows\Web\Screen
    ren img100.jpg img99.jpg
    ren img101.jpg img100.jpg
    ren img102.jpg img101.jpg
    ren img103.jpg img102.jpg
    ren img104.jpg img103.jpg
    ren img99.jpg img104.jpg
    cd \ProgramData\Microsoft\Windows
    takeown /F SystemData /R /A /D Y
    Rem The /R makes it recursive, and the /A assigns Admin group, /D is default answer for “are you sure” prompts.
    del SystemData\S-1-5-18\ReadOnly\LockScreen_Z\*.jpg
    ————- end script ———–

  4. I took this a step further.
    I run the batch file as a scheduled task triggered by system startup, and runs under the SYSTEM account.
    Because it now runs under the system account that owns the image, the “takeown” lines can be removed. I no longer need to take ownership because I am getting the owner to do the task.

    I now get a new image each time I restart the the PC, once changed the image persists during logoff/logon and only changes after shutdown/restart, or if I choose to run the batch file manually again.

Leave a Reply

Your email address will not be published. Required fields are marked *

3 × four =