A thread on which to be Microsoft

*lets you enter log in password*

*Brings up your username*

*Swirls*

*Swirls*

*Swirls*

*Swirls*

User goes for coffee and comes back 

*Swirls*

*Swirls*

SORRY THAT PASSWORD WAS NOT CORRECT LOL

*u want this amazing software*

*oh no it won’t work on that os*

*yes, only on this os*

*gr7, it comes bundled with all this other software which u must buy*

*well, yes, they r not useful, but it comes as a bundle*

*sits at desk*

*opens laptop*

*logs in using biometrics*

*works flawlessly as always*

*briefly wonders why certain people struggle with tech*

*teams takes ages to load tho, stupid teams*

It is totes weird that a typo on password entry takes the system so long to recognise as incorrect. I swear I know if I cocked it up because it takes longer to recognise it's not the right password than it does to go to the start screen when I put it in correctly

Password cached locally so if you get it right it just logs you in 99 times out of 100. If you get it wrong then it has to go check on the network what your current password is (short delay) and then there is a standard bad password delay to prevent brute force hacking (longer delay).

The trick is to get your password right. 

i heart fingerprint login, except that our work system makes you type your full password once every two weeks and obviously by then i've totally forgotten what it was

i heart fingerprint login, except that our work system makes you type your full password once every two weeks and obviously by then i've totally forgotten what it was

This, only at my place it's once every month that you have to use your password, which makes it even more unlikely that I'll remember what it is. The time I waste talking to IT to override and reassign is more than the time it would take for me to type the password everytime I log in. Of course I can just scribble down the password on a Post It note but that defeats the purpose even more. I have deactivated this "convenience" and opted for password login every time.

Ahh that makes sense Rof Royalty; thank you for explaining. I do think the security delay should only kick in after 3 attempts or something to allow for butterfingers, but I get that some time would be needed to check if the local stored password is current when it gives an unexpected value.

Ahh that makes sense Rof Royalty; thank you for explaining. I do think the security delay should only kick in after 3 attempts or something to allow for butterfingers

By default I think it does, but I bet some corporate IT best practice guide says that you should have it delay for every bad attempt on work devices so they will have changed the settings.