The instruction means exactly what it says: on a desktop installation of Anthropic's Claude, a fault that survives a simple relaunch is handled inside the app's advanced options, where a repair action restores the local installation without touching your account data. If repair doesn't clear it, the next two fallbacks are reinstalling the app or contacting your organization's administrator. That order matters, and getting it backwards wastes time — a full reinstall is the slowest option and an administrator ticket can take days.
What follows traces that path precisely, including what each step actually changes on your machine, how to read the failure that sent you there, and when repair is the wrong tool entirely. If you're here because a help-desk reply or internal note pointed you to advanced options, this is the route it described.
What the Claude repair option actually does under the hood
The repair action in Claude's advanced options rebuilds the parts of the local installation that a normal launch doesn't verify. Think of it as three jobs in sequence. First, it re-registers the app's background services — the helper processes that sit between the Claude window and your operating system. Second, it re-creates or resets cache and configuration files that can corrupt when an update is interrupted, a disk fills up mid-write, or antivirus software quarantines a file. Third, it validates file integrity against what the installer originally wrote.
Your conversations and account credentials live on Anthropic's servers, so repair doesn't touch them. What it does touch is the local shell around those conversations: window state, cached assets, update records, and the service registrations. That's why a repair fixes a blank window, a frozen splash screen, or repeated "something went wrong" toasts, but won't fix a wrong password (that's a credential issue) or a corporate firewall blocking Anthropic's endpoints (that's a network policy issue).
Repair is also non-destructive to settings you've entered — language, theme, notification choices. If repair finishes and those reset anyway, that's a signal the configuration folder itself is being blocked from writing, which points toward permissions or security software rather than the app.
One practical note: repair requires the app to write to its own installation directory. If Claude sits in a managed location on a corporate machine, the repair may fail partway with a permissions error — a failure case almost no walkthrough mentions. That error is your cue to skip to the administrator step rather than retrying repair three times.
Locating advanced options and running repair in order
Do the steps in this order. Each one assumes the previous step either didn't appear or didn't work, so you're not repeating effort.
1: Quit Claude completely. Close the window, then confirm the process ended — on Windows, check Task Manager's Details tab; on macOS, check Activity Monitor. A repair launched over a running instance can fail to replace locked files. 2: Relaunch once. Open Claude again. A single clean relaunch clears a surprising share of transient faults and costs seconds. 3: Open the app menu or settings. In the desktop app, look for the menu bearing the app's name (macOS menu bar) or the gear icon in the sidebar or tray (Windows and Linux builds). Exact label wording varies by version; if you can't find it, the current label is listed in Anthropic's help center for your platform. 4: Find Advanced options. It usually sits under Settings or Help, sometimes behind a "More," "Troubleshooting," or "About" item. Submenu placement has moved between releases, so scan for the word "Advanced" rather than a fixed position. 5: Select Repair. Click it once and let it finish. Expect 1–3 minutes on a typical machine; a spinning indicator or progress text should appear. Don't click twice. 6: Sign in if prompted. Repair can drop your session token even though your account data is intact. Sign back in with your usual method. 7: Test with one conversation. Open a single existing chat and send one short message. If that works, the fault is cleared.
If repair fails or does nothing, close the app, wait ten seconds, and relaunch before trying the fallbacks below. If it errors partway with a message about permissions or a locked file, stop here and go to the administrator path — retrying won't clear a permission block.
Diagnosing which failure the repair is meant to fix
Repair is a generalized fix, but it earns its keep on a specific family of symptoms. If you can name the symptom, you know whether repair is even the right door.
| Symptom | Repair helps | Reinstall is the better call |
|---|---|---|
| Blank or white window after launch | Yes, usually | Second attempt if repair fails |
| Frozen splash screen | Yes, often | If repair and relaunch both fail |
| "Something went wrong" on every message | Yes, if local cache is corrupt | If the error persists after repair |
| App updates repeatedly but reverts | Yes, service registration is broken | If the update loop continues |
| Login rejected with correct password | No — credential issue | No — check account or SSO |
| "Cannot reach server" or timeouts | No — network or firewall | No — check proxy or policy |
| Install won't complete at all | No | Yes, a clean reinstall |
The left column is your repair checklist; the right column tells you when to stop tinkering and escalate. Reaching for a full reinstall first is common and wasteful — it re-downloads the entire app when a 1–3 minute repair would have done the job.
A less obvious case: if Claude works fine in a browser but the desktop app fails on the same account and network, the problem is almost certainly local to the installation, which is squarely repair territory. The reverse — desktop works, browser fails — points at the browser, not the app, and repair won't help.
Reinstalling the Claude desktop app when repair won't stick
Reinstall after repair fails, not before. The order protects your time: repair takes minutes, a reinstall takes longer depending on your download speed and whether an IT department must approve the installer.
A clean reinstall has three stages. First, uninstall the app through the platform's normal route — Apps & Features on Windows, dragging to the Trash plus emptying it on macOS for a full removal, or the system package manager on Linux. Second, remove leftover configuration folders if the uninstaller leaves them; the installer recreates them fresh, and stale files are the very thing you're trying to escape. Third, download the current installer from Anthropic's official site and run it.
Here's the part most guides skip: reinstalling over a still-running background service can produce the same broken state you started with. Before you run the new installer, verify no Claude helper processes remain in Task Manager or Activity Monitor, and restart the machine if you can't kill them cleanly. A restart between uninstall and reinstall costs minutes and prevents a repeat failure.
On managed machines, the installer may be blocked or redirected to an internal deployment. If the official installer won't run, don't hunt for a workaround — that's the administrator's territory.
When the fix belongs to your administrator, not your machine
The line is simple: if you can't change the thing that's broken, you can't repair it. On a work or school device, the installation directory, the security software, the proxy settings, and often the ability to install anything at all are controlled by someone else.
Signs you're past the boundary include an installer that requires credentials you don't have, a repair that fails citing permissions, security software that quarantines Claude's files on each launch, or a network that blocks the app's endpoints even when your browser reaches the web fine. Any one of those means an administrator needs to act.
When you contact them, give them the three facts that shorten the ticket: the exact error text (photograph or copy it), what you already tried (relaunch, advanced options repair, reinstall), and whether browser access to Claude works on the same machine. That last detail instantly separates a network policy problem from a local installation problem, and it's the question IT will ask anyway.
Don't attempt to bypass corporate controls to force a reinstall. On managed devices that can violate policy, and it usually fails anyway because the blocking happens at a layer you can't reach.
Repair versus reinstall versus escalation: cost, time, and what each one risks
Putting the three options side by side makes the order obvious, and the time figures below come from normal desktop-install behavior on a standard broadband connection — your download speed and any IT approval queue will stretch the reinstall figure.
| Path | Typical time | What it changes | Risk | Best for |
|---|---|---|---|---|
| Relaunch | Under 1 minute | Nothing on disk | None | Transient freezes |
| Advanced options → Repair | 1–3 minutes | Services, cache, file integrity | Low; session sign-in may be needed | Crashes, blank windows, error loops |
| Reinstall | 10–30 minutes, longer with IT approval | Entire local installation | Loses local cache and settings | Repair failed or install is broken |
| Administrator ticket | Hours to days | Policy, permissions, deployment | None to you | Managed devices, blocked installs |
The arithmetic favors sequence, not guesswork. Trying relaunch, then repair, then reinstall covers the common failures in under five minutes of your own effort; jumping straight to reinstall spends a quarter-hour to half-hour re-downloading an app when a two-minute repair might have cleared the fault. The escalation path is the only one measured in days, which is why it belongs last — and only when the earlier options are genuinely unavailable to you.
Mistakes that make the Claude repair loop repeat
The most common mistake is running repair while the app is open. Locked files can't be replaced, so the repair half-succeeds and the fault returns on next launch. Quit fully, confirm the process is gone, then repair.
The second is repairing repeatedly without changing anything between attempts. Repair is not iterative — if it fails twice under identical conditions, the cause sits outside what it touches: permissions, security software, or a corrupted installer. Escalate instead of looping.
A third mistake is assuming repair erased your chats. It doesn't; they live on Anthropic's servers. If conversations genuinely vanish after a repair, the more likely explanation is that you signed into a different account or workspace, which is worth checking before you panic or file a ticket.
Finally, ignoring the pattern behind repeated failures costs the most time. If Claude breaks every time the app updates itself, the update mechanism or the security software watching it is the culprit — that's administrator territory, and the earlier you say so, the faster it gets fixed.
What changes across Windows, macOS, Linux, and managed devices
The path is the same everywhere; the labels and obstacles are not. On Windows, the app menu and settings region carry the advanced options, and the installer runs as an executable — the classic obstacle is antivirus blocking the helper service. On macOS, advanced options typically live in the app's own menu behind Settings or About, and Gatekeeper can block the installer if it wasn't obtained through the approved route.
Linux builds vary most because they arrive through a package manager or an AppImage-style bundle. Repair behavior depends on which packaging you used, so identify that first — a package-manager install may repair through the package tool itself, while a bundled install handles it in-app. On managed Windows and macOS machines, the installer may be replaced by an internal deployment package, which means "reinstall" actually means "ask IT to push the current version."
None of these differences change the order of operations. Relaunch, repair, reinstall, escalate — and let the platform's labels guide you at each stop, confirming exact wording on Anthropic's help center for your version when a menu item has moved.
FAQ
Does selecting Repair delete my Claude conversations?
No — conversations are stored server-side with your account, not in the local installation repair touches. Repair rebuilds services, cache, and file integrity around the app. If a chat looks missing afterward, check that you signed into the same account and workspace before assuming data loss.
Why does Repair fail with a permissions error?
Because the app can't write to its own installation directory, which on managed devices is controlled by IT policy. That error means repair is the wrong tool, not that you did it wrong. Stop retrying and send the error text to your administrator.
How long should the repair take before I give up?
Give it three minutes on a normal machine, longer on older hardware or a slow disk. If no progress indicator appears after that, quit, confirm the process ended, and relaunch once. Two failed repairs under identical conditions mean the cause is outside the app.
Is reinstalling faster than troubleshooting?
Rarely. A reinstall typically costs 10–30 minutes of download and setup, sometimes days if IT must approve it, while a repair takes 1–3 minutes. Reinstall only after repair fails, and clear leftover processes first so you don't reinstall into the same broken state.
Can my administrator run the repair for me remotely?
Often yes, if the device is managed through standard endpoint tools — but many administrators prefer to push a fresh deployment instead, which is equivalent to a reinstall. Ask which they'll do, because a pushed reinstall resets local settings that a repair would have preserved.
What if Claude works in the browser but not in the desktop app?
That pattern points at the local installation, which is exactly what advanced options repair is designed to fix. Try the repair before anything heavier. If it clears the fault, you've avoided a reinstall entirely.
Does the repair option exist on the mobile apps?
The desktop app is where local installation repair applies; mobile apps update and reinstall through the app store instead. On a phone, the equivalent first step is updating the app, then deleting and reinstalling it from the store if the fault persists.
Will repair fix a login that keeps getting rejected?
No. Credential rejections are account or identity-provider issues, not local corruption. Verify your password in a browser first; if that also fails, the fix is with your account or your organization's sign-in system, not the app's repair function.