This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Again, can we please stick with "This" issue which is still not resolved?
Please do not hijack this thread, since it is critical that we keep it rolling, if we want to have a chance that it will be addressed and fixed.
Users with other, unrelated question/issues should open their own threads.
Thanks
I confirm, the problem persists, it is never possible that Microsoft will not solve the problem.
Yup, same problem here.
My company offers a CRM to its users, a lot of people can't connect their personal Outlook.com accounts any more because of this issue.
We're patiently waiting for Microsoft to fix this, but they don't seem to be willing to do much.
Glad to see this topic back on trend. In late January, MS obviously implemented programatic changes. Since this is such a widespread issue, that MS seems incapable of solving, why not roll back to when this problem didn't exist, and then slowly implement changes, pausing to see if the problem reoccurs?. Then they'll know the culprit. Did this back when I was in charge of the IT department at my company. Maybe a lot bigger than we know, but a solution exists. MS needs to assure all possibilities are on the table.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 12%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER6%3C/text%3E%3C/svg%3E)
I left a comment yesterday because I was having problem connecting a new employee mailbox (Outlook 2016 desktop to 365 hosted mailbox). I did everything possible (reg hack) even when it does not apply to Outlook 2016 but still couldn't get the new mailbox added into Outlook 2016. The error says something like "we can't add the account right now..." (not the exact words).
This morning I continued to troubleshoot the problem but didn't succeed so I gave up, again.
About an hour later, the user sent me an email. She said she was able to use Outlook 2016 to access her mailbox. That tells me the problem is on the back end. I did nothing on the PC to get Outlook 2016 to connect. It didn't connect earlier and suddenly it connects successfully. Whatever it is you guys are doing is the source of the problem.