›_ Claude Code Issues
Claude Code Issues / #55465

[BUG] Claude Desktop for Windows — MSIX Installs Successfully but App Cannot Launch (Entry Point Missing / Broken)

Resolved 💬 4 comments Opened May 1, 2026 by SajithKSwami Closed Jun 18, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

<HTML><HEAD></HEAD><BODY><!--StartFragment --><strong><p>Summary</strong></p>
<p>Claude Desktop for Windows installs successfully via MSIX and reports a clean, fully registered package (<code>Status: Ok</code>), but <strong>cannot be launched in any way</strong>.<br/>
The AppX entry point appears to be <strong>missing or invalid</strong>, causing Windows to open the <strong>Documents</strong> folder instead of launching Claude.</p>
<p>This is <strong>not</strong> the same issue as GitHub Issue #28892.<br/>
That issue is about <strong>Store redirect / protocol handler failures</strong>.<br/>
My issue is about a <strong>successful MSIX install with a broken entry point</strong>.</p>
<p>This appears to be a <strong>packaging or manifest error</strong> in the Claude MSIX bundle.</p>
<p></p>
<p>📌 <strong>Environment</strong></p>
<p>
  |  
-- | --
  |  
  |  
  |  
  | Claude_1.5354.0.0_x64__pzs8sxrjxfjjc
  | 1.28.240.0
  | DISMSFC
  | Add-AppxPackage

</p>
<p></p>
<!--EndFragment --></BODY></HTML>

What Should Happen?

📌 Final Installed Package State (Successful Install)
After resolving earlier deployment locks, the MSIX installs cleanly:
Name : Claude
Version : 1.5354.0.0
PackageFullName : Claude_1.5354.0.0_x64__pzs8sxrjxfjjc
InstallLocation : C:\Program Files\WindowsApps\Claude_1.5354.0.0_x64__pzs8sxrjxfjjc
Status : Ok
IsPartiallyStaged : False


This confirms:

  • MSIX installed successfully
  • Package registered correctly
  • No partial staging
  • No corruption
  • No App Installer issues

❌ Actual Behavior — Claude Cannot Launch
Attempts to launch Claude fail in all methods:
Start Menu
No entry appears.
Win + R → claude
No execution alias exists.
shell:AppsFolder
Claude does not appear.
Direct entry point
explorer.exe shell:AppsFolder\Claude_pzs8sxrjxfjjc!App

Instead of launching Claude, Windows opens the user’s Documents folder.
This is Windows’ fallback behavior when an AppX entry point is missing or invalid.

🚨 Critical Finding — Entry Point Missing / Broken
The MSIX package is installed and registered, but:

  • No valid <Application> entry exists
  • No valid executable is mapped
  • No execution alias is created
  • The entry point ID (Claude_pzs8sxrjxfjjc!App) does not resolve
  • Windows falls back to opening Documents

This is a manifest / packaging issue, not a Windows issue.

🧪 All Troubleshooting Steps Attempted
✔ 1. Full OS Health Checks
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

→ No integrity violations.

✔ 2. Removed all previous Claude remnants

  • Removed AppX packages
  • Removed WindowsApps folders
  • Removed execution aliases
  • Removed stale registry entries

✔ 3. Fixed ghost deployment lock (0x80073D02)
Initial error:
Unable to install because the following apps need to be closed Claude_1.5354.0.0_x64__pzs8sxrjxfjjc


Resolved by:

  • Killing background processes
  • Restarting AppXSvc
  • Rebooting
  • Reinstalling MSIX

✔ 4. Successful reinstall via PowerShell
Add-AppxPackage -Path ".\Claude.msix"

MSIX installs cleanly.

✔ 5. Verified package registration
Get-AppxPackage -Name Claude

Shows Status: Ok.

✔ 6. Attempted all launch methods

  • Start Menu
  • Win+R alias
  • AppsFolder
  • Direct entry point
  • Manual EXE launch (folder inaccessible by design)

All fail.

✔ 7. Compared with Issue #28892
Issue #28892 is about:

  • Store redirect
  • Protocol handler failure
  • Installer not registering MSIX

My case is different:

  • MSIX installs successfully
  • MSIX registers successfully
  • Entry point is missing or broken

Therefore, Issue #28892 steps do not apply.

