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

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.

 

It appears that the "Other User" sign-in only uses the default background when not using Spotlight since it's not tied to a user account.

As a test, you might see if using the tutorial below to force a default lock screen background may also be used on the "Other User" sign-in screen.

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

 

Does is show the proper background image on the "Other User" sign-in screen when you have the lock screen enabled again?

 

Yeah.

 

Odd. I added a note to the tutorial for this for others to be aware of.

 

Can you link me to that one? You mean a similar tutorial here on tenforums regarding disabling the lock screen, or just this thread? I've already forgotten what happens when the sign-in screen defaults to displaying the user name when combined with that buggy lock screen hack. It may be a more general issue than simply what this thread refers to. I can test that tonight and get back with you.

 

I added the note at the top of the tutorial on the first page here. *Smile

 

Okay, no problem, I will test the more general case and get back with you.

 

Ok. I look forward to hearing your results.

 

Another lockscreen disabler solution has been proposed elsewhere, this time as a Windows service, but, after testing it, it suffers from the same issue, as far as the buggy background image behavior is concerned, that the task scheduler solutions that I've tried suffer from. Here it is, though, for reference: ***

Btw, I'm about to test the more general case in a little while -- I haven't forgotten.

 

Alright, I'm still doing some testing of the general case, but one thing that I found that needs testing from others is:

If you: 1.) Select a custom lock screen background picture, 2.) Enable "Do not display last user name", 3.) Enable "Require users to press Ctrl+Alt+Delete" in netplwiz.exe, 4.) Enable "Show lock screen background picture on the sign-in screen" in Personalization -> Lock screen.

In this arrangement, what happens when you hit Ctrl+Alt+Delete and select "Switch User" (don't use other methods to get there, make sure to specifically use Ctrl+Alt+Delete)?
Which background do you see for the Ctrl+Alt+Delete screen, and which background do you see for the sign-in screen? For me, I get the cave/beach background for both, and in rare cases I'll get a solid blue background. Neither of these match my settings. If you guys get similar results, how might someone go about changing these? Is this not a bug?

 

I'm seeing the background picture I selected for both the lock and sign-in screen with those settings.

 

Hmm, then this could be the root of the issue that I'm experiencing. My guess is that since the standard lock screen doesn't appear when running Switch User from Ctrl+Alt+Delete (this is independent of whether "Requires users to press Ctrl+Alt+Delete" is enabled), the buggy state of my backgrounds isn't getting reset to whatever I newly select (as having the Lock screen run seems to initialize the new settings). So, these two remain stuck with the cave/beach background. I wonder if I could have the system run the Lock screen app in the background as a scheduled task while the Switch User screen is displayed, which might get it to become unstuck. I'll have to try that, though I don't have much faith in it working. Anyway, really, really weird.