Why does 0x80049dd3 come up in the Outlook desktop app?

Anonymous
2024-12-13T14:12:30+00:00

In Windows 10 when I open or work with mail in the Outlook desktop app (local installation) the message no access keeps coming up.

Then I get a message that I have to select continue to sign in to this account, or manage to remove the account.

Then the message something went wrong, try again later 0x80049dd3 comes up.

I can then select send feedback or cancel as I choose, and then I get logged in and can continue working.

Can something be done to get this away, so that I don't often get interruptions with this?

Is it a known bug, and/or could it pose a security risk?

***Moved From Windows / Windows 10 / Security and privacy***

Outlook | Windows | New Outlook for Windows | For business

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.

0 comments No comments

68 answers

Sort by: Newest
  1. Anonymous
    2024-12-15T18:02:41+00:00

    In my case, I log in using PIN but I did not enable the passwordless login and have the issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-12-15T17:55:33+00:00

    Same issue , I thought I had been hacked ? .

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-12-15T17:04:13+00:00

    I have the same issue, so can I please also be contacted when the solution is discovered.

    Thanks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-12-15T16:58:09+00:00

    I do wonder how people with this problem use passwordless login for these accounts.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-12-15T14:35:46+00:00

    I only got the 0x80049dd3 problem yesterday and I installed KB5048652 on Tuesday evening. All was fine till Friday. So, I believe it may not be KB5048652.

    Was this answer helpful?

    0 comments No comments