›_ Claude Code Issues
Claude Code Issues / #68909

[BUG] NeedsRemediation

Resolved 💬 2 comments Opened Jun 16, 2026 by zeoex Closed Jun 19, 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?

Claude Desktop (Windows MSIX) — package ends up Modified, NeedsRemediation and crashes after auto-update; antivirus ruled out

Summary

Claude Desktop on Windows (MSIX) worked fine until an automatic update. After the update, the app opens for a moment, shows an "updating" state, closes, and never reopens — Windows then offers the "Advanced options → Repair" dialog. The package is permanently stuck in Modified, NeedsRemediation.

A clean uninstall + reinstall does not fix it: the install reports success, but the package immediately ends up Modified again after the app updates. This reproduces with no antivirus running, which rules out AV interference as the cause. The most likely cause is the in-app updater writing to its own MSIX package files, which breaks MSIX integrity and causes the launch to fail.

Environment

  • App: Claude Desktop, version 1.12603.1.0 (MSIX)
  • PackageFullName: Claude_1.12603.1.0_x64__pzs8sxrjxfjjc
  • Install source: official installer from https://claude.com/download (staged MSIX Claude-<id>.msix)
  • OS: Windows 11 (build: _<completar: winver o [System.Environment]::OSVersion>_)
  • Security software present: Kaspersky Small Office Security 21.25 (service AVP21.25) and Windows Defender
  • Both AV engines were inactive during the failing reinstall (see "AV ruled out" below)

Steps to reproduce

  1. Have Claude Desktop (MSIX) installed and working.
  2. Let it auto-update (or trigger the in-app update).
  3. App opens briefly, shows "updating", closes, won't relaunch.
  4. Get-AppxPackage *Claude* → Status: Modified, NeedsRemediation.
  5. Attempt to fix — all of the following reproduce the broken state:
  • Get-AppxPackage *Claude* | Reset-AppxPackage → still NeedsRemediation
  • Add-AppxPackage -Register ...AppxManifest.xml → still NeedsRemediation
  • Get-AppxPackage *Claude* | Remove-AppxPackage -AllUsers then reinstall from claude.com/download → install succeeds, but ends Modified again

Expected vs actual

  • Expected: after a clean install, package is Status: Ok and the app launches.
  • Actual: package is Status: Modified, NeedsRemediation; app crashes on launch; the package executable is effectively unavailable.

AV ruled out

During the reproducing reinstall, neither antivirus was scanning:

Get-MpComputerStatus | Select AMRunningMode, RealTimeProtectionEnabled
AMRunningMode : Not running
RealTimeProtectionEnabled : False

Get-Service AVP21.25
Status: Stopped   (Kaspersky Small Office Security Service 21.25)

The package still ended up Modified with no real-time protection active, so antivirus is not the corrupting agent.

Key deployment log (Microsoft-Windows-AppXDeploymentServer/Operational)

Install (Add) reports success, yet the package ends Modified. SID and username redacted as <SID> / <user>.

# --- Remove succeeds ---
16:19:55  Id 603   Started Remove (RemoveForAllUsers) on Claude_1.12603.1.0_x64__pzs8sxrjxfjjc
16:19:55  Id 400   Remove on volume C: finished successfully
16:19:55  Id 472   Moved package folder to ...\WindowsApps\Deleted\Claude_1.12603.1.0_..., Result: 0x0

# --- Add (install) from downloaded MSIX, reports success ---
16:21:06  Id 603   Started Add with options ForceApplicationShutdownOption, ForceUpdateFromAnyVersion
                   source: file:///C:/Users/<user>/AppData/Local/Temp/Claude-<id>.msix
16:21:12  Id 5507  Claude_1.12603.1.0_... : ...\microsoft.system.package.metadata\Resources.????????.pri
                   : No shared merged files found
16:21:12  Id 5507  Claude_1.12603.1.0_... : ...\microsoft.system.package.metadata\<SID>-MergedResources-*.pri
                   : No user-specific merged files found
16:21:12  Id 400   Add on volume C: finished successfully (source: Claude-<id>.msix)
16:21:12  Id 613   Add performance summary: Overall 6344 ms, Stage required 5328 ms, Registration 79 ms

# --- Immediately afterward: Get-AppxPackage *Claude* | Select Status ---
Status: Modified, NeedsRemediation

Notes

  • The "Repair" / "Reset" path offered by Windows does not durably fix it, because the package is re-corrupted whenever the app updates.
  • This looks related to the post-update crash reports on Windows MSIX (e.g. issues describing the app opening then dying in a loop right after an auto-update).
  • Likely root cause to investigate: the in-app updater modifying files inside the installed MSIX package directory, which invalidates MSIX integrity and triggers NeedsRemediation.

