Using classic Outlook for Windows in business environments
I brought it up because of some other issues that popped up recently
Windows 10 users report app gremlins after Microsoft update (msn.com)
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have this problem - Outlook 2016 doesn't accept password or app password - and i think it is a growing World wide Microsoft problem :-(
See also here: https://www.reddit.com/r/Outlook/comments/19dx64p/outlook_2013_windows_10_suddenly_not_accepting/Outlook gives me this: (startede yesterday)
I have 2 PC's with HOTMAIL accounts in Outlook 2016 ...
They both have this error.
I do get mails ... but I can´t send mails. Yesterday it did work for 1-2 hours ... but right now the error is there all the time :-(
Please help me.
Thanks in advance
Pierre
Using classic Outlook for Windows in business environments
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I brought it up because of some other issues that popped up recently
Windows 10 users report app gremlins after Microsoft update (msn.com)
The only workaround right now is to go into airplane mode, wait ~30 seconds, and then try again. May need to repeat a couple times. You should stay connected for a while, then when you get the error again just bounce the network again (no need to delete and re-add the account).
MS is working on a fix, no ETA.
Also make sure you have 2factor authentication enabled and are using an app password, not a regular password.
If you have 2FA enabled on your account, Outlook 365 should use modern authentication, at least with outlook.com, and I don't see why hotmail would be any different. My two PCs with O365 to outlook.com have not had a single disconnect using 2FA and modern auth.
Legacy passwords are being phased out.
That's not going to impact authentication. Even if it is TPM 1.0, that's not used for this authentication.
Now if you're running really old OS with TLS 1.0 or 1.1 only then that could do it.
I have a Core 2 Quad machine that is over 15 years old, has not had the issue once.
Is the one with the problem Old hardware by any chance (like core 2 proc?)