Fix Outlook IMAP Server Not Connecting
Why Outlook IMAP Server Not Connecting Happens
I've seen this exact scenario play out on dozens of machines: Outlook is pulling your mail just fine for months, then one morning it stops dead. No warning, no obvious change on your end. You get a spinning icon, a generic error dialog, or worse , complete silence. You remove the account, try to add it back, and now Outlook won't even handshake with the server. It's infuriating, especially when your inbox is your lifeline for work.
Here's the honest truth about why Outlook IMAP server not connecting problems happen: it's almost never one single cause. It's usually a collision of two or three things hitting at once. A Windows update silently changes a security policy. Your antivirus auto-updated and flipped on SSL scanning. A saved password in Windows Credential Manager went stale after a server-side password reset. Any one of these can break a connection that was working perfectly the day before.
The most common root causes I diagnose are:
- Stale or corrupted credentials stored in Windows Credential Manager , Outlook tries the old cached password, the server rejects it, and Outlook just gives up instead of prompting you again properly.
- Antivirus SSL/TLS inspection interfering with the encrypted IMAP connection on port 993. Products like Avast, Bitdefender, ESET, and even Windows Defender with network inspection features can silently intercept the TLS handshake and break it.
- Wrong server settings after reinstall, specifically port numbers, encryption method (SSL/TLS vs. STARTTLS), or the incoming server hostname typed with a small typo. IMAP on port 143 with STARTTLS and IMAP on port 993 with SSL/TLS are different configurations, and mixing them up causes immediate connection failure.
- A corrupted Outlook profile, the .ost file or the profile itself gets into a broken state, and even correct credentials can't establish a session.
- Firewall rules or ISP port blocking, some ISPs block outbound port 993 or 143 at the router level, particularly on business-grade connections after a firmware update.
- OAuth2 / modern authentication conflicts, if your mail provider switched to requiring OAuth2 (Google Workspace, for instance), Outlook's legacy basic authentication flow hits a wall.
Microsoft's error messages don't help much here. You'll see things like error 0x800CCC0E ("Cannot connect to the server"), 0x800CCC1A ("Your server does not support the connection encryption type you've specified"), or just "The connection to the server failed." None of these tell you what actually broke. That's what this guide is for.
The good news: the fix is almost always solvable without touching your mail provider's backend. 85–90% of Outlook IMAP connection issues I've seen are resolved by the first three steps below. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before running through the full diagnostic, try this one action. It clears the most common cause, stale cached credentials, in under two minutes.
Open Control Panel (search for it in the Start menu, not Settings, actual Control Panel). Go to User Accounts → Credential Manager → Windows Credentials. Look through the list for any entry that contains the name of your mail server, your email address, or the word "MicrosoftOffice". You'll likely find entries labeled something like MicrosoftOffice16_Data:your@email.com or your IMAP hostname directly.
Click the dropdown arrow on each of those entries, then click Remove. Remove every single one related to your email or Outlook. Don't worry, you won't lose your email data, you're just clearing the saved login tokens.
Now restart Outlook completely. When it tries to connect to your IMAP server, it will prompt you for your credentials fresh. Enter your current password (make sure it's the current one, if you recently changed it on the mail provider's side, that alone would explain everything). Check the box that says "Remember my credentials" and click OK.
Watch the bottom status bar in Outlook. If you see it cycle through "Connecting…" and then show the folder list or message count, you're done. The fix worked.
If Outlook still throws an error or the status bar just stays stuck on "Disconnected" or "Trying to connect…", don't panic. That means there's a second layer to the problem, either the server settings themselves are wrong, or something else on your machine is interfering with the connection. Work through the numbered steps below and you'll get there.
This sounds obvious, but I can't count how many times I've seen a single wrong port number or a mismatched encryption setting cause a complete connection failure. When Outlook IMAP settings are not working, the first thing to nail down is whether the server address, port, and encryption method are precisely correct.
In Outlook, go to File → Account Settings → Account Settings. Double-click your email account. Click More Settings in the bottom right. Navigate to the Advanced tab.
You need to verify:
- Incoming server (IMAP): This should be your provider's IMAP hostname (e.g.,
imap.gmail.com,outlook.office365.com,imap.mail.yahoo.com, or your custom domain's mail server) - Incoming server port: Should be 993 if using SSL/TLS, or 143 if using STARTTLS
- Encryption method: For port 993, set to SSL/TLS. For port 143, set to STARTTLS. Do NOT mix these, port 993 with STARTTLS will fail every time
Also check the Outgoing Server (SMTP) tab, a broken SMTP config can sometimes prevent Outlook from fully initializing the IMAP session too. SMTP should typically be port 587 with STARTTLS, or port 465 with SSL/TLS.
On the Outgoing Server tab, make sure "My outgoing server (SMTP) requires authentication" is checked and set to "Use same settings as my incoming mail server".
Click OK, then click Next and let Outlook run its test. If it completes both the incoming and outgoing tests with green checkmarks, your settings are correct and you can move to Step 2. If the incoming test fails with a red X and shows a timeout error, double-check the hostname spelling, a single extra character will cause an IMAP connection timeout error that looks identical to a network problem.
Even if you already tried the quick fix above, do this more thoroughly. Windows Credential Manager can hold multiple layers of credentials for the same account, some tied to Outlook directly, some to the Windows identity framework, and a partial clear doesn't always do the job.
Close Outlook completely first. Check Task Manager (Ctrl+Shift+Esc) to confirm no OUTLOOK.EXE process is running in the background.
Open Credential Manager: press Win+R, type control /name Microsoft.CredentialManager, and hit Enter. Click Windows Credentials.
Look for and remove all of the following if they appear:
- Any entry containing your email address
- Any entry containing your IMAP server hostname
- Entries starting with
MicrosoftOffice15_,MicrosoftOffice16_, orMicrosoftOffice17_ - Entries starting with
MS.Outlook. - Any entry with your mail provider's domain (e.g.,
gmail.com,yahoo.com)
If you use a work domain account, also look under Certificate-Based Credentials for any expired certificates tied to your mail server.
After removing all entries, also run this PowerShell command as Administrator to clear any persisted MAPI profile tokens that Credential Manager doesn't always show in the GUI:
cmdkey /list | ForEach-Object { if ($_ -match "Target: (.+)") { cmdkey /delete:$Matches[1] } }Note: this clears all stored credentials system-wide, so you'll need to re-enter passwords for other apps too. Skip it if that's inconvenient, it's a nuclear option that's only worth it if everything else is stuck.
Now relaunch Outlook and enter your credentials when prompted. If you've recently changed your mail password and are using app-specific passwords (required by Gmail, Yahoo, and others when 2FA is on), make sure you're entering the app password, not your regular account password.
This is the sneaky culprit that bites people hardest. Antivirus programs intercept encrypted connections by installing their own root certificate and acting as a man-in-the-middle on your TLS sessions. When they do this to an IMAP over SSL connection on port 993, Outlook sees a certificate that doesn't match the mail server's expected cert, and the connection fails. You'll often see Outlook IMAP certificate errors or get error 0x800CCC1A as a result.
The frustrating part: this often breaks suddenly because the antivirus auto-updated and either changed its SSL scanning behavior or the mail server updated its certificate chain in a way that the AV's proxy doesn't handle correctly.
How to disable it varies by product:
- Avast / AVG: Open Avast → Menu → Settings → Protection → Core Shields → Web Shield → uncheck "Enable HTTPS scanning"
- Bitdefender: Open Bitdefender → Protection → Online Threat Prevention → toggle off "Encrypted web scan"
- ESET NOD32/Smart Security: Open ESET → Setup → Internet protection → Web access protection → uncheck "Enable application protocol content filtering over SSL/TLS"
- Kaspersky: Settings → Security settings → Network settings → uncheck "Inject script into web traffic to interact with web pages"
- Norton 360: Settings → Firewall → Traffic Rules, look for any rule blocking port 993 or 143
After disabling the SSL scan setting, restart Outlook and test. If it connects immediately, you've found your culprit. You can either leave SSL scanning off (which is usually fine, your OS and Outlook handle the encryption themselves), or add your mail server's hostname to the AV's exclusion list so it stops intercepting that specific connection.
Also check Windows Defender Firewall. Press Win+R, type wf.msc, and check the Outbound Rules list for anything blocking OUTLOOK.EXE on ports 993 or 143.
When you removed and reinstalled the account, Outlook may have left behind a corrupted .ost file that's now interfering with the new account setup. The Outlook IMAP connection interrupted issue is sometimes caused not by a network problem at all, but by a broken local data store that Outlook can't sync into.
First, find your .ost file location. In Outlook, go to File → Account Settings → Account Settings → Data Files tab. Note the path shown, it's usually something like C:\Users\YourName\AppData\Local\Microsoft\Outlook\your@email.com.ost.
Close Outlook completely. Now find SCANPST.EXE, the Inbox Repair Tool. Its location depends on your Office version:
# Office 365 / Microsoft 365 (64-bit):
C:\Program Files\Microsoft Office\root\office16\SCANPST.EXE
# Office 2021 (32-bit):
C:\Program Files (x86)\Microsoft Office\root\office16\SCANPST.EXERun SCANPST.EXE. Click Browse and navigate to your .ost file. Click Start. If it finds errors, click Repair. This can take a few minutes on large mailboxes.
If SCANPST reports the file is too corrupted to repair, or if it repairs but Outlook still won't connect, delete the .ost file entirely. Don't worry, .ost files are local caches only. Your actual mail lives on the server. When you reopen Outlook, it will create a fresh .ost and re-sync everything from the IMAP server.
To delete it: with Outlook closed, navigate to the path you noted above and delete the .ost file. Then reopen Outlook. You should see it begin syncing fresh. This alone resolves a surprising number of Outlook cannot connect to incoming mail server errors after account reinstall.
If you've cleared credentials, confirmed server settings, disabled SSL scanning, and repaired the data file and it's still not working, the Outlook profile itself is corrupted. This is especially common when people remove and re-add the account multiple times trying to fix it, which can layer broken profile data on top of broken profile data.
The fix is creating a brand new Outlook profile. Here's how to do it without losing anything:
Close Outlook. Press Win+R and type control mlcfg32.cpl and hit Enter. This opens the Mail setup panel directly. Click Show Profiles.
Click Add to create a new profile. Give it a name like "Fresh Profile" or your name. Click OK. Outlook's account setup wizard will open, go through it manually, selecting "Manual setup or additional server types", then "POP or IMAP". Fill in your IMAP settings exactly as verified in Step 1.
Back in the Mail setup panel, change the setting at the bottom to "Always use this profile" and select your new profile name. Click OK.
Launch Outlook. It will open with the new clean profile. Enter your credentials when prompted. Watch the status bar, you should see it connect and begin downloading your folder list within 30–60 seconds.
If this works (and it usually does at this point), you can either keep using the new profile or, once you've confirmed everything is working, go back to the Mail setup panel and delete the old broken profile to clean things up. Your old profile's .ost file remains on disk if you ever need to extract anything from it, but the new sync from the server will have everything current.
Advanced Troubleshooting
If you've worked through all five steps and the Outlook IMAP server not connecting issue persists, it's time to dig deeper. These are the scenarios I see in enterprise environments, domain-joined machines, and cases where something at the network or policy level is overriding what you configure in Outlook's GUI.
Check Event Viewer for Exact Error Codes
Press Win+R, type eventvwr.msc, and navigate to Windows Logs → Application. Filter by Source = "Outlook" or look for Error-level events in the time window when Outlook fails to connect. You're looking for event IDs in the 4000–4999 range. An entry with event ID 4608 or a description mentioning "SSL negotiation failed" or "certificate validation failed" points to the antivirus SSL issue from Step 3. A message about "authentication failure" with error code 0x800CCC90 means the server is rejecting your credentials specifically, likely an app password issue.
Test Raw IMAP Connectivity with PowerShell
This bypasses Outlook entirely and tells you whether the connection problem is Outlook-specific or network-level:
Test-NetConnection -ComputerName imap.yourmailserver.com -Port 993Replace imap.yourmailserver.com with your actual IMAP hostname. If TcpTestSucceeded : False comes back, the port is blocked at your firewall, router, or ISP level, Outlook isn't the problem at all. Check your router's firewall settings and, if you're on a corporate network, contact your network admin about outbound port 993 being blocked.
Group Policy and Registry Checks (Domain-Joined Machines)
On machines joined to a company Active Directory domain, Group Policy can force specific security settings that prevent Outlook IMAP authentication. Run gpresult /h C:\gpresult.html in an elevated Command Prompt and open the HTML report. Look under Computer Configuration → Windows Settings → Security Settings for any TLS version restrictions. If the domain policy forces TLS 1.3 only and your mail server's IMAP implementation hasn't been updated to support TLS 1.3, every connection will fail silently.
You can also check the registry directly:
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\ProtocolsIf you see subkeys for TLS 1.0 or TLS 1.1 with a DisabledByDefault DWORD value of 1 and an Enabled DWORD of 0, and your mail server only supports those older protocols, that's your conflict. The right fix is getting your mail server updated, not re-enabling legacy TLS on the client.
OAuth2 / Modern Authentication
If you're connecting to Gmail, Google Workspace, Yahoo Mail, or Microsoft 365, check whether your provider has disabled basic authentication (username + password) in favor of OAuth2. Google completed their basic auth deprecation for personal Gmail accounts in 2024. If Outlook is using basic auth to connect to a server that no longer accepts it, you'll get authentication rejected errors that look like a settings problem but are actually a protocol mismatch. The fix is ensuring Outlook is set to use Modern Authentication, in the account setup, look for an option to sign in via browser-based OAuth flow rather than entering credentials directly in the Outlook dialog.
gpresult ready, it'll save significant time on the call.
Prevention & Best Practices
Once you've got your Outlook IMAP connection working again, a few habits will keep it that way. Most of the "it just broke overnight" incidents I've seen are entirely preventable.
First, set up app-specific passwords now if your mail provider supports them, and use one exclusively for Outlook. Gmail, Yahoo, Apple Mail, and Fastmail all offer app passwords. When you change your main account password (which you should do periodically), your Outlook app password stays valid until you explicitly revoke it. No more broken connections after a password reset.
Second, keep a note of your exact IMAP settings somewhere outside of Outlook, a text file, a password manager note, anything. When you have to remove and re-add the account, you want the exact hostname, port, and encryption method in front of you. Not having to guess or look it up prevents half the reinstall errors.
Third, be deliberate about antivirus updates. Don't let your AV update silently in the background without checking whether it changed SSL scanning behavior. After any major AV update, do a quick test, send yourself an email and confirm Outlook receives it within a couple of minutes.
Fourth, if you're on Windows 11 and using Microsoft 365, keep Outlook updated through File → Office Account → Update Options → Update Now. Outdated Outlook builds have known IMAP authentication bugs that were fixed in later releases. Running a 2-year-old build is a common cause of Outlook IMAP authentication failed errors that look mysterious until you check the version number.
- Create an app-specific password for Outlook at your mail provider's security settings page, insulates you from future password changes breaking the connection
- Store your IMAP server settings (hostname, port, encryption type) in your password manager alongside your credentials so reinstalls take 60 seconds instead of 20 minutes
- Add your IMAP server hostname to your antivirus's SSL scanning exclusion list so AV updates can't silently break the connection again
- Run
Test-NetConnection -ComputerName [your imap server] -Port 993as a quick sanity check any time Outlook stops connecting, rules out network issues in 5 seconds flat
Frequently Asked Questions
Why does Outlook say "Cannot connect to the server" with error 0x800CCC0E?
Error 0x800CCC0E is a socket connection error, it means Outlook couldn't even establish a TCP connection to your IMAP server. The most likely causes are a wrong hostname, the wrong port number, a firewall or antivirus blocking the outbound connection, or your ISP blocking port 993. Run Test-NetConnection -ComputerName [your imap server] -Port 993 in PowerShell to check whether the port is actually reachable from your machine. If that test fails, the problem is network-level, not Outlook-level.
I deleted the account and now Outlook keeps asking for my password but never actually connects, what's going on?
This is almost always stale credentials stuck in Windows Credential Manager. Outlook tries the old cached password, the server rejects it, and instead of clearing the cache and asking you for a fresh password, Outlook just loops. Go to Control Panel → Credential Manager → Windows Credentials and remove every entry associated with your email address or mail server. Then restart Outlook and enter your credentials fresh when prompted. Make sure you're using your current password, or an app-specific password if your provider requires it.
My IMAP was working fine and stopped after a Windows Update, how do I fix it?
Windows Updates, particularly cumulative security updates, occasionally tighten TLS settings or change how the SCHANNEL provider handles certificate validation. First, check whether your antivirus updated around the same time, that's usually the actual cause. If it's genuinely the Windows Update, check Event Viewer (Windows Logs → Application) for SSL or certificate error events from Outlook. You can also temporarily disable your VPN if you're using one, some updates reset VPN split-tunneling rules that were allowing IMAP traffic through. In most cases, clearing credentials and rebuilding the Outlook profile resolves post-update IMAP failures.
Does it matter whether I use IMAP port 993 or 143 in Outlook?
Yes, significantly, and the port and encryption type must match each other, not just be in the right neighborhood. Port 993 uses implicit SSL/TLS, meaning the encrypted connection is established before any IMAP communication happens. Port 143 uses STARTTLS, which starts as a plaintext connection and then upgrades to encrypted. If you put port 993 with STARTTLS, or port 143 with SSL/TLS, the handshake will fail immediately. Always use 993 + SSL/TLS together, or 143 + STARTTLS together. When in doubt, 993 with SSL/TLS is the modern standard and what most providers recommend.
Can I use Outlook to connect to Gmail IMAP or has Google blocked that?
You can still use Outlook with Gmail IMAP, but the setup requirements changed in 2024. Google no longer allows basic authentication (username + plain password) for Gmail through third-party clients. You need to either enable OAuth2 sign-in in Outlook (which opens a browser window to authenticate via Google's own login page) or generate a Gmail App Password under your Google Account → Security → App passwords, and use that app password in Outlook's password field instead of your regular Gmail password. Also make sure IMAP is enabled in Gmail Settings → See all settings → Forwarding and POP/IMAP.
Is there a way to test whether my IMAP server connection is working without using Outlook?
Yes, and it's a useful diagnostic step. In PowerShell, run Test-NetConnection -ComputerName imap.yourserver.com -Port 993 to check TCP connectivity. For a deeper test that actually initiates an IMAP session, you can use the free tool Thunderbird as a quick test client, if Thunderbird connects successfully with the same settings, the problem is specific to Outlook (profile, credentials, or installation) rather than network-level. Microsoft also offers the Remote Connectivity Analyzer at testconnectivity.microsoft.com for Exchange/Microsoft 365 accounts specifically.