Workaround currently in use

Using Claude on the web (claude.ai) until a fixed desktop build ships.

What Should Happen?

Claude Desktop (Windows MSIX) — package ends up Modified, NeedsRemediation and crashes after auto-update; antivirus ruled out

Summary

Claude Desktop on Windows (MSIX) worked fine until an automatic update. After the update, the app opens for a moment, shows an "updating" state, closes, and never reopens — Windows then offers the "Advanced options → Repair" dialog. The package is permanently stuck in Modified, NeedsRemediation.

A clean uninstall + reinstall does not fix it: the install reports success, but the package immediately ends up Modified again after the app updates. This reproduces with no antivirus running, which rules out AV interference as the cause. The most likely cause is the in-app updater writing to its own MSIX package files, which breaks MSIX integrity and causes the launch to fail.

Environment

  • App: Claude Desktop, version 1.12603.1.0 (MSIX)
  • PackageFullName: Claude_1.12603.1.0_x64__pzs8sxrjxfjjc
  • Install source: official installer from https://claude.com/download (staged MSIX Claude-<id>.msix)
  • OS: Windows 11 (build: _<completar: winver o [System.Environment]::OSVersion>_)
  • Security software present: Kaspersky Small Office Security 21.25 (service AVP21.25) and Windows Defender
  • Both AV engines were inactive during the failing reinstall (see "AV ruled out" below)

Steps to reproduce

  1. Have Claude Desktop (MSIX) installed and working.
  2. Let it auto-update (or trigger the in-app update).
  3. App opens briefly, shows "updating", closes, won't relaunch.
  4. Get-AppxPackage *Claude* → Status: Modified, NeedsRemediation.
  5. Attempt to fix — all of the following reproduce the broken state:
  • Get-AppxPackage *Claude* | Reset-AppxPackage → still NeedsRemediation
  • Add-AppxPackage -Register ...AppxManifest.xml → still NeedsRemediation
  • Get-AppxPackage *Claude* | Remove-AppxPackage -AllUsers then reinstall from claude.com/download → install succeeds, but ends Modified again

Expected vs actual

  • Expected: after a clean install, package is Status: Ok and the app launches.
  • Actual: package is Status: Modified, NeedsRemediation; app crashes on launch; the package executable is effectively unavailable.

AV ruled out

During the reproducing reinstall, neither antivirus was scanning:

Get-MpComputerStatus | Select AMRunningMode, RealTimeProtectionEnabled
AMRunningMode : Not running
RealTimeProtectionEnabled : False

Get-Service AVP21.25
Status: Stopped   (Kaspersky Small Office Security Service 21.25)

The package still ended up Modified with no real-time protection active, so antivirus is not the corrupting agent.

Key deployment log (Microsoft-Windows-AppXDeploymentServer/Operational)

Install (Add) reports success, yet the package ends Modified. SID and username redacted as <SID> / <user>.

# --- Remove succeeds ---
16:19:55  Id 603   Started Remove (RemoveForAllUsers) on Claude_1.12603.1.0_x64__pzs8sxrjxfjjc
16:19:55  Id 400   Remove on volume C: finished successfully
16:19:55  Id 472   Moved package folder to ...\WindowsApps\Deleted\Claude_1.12603.1.0_..., Result: 0x0

# --- Add (install) from downloaded MSIX, reports success ---
16:21:06  Id 603   Started Add with options ForceApplicationShutdownOption, ForceUpdateFromAnyVersion
                   source: file:///C:/Users/<user>/AppData/Local/Temp/Claude-<id>.msix
16:21:12  Id 5507  Claude_1.12603.1.0_... : ...\microsoft.system.package.metadata\Resources.????????.pri
                   : No shared merged files found
16:21:12  Id 5507  Claude_1.12603.1.0_... : ...\microsoft.system.package.metadata\<SID>-MergedResources-*.pri
                   : No user-specific merged files found
16:21:12  Id 400   Add on volume C: finished successfully (source: Claude-<id>.msix)
16:21:12  Id 613   Add performance summary: Overall 6344 ms, Stage required 5328 ms, Registration 79 ms

# --- Immediately afterward: Get-AppxPackage *Claude* | Select Status ---
Status: Modified, NeedsRemediation

Notes

  • The "Repair" / "Reset" path offered by Windows does not durably fix it, because the package is re-corrupted whenever the app updates.
  • This looks related to the post-update crash reports on Windows MSIX (e.g. issues describing the app opening then dying in a loop right after an auto-update).
  • Likely root cause to investigate: the in-app updater modifying files inside the installed MSIX package directory, which invalidates MSIX integrity and triggers NeedsRemediation.

Workaround currently in use

Using Claude on the web (claude.ai) until a fixed desktop build ships.

