Windows 10: Stuck On Lock Screen no matter what key I press

I don’t know why this is happening. I can’t log in on my computer. Any key I press does NOT work. I hit a key, it thinks for a second and than it goes back to the Lock Screen PLEASE HELP.

:)

 

Computer stuck at lock screen and after Anniversary Update on Windows 10

The first suggestion is not helpful since the problem is that we have many open programs stuck behind the lock screen.

I have run into this problem and tried the On-screen keyboard but it does not help.

An additional data point is that it does not matter what password is entered.

Enter correct password -> spinner shows up, after about 30 seconds the spinner goes away and the screen remains locked.

Enter blank password (simply hit Enter) -> same behaviour as above.

The behaviour is the same whether using physical or On-screen keyboards.

 

Lock screen image stuck

hello,

I have one PC stuck with the mountains lock screen image and another one with a nicer but still stuck image with the "thanks for sending us feedback" caption, usually there's do you like yes or not.

Is it a problem on MS end this time? I tried the reset steps so many times, usually after 10-15 minutes the lock screen picks up when there's the mountain one for any reason, but not this time.

thanks

 

Press Shift Key to turn off Caps Lock

Actually, I get asked this quite a lot

There is, however, a very good reason to prefer this (old) „Typewriter Caps lock“-behavior over the new default, and it's simply this: if „Press the SHIFT key“ (instead of „Press the CAPS LOCK key“) is selected, then the behavior of „Caps lock“ changes from being a „toggle key“ to being a key that can only be used to turn „Caps lock“ on – to turn „Caps lock“ off, one has to press (either) one of the Shift keys.

This can be advantageous for touch typists, who are used to writing long passages of text without looking at the keyboard, and especially so if they're (C/C++) programmers, who may still regularly find themselves typing in variable names of CONSTANTS_IN_UPPERCASE.

That's because, if Caps lock is not a toggle key, it's not necessary to keep track of its current „toggle state“ in your head:

• If I want „Caps lock“ to be on, I can press CAPS as often as I like. If it happened to be enabled already, nothing changes; otherwise, I can be sure it's enabled afterwards.
  
  
• If I want „Caps lock“ to be off, I can simply press SHIFT

This sounds like a hypothetical advantage, but it's not. I work as a programmer, and I often find myself typing in code like the following:

/* Some debugging code; will only be included in debug builds: */
#if defined _DEBUG

Afterwards, I may pause a little, to think about the code line I would like to type in next. Now, if „Caps lock“ is a toggle key, I may (once I decide to continue) be unsure if I actually remembered to turn „Caps lock“ off at the end of ‘_DEBUG’.

Did I? Did I not? – The only way to be sure, is to look.

This is not so, if the „Press the SHIFT key“ behavior is enabled. If unsure, I can just press SHIFT once, be sure of the set state, and merrily continue may way.

That, for me, is the single most important reason to prefer the „Press the SHIFT key“ setting. Also, interestingly, this used to be the default behavior in the old days … at least, until Microsoft decided to ditch Windows 9x in favor of Windows NT¹.

¹ Actually, my memory could be wrong in this regard and I'm not completely sure … maybe someone more knowledgeable in those matters can confirm that the „Caps lock“ default behavior was indeed changed during the switch from Windows 9x to Windows XP?