How To Resolve Can’t Type Password at Login Screen on Windows 11/10? | Keyboard Not Working Fix

Have you checked for a dedicated ‘Log’ button or switch on your keyboard or laptop?

This one tripped me up for a while. Some keyboards, especially on laptops, hide a tiny button or switch labeled “Log” or “Log On” somewhere around the edges or in the function key cluster. On laptops, it’s often a tiny physical switch or a function toggle that completely disables or enables the keyboard input. If you’re stuck on the Windows login screen and nothing you type is registering, it’s worth checking if such a switch exists and flipping it off or on. It’s typically placed on the side, top corner, or integrated into another key with a Fn layer. On many laptops, this is actually a Function key toggle or a separate physical switch. Turning it off should allow your keystrokes to appear in the password field again. Honestly, it sounds obvious now, but I’ve missed this, and it can be the reason why your keyboard acts dead even if it’s fine otherwise.

Try reconnecting or swapping out your keyboard

If you’re on a desktop with a wired keyboard, re-plugging it is simple but sometimes effective. USB ports can be flaky—especially if you’re using a front port or a hub. I’ve had times where disconnecting the USB cable, waiting a second, then plugging it into a different port (preferably one directly on the motherboard rather than a hub) fixed the issue. It’s a quick check—if your keyboard still doesn’t work after that, try another keyboard entirely. This isn’t just about testing hardware; it can point toward whether the problem is with the keyboard itself or something deeper (like the USB port or driver). On my older ASUS, sometimes the port was just dead, or the connection was loose. If you’re on a laptop, try plugging in a different USB keyboard to see if that one works better. If it does, you’re probably dealing with a hardware fault or port problem in your original device. Worth spending a few minutes on this before digging into more complicated stuff.

Check if your wireless keyboard is connected and powered

Wireless keyboards can be the sneakiest culprits here. They rely on either Bluetooth or special RF receivers plugged into your USB port. First off, make sure it’s charged—nothing like realizing the battery died at the worst moment. After that, double-check if it’s properly paired or connected. You can do this via Windows’ Bluetooth settings: Settings > Devices > Bluetooth & other devices. Sometimes Bluetooth gets turned off after updates or restarts, and the keyboard is just sitting there, not actually connected. Also, head over to Device Manager and look under Bluetooth. Confirm the Bluetooth adapter shows as enabled and working properly—no warning icons or disabled statuses. Re-pairing the device can often fix the problem — especially if everything looks fine but you can’t type. It’s frustrating when the device shows as connected but doesn’t actually send keystrokes, but re-establishing the link often clears it up.

Rebooting can fix a lot of weird glitches

I know, everyone says “restart,” but honestly, it still works. Sometimes Windows hiccups and fails to recognize the keyboard properly, especially on login screens, USB issues, or after updates. The trick that finally made a difference for me was doing a forced shutdown: hold down your Power button until it turns off, then if possible, unplug the power cord or take out the battery (if your laptop has a removable one). Wait a minute or two—just long enough to drain residual power—then plug everything back and start the system again. I’ve seen this reset hardware caches and make the keyboard show up again. In a few cases, that’s all it took to get my typing back at login time. Easy fix if you’re desperate before diving into driver updates or BIOS fiddling.

Use the virtual keyboard at the login screen

If you’re really stuck and your physical keyboard refuses to do anything, access the Windows On-Screen Keyboard. On the login page, look for the “Ease of Access” icon — it’s usually a little icon at the bottom right or corner of the login screen. Clicking that lets you select “On-Screen Keyboard”. Alternatively, from within the system, you can press Windows + Ctrl + O to turn it on. Once the virtual keyboard pops up, use your mouse to click in your password box and type your password. It’s often a lifesaver when dealing with software glitches, or even driver issues that keep your physical keyboard from working at startup. This way, you can get into Windows and troubleshoot from there rather than being totally locked out.

Verify if any background apps are interfering with keyboard input

Sometimes, the problem isn’t hardware or connection — it’s certain applications or utilities starting up with Windows that hijack input drivers. To check, press Ctrl + Shift + Esc to open Task Manager. Head to the “Startup” tab. Here’s where a lot of stuff hides. Look for any unfamiliar or suspicious entries that could be causing issues — security tools, language utilities, or UI overlays that might conflict with your keyboard drivers. Disable any that look suspect by selecting and clicking “Disable”. After that, try rebooting and see if your keyboard works at the login screen. Sometimes, a glitchy app or driver conflict can hijack input right during startup, and disabling these pesky programs can solve the problem. You can also dig into Event Viewer (type eventvwr.msc in the run dialog), just to look for warnings or errors related to input devices to supplement your troubleshooting.


In the end, if you can’t type your password at login, it’s almost always a hardware toggle, connection issue, driver hiccup, or a conflicting app messing things up. Picking through these common pitfalls—checking switches, reconnecting devices, trying different keyboards, using the virtual keyboard, and inspecting startup programs—can usually get things back on track. Don’t get discouraged — I’ve been there, and it’s often simpler than it looks once you punch through the confusion.

Hope this helped — it took way too long for me to figure it out myself. Anyway, hope this saves someone else a weekend.