Do Not Display Last Signed-in User Name on Windows 10 Sign-in  

thank u bro OPTION ONE :- working %100 windows 10

I noticed that when doing this, the sign-in screen's background no longer respects the setting of the previous user. Instead, it uses whatever is set by the hidden administrator account. Luckily, TenForums also provides steps for how to login to this account: Administrator account - Enable or Disable in Windows 10 - Windows 10 Forums

Edit: Nope, this only worked temporarily. It either switched back to a default Spotlight photo after making the administrator account inactive again, or simply changed it back to a Spotlight photo for some other reason.

Does anyone know how to properly change the sign-in screen background color/picture (not the lock screen) when not displaying the user name?

Brink said:

Hello mmortal03, :)

The sign-in screen will use the same background as your lock screen if turned on using OPTION ONE below.

https://www.tenforums.com/tutorials/9...dows-10-a.html

No, I tried that, but that only works if Do Not Display User Name is disabled.

Brink said:

It's working fine on my system with Do Not Display User Name is disabled.

What build of Windows 10 do you have installed?

Anniversary Edition.

Brink said:

It should be working for you then. You might try the method in the tutorial below to see if it may work for you instead.

https://www.tenforums.com/tutorials/2...dows-10-a.html

No, while it will show whatever I select as a background on the Switch User screen (the one that says "Other user"), the issue is that the "Unlock the PC" screen that appears when you lock the machine, it shows that rock formation spotlight background no matter what I select as a picture.

However, if I choose "Windows spotlight" instead of picture, *then* it will show something different on the "Unlock the PC" screen. If I switch it back to a picture of my choosing, though, *only* the "Other user" screen will show my selected picture, but the "Unlock the PC" screen will then revert back to the rock formation picture.

This must be a bug in Windows in certain configurations, but I haven't been able to figure out what the cause is.