You try to open Claude Desktop on Windows, and instead of the app you get this dialog — this article walks through how to fix it. On English-language Windows it reads:

This app can't open
There's a problem with Claude. Reinstall the application from its original install location or contact your administrator.

On Windows set to other languages the same dialog appears in translation (a Japanese-language report is GitHub #83730). The short answer: do not uninstall straight away. One read-only line of PowerShell tells you whether a plain reinstall will do, or whether you should start with Repair. Several people report that uninstalling emptied the Claude Code session list in the desktop app (the conversation logs themselves survive — see §4).

🧭 Seeing a different message? Go here instead

"Can't open this app" + select Repair

Windows points you to Repair → how to fix it with Repair

"Another program is currently using this file"

0x80070020 right after an update → how to fix it by signing out

It froze and crashed while you were using it

The crash that came before the dialog → the GPU process gone article

⚠️ How solid this is: neither Anthropic's help center nor its documentation explains this error message or how to fix it (as of September 30, 2026; the pages checked are listed in §1). The steps below come from user reports filed in GitHub's anthropics/claude-code repository, cross-checked against Microsoft's official PowerShell documentation. Anything based on reports is marked 🟡 Reported; anything checked against official sources is marked ✅ Confirmed.

What Get-AppxPackage shows decides your route

Nothing is returned

The package is gone. Just reinstall (§3-A)

Status is anything but Ok

Modified, NeedsRemediation and the like. End processes → Repair → re-register → install over the top (§3-B)

Still won't open

Back up → remove → restart → reinstall. Only now do you uninstall (§3-C)

Contents

1. What this error is — a Windows message with no official explanation

This dialog does not come from the Claude app. It is the message Windows shows when it refuses to launch a packaged (MSIX) app — not a single line of Claude's own code has run. The same wording has been reported for apps other than Claude (for example, on the Tom's Hardware forums).

🟡 Reported: the wording quoted in GitHub reports varies slightly from one to the next. Even in English alone there are these variants:

Quoted wording (excerpt) Reports
There's a problem with Claude. Reinstall the application … or contact your administrator. #84725, #86509 and many others
There is a problem with Claude. Reinstall the app from its original install location … #86425
… or contact the administrator. #85174
Heading reads "This app can't open" or "Can't open this app" #85317, #84333

Whether that comes from different Windows versions or from how each reporter copied it down is unclear. All of them give the same instruction — reinstall from the original install location — so this article treats them as one error.

What the official sources say

On September 30, 2026, I read the following pages in full. None of them mentions this error message, or what to do when the app will not start on Windows.

On GitHub, an Anthropic staff member closed #84725 (a report of this exact message) as a duplicate of #80444. That issue, #80444, was closed as "completed" on September 15, 2026, with no note on what was fixed. On September 22 a user left a comment asking whether it had been fixed, and in which version. I could find no official announcement of a fix.

2. Check the state first (read-only)

Run the following in PowerShell (no admin rights needed). It is a read-only command that changes nothing.

Get-AppxPackage -Name Claude | Select-Object Name,Version,Status,IsPartiallyStaged,SignatureKind

On a healthy install, Status is Ok. For reference, here is the output Claude Code got when it ran this on the author's machine (Windows 11 Home 10.0.26200, Claude Desktop MSIX build 2.16120.0.0) on September 30, 2026:

Name              : Claude
Version           : 2.16120.0.0
Status            : Ok
IsPartiallyStaged : False
SignatureKind     : Developer

On machines showing the error, reports split into two outcomes:

Nothing is returned

The package registration itself is gone. Only the Start menu shortcut remains, pointing at an app that no longer exists. The reporter of #84725 noted that the package's data folder had disappeared as well.

Status: Modified, NeedsRemediation

The package is still there, but Windows has decided it was tampered with and blocks it from launching. Most reports fall here: #85317, #86509, #82381 and others.

If Status is Ok and the app still will not start, you may have a different kind of breakage from the one this article covers. See §7 of the Repair article (a package with no working entry point).

SignatureKind reads Developer because the app is distributed outside the Microsoft Store. The reporter of #80444 traced it in the event log: because of this, the automatic repair Windows attempts through the Store kept failing (🟡). Leaving it alone will not fix it; you have to fix it by hand.

3. The order to try fixes — lightest first

Work from the top and stop as soon as the app opens. If §2 returned nothing, start at A; otherwise start at B. C (uninstalling) comes last.

A. The package is gone → just reinstall

The registration is already gone, so there is nothing broken to remove. Download the installer from the official download page and run it. 🟡 Reported: the reporter of #84725 says reinstalling the official MSIX with Add-AppxPackage brought it back to Status: Ok without a restart.

