Few tiny software failures feel as disruptive as opening an email you need immediately and getting a blunt refusal instead: “Your message can’t be displayed right now.” Outlook may still show the inbox, the subject line, and perhaps even a preview, yet the body of the message refuses to load. It is the digital equivalent of a quest-giver offering a mission and then vanishing before explaining what to do.

The encouraging part is that this error is often tied to cached data rather than lost mail. Outlook uses temporary local files and browser-stored website data to make mailboxes load more quickly. Usually that background system is useful. But stale, overloaded, or corrupted cache data can interfere with synchronization and prevent a message from rendering properly.

The usual remedy is to clear the relevant Outlook cache, then refresh or sign in again. This should not remove messages, contacts, calendar entries, or other content stored in the mailbox. Instead, Outlook is prompted to build fresh local copies and request current data again. The exact route depends on whether the problem occurs in the desktop application or Outlook on the web.

Before clearing anything: identify where the error happens

Start by separating the app problem from the browser problem. If the error appears in the Windows or macOS Outlook application, use the desktop instructions below. If it appears while visiting Outlook through Edge, Chrome, Firefox, Safari, or another browser, clear data for the Outlook site rather than immediately wiping every website’s history.

That distinction matters. Removing all browser cookies is the broadest possible reset, but it will sign you out of many unrelated services. Targeting Outlook’s own saved data is generally more convenient and makes troubleshooting less destructive. It is the same sensible approach used for plenty of account-based tools: reset the one misbehaving piece first, rather than performing a full-system respawn.

If you use multiple devices, also make a mental note of whether the troublesome email opens elsewhere. A message that works in Outlook on the web but fails in the desktop app points toward an app-side cache or synchronization issue. A message that fails in one browser but works in another suggests browser data or an extension may be the obstacle.

Fix the error in the Outlook desktop app

Windows: clear the RoamCache folder

On a Windows PC, fully close Outlook before deleting its cache files. Do not simply leave the main window minimized; make sure the program is no longer running. Then follow these steps:

  1. Press Windows + R to bring up the Run dialog.
  2. Enter %localappdata%MicrosoftOutlookRoamCache and press Enter.
  3. In the RoamCache folder, select the files inside it.
  4. Delete the selected files, either with the Delete key or the right-click menu.
  5. Open Outlook again and allow it time to reload mailbox information.

The important detail is that you are clearing temporary cached files, not deleting the mailbox itself. Once Outlook reconnects, it can retrieve up-to-date content again. Depending on the size of the mailbox and the connection, the first refresh after the reset may take longer than normal.

macOS: reset the affected account

On a Mac, the available route is an account reset within Outlook rather than manually browsing to the Windows-style RoamCache location. The process is straightforward:

  1. Open Outlook.
  2. Choose Tools from the top toolbar, then select Accounts.
  3. Pick the account experiencing the issue from the panel on the left.
  4. Select the three-dot menu.
  5. Choose Reset Account and confirm the choice.

Resetting the account makes Outlook rebuild its local view of that account. As with the Windows cache cleanup, the goal is to refresh local data rather than erase email, events, or people. Give Outlook a moment to complete the rebuild after confirming the reset.

If a desktop-cache reset does not solve the issue, reinstalling the Outlook app is a further option. That is a more substantial step, so it makes sense after trying the focused cache reset first.

Fix the error in Outlook on the web

For browser-based Outlook, cookies and site storage are the main suspects. These records help a site remember sessions and load quickly, but they can occasionally become the bad save file in an otherwise functional setup. Clear Outlook-specific data, reload the page, and sign in again.

Microsoft Edge: remove Outlook cookies and site data

People signed into Edge on several devices may want to avoid propagating the cleanup through browser syncing. In Edge, open the three-dot menu, choose Settings, go to Profiles, then Sync. Turn off the relevant sync options before the cleanup if the intent is to affect only the current device, and remember to turn them back on afterward.

To remove Outlook cookies in Edge:

  1. Open Outlook on the web.
  2. Select the lock icon in the address bar.
  3. Open Cookies and site data, then choose Cookies.
  4. Remove each Outlook-related cookie listed under Allowed.
  5. Refresh Outlook and sign in again.

If removing individual cookies does not work, Edge’s developer tools offer a deeper site reset. With Outlook open, press F12 and select the option to open DevTools if prompted. Use the plus icon to add or select the Application panel, choose Storage in the left-side menu, select the applicable options under Clear site data, and use Clear selected. Reload the page and authenticate again.

Google Chrome: hard reload first, then clear site storage

Chrome offers a quick cache-focused attempt before a fuller cleanup. While Outlook is open, press F12 to open Developer Tools. With that panel still visible, right-click the browser Refresh button near the address bar and choose Empty Cache and Hard Reload. This forces Chrome to fetch page resources again rather than leaning on its normal cached version.

If that does not solve the display issue, clear the saved Outlook data directly. Select the site-information icon at the left of the address bar, open Cookies and site data, then use Manage on-device site data. Delete Outlook entries with the trash-can controls, refresh the page, and sign in again.

Firefox: clear data from the page controls

Firefox keeps the route relatively compact. Navigate to Outlook on the web and select the shield icon to the left of the address bar. Choose Clear cookies and site data, confirm the clearing action, refresh the page, and log back in. This removes the site’s stored browser information while leaving other websites alone.

Safari: use Manage Website Data

Safari users can remove Outlook’s stored data from the browser settings:

  1. Choose Safari in the top menu bar, then select Settings.
  2. Open the Privacy section.
  3. Select Manage Website Data.
  4. Search for Outlook.
  5. Select its matching entries and choose Remove.
  6. Return to Outlook, refresh it, and sign in again.

Safari’s control may list more than one related entry, so check the search results carefully and remove the Outlook-related records before revisiting the site.

When cache clearing does not do the trick

If Outlook continues to show the error after a focused reset, browser extensions are the next practical thing to investigate. Ad blockers, privacy extensions, script blockers, and similar tools can sometimes interrupt elements that a web app needs in order to load message content. Temporarily disabling an extension or opening Outlook in another browser can help isolate that possibility.

A useful test is simple: if the same account works in a second browser, the mailbox itself is less likely to be the issue. The first browser’s stored data, settings, or installed extensions deserve attention. If the issue follows the account across browsers and the desktop app, it may be broader than a single local cache problem.

Browser and account housekeeping can feel unglamorous, but it is often the fastest route back to a working inbox. The same principle applies to other connected tools: keeping software current and knowing which local data can safely be refreshed prevents a minor glitch from becoming a full side quest. For another example of how connected-device features can depend on software support, see our coverage of Verizon and EE adding iOS 27 iPhone Handoff support.

For Outlook’s message-display problem specifically, begin with the smallest targeted reset: RoamCache on Windows, an account reset on macOS, or Outlook-only cookies and site data in a browser. Reload, sign in, and check the message again. In many cases, that is enough to get the inbox out of its error-state boss battle and back to displaying the mail that was there all along.