Error Messages/Logs

Steps to Reproduce

Claude Desktop (Windows MSIX) — package ends up Modified, NeedsRemediation and crashes after auto-update; antivirus ruled out

Summary

Claude Desktop on Windows (MSIX) worked fine until an automatic update. After the update, the app opens for a moment, shows an "updating" state, closes, and never reopens — Windows then offers the "Advanced options → Repair" dialog. The package is permanently stuck in Modified, NeedsRemediation.

A clean uninstall + reinstall does not fix it: the install reports success, but the package immediately ends up Modified again after the app updates. This reproduces with no antivirus running, which rules out AV interference as the cause. The most likely cause is the in-app updater writing to its own MSIX package files, which breaks MSIX integrity and causes the launch to fail.

Environment

  • App: Claude Desktop, version 1.12603.1.0 (MSIX)
  • PackageFullName: Claude_1.12603.1.0_x64__pzs8sxrjxfjjc
  • Install source: official installer from https://claude.com/download (staged MSIX Claude-<id>.msix)
  • OS: Windows 11 (build: _<completar: winver o [System.Environment]::OSVersion>_)
  • Security software present: Kaspersky Small Office Security 21.25 (service AVP21.25) and Windows Defender
  • Both AV engines were inactive during the failing reinstall (see "AV ruled out" below)

Steps to reproduce

  1. Have Claude Desktop (MSIX) installed and working.
  2. Let it auto-update (or trigger the in-app update).
  3. App opens briefly, shows "updating", closes, won't relaunch.
  4. Get-AppxPackage *Claude* → Status: Modified, NeedsRemediation.
  5. Attempt to fix — all of the following reproduce the broken state:
  • Get-AppxPackage *Claude* | Reset-AppxPackage → still NeedsRemediation
  • Add-AppxPackage -Register ...AppxManifest.xml → still NeedsRemediation
  • Get-AppxPackage *Claude* | Remove-AppxPackage -AllUsers then reinstall from claude.com/download → install succeeds, but ends Modified again

Expected vs actual

  • Expected: after a clean install, package is Status: Ok and the app launches.
  • Actual: package is Status: Modified, NeedsRemediation; app crashes on launch; the package executable is effectively unavailable.

AV ruled out

During the reproducing reinstall, neither antivirus was scanning:

Get-MpComputerStatus | Select AMRunningMode, RealTimeProtectionEnabled
AMRunningMode : Not running
RealTimeProtectionEnabled : False

Get-Service AVP21.25
Status: Stopped   (Kaspersky Small Office Security Service 21.25)

The package still ended up Modified with no real-time protection active, so antivirus is not the corrupting agent.

Key deployment log (Microsoft-Windows-AppXDeploymentServer/Operational)

Install (Add) reports success, yet the package ends Modified. SID and username redacted as <SID> / <user>.

# --- Remove succeeds ---
16:19:55  Id 603   Started Remove (RemoveForAllUsers) on Claude_1.12603.1.0_x64__pzs8sxrjxfjjc
16:19:55  Id 400   Remove on volume C: finished successfully
16:19:55  Id 472   Moved package folder to ...\WindowsApps\Deleted\Claude_1.12603.1.0_..., Result: 0x0

# --- Add (install) from downloaded MSIX, reports success ---
16:21:06  Id 603   Started Add with options ForceApplicationShutdownOption, ForceUpdateFromAnyVersion
                   source: file:///C:/Users/<user>/AppData/Local/Temp/Claude-<id>.msix
16:21:12  Id 5507  Claude_1.12603.1.0_... : ...\microsoft.system.package.metadata\Resources.????????.pri
                   : No shared merged files found
16:21:12  Id 5507  Claude_1.12603.1.0_... : ...\microsoft.system.package.metadata\<SID>-MergedResources-*.pri
                   : No user-specific merged files found
16:21:12  Id 400   Add on volume C: finished successfully (source: Claude-<id>.msix)
16:21:12  Id 613   Add performance summary: Overall 6344 ms, Stage required 5328 ms, Registration 79 ms

# --- Immediately afterward: Get-AppxPackage *Claude* | Select Status ---
Status: Modified, NeedsRemediation

Notes

  • The "Repair" / "Reset" path offered by Windows does not durably fix it, because the package is re-corrupted whenever the app updates.
  • This looks related to the post-update crash reports on Windows MSIX (e.g. issues describing the app opening then dying in a loop right after an auto-update).
  • Likely root cause to investigate: the in-app updater modifying files inside the installed MSIX package directory, which invalidates MSIX integrity and triggers NeedsRemediation.

Workaround currently in use

Using Claude on the web (claude.ai) until a fixed desktop build ships.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.1

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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