How to Get Outlook Mail or Hotmail in Windows Live Mail

If you’re here because you miss the glorious simplicity of Windows Live Mail (WLM)one inbox, one button, zero “AI-powered
synergy dashboards”I get it. Windows Live Mail was like a diner booth: not fancy, but it always had coffee and never asked you
to “re-authenticate” while you’re trying to forward Aunt Linda’s casserole recipe.

Unfortunately, email security has changed a lot since WLM’s heyday. And Microsoft has changed even more. In 2024, Microsoft
finished turning off the old “just send a username and password” login method (Basic Authentication) for Outlook.com accounts.
Windows Live Mail doesn’t speak the modern login language (OAuth2/Modern Authentication), so it usually can’t connect anymore.

This article gives you:

• A clear explanation of what changed (and why WLM struggles).
• What still works (spoiler: mostly migration, forwarding, and modern clients).
• Legacy settings and setup steps (useful for archival/testing, or if you’re in a rare edge case).
• A practical plan to move without losing years of old mail.

The uncomfortable truth: Windows Live Mail is retired

Windows Live Mail was part of “Windows Essentials,” a suite Microsoft stopped supporting years ago. That means no security
updates, no fixes, and no official compatibility promises when the world (and authentication standards) moved on.

What changed: Basic Auth vs. Modern Auth (OAuth2) in plain English

Think of Basic Authentication like giving a valet your house key and hoping for the best. It’s simple, but if that key is copied,
you’re done. Modern Authentication (OAuth2) is more like giving the valet a temporary parking pass that only works for one garage,
for a limited time, and can be revoked instantly.

Microsoft now requires Modern Authentication for connecting third-party email apps to Outlook.com accounts. Many modern clients
(Outlook, Thunderbird, Apple Mail, etc.) can pop open a secure sign-in window and complete OAuth2. Windows Live Mail can’t.

Best options in 2026 (that don’t fight Microsoft’s security rules)

Option 1: Use Outlook (desktop or mobile) and keep life simple

If you want the “officially supported” route, Microsoft wants you on Outlook. It supports Modern Authentication automatically,
and it’ll keep working as Microsoft changes the backend.

• Pros: Most compatible; best calendar/contacts integration; least troubleshooting.
• Cons: Different interface from WLM; can feel heavier.

Option 2: Use Mozilla Thunderbird (free) with OAuth2

Thunderbird is a popular “power user but not complicated” alternative that supports OAuth2 for Microsoft accounts. That means it
can sign in the modern way WLM can’t.

• Pros: Free; supports OAuth2; flexible; solid import/export options.
• Cons: Not as “Windows-native” as WLM felt; takes a few minutes to learn.

Option 3: Use the web (Outlook.com) and stop installing problems

If you just need access and don’t care about a desktop client: the browser is the zero-drama option. No ports, no SSL settings,
no mysterious 0x800-something error codes that look like a robot’s social security number.

Option 4: Keep WLM for your old mail archive, but use a modern client for new mail

This is the “I’m not ready to say goodbye” compromise. Many people keep WLM installed purely to search old messages stored locally,
while new mail lives in a modern client that can actually authenticate.

If you insist on trying Windows Live Mail anyway (legacy setup guide)

This section is for:

• People restoring old systems for archival purposes.
• Curiosity (no judgmenttech nostalgia is real).
• Rare scenarios where a mailbox still allows legacy access (uncommon for Outlook.com/Hotmail).

Important: Even with perfect settings, sign-in may fail because Windows Live Mail can’t do OAuth2.

Step-by-step: Add Outlook.com/Hotmail to Windows Live Mail

1. Open Windows Live Mail.
2. Go to the Accounts tab.
3. Click Email.
4. Enter your email address and password (or app password if you’re testing and your account still allows it).
5. Check Manually configure server settings.
6. Click Next.

Recommended server settings (current Microsoft guidance)

Microsoft’s published settings for Outlook.com typically look like this:

IMAP (recommended over POP for most people)

• Incoming (IMAP) server: outlook.office365.com
• Port: 993
• Encryption: SSL/TLS
• Username: your full email address ([email protected])

POP (only if you want download-only behavior)

• Incoming (POP) server: outlook.office365.com
• Port: 995
• Encryption: SSL/TLS
• Username: your full email address

SMTP (sending mail)

• Outgoing (SMTP) server: smtp-mail.outlook.com
• Port: 587
• Encryption: STARTTLS
• Requires authentication: Yes (use same credentials as incoming)

You may also see older guides referencing servers like imap-mail.outlook.com or pop-mail.outlook.com.
Those were common in past configurations. The bigger issue today, however, is authentication: if the client can’t do OAuth2,
it may fail regardless of which server name you type.

Enable POP or IMAP in Outlook.com settings

Outlook.com may require you to explicitly enable POP or IMAP access in its web settings. In Outlook.com:

1. Open Settings (gear icon).
2. Go to Mail settings related to forwarding and IMAP/POP.
3. Toggle “Let devices and apps use IMAP” or “Let devices and apps use POP” to ON.
4. Save.

Common failure symptoms (and what they usually mean)

• Endless password prompts: typically a sign the app is using Basic Auth and the server is refusing it.
• “Authentication failed” or “server rejected your login”: often OAuth2 is required; WLM can’t comply.
• You can receive but not send: SMTP authentication checkbox off, wrong port, or encryption mismatch.
• SSL/TLS errors: older OS certificate stores can break modern TLS handshakes.

Workarounds that keep Windows Live Mail in the picture

Workaround 1: Forward Outlook.com mail to another inbox WLM can access

If you have another mailbox hosted somewhere that still allows legacy IMAP/POP (for example, a private domain mailbox on a server
you control), you can forward Outlook.com mail there. Then WLM checks the forwarded mailbox.

Downsides: replies won’t automatically come “from” your Outlook.com address unless you send via Outlook.com or a modern client.
Also, many major providers are also moving away from basic password loginsso choose this path carefully.

Workaround 2: Use WLM as a local archive viewer

This is the most realistic way to keep WLM useful:

• Keep all your old mail in WLM for searching and reading.
• Use Outlook, Thunderbird, or the web for current mail.

How to migrate off Windows Live Mail without losing email

Migration sounds scary until you realize your email isn’t trapped in a mystical vaultWLM stores messages as files, and modern
clients can import them.

Step 1: Back up your Windows Live Mail message store

Before touching anything: make a backup copy of your Windows Live Mail folder. On many systems, it’s under your user profile’s
AppData area (a hidden folder). Copy the entire “Windows Live Mail” folder to an external drive or a safe location.

Step 2: Export messages (the “official-feeling” method)

1. In WLM, go to File (or the menu button).
2. Choose Export email → Email messages.
3. Choose a format/location and export.

Step 3: Import into a modern client

Two popular landing zones:

• Thunderbird: great for importing folders of .EML files and then connecting to Outlook.com with OAuth2.
• Outlook: ideal if you want the most seamless Microsoft ecosystem experience (mail, calendar, contacts).

Step 4: Verify, then retire WLM (or keep it as a museum piece)

Once you can read the old mail and your Outlook.com mailbox works in the new app, you’re done. Keep the backup anyway. Storage is
cheap. Regret is expensive.

Security note: beware “free Windows Live Mail downloads”

Since Windows Essentials is no longer supported or available as an official download in the usual way, random sites offering “free
installers” can be risky. If you’re running WLM today, treat it like an old car without airbags: it can still drive, but don’t
pretend it’s safe in modern traffic.

Conclusion

Getting Outlook.com or Hotmail into Windows Live Mail used to be a simple “enter IMAP and SMTP settings” task. Today, the bigger
story is authentication: Microsoft requires Modern Authentication (OAuth2), and Windows Live Mail doesn’t support it. That’s why
direct syncing generally fails.

The smartest move is to switch to a modern client (Outlook or Thunderbird) and migrate your old WLM messages so you keep your
history. If you’re determined to keep WLM involved, use it as a local archive viewer and let a supported app handle the living,
breathing inbox.

Real-World Experiences (and Lessons Learned) from People Trying to “Make WLM Work”

If you’ve ever tried resurrecting Windows Live Mail for Outlook.com in the modern era, you’ve probably met the same three
characters everyone meets: the Endless Password Prompt, the Mysterious Server Error, and the Friend Who Says “It Works on My
Computer” (which is never as comforting as they think it is).

One common pattern: users assume the server settings are wrong because WLM keeps rejecting the password. So they try a different
server name, then another, then a third, and eventually they’re googling “imap-mail outlook office365 what is reality” at 2 a.m.
The truth is that the server name is often the least important part. When a provider requires OAuth2, typing the correct password
into an app that can’t perform modern sign-in is like giving the right answer to the wrong question. WLM is asking, “Is this the
right password?” Microsoft is responding, “Cool storyplease open a secure login window and prove it’s really you.”

Another frequent detour is the “app password” rabbit hole. People hear that an app password can help older apps, so they set up
two-factor authentication, generate an app password, and paste that into WLM. Sometimes, in the past, this worked as a bridge.
But after Microsoft’s shift away from Basic Authentication, many users report that app passwords don’t rescue truly legacy clients
anymore. The reason is simple: an app password still behaves like a password. If the system is refusing password-only sign-ins,
a fancier password doesn’t change the rules of the game.

Then there’s the “it receives but won’t send” chapter. In older configurations, SMTP failures were often caused by missing the
“requires authentication” checkbox, using port 25 (which many networks block), or mismatching encryption settings. People would
proudly announce, “I fixed it!” after switching to port 587 with STARTTLSuntil the next day, when the login prompts returned,
because authentication was the real blocker all along.

The most successful real-world strategy tends to be the least dramatic: accept that WLM is now best as an archive viewer.
Users who export their WLM messages, import them into a modern client, and then connect Outlook.com via OAuth2 usually report a
huge drop in daily frustration. They still get the comfort of searching years of old mail (“Where is that invoice from 2018?”),
but they stop wrestling with an authentication system that WLM was never built to understand.

Finally, a practical tip that shows up repeatedly in support threads: if you’re migrating, don’t do it “live” without a backup.
People who copy the full Windows Live Mail store folder first can experiment fearlessly. People who don’t… learn the meaning of
the phrase “irreversible life lesson” when a folder goes missing. Back up first, migrate second, celebrate third.