If you would rather install the MSIX directly instead of using the installer, the download URL and install method are in Anthropic's official help article (✅). The command for installing it for a single user is:

Add-AppxPackage -Path "Claude.msix"

B. Status is anything but Ok → end processes → Repair → re-register

B-1. End any leftover processes. Many reports say that even after the window disappears, claude.exe or cowork-svc.exe keeps running, holds on to the package files and makes the repair fail (#80444, #85317). Stopping the service on the second line needs an elevated (admin) PowerShell.

Get-Process claude*,cowork* -ErrorAction SilentlyContinue | Stop-Process -Force
Stop-Service CoworkVMService -ErrorAction SilentlyContinue

B-2. Click Repair. Settings → Apps → Installed apps → the "…" next to Claude → Advanced options → Repair. Microsoft's official help gives the same order: when an app is not working right, try Repair first, and Reset only if that does not help (✅).

🟡 Reported: reports disagree on how well Repair works. The author of #80444 wrote that Repair is the only thing that reliably works, but the same thread also has a report that on Windows 10, Repair only re-registers the package without downloading it again, so the app did not come back, and another where Repair failed with "We couldn't repair this app" no matter how many times it was clicked. If it does not work, move on to B-3.

💡 Do not click Reset yet. It sits right next to Repair, and Windows itself warns on that screen that "The app's data will be deleted" (the actual wording is checked on a real machine in the Repair article). The session list from §4 counts as that app data. If you do press it, take the §4 backup first.

B-3. Re-register the package. This is the next step when Repair fails. It is the command the reporter of #85317 used, rewritten to target only the current user.

Get-AppxPackage -Name Claude | ForEach-Object {
  Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppxManifest.xml"
}

✅ Confirmed: Microsoft's Add-AppxPackage documentation describes -DisableDevelopmentMode as the way to register an existing app package installation that has been disabled, did not register, or has become corrupted. 🟡 That said, reports include both cases where this brought the app back and cases where Modified, NeedsRemediation stayed put (in #87750, neither Repair, Reset nor re-registering helped). If it fails with 0x80073D02 (in use), go back to B-1 and end the processes.

B-4. Run the official installer over the top, without uninstalling. 🟡 Reported: one user in #83932 found that re-registering did not help, but simply running the official installer again brought it back to Status: Ok with the app data intact — and recorded recovering the same way several times. The same thread also has a report of the installer failing with 0x80073CF9. It loses less than removing the app, so it is worth one try before C.

C. Still won't open → back up → remove → restart → reinstall

🟡 Reported: the reporter of #87750 says the app only started again after removing the package entirely, restarting, and then reinstalling. This is the first step that deletes app data, so take the §4 backup first, without fail.

Get-Process claude*,cowork* -ErrorAction SilentlyContinue | Stop-Process -Force
Get-AppxPackage -Name Claude | Remove-AppxPackage
Restart-Computer

After the restart, reinstall from the official download page, just as in A.

4. What uninstalling deletes and what it keeps

The worry that reinstalling will wipe out your work can be answered storage location by storage location.

Data Where it lives When the package is removed
claude.ai chat history Anthropic's servers Kept (visible again once you sign in)
Claude Code conversation logs .jsonl files under %USERPROFILE%\.claude\projects\ Kept (they live outside the package)
The desktop app's session list (titles, folders) %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude-code-sessions\ Deleted (the list comes back empty)

🟡 Reported: the third row is the trap. The reporter of #81907 says that after reinstalling, the session list in the app's Code tab was empty (31 sessions), yet every log in ~/.claude/projects was still there, and running claude --resume in a terminal listed all 31. #83730 describes the same thing: about eight folders of organized sessions came back empty, while claude --resume showed 49 sessions. The list location comes from the #81907 reporter's own digging, and they also note that the app has no way to rebuild the list.

On the author's machine (September 30, 2026, same machine as above), Claude Code counted 352 files in that list (local_*.json) and 173 conversation logs directly under each project in .claude\projects (I have not checked why the two numbers differ). It is the list side that gets deleted. The numbers depend entirely on how you use the app, so count them on your own machine.

The backup to take before §3-C

Before removing the package, copy these two locations to your desktop. Caches are not needed for a restore, so they are left out.

$dst = "$env:USERPROFILE\Desktop\claude-backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Force $dst | Out-Null
robocopy "$env:USERPROFILE\.claude" "$dst\dot-claude" /E /R:1 /W:1 /NFL /NDL
robocopy "$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude" "$dst\app-data" /E /R:1 /W:1 /NFL /NDL /XD Cache "Code Cache" GPUCache

The first copy, .claude, survives the package removal anyway, but it is worth taking too in case something gets deleted by mistake along the way. The second copy is the part that removal deletes. I have not verified that copying it back after reinstalling restores the list — the #81907 reporter rebuilt the list by hand, and notes that when a file was in the wrong format, the app opened it and then dropped the link to it. What can be said for certain is that the conversation logs survive, and you can pick up where you left off with claude --resume.

5. -PreserveApplicationData will not save your data

You may come across advice that adding Remove-AppxPackage -PreserveApplicationData lets you remove the app while keeping its data. It does not work for an ordinary package like Claude Desktop.

✅ Confirmed: Microsoft's Remove-AppxPackage documentation says this option applies only to apps under development, and can be specified only for apps registered from loose files.

🟡 Reported: in practice, #83932 records a data-preserving removal being refused with 0x80073CFA. #80444 also has a log pasted in showing Claude's own installer failing for the same reason (developer mode required). If you want to keep the data, copying the folders as in §4 is the only way.

6. Why it happens — the reported triggers

🔴 Unconfirmed: Anthropic has not explained the cause. What follows is what was happening just before the error, according to GitHub reports. The common thread is that the app failed to shut down cleanly, after which Windows judged the package to be broken.

A crash in the built-in browser

Right after an external site is opened in the browser pane, the GPU process or similar crashes and takes the whole app down (#80444, #87750). This is the most frequently reported trigger.

An auto-update while the app is running

An update lands while the app is in use, fails with 0x80073D02 (in use), and leaves the package broken (#86425, #85174, #83932).

A freeze during heavy work

While Claude Code is in the middle of a long task, the app vanishes without warning (#85317, #84725).

Cowork service registration fails

Registering the bundled service stops with 0x80073D28, leaving a half-finished registration behind (#87161, #88500).

How the browser-pane crash happens, and how to avoid it, is covered in the GPU process gone article. The reports date from July to September 2026 and span several app versions as well as both Windows 10 and 11. As of September 30, I found nothing showing it was fixed in a particular version.

How this differs from the "select Repair" dialog

"Can't open" comes in two wordings: the one where Windows directs you to Repair (the Repair article), and this article's "reinstall from the original install location". I found no documentation of which state triggers which message. Lining up the reports, this article's wording shows up both when the package has disappeared (#84725) and when it is NeedsRemediation (#86509 and others). Whichever message you see, the reliable move is to check the state with the one line from §2 before choosing a fix.

7. Making it less likely to happen again

There is no official way to prevent it entirely. From the reports, three things lower the odds:

  • Do not open external sites in the app's browser pane. Many reports name this as the trigger. There are reports of the crashes stopping once site checks were handed off to a regular browser, Claude in Chrome, or WebFetch (the #80444 thread).
  • Quit from the system tray before stepping away. Closing the window with × leaves the app running in the background. Since an update landing mid-use is one of the triggers, right-click the icon in the notification area and quit when you are not using it.
  • Keep the §2 command and the §4 backup steps somewhere handy. If you only start looking once it breaks, it is tempting to panic and jump straight to uninstalling.

Summary

"There's a problem with Claude. Reinstall the application from its original install location" is the message Windows shows when it refuses to launch Claude Desktop (MSIX), and Anthropic's official help has no explanation for it (as of September 30, 2026). The dialog tells you to reinstall, but the first thing to do is check the state with Get-AppxPackage.

If the package is gone, reinstalling is enough. If it shows Modified, NeedsRemediation, work through the lighter fixes in order: end the processes and Repair, then re-register, then run the installer over the top, and only if all of that fails, back up, remove and reinstall. A reinstall keeps your chat history and your Claude Code conversation logs, but reports say the desktop app's session list is lost, so copy it before removing anything. Even if it is lost, claude --resume lets you continue where you left off.

FAQ

Q1. Can't I just reinstall straight away, as the message says?

That often fixes it, but there are reports that removing the package wiped the desktop app's session list (#81907, #83730). Check the state first with Get-AppxPackage -Name Claude. If nothing is returned, there is nothing to remove, so a plain reinstall is all you need.

Q2. Will I lose my Claude Code work?

The conversation logs live in %USERPROFILE%\.claude\projects\ and survive removing the package. Even when the app's list is empty, running claude --resume in a terminal has been reported to list them. claude.ai chat history is stored server-side and is not affected.

Q3. Has Anthropic released an official fix?

Not that I could confirm as of September 30, 2026. The related #80444 was closed as "completed" on September 15, but with no explanation of what was fixed or in which version.

Q4. Can I keep my data by removing the app with -PreserveApplicationData?

No. Microsoft's documentation limits that option to apps under development, and with Claude Desktop it has been reported to be refused with 0x80073CFA. Copy the folders you want to keep before removing the app (§4).

Related articles