New Outlook “Something Went Wrong” Error: 7 Fixes

You click the Outlook icon and, instead of your inbox, you get a plain error page: “Something went wrong.” Sometimes there is a code in brackets — [1001] is the common one — and sometimes it appears halfway through adding an account. Either way, the new Outlook for Windows refuses to start properly, and the message tells you almost nothing about why.

Here is what it actually means: the new Outlook is a web-based app, and it keeps your sign-in tokens and local mailbox state in a data folder on your PC. When that local state gets damaged — an interrupted app update, an account change, a Windows sign-in change — the app cannot start a session and falls back on its one generic error page. Your mail is not damaged; it lives on the server. The fixes below rebuild the app’s local state, from least to most drastic. None of them uses Classic Outlook tools, because the new app does not have them: no Safe Mode, no ScanPST, no Control Panel profiles.

Quick Answer: Fully close the new Outlook (Task Manager > End task) and reopen it (Fix 1). If the error stays, go to Settings > Apps > Installed apps > Outlook > Advanced options and run Repair, then Reset (Fix 2). Still stuck? Rename the app-data folder %localappdata%\Microsoft\Olk so the app rebuilds it clean (Fix 3), then re-add your account (Fix 4). If your error shows [1001], it is the sign-in variant — check the fixes in that section below. If it says “couldn’t set up your account,” skip to the last section — that is a different problem.

Why “Something Went Wrong” Appears in the New Outlook

The error page itself is deliberately vague — it is the app’s catch-all screen for “I could not start a working session.” Behind it sit three distinct situations, and telling them apart saves you time:

• No code, appears on open. The app’s local state — cached sign-in tokens and mailbox data stored under %localappdata%\Microsoft\Olk — is corrupt or out of sync with the server. This is the Repair/Reset case (Fixes 2–3).
• [1001] in the message. This is the sign-in variant: the app could not complete authentication. A stale token, a second Microsoft account on the PC confusing the sign-in, or a wrong system clock are the usual causes.
• “Something went wrong and Outlook couldn’t set up your account.” This appears while adding an account, and it means Outlook could not discover the account’s server settings automatically — the custom-domain case, covered at the end of this guide.

If Outlook will not open at all in Classic Outlook — it never gets as far as an error page, or it crashes on launch — that is a different problem with a different fix stack; start with our Outlook not opening on Windows 11 guide. And if Classic Outlook opens but freezes on the Loading Profile screen, see Outlook stuck on loading profile. This guide is only for the new app.

Fix 1: Fully Close the App and Reopen It (Then Update)

A stuck background process is the cheapest cause to rule out, and a plain close does not always kill it — the new Outlook can linger in the background after its window closes.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Find Outlook in the Processes list, select it, and click End task.
3. Reopen Outlook from the Start menu and see whether it starts cleanly.

If it opens, update it before you do anything else — app updates quietly fix a large share of these errors: open the Microsoft Store, go to Library, and click Get updates. If the error returns on the next launch, move to Fix 2.

Fix 2: Repair the App, Then Reset It

Windows gives every Store app a two-stage repair, and this is the new Outlook equivalent of Classic’s Office Repair.

1. Open Settings > Apps > Installed apps.
2. Find Outlook, click the three dots (…) next to it, and choose Advanced options.
3. Scroll to the Reset section and click Repair first. Repair fixes the app’s files and settings without removing your accounts.
4. Reopen Outlook. If the error is still there, return to the same screen and click Reset. Reset clears the app’s local data completely — you will sign in again afterwards, and your accounts will need to be re-added if they do not reappear. Your mail itself is on the server and is not touched.

Most “Something went wrong” cases end at Repair or Reset. If yours survives both, the cached state those tools leave behind is the problem — which is what Fix 3 removes by hand.

Fix 3: Clear the Olk App-Data Folder

The Olk folder is where the new Outlook stores its local state. Renaming it forces the app to build a fresh one on the next launch — the manual version of Reset, and the step that clears stubborn token and cache corruption.

1. Close Outlook completely — use Task Manager > End task again so nothing is running.
2. Press Windows key + R, type %localappdata%\Microsoft\Olk and press Enter. File Explorer opens inside the Olk folder.
3. Go up one level (to the Microsoft folder), right-click the Olk folder, and rename it to Olk.old. (Renaming, not deleting, keeps a way back.)
4. Reopen Outlook. It creates a clean Olk folder; sign in and re-add your account when prompted.

If the app now opens normally, you are done — the old folder can be deleted later once you are sure everything works. If it still fails, the account entry itself may be the damaged piece, which is Fix 4.

Fix 4: Remove and Re-Add Your Account

If the app opens but errors as soon as it touches one particular account — or right after you added it — remove that account and add it fresh so Outlook rebuilds its sign-in from scratch.

1. In the new Outlook, click the gear icon (Settings) at the top right.
2. Go to Accounts > Your accounts.
3. Select the account, click Manage, and choose Remove (depending on the account type it may say “Remove from this device”).
4. Restart the app, then return to the same screen and click Add account. Enter the address and complete the sign-in.

