win10 password problems
-
I'm at a loss to explain why this is happening based only on what you describe -- clever approach though. :-D All of that aside … have you considered using a Windows Hello PIN to log in instead of a big fat password every time? That's even a bit more secure, since PINs are local to your machine and wouldn't work anywhere else even if they were compromised (unless, of course, it's your machine itself that gets compromised.) Why a PIN is better than a password[^]
Thanks for taking your valuable time to read my too-long post. :thumbsup: Also, I was just curious about the PIN thing and didn't understand how it could be secure. Makes sense that it only works on the local machine and that is how it is secure. Thanks for mentioning that.
-
Happens to me anytime that Caps Lock light is on.
-
This might be completely unrelated, but it's food for thought anyway. There is one common username/password I prefer to use to log onto my different machines. However, I have a laptop (a netbook), on which I *cannot* use this password with some Linux distribution (I forget which--maybe some version of Lubuntu, because it's supposedly low-overhead) because it simply refuses to let me type a specific key (lowercase 'm') when attempting to log in. No "." character gets added in the password field, unlike every other key for the password. The button isn't broken; when I initially entered it during the account creation, the key was functional, and at no other time does the key ever misbehave. For example, in any plain text field, if I press 'm', there's no problem. I even reinstalled the OS, after I realized what was going on, and paid close attention to the password field as I entered the password when (re-)creating the account. It gets accepted at that time. Yet once I'm at the actual login screen, it's rejected. Being a laptop, some of the keys serve double-duty and are used as the numeric keypad as well - 'm' gets assigned to '0', and the NumLock key is used to switch between numbers and letters. However, no matter how many times I press NumLock at the login screen, pressing '0'/'m' registers no additional keystroke.
I've also seen it where a key is misbehaving. Especially on laptops, I've seen stuck alt or shift keys, etc. One thing that happens on our iMacs is that if you hit space to wake the computer up and turn on the monitor to show the login page, it actually puts a space before your username and won't log in properly. It's really hard to see because the text is barely moved over.
-
Do any of you ever attempt to log onto your win10 computer and it tells you that you are typing an incorrect password but you know you are not? I'm having a wifi adapter problem and at times I leave my computer and it goes offline and then the machine will tell me that I'm using an incorrect password even though I am not. Just curious if others are seeing this. I also have a lot of these in my Event Log:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.EDIT I searched for that CLSID and found a youtube that really does explain the problem. How to fix Event ID 10016 DistributedCOM ShellServiceHost errors - YouTube[^]
I have a laptop that has no numlock indicator light and no numeric keypad. Prior to entering the Bitlocker password, Windows turns on the numlock. And that creates *r6b3e0s w5th y64 *assw6rd. To make it more logical, in your second try, the numlock is turned off. Go figure.
-
Do any of you ever attempt to log onto your win10 computer and it tells you that you are typing an incorrect password but you know you are not? I'm having a wifi adapter problem and at times I leave my computer and it goes offline and then the machine will tell me that I'm using an incorrect password even though I am not. Just curious if others are seeing this. I also have a lot of these in my Event Log:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.EDIT I searched for that CLSID and found a youtube that really does explain the problem. How to fix Event ID 10016 DistributedCOM ShellServiceHost errors - YouTube[^]
I have a Win 10 Pro with latest updates that boots very fast. But sometimes, for a brief second, it will flash "Invalid password" before showing the actual logon screen. My guess: extra keyboard buffer char(s) / activity on startup. Scary, though.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
I have a Win 10 Pro with latest updates that boots very fast. But sometimes, for a brief second, it will flash "Invalid password" before showing the actual logon screen. My guess: extra keyboard buffer char(s) / activity on startup. Scary, though.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
Very interesting. Thanks for sharing that. That's the kind of stuff that I was wondering about -- if there is some odd behavior surrounding it.
What was once simply a "typewriter" (i.e. the KB), is now a "device"; with different connection options, "smarts / programmability", etc. It may be down to "(re)connections to Windows not initialized properly ... in certain cases".
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal