Post-update errors have their own logic. Half-applied updates and mismatched app builds cause most of them — finish the updates properly before repairing anything else.
It worked yesterday, an update ran overnight, and this morning Outlook greets you with Cannot display the folder. The temptation is to undo everything. Resist it. Post-update errors follow a pattern, and the first moves are about completing the update, not reversing it.
When an error's birthday is an update, the most common real cause is not the update itself — it is an update half applied. Your Outlooks update through three separate doors, so check all three:
A new Outlook from this month sharing a data file with a classic Outlook from last season is exactly the mixed-build setup where the olk.exe conflict breeds.
Updates to either app replace files that a running process may still be holding in its old form. One full Restart after everything is installed puts both apps, their services and the data file locks into a single clean state. Test the folder again before changing anything else — a surprising number of post-update errors are finished at exactly this point.
Sometimes the update genuinely ships a bug — it happens to every large product, and Microsoft handles it in the open: it maintains fixes or workarounds for recent issues in the new Outlook for Windows pages listing known problems and their workarounds. If your error matches a listed issue, the honest move is to apply the listed workaround or wait for the fix build, not to keep rebuilding your PC around a bug that is not yours.
An interrupted Store update can leave the new Outlook half-installed. That is precisely what Repair exists for: Settings → Apps → Installed apps → Outlook (new) → Advanced options → Repair, which restores the app's files without deleting its data. For classic Outlook, the equivalent is the Microsoft 365 repair from the same Installed apps list. Reset only if Repair changes nothing.
Store apps do not offer a roll back to last version button, and pretending otherwise wastes your day. If a fresh bug is blocking your work, the professional bridge is simple: work in the other app — classic Outlook remains fully usable — send the error through the new app's Help → Support or Feedback so the report reaches the team, and let the next build close the issue. Your mail is never trapped; it lives on the server and both apps read the same mailbox.
The video shows the conflict fix that solves the everyday version of this error — this page adds the update-day routine around it.
▶️ Watch Full VideoAlmost never. What updates usually change is the app build, which exposes the sharing conflict or leaves the app half-installed. Your data file is normally untouched — which is why the fixes here target apps and locks, not the file.
Windows Store apps do not provide a version rollback. Repair the app, use classic Outlook as a bridge, and let the next Store build carry the fix.
Microsoft publishes fixes-or-workarounds pages for recent issues in the new Outlook. If your exact error is listed there with a workaround, follow that — it comes from the team that owns the bug.