For Gmail and Yahoo accounts, the re-add has its own sign-in quirks — our guides to adding Gmail to the new Outlook and adding Yahoo to the new Outlook walk through those browser sign-in steps in detail.

Fix 5: Reinstall the New Outlook From the Microsoft Store

If the error survives a fresh Olk folder and a fresh account, the app installation itself is damaged. Reinstalling is safe — everything that matters is stored against your account on the server.

1. Go to Settings > Apps > Installed apps > Outlook > … > Uninstall.
2. Open the Microsoft Store, search for Outlook for Windows, and click Install (or Get).
3. Open the app and sign in with your account.

That is the end of the general fix stack. The two named variants below have their own, shorter paths — check whether yours matches before you repeat the steps above.

Seeing [1001]? The Sign-In Variant

The [1001] code is the authentication flavour of this error: Outlook tried to sign you in and the sign-in itself failed. Work through these in order:

1. Fix the clock first. Sign-in tokens are time-sensitive, and a drifting PC clock breaks them. Go to Settings > Time & language > Date & time, turn on Set time automatically, and click Sync now.
2. Check for competing accounts. Go to Settings > Accounts > Email & accounts. If an old work, school or second Microsoft account is listed there and you do not use it for mail, the app can grab its token and fail. Remove the account you do not use, restart the PC, then open Outlook and sign in with the right account.
3. Clear the cached token. If it still fails, do Fix 3 (rename the Olk folder) — that is where the bad cached sign-in lives — then sign in again.

“Outlook Couldn’t Set Up Your Account” — the Other Variant

If the message appears while adding an account and reads “Something went wrong and Outlook couldn’t set up your account,” the app never got as far as sign-in — it could not find the account’s server settings automatically. This is mostly a custom-domain mailbox problem (your own domain on Microsoft 365 or another host):

1. For a Microsoft 365 custom domain, the domain’s DNS needs its Autodiscover record: a CNAME record named autodiscover pointing to autodiscover.outlook.com, set wherever your domain’s DNS is managed (registrar or DNS host). If that record is missing or points somewhere old, automatic setup fails with exactly this message.
2. Fix or add the record, allow time for DNS to update (it can take a while), then try adding the account again.
3. If your mail is hosted elsewhere, check the provider’s own setup page for its autodiscover/automatic-setup requirements, or ask your domain admin to confirm the records match the host’s published values.

How to Stop “Something Went Wrong” Coming Back

• Keep the app updated — check the Microsoft Store Library for updates after any Windows update; the two often land together and a half-updated app is a common trigger.
• Let updates finish. Closing the app (or the laptop lid) mid-update is how its local state gets damaged in the first place.
• After changing your Microsoft account password, open the new Outlook and complete one clean sign-in rather than dismissing prompts — stale tokens are behind most repeat appearances.
• Keep the PC clock on automatic time. It sounds unrelated; for sign-in errors like [1001], it is one of the top causes.

Frequently Asked Questions

Outlook won’t start — I receive a message “Something went wrong.” How can I open Outlook?

Work through the app-level repairs in order: fully close Outlook in Task Manager and reopen (Fix 1); run Repair, then Reset, from Settings > Apps > Outlook > Advanced options (Fix 2); rename the %localappdata%\Microsoft\Olk folder so the app rebuilds its local state (Fix 3); then remove and re-add your account (Fix 4). One of those four resolves the great majority of cases, because the error almost always means damaged local state, not a damaged mailbox.

What does [1001] mean in Outlook?

[1001] is the sign-in variant of the “Something went wrong” error — the app could not complete authentication. The usual causes are a stale or wrong cached token, a second Microsoft/work account on the PC being picked up instead of yours, or a system clock that has drifted. Fix the date and time sync, check Settings > Accounts > Email & accounts for accounts you do not use, then rename the Olk folder to clear the cached token.

Will Reset delete my emails?

No. Reset clears the new Outlook’s local data — its cache, tokens and settings on this PC. Your emails, calendar and contacts are stored on the mail server against your account, and they download again when you sign back in. What you will need to redo is the sign-in itself, and possibly re-adding an account that does not reappear automatically.

Why does “Something went wrong” happen right after adding an account?

Because adding the account is the moment the app writes new sign-in tokens and local mailbox state — if that write goes wrong (an interrupted sign-in, a browser sign-in that was cancelled, or a settings discovery failure), the damaged state is what the app trips over on the next launch. Remove the account and add it again, completing the sign-in fully; for a custom-domain account, check the “couldn’t set up your account” section above instead.

Is this the same as Classic Outlook’s startup errors?

No. Classic Outlook has its own startup failures — it may not open at all, hang on Loading Profile, or ask for profiles and data-file repairs (ScanPST) — and none of those tools exist in the new app. If the window title and layout are the modern one and the error page says “Something went wrong,” you are in the new Outlook and this guide’s app-repair stack is the right one.

---

Still seeing “Something went wrong”? Tell us the exact wording on the error page — and whether [1001] appears — via our Contact page: servicedesk@howtofixerroronline.com, available 24 hours. If Outlook will not open at all rather than showing this error, our Outlook not opening guide is the right starting point, and the full error list lives on the Error Codes hub.