🧩 Root Cause (Based on All Evidence)
✔ MSIX installs
✔ MSIX registers
✔ Package is healthy
❌ Entry point missing
❌ Alias missing
❌ App cannot launch
❌ AppsFolder entry point opens Documents
This is a Claude MSIX packaging bug.
The AppxManifest.xml likely has:

  • Missing <Application> entry
  • Incorrect Executable path
  • Incorrect EntryPoint
  • Incorrect Id
  • Missing alias registration

🛠 What Claude Engineering Needs to Investigate

  1. Validate the MSIX manifest
  • Is <Application Id="App"> defined?
  • Does it point to a valid executable?
  • Does the executable exist in the package?
  1. Validate execution alias creation
  • Should claude.exe be created in WindowsApps?
  • Why is it missing?
  1. Validate entry point ID
  • Is Claude_pzs8sxrjxfjjc!App correct?
  • Does it match the manifest?
  1. Validate packaging pipeline
  • Is the MSIX built correctly?
  • Are required fields missing?
  1. Confirm minimum supported App Installer version
  • Does Claude require a newer App Installer than 1.28.240.0?

Error Messages/Logs

Error Messages / Logs
1. Initial MSIX install failure (ghost deployment lock)
Add-AppxPackage : Deployment failed with HRESULT: 0x80073D02,
The package could not be installed because resources it modifies are currently in use.

error 0x80073D02: Unable to install because the following apps need to be closed:
Claude_1.5354.0.0_x64__pzs8sxrjxfjjc.

NOTE: For additional information, look for [ActivityId] 5fae2201-d980-0000-a59f-d05f80d9dc01
in the Event Log or use the command line:
Get-AppPackageLog -ActivityID 5fae2201-d980-0000-a59f-d05f80d9dc01


This indicates Windows believed a ghost Claude process was still running even though no package was installed.

2. Path error before correct directory was used
Add-AppxPackage : Cannot find path 'C:\WINDOWS\system32\Claude.msix' because it does not exist.


(Not a bug — included for completeness.)

3. Successful installation output
Name              : Claude
Publisher         : CN="Anthropic, PBC", O="Anthropic, PBC", L=San Francisco, S=California, C=US
Architecture      : X64
Version           : 1.5354.0.0
PackageFullName   : Claude_1.5354.0.0_x64__pzs8sxrjxfjjc
InstallLocation   : C:\Program Files\WindowsApps\Claude_1.5354.0.0_x64__pzs8sxrjxfjjc
IsFramework       : False
IsBundle          : False
IsPartiallyStaged : False
SignatureKind     : Developer
Status            : Ok


This confirms the MSIX installed successfully and is fully registered.

4. Entry point failure (critical)
Attempting to launch Claude via the AppX entry point:
explorer.exe shell:AppsFolder\Claude_pzs8sxrjxfjjc!App


Result:
Instead of launching Claude, Windows opens:
C:\Users\<User>\Documents


This is Windows’ fallback behavior when an AppX entry point is missing or invalid.

5. No Start Menu entry / No execution alias
- No claude.exe or Claude.exe in:
C:\Users\<User>\AppData\Local\Microsoft\WindowsApps\
- No Claude entry in:
shell:AppsFolder


This confirms the MSIX did not register a valid entry point or alias.

6. WindowsApps folder inaccessible (expected)
Attempts to open:
C:\Program Files\WindowsApps\Claude_1.5354.0.0_x64__pzs8sxrjxfjjc


→ Access denied (normal Windows behavior).
Included for completeness.

✔ Summary of Logs
- 0x80073D02 ghost deployment lock
- Successful MSIX installation (Status: Ok)
- Entry point fails → opens Documents
- No Start Menu entry
- No execution alias
- No AppsFolder entry
- Manifest appears to lack a valid <Application> entry

Steps to Reproduce

Steps to Reproduce

  • Download the Claude Desktop MSIX installer
  • File: Claude.msix
  • Architecture: x64
  • Source: Official Claude Desktop download page.
  • Open PowerShell
  • Run as a normal user or Administrator (both produce the same result).
  • Navigate to the folder containing the MSIX file

Example:
cd "$HOME\Downloads"

  • Install Claude using Add-AppxPackage

Add-AppxPackage -Path ".\Claude.msix"

  • Installation completes successfully.
  • No errors are shown.
  • Get-AppxPackage confirms:

Status : Ok
IsPartiallyStaged : False
InstallLocation : C:\Program Files\WindowsApps\Claude_1.5354.0.0_x64__pzs8sxrjxfjjc
- Attempt to launch Claude from the Start Menu

  • Search for Claude or Claude Desktop
  • No entry appears.
  • Attempt to launch Claude using the execution alias
  • Press Win + R
  • Type:

claude

  • Nothing launches (alias not created).
  • Attempt to launch Claude from AppsFolder
  • Run:

shell:AppsFolder

  • Claude does not appear in the list of installed apps.
  • Attempt to launch Claude using the AppX entry point directly

Run:
explorer.exe shell:AppsFolder\Claude_pzs8sxrjxfjjc!App

  • Actual result:
  • Windows opens the user’s Documents folder

(C:\Users\<User>\Documents)

  • Claude does not launch.
  • Verify that the execution alias was not created

Check:
C:\Users\<User>\AppData\Local\Microsoft\WindowsApps\

  • No claude.exe or Claude.exe exists.
  • Verify that the package is installed but unusable

Get-AppxPackage -Name Claude

  • Output shows:
  • Status: Ok
  • IsPartiallyStaged: False
  • Valid InstallLocation
  • But no way to launch the app.

Minimal Reproduction Summary- Install Claude via MSIX

  • Installation succeeds
  • App cannot launch
  • Entry point resolves incorrectly
  • Windows opens Documents instead of Claude

This reliably reproduces the issue on a clean, healthy Windows 11 system.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Desktop MSIX: 1.5354.0.0 (x64)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

System Health Verification
The Windows system was verified to be healthy before installation:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Both commands completed with no integrity violations.

No Third‑Party Modifications

  • No antivirus other than Windows Defender
  • No App Installer overrides
  • No sideloading policies
  • No Group Policy restrictions
  • No custom WindowsApps permissions

This is a standard Windows 11 x64 environment.

WindowsApps Folder Access
Attempts to inspect:
C:\Program Files\WindowsApps\Claude_1.5354.0.0_x64__pzs8sxrjxfjjc

result in Access Denied, which is expected behavior on modern Windows builds.
This confirms the package is installed but does not allow verification of the executable or manifest contents.

Behavior Consistency
The issue reproduces 100% consistently:

  • After fresh reboots
  • After clearing AppX caches
  • After removing all previous Claude remnants
  • After reinstalling the MSIX
  • After verifying system health

The behavior does not change across attempts.

Difference from Issue #28892
This issue is not related to:

  • Microsoft Store redirect
  • Protocol handler failures
  • “Get an app to open this link” popup
  • MSIX failing to register

In this case:

  • MSIX installs successfully
  • MSIX registers successfully
  • Package status is Ok
  • But entry point is missing or invalid

This is a different class of bug.

Expected Entry Point Behavior
The following command should launch Claude:
explorer.exe shell:AppsFolder\Claude_pzs8sxrjxfjjc!App

Actual result:
Windows opens the user’s Documents folder instead.
This is Windows’ fallback behavior when an AppX entry point is not found.

Execution Alias Missing
Expected alias location:
C:\Users\<User>\AppData\Local\Microsoft\WindowsApps\

No claude.exe or Claude.exe is created.
This confirms the MSIX did not register an alias.

No Start Menu Entry
After installation:

  • No “Claude”
  • No “Claude Desktop”
  • No “Anthropic” folder

This indicates the manifest did not create a Start Menu shortcut.

No App Registration in AppsFolder
Running:
shell:AppsFolder

shows no Claude entry, even though the package is installed.

Logs Available on Request
I can provide:

  • AppXDeployment‑Server logs
  • Event Viewer logs
  • PowerShell transcript
  • Screenshots of all behaviors
  • Full MSIX installation output

Summary
All evidence points to a packaging / manifest issue:

  • MSIX installs correctly
  • Package registers correctly
  • But the app has no valid entry point
  • No alias
  • No Start Menu entry
  • No AppsFolder entry
  • Entry point ID resolves incorrectly
  • Windows opens Documents instead of launching Claude

This is a Claude MSIX packaging bug, not a Windows or App Installer issue.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