Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened: causes and fixes

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Classic Outlook for Windows shows "Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened." followed by a last sentence, and that last sentence tells you which fault you have. "The attempt to log on to Microsoft Exchange has failed." can point to a service-side limit that Microsoft documents as a known issue; the Fiddler trace below confirms it. "There is not enough memory available to perform the operation." points to a mailbox property in cached mode. If the message names neither, the Inbox Repair situation below is the remaining case covered here.

Read the last sentence of your message first, then run the read-only checks below. Nothing before the Fix section changes a mailbox, a profile or a file.

What the error means

The first three sentences are the same in every case: Outlook could not open the folder structure of the profile it was told to load. Microsoft's pages describe different reasons behind that single message, and its known-issue page says so plainly: "This error message can occur for different reasons."

Microsoft documents these situations:

  • Exchange Online sign-in limit. The known-issue page for Outlook for Microsoft 365 (last updated 20 October 2025) lists the full message as "Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed." and says that recent support cases were for user mailboxes. The status on the page is "FIXED", and it adds that the service team is monitoring to confirm the issue is addressed.
  • Cached mode and a mailbox property over 32 KB. Microsoft's cached-mode page covers the message that ends "There is not enough memory available to perform the operation." It applies to Outlook 2019, 2016, 2013 and 2010. The cause it gives: the hidden PR_OST_OSTID property in the mailbox grows by about 20 bytes every time a new cached mode profile is created for that mailbox, and the error starts when the data passes about 32,720 bytes.
  • The Inbox Repair situation. Microsoft's page on the Inbox Repair tool lists "You receive a message that Outlook can't open the set of folders" among the situations in which to use the tool.

No page under Sources gives another cause for this message. None gives figures for how many cases fall under each situation, so the list below is in no order of likelihood.

Likely causes

Cause What you see How to confirm
Exchange Online authentication concurrency limit The message ends "The attempt to log on to Microsoft Exchange has failed." Microsoft names Outlook on the web as a workaround A Fiddler trace taken while you reproduce the problem contains ClientBackoffException and "Authentication concurrency limit is reached."
Mailbox property PR_OST_OSTID larger than 32 KB The message ends "There is not enough memory available to perform the operation." It also appears when you create a new cached mode profile The mailbox is shared by many users, is a shared resource mailbox with Download shared folders on, or has had many cached mode profiles created
Inbox Repair situation (.pst or .ost data file) The message names no server or memory problem; the profile uses a local data file The Inbox Repair tool reports errors in the file
A different fault with the same first sentence Neither of the endings above No page under Sources gives a further cause

Prove the cause before changing anything

All of these are read-only.

  1. Write down the exact ending of the message. The two endings above separate the first two causes.
  2. Open the mailbox in Outlook on the web. Microsoft's known-issue page lists Outlook on the web (OWA) as a workaround, so trying the mailbox there is a useful comparison. The page does not say what you will see.
  3. For the Exchange Online limit, Microsoft says to confirm by capturing a Fiddler trace while you reproduce the problem and searching it for these lines:
Microsoft.Exchange.RpcClientAccess.ServerTooBusyException: Client is being backed off
---> Microsoft.Exchange.RpcClientAccess.ClientBackoffException: ErrorCode: ClientBackoff, LID: 49586 - Authentication concurrency limit is reached.
  1. For the data file, find out which files the profile uses. Close Outlook, open Mail in Control Panel, select Show Profiles, select the profile, then Properties, then Data Files; that route is on Microsoft's 0x8004010F page. Microsoft's Inbox Repair page gives File > Account Settings > Account Settings > Data Files for a running Outlook; the Data Files tab lists every .pst and .ost file with its account. Note each file's name and folder.

Example (illustrative): at contoso.com.au a shared mailbox support@contoso.com.au is used by eleven staff on rds01. On Monday three of them get the message ending "There is not enough memory available to perform the operation." and the same message appears when IT builds a new profile on app01. That matches the cached mode page, which lists many users opening a shared resource mailbox with Download shared folders enabled. The mailbox can be reached in Outlook on the web.

Fix

Cause 1: Exchange Online authentication concurrency limit

Microsoft's page says: "If you experience this issue, the only way to address it is to open a support case from the Microsoft 365 Admin portal. Exchange Online support will need to request a change from the service to mitigate."

The workaround on the page is to use Outlook on the web or new Outlook for Windows. Using Outlook on the web changes nothing on the machine. Microsoft's page gives no steps for new Outlook for Windows beyond naming it, and the page says the status is "FIXED" and being monitored, so a fresh occurrence still goes to a support case.

Cause 2: the PR_OST_OSTID property

Microsoft's fix is to remove the data in the PR_OST_OSTID binary property with the MFCMAPI tool, on the mailbox's default store. That edits a hidden property of the mailbox itself. Microsoft's page gives no way to restore the data once it has been deleted and no save-first step, so no steps are given for it. Read Microsoft's page, "You cannot start Outlook in cached mode or create a new cached mode profile", and have an administrator who has used MFCMAPI work through it on the affected mailbox.

What you can do without changing the mailbox is to stop adding to the property. The page lists the scenarios: many users signing in to one mailbox, many users opening a shared resource mailbox with Download shared folders enabled, and repeated creation of new cached mode profiles for one mailbox. Avoid building throwaway cached mode profiles for that mailbox while you investigate.

Inbox Repair situation

Microsoft's page on the Inbox Repair tool (SCANPST.EXE) names this error as a reason to use it. The page recommends a backup first, and says the tool creates its own backup file during repair.

Before you repair it, copy the data file you noted under Prove the cause to a new name in File Explorer, with Outlook closed, for example mailbox-before-repair.pst. Do not overwrite an earlier copy.

Risk: The next step runs the Inbox Repair tool on the data file. Microsoft's page says the repair can leave a Recovered Personal Folders folder or a Lost and Found folder, that the recreated folders may be empty, and that "items may not be recovered if they were permanently deleted or corrupted beyond repair".

  1. Exit Outlook and browse to the folder that holds SCANPST.EXE. Microsoft's page gives C:\Program Files (x86)\Microsoft Office\root\Office16 for Outlook 2016 and 2019.
  2. Open SCANPST.EXE, select Browse, choose the original .pst file (not the copy you saved) and select Start.
  3. If the scan finds errors, select Repair. Microsoft says you might need to run the tool several times.
  4. Start Outlook with the profile that uses the repaired file.

To undo it: the tool leaves a backup file with the same name and a .bak extension in the same folder. Microsoft's page says to make a copy of the .bak file, rename the copy with a .bak.pst extension (for example name.bak.pst) and bring it into Outlook with the Import and Export Wizard to recover extra items. To put the file back exactly as it was before the repair, close Outlook and copy your saved copy back into the folder under the original file name, replacing the repaired file.

For an Exchange account the page says the offline file (.ost) can be deleted and Outlook recreates it the next time it opens. Microsoft does not say how long the recreation takes. The Inbox Repair tool does not connect to or analyse data stored in an Exchange mailbox, according to the same page. Deleting the file is a separate change, covered in the next paragraph.

Before you delete an .ost file, close Outlook and find the right file: in Mail, Show Profiles, Properties, Data Files, the .ost file is the one listed against the Exchange account's name, and a .pst file is never the file to delete. Note its path, then copy it to a new name such as account-before-delete.ost.

Risk: The next step deletes the offline Outlook Data File (.ost) of an Exchange account. Microsoft's page says Outlook creates it again on the next start, and gives no figure for how long that takes or what happens to anything that exists only in the old file. Do it only for an Exchange account, never for a .pst.

Delete only that .ost file, then start Outlook.

To undo it: Microsoft's page describes no way back, because Outlook recreates the file. If you still want the old file, close Outlook and copy your saved file back under the original name and folder, replacing the file Outlook created; Microsoft's page does not describe this restore.

Confirm the fix

  • Classic Outlook starts with no message and shows the folder list.
  • Send and receive complete for the profile.
  • For the data-file case, the folder list matches what the user expects, and nothing is left under a Recovered Personal Folders folder or a Lost and Found folder.

What to watch afterwards

  • Whether the message returns on a mailbox that many people open. The cached-mode page ties the growth of the property to repeated profile creation and to shared mailboxes.
  • Whether the same message appears for several users at once. Microsoft's known-issue page says recent support cases were for user mailboxes.
  • The .bak file and your own copies. Keep them until the user confirms nothing is missing, then remove them.

Risks and limits

These steps have not been run or lab-tested.

Microsoft's known-issue page names Outlook for Microsoft 365 and gives no version range or tenant detail, and its status wording ("FIXED", "monitoring to confirm") describes the service at the date shown on the page. The cached-mode page covers Outlook 2010 to 2019. No page under Sources links the command-line switches /safe or /resetnavpane to this error. The switch list describes /safe as starting Outlook with COM add-ins turned off, and /resetnavpane as clearing and regenerating the Folder Pane for the current profile.

Microsoft's Inbox Repair page says that for an Exchange account you can delete the offline Outlook Data File (.ost) and Outlook will recreate it. It gives no figure for what happens to anything that exists only in the old file.

Sources