Error: Something went wrong. Try again later. 0x80049dd3 Affects: New Outlook for Windows (Windows 10/11), Microsoft 365 Time: 5-10 minutes
Quick Fix
Click Cancel when the error appears. In most cases, this dismisses the sign-in prompt and restores access to your inbox. The error will reappear periodically (roughly every 20 minutes) but clicking Cancel each time allows continued use.
This is a known Microsoft bug. No permanent fix is available as of December 2025.
Step-by-Step
Step 1: Dismiss the Error
When the "Something went wrong" dialog appears with error code 0x80049dd3:
- Click Cancel (not Continue)
- Your inbox should become accessible
- Repeat as needed when the prompt returns
Step 2: Clear the Web Account Manager Cache
If dismissing the error does not work, clear the authentication broker cache:
# Stop Outlook first
Stop-Process -Name "olk" -Force -ErrorAction SilentlyContinue
Stop-Process -Name "outlook" -Force -ErrorAction SilentlyContinue
# Clear the AAD Broker Plugin cache
$brokerPath = "$env:LOCALAPPDATA\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy"
if (Test-Path $brokerPath) {
Remove-Item -Path "$brokerPath\AC\TokenBroker\Cache\*" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item -Path "$brokerPath\Settings\*" -Force -Recurse -ErrorAction SilentlyContinue
}
# Clear the Microsoft Account cache
$accountPath = "$env:LOCALAPPDATA\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy"
if (Test-Path $accountPath) {
Remove-Item -Path "$accountPath\AC\TokenBroker\Cache\*" -Force -Recurse -ErrorAction SilentlyContinue
}Restart Outlook after clearing the cache.
Step 3: Repair Office Installation
If cache clearing does not resolve the issue, run an Online Repair:
- Open Settings > Apps > Installed apps
- Find Microsoft 365 or Microsoft Office
- Click the three dots > Modify
- Select Online Repair (not Quick Repair)
- Follow the prompts and restart when complete
Step 4: Verify
Launch Outlook and check if the sign-in completes without the 0x80049dd3 error.
Why This Happens
The 0x80049dd3 error is a bug in the Modern Authentication flow used by the new Outlook app on Windows. The Web Account Manager (WAM) broker fails to properly hand off authentication tokens during sign-in.
Microsoft confirmed the issue on December 17, 2024 and stated it is under investigation. Despite claims of a fix in the Feedback Hub, user reports indicate the problem persists as of December 2025.
The bug primarily affects:
- New Outlook for Windows (the replacement for Mail and Calendar)
- Microsoft 365 personal and business accounts
- Both Windows 10 and Windows 11
Classic Outlook (the older desktop app included with Office) is generally not affected.
Alternative Solutions
Option A: Use Outlook on the Web
Access your email through a browser at https://outlook.office.com until Microsoft releases a fix.
Option B: Switch to Classic Outlook
If you have a Microsoft 365 subscription that includes Outlook:
- Open the new Outlook app
- Click the toggle in the top-right corner labeled "New Outlook"
- Switch back to the classic version
Option C: Add ADAL Registry Key (Temporary Workaround)
Force legacy authentication by enabling ADAL:
# Create the registry key if it doesn't exist
New-Item -Path "HKCU:\Software\Microsoft\Office\16.0\Common\Identity" -Force
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Common\Identity" -Name "EnableADAL" -Value 1 -Type DWordNote: This is a temporary workaround and may not work in all configurations. Modern Authentication is required for some security features.
Current Status
Microsoft has acknowledged the 0x80049dd3 bug multiple times:
- December 6, 2025: Initial reports surfaced
- December 13, 2025: Microsoft claimed the issue was resolved
- December 17, 2025: Microsoft confirmed the fix did not work and reopened investigation
- December 2025: Issue persists for many users
No official fix timeline has been provided. Monitor the Microsoft 365 Service Health dashboard for updates.
Tags: #outlook #error-fix #microsoft-365 #authentication #windows