Status on September 4, 2026: Microsoft officially lists this issue as FIXED (support page updated February 3, 2026) — the fix ships through Windows Update. If classic Outlook still hangs, freezes, or will not reopen on your PC, you are either missing the fix update or carrying leftover PST damage. Both are recoverable, step by step, below.

On January 13, 2026, Patch Tuesday arrived — and for a large group of users, classic Outlook for Windows never truly worked again that day. It would hang mid-launch, freeze while checking mail, refuse to close (lingering invisibly in Task Manager), or never reopen at all. The common thread: POP email accounts and PST data files, especially PSTs stored inside OneDrive folders.

The internet's first reaction was blunt: "uninstall KB5074109." That was January's answer. Today's answer is better: Microsoft has fixed the underlying bug, and the real job for most affected PCs is running the recovery ladder — updating properly, repairing the mail data the hang left behind, and undoing the OneDrive setup that turned a Windows bug into a frozen inbox. This guide walks all of it, safely, in order.

Quick Answer

KB5074109 (January 13, 2026) made classic Outlook hang or fail to reopen for POP/PST profiles — Microsoft has fixed it via Windows Update. Recovery order: (1) run Windows Update until "You're up to date," restarting as asked. (2) If Outlook won't close, end OUTLOOK.EXE in Task Manager and restart the PC. (3) Folder errors or missing mail → back up the PST, then run the built-in ScanPST repair tool. (4) Move active PSTs out of OneDrive-synced folders. (5) Still broken → new Outlook profile, then Office Quick/Online Repair. Uninstalling the KB is now a last-resort edge case, not the plan.

Key Takeaways

  • The bug is officially fixed — the fix arrives through Windows Update, not a separate download.
  • Victims shared one profile type: classic Outlook + POP accounts or PST files, worst when the PST lived in a OneDrive folder.
  • Root cause: the update changed how Windows handles locked files, and OneDrive's sync lock could deadlock Outlook's PST writes — a waiting game with no winner.
  • Exchange and Microsoft 365 accounts were not affected — the break was in the POP/PST local-storage path.
  • "Uninstall KB5074109" is outdated advice for 2026: it reopens 100+ patched security holes to solve a problem an update now solves.
  • If the hang damaged your mail data, the free built-in ScanPST tool repairs it — never a "PST repair" download from an ad.

What actually broke — in plain words

Classic Outlook stores POP mail in a .pst file — one file holding your entire mailbox. Windows Update KB5074109 changed how Windows treats files that are locked by another process. When your PST sits in a folder OneDrive syncs, there are suddenly two giants claiming the same file: Outlook writing mail, OneDrive locking it to upload it. After the update, that standoff could become permanent — Outlook waiting forever for a file lock that never releases. Result: a frozen window, a process that will not die, and an inbox that exists but cannot open.

That is also why the damage was so selective:

Your setup Was it hit?
Classic Outlook, POP account, PST in OneDrive folder 🔴 Hardest hit — hangs, fails to close or reopen
Classic Outlook, POP/PST stored locally 🟠 Often affected, usually milder
Classic Outlook, Exchange / Microsoft 365 account 🟢 Not affected — different code path
New Outlook for Windows / Outlook on the web 🟢 Not affected — different app entirely

If your Outlook trouble started after a different kind of update mess — monthly updates failing with error codes — that is a separate documented issue with its own guide: Windows Update error 0x80073712: 6 real fixes.

The recovery ladder — run it in order

1. Get the fix: update until Windows is truly done

The repair ships inside normal cumulative updates. Open Settings > Windows Update, click Check for updates, install everything, restart when asked, then check again — repeat until the page literally says "You're up to date." One pass is often not enough; the fix may arrive as a second wave after the first restart. If the update itself stalls, see Windows 11 update stuck at 0%, 99%, or 100%.

2. If Outlook won't close or reopen — end the ghost

A hung Outlook often leaves an invisible OUTLOOK.EXE running, and every new launch quietly fails because of it. Open Task Manager (right-click the taskbar), find Outlook under Details if needed, and End task. Command-line alternative: taskkill /f /im outlook.exe. Then restart the PC after step 1's updates are in, and launch Outlook fresh.

3. Folder errors or missing mail → repair the PST (free, built-in)

The deadlock could leave the PST slightly damaged. First: copy the PST file somewhere safe (find it via File > Account Settings > Data Files > Open File Location). Then run Microsoft's own inbox repair tool, ScanPST (Scanpst.exe lives inside your Office program folder — search Windows for it by name). Point it at the PST, check "Make backup of scanned file before repairing", and let it run — it can take a while on large mailboxes and may need multiple passes until it reports zero errors. Never delete a PST to "fix" Outlook — that is deleting your mail.

4. Move active PSTs out of OneDrive — permanently

This is the habit that turned a Windows bug into a frozen inbox. Pause OneDrive sync (OneDrive icon → Pause syncing), then move the PST to a purely local folder — for example C:\Mail\ — and reattach it in Outlook via File > Account Settings > Data Files. Keep backups of that folder on a schedule if you like, but an actively syncing PST is a known fragility even outside this bug. Microsoft's own guidance for this incident says the same.

5. Still misbehaving → build a fresh Outlook profile

Profiles accumulate damage of their own. Close Outlook, open Control Panel > Mail (Microsoft Outlook) > Show Profiles > Add, name it, and set up your account again (point it at your repaired/local PST when asked). A clean profile on a patched Windows has fixed a remarkable share of "Outlook is weird" cases forever.

6. Repair Office itself — Quick, then Online

