Fix it now
The profile is pointing at a store Outlook cannot mount, so there are no folders to show. The reliable fix is to note where the current default data file lives, then build a new profile that points at that same file.
Outlook.exe /safe
- Close Outlook and end any Outlook process on the Details tab of Task Manager.
- Start Outlook without add-ins using the command above. If it opens, the fault is an add-in or a view rather than the store.
- If it still fails, open Control Panel and choose Mail, then Show Profiles. Select the current profile, choose Properties, then Data Files, and write down the name and location of the file marked as the default.
- Back on the General tab, choose Add, name a new profile and let it configure the account from the email address.
- During setup, attach the existing data file you noted rather than letting Outlook start an empty one, unless the account is server-based and you want a fresh cache.
- Choose Always use this profile, select the new profile, and start Outlook.
For a personal data file that holds the only copy of anything, copy it somewhere safe before you attach or repair it. Repair rewrites the file in place.
If Outlook opens to the folder list, you are done. The next section explains what has to happen at startup and which of the four failures you are looking at.
Why it happens
An Outlook profile is a configuration record, not your mail. It lists the accounts, the servers, the settings and the paths of the data files a session should mount. Startup runs in a fixed order: read the profile, load each configured provider, mount each store, then draw the window. This message appears when a store fails to mount and there is no fallback, so there is no folder tree left to display.
Only a handful of things cause that. The file is not where the profile says it is, because it was moved, restored to a different path, or lives on a share that has not connected yet. The file is open in another process. It sits somewhere Outlook does not support for a cached file, such as a network share or a redirected folder. Or the container itself is damaged and the header will not parse.
Microsoft’s own guidance for a profile that will not open its data file is to read the default data file’s location out of the broken profile first, then create a new profile and point it at that file. That order matters. Creating a profile without noting the path leaves you hunting for a file whose location only the old profile knew.
One thing this article can tell you that most cannot: 0x80040900 is not the code behind this dialog, whatever a search result told you. Microsoft publishes it as NamedPropertyQuota – the store cannot hold any more named property mappings – which is a mailbox-side limit on custom properties, not a startup failure. If you genuinely have that code, you are looking at a different problem in a different place.
The profile points at a data file that is no longer there
You have this one if The message names a .pst or .ost file and that path does not exist on disk.
- Open Control Panel, Mail, Show Profiles, select the profile, choose Properties, then Data Files, and read the paths listed.
- If the file has moved, remove the entry and add the file again from its current location.
- If the file was deleted and the account is Exchange, Microsoft 365 or IMAP, remove the entry and let Outlook rebuild the cache from the server.
- If it is a .pst holding local-only mail, restore it from backup before you change anything in the profile.
The cached data file is damaged or was interrupted mid-write
You have this one if The account is server-based, the file exists, and it still refuses to mount. Usually follows a crash, a forced shutdown or a disk that filled.
- Confirm the account is Exchange, Microsoft 365 or IMAP, so the .ost is only a cache.
- Close Outlook, take the path from the profile’s Data Files tab and rename the file with a .old suffix.
- Start Outlook. It creates a new cache and downloads the mailbox again.
- Let the first synchronisation finish before judging performance on a large mailbox.
Never rename a data file for an account whose only copy of the data is local. IMAP accounts with local-only folders and old archived items are the trap.
An add-in or a view is stopping startup, not the store
You have this one if Safe mode starts normally while an ordinary launch fails immediately.
- Start with
Outlook.exe /safeand confirm it opens. - Turn every COM add-in off from File, Options, Add-ins, then reintroduce them one at a time until the fault returns.
- If a corrupted navigation pane is suspected,
outlook.exe /resetnavpanerebuilds that state, although Microsoft’s current command-line switches article no longer lists the switch.
Treat undocumented startup switches as a diagnostic of last resort. Everything they do can also be reached by building a new profile, which is the supported route.
The data file is somewhere Outlook does not support
You have this one if The .ost or .pst is on a mapped drive, a network share, or a folder being synchronised to cloud storage.
- Close Outlook and move the data file to a local path.
- Re-add the file to the profile from its new location.
- Exclude that folder from any sync client so it is not copied while Outlook holds it open.
Outlook data files over a network link work until latency or a dropped connection damages one, at which point this error is how you find out.
Full reference
The startup sequence, and where each failure lands
| Stage | What has to succeed | How it fails here |
|---|---|---|
| Read the profile | The profile exists and is readable | Outlook offers to create a new profile instead |
| Load providers | Each configured service loads | A provider error, often after an interrupted update |
| Mount stores | Every data file opens | This dialog: no folders to display |
| Draw the window | Views and navigation state parse | Starts in safe mode but not normally |
Building the replacement profile properly
- Open Control Panel and choose Mail, then Show Profiles.
- Select the current profile, choose Properties, then Data Files, and note the name and location of the default file.
- Return to the General tab and choose Add.
- Name the new profile and enter the account details, letting the setup configure the account from the email address where it can.
- Where you need to keep an existing data file, attach it during setup rather than afterwards.
- On the General tab, choose Always use this profile and select the new one.
- Start Outlook and let it complete a first synchronisation before judging anything.
Startup switches, and what is actually documented
Microsoft’s current command-line switches article documents only /nopreview for classic Outlook and --profile for new Outlook. The older switches below still work in current classic builds and are widely used, but they are no longer in the published list, so treat them as unsupported diagnostics rather than as instructions you can rely on.
| Switch | What it does | Documented |
|---|---|---|
Outlook.exe /safe |
Starts without add-ins | Yes, in Microsoft’s Outlook troubleshooting guidance |
outlook.exe /nopreview |
Starts without the Reading Pane | Yes, in the command-line switches article |
outlook.exe /resetnavpane |
Rebuilds navigation pane state | No longer listed |
outlook.exe /cleanviews |
Resets all views to defaults | No longer listed |
outlook.exe /profiles |
Prompts for a profile at startup | No longer listed |
/cleanviews discards every custom view in the mailbox. Anyone who has built views by hand will have to build them again, and there is no undo.
Repairing a personal data file
Where the store that will not mount is a .pst holding the only copy of the data, the Inbox Repair Tool that ships with Office is the first attempt. Copy the file somewhere safe before you point it at anything: repair rewrites the file in place, and a failed pass can leave you with less than you started with. Run it repeatedly until it reports no errors, and do not interrupt a pass part way through. Time taken scales with file size, and a large file can need several passes.
If a new profile fails the same way
- Test with a brand new Windows user account on the same machine. If Outlook starts there, the machine is fine and the old Windows profile is not.
- Check whether the data file is locked by another process before assuming damage; a sharing violation and a mount failure look identical from the splash screen.
- Check the Application log for errors logged at the moment of the failed start.
- Confirm the account is not mid-migration. A mailbox being moved can refuse desktop connections until the move completes.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
Cannot start Microsoft Outlook |
Startup stopped before the main window could be created; Microsoft does not publish this string with a documented cause | not published by the vendor |
The set of folders cannot be opened |
At least one configured store failed to mount, so there is no folder tree to display; not published with a documented cause | not published by the vendor |
0x80040900 |
NamedPropertyQuota: the store cannot hold any more named property mappings. It is a mailbox property limit, not the startup failure this dialog reports | Microsoft Learn |
0x8004011C |
Seen alongside profile and provider failures; Microsoft publishes no meaning for this value | not published by the vendor |
0x8004010A |
ObjectDeleted: an operation failed because the object was deleted separately | Microsoft Learn |
Confirm the fix worked
- Outlook opens straight to the folder list with no dialog.
- A manual send and receive completes without an error.
- Control Panel, Mail, Show Profiles confirms the intended profile is the default.
- File, Account Settings, Data Files lists only files that exist and mount cleanly.
- Close Outlook and reopen it twice to confirm the first success was not luck.
Questions people ask about this
Will a new profile lose my mail?
For Exchange, Microsoft 365 and IMAP accounts the mail lives on the server and comes straight back. What does not follow automatically is local-only content: personal data files must be re-added, and signatures live on disk under your Windows profile, so copy that folder first. Rules and autocomplete data held in the mailbox return with the account.
Is 0x80040900 the code for this error?
No, and this is worth being clear about because a great deal of search-engine material says otherwise. Microsoft publishes 0x80040900 as the named property quota on a store being exhausted. It has nothing to do with a profile failing to mount its stores at startup.
Do I have to buy a repair tool?
No. The Inbox Repair Tool ships with Office and is the right first attempt for a damaged personal data file. Third-party recovery products exist and some are capable, but exhaust the built-in tool and any backup or server copy first.
How do I stop this happening again?
Keep data files on local disks, shut Outlook down properly rather than powering off, keep personal data files out of synchronised folders and off network shares, and keep the mailbox comfortably under its quota. Most repeat cases trace to one of those four.
Outlook offers to create a new profile when I start it. Should I let it?
Not before you have read the old profile’s data file paths. Once the old profile is gone you have lost the record of where its files were, and finding a personal data file on a machine you do not know is slower than it sounds.