If Outlook still misfires, the Office installation may be bruised. Settings > Apps > Installed apps > Microsoft 365 > Modify — run Quick Repair first (fast, local); if symptoms survive, run Online Repair (slower, reinstall-in-place, keeps your mail and settings).

7. The January answer, demoted: uninstall KB5074109

Only for the rare PC that cannot take updates right now (for example, offline, or blocked by a separate update failure). Settings > Windows Update > Update history > Uninstall updates → pick KB5074109 → restart; command-line form: wusa /uninstall /kb:5074109. Then pause updates for one week — not forever — and re-enable so the real fix and its 100+ security patches come back. Staying unpatched to keep email working is borrowing tomorrow's breach for today's convenience.

Match your symptom to your next move

What you see Do this
Outlook hangs after the January 2026 update Step 1 (update fully) → Step 2 (kill ghost process)
Outlook will not reopen after closing Step 2, then Step 1, then Step 5 if needed
"Cannot open" errors on folders, missing local mail Step 3 — ScanPST on a backed-up PST
Works only in Outlook Safe Mode Disable add-ins one at a time (File → Options → Add-ins)
Send/receive broken even after patching Step 5 — new profile
Everything above failed Step 6 — Online Repair; then our Installation Assistant vs Windows Update guide if Windows itself needs servicing

Do this, never that

✅ Safe and effective ❌ Breaks things further
Back up the PST before any repair touches it Deleting the PST / creating a new one "from scratch" (deletes mail)
Use built-in ScanPST for folder errors Downloading "PST repair tools" from ads — that is scareware's favorite costume
Keep the active PST in a local folder Leaving the live PST inside a OneDrive-synced folder
Uninstall the KB only as a last resort, updates paused briefly Staying unpatched for months to keep Outlook alive
New profile + Office repair on a patched system Registry edits and "Outlook fixer" EXEs from search ads

One sitting, in order — stop as soon as Outlook behaves:

  1. Windows Update until "You're up to date" + restarts (Step 1).
  2. Kill any ghost OUTLOOK.EXE, relaunch (Step 2).
  3. Folder errors → back up PST → ScanPST (Step 3).
  4. PST out of OneDrive into C:\Mail\ (Step 4).
  5. New profile (Step 5) → Office repair (Step 6).
  6. Edge cases only: uninstall KB + pause updates one week (Step 7).

Frequently asked questions

Is the KB5074109 Outlook bug fixed?

Yes. Microsoft's support page lists it as fixed (status updated February 3, 2026), with the repair delivered through Windows Update. Run updates until "You're up to date" and restart — that is how the fix reaches you.

Did KB5074109 break Outlook for everyone?

No. It hit classic Outlook profiles using POP accounts or PST files — hardest when the PST was stored in a OneDrive folder. Exchange/Microsoft 365 accounts, new Outlook, and Outlook on the web were not affected.

Why did OneDrive make it worse?

OneDrive locks files while syncing them. The update changed how Windows handles locked files, so Outlook could end up waiting forever for its own PST while OneDrive held the lock — a deadlock between two Microsoft processes over one file.

Should I uninstall KB5074109 today?

Almost certainly not. That was January's workaround; the proper fix now arrives through Windows Update, and uninstalling re-exposes over 100 security vulnerabilities the patch closed. Reserve it for rare edge cases — and even then, pause updates for a week, not forever.

My folders error out or mail went missing. Is my data gone?

Very likely not — the PST is probably damaged, not emptied. Copy it somewhere safe, then run the built-in ScanPST tool repeatedly until it reports zero errors. Do not delete the file or let any "repair tool" from an ad touch it.

Is it safe to keep my PST in OneDrive after this?

For an active, constantly-written PST — no. Keep the live file in a local folder and back it up on a schedule instead. This is the same guidance Microsoft gave during the incident, and it protects you from the next sync conflict too.

Outlook still won't close properly even now. What next?

End OUTLOOK.EXE in Task Manager, confirm Windows is fully updated, then work the ladder: ScanPST, PST out of OneDrive, new profile, Office Online Repair. In the vast majority of documented cases the freeze disappears somewhere along that list.

The bottom line

The January 2026 Outlook freeze was a perfect storm: a security patch, a mail format that lives in one file, and a sync engine that locks it. Microsoft has since fixed the Windows side — your side of the recovery is updating fully, repairing the PST if the deadlock bruised it, and moving the live file out of OneDrive so the storm can't reform. Work the ladder in order, stop when Outlook behaves, and treat any advertised one-click "Outlook repair" as the actual malware. More fixes for Windows' rough edges live in All Guides — updated with every new guide. And if a window ever screams that your mail is "corrupted" unless you call a number, that is the fake-popup pattern: how to remove fake virus pop-ups.

Sources

  1. Microsoft Support, "Classic Outlook profiles with POP accounts and PSTs hang after Windows updates on January 13, 2026" — STATUS: FIXED, updated February 3, 2026. support.microsoft.com
  2. iTechGuides, "Windows 11's January 2026 update caused Outlook problems — but Microsoft says it's fixed," August 2026. iTechGuides
  3. WinBuzzer, "Windows 11 update issues force user choice: Outlook email access or system security," January 2026. WinBuzzer
  4. Microsoft Q&A, "Outlook issue since 1/14/26 update" — community-verified uninstall steps and the Windows 10 equivalent (KB5078129). learn.microsoft.com
  5. WindowsForum, "KB5074109 Outlook hang after January 2026 Patch Tuesday" — recovery checklist and PST/OneDrive mitigation. windowsforum.com

Article notes

First published. Fix status verified against Microsoft's support page (STATUS: FIXED, February 3, 2026) and current reporting; recovery ladder ordered safest-first for patched and unpatched PCs.