[BUG] Claude Desktop MSIX install fails 0x80073CF9 / 0x80070490 — orphaned StateRepository PackageFamily row (AtlasOS) — and where should Desktop/Cowork bugs actually be filed?
Preflight Checklist
- [x] This is a single bug report (please file separate reports for different bugs)
- [ ] I have searched existing issues and this hasn't been reported yet
- [ ] I am using the latest version of Claude Code
What's Wrong?
First, a question about process: I understand this repo is for Claude Code (CLI), and Desktop issues often get closed here as out-of-scope. But I genuinely can't find any other surface to report a Claude Desktop / Cowork bug — support.claude.com has no technical bug-report channel, and the in-installer error dialog just points back to "share this log." So I'm posting here for lack of anywhere else. Where are Claude Desktop and Cowork installer bugs supposed to be filed? If there's a correct channel, please point me to it and I'll move this. In the meantime, this is a real, reproducible blocker affecting AtlasOS users, and a previous identical report (#40682) was closed as invalid without a fix or a redirect.
The bug (independent reproduction of #40682):
Claude Desktop MSIX install fails instantly, every time, with HRESULT 0x80073CF9, inner error 0x80070490 ("Failure in the Evaluated state handler"). Root cause is an orphaned PackageFamily row for Claude_pzs8sxrjxfjjc in the StateRepository SQLite DB with no corresponding Package entry. Windows treats every fresh install as an update-over-missing-files and rejects it. AppXDeploymentServer Event ID 472 confirms Windows tries to move a non-existent package folder (0x80070002) on every attempt.
Environment:
OS: Windows 11 Pro 24H2, build 10.0.26100, x64 (AMD)
Debloat: AtlasOS applied (this is the common factor with #40682, whose reporter was on Canary 26200 + AtlasOS — different Windows build, same Atlas, same failure → points squarely at Atlas, not the Windows build)
Installer versions tried: 1.6608.2 (May), 1.9255.0 (late May), 1.15200.0 (today) — all fail identically
Plan: Max
Single physical drive (C: only) — no cross-volume redirection possible
Sideloading: enabled. Developer Mode: enabled (no effect). S Mode: false
Is elevated: true confirmed in log — not an admin issue (the installer's "Administrator access required" dialog is misleading; elevation succeeds, then AddPackage fails)
Log excerpt (Get-AppxLog):
605 Error 0x80070490: Failure in the Evaluated state handler.
472 Moving package folder ...\WindowsApps\Claude_1.15200.0.0_x64__pzs8sxrjxfjjc to ...\WindowsApps\Deleted\... Result: 0x80070002.
401 Deployment Add operation ... failed with error 0x80070490.
404 AppX Deployment operation failed ... with error 0x80073CF9.
Everything tried that did NOT fix it:
Get-AppxPackage -AllUsers Claude → nothing (ghost invisible to cmdlets)
Get-AppxPackage -AllUsers | ? PackageFamilyName -like "pzs8sxrjxfjjc" → nothing
Deleted %LOCALAPPDATA%\AnthropicClaude (old Squirrel) and %LOCALAPPDATA%\Packages\Claude_*
Created C:\Windows\AUInstallAgent with SYSTEM + Administrators Full Control
Get-ChildItem "C:\Program Files\WindowsApps" -Filter "Claude" -Force → nothing (no physical ghost)
Re-registered all packages (Get-AppxPackage -AllUsers | Add-AppxPackage -Register ...)
DISM /Online /Cleanup-Image /RestoreHealth → clean. sfc /scannow → no integrity violations
Multiple reboots
Enabled Developer Mode
Confirmed working: Microsoft Store opens and works; Get-Service vmms → Running; Get-Service AppXSvc → Running. So the MSIX subsystem and virtualization are both fine in general — only this specific orphaned Claude row blocks deployment.
Why this matters / suggested fix: Per #40682, even manual StateRepository-Machine.srd replacement doesn't resolve it, and the orphaned row is unreachable via standard tooling. This is a hard blocker for AtlasOS (and likely other debloated-Windows) users. A cleanup step in the installer that detects an orphaned PackageFamily row with no Package entry and removes it (or runs RemovePackage on the family) before AddPackage would fix this entire class of failure. Happy to provide full logs, run SQLite queries against the StateRepository, or test a patched installer.
What Should Happen?
The Claude Desktop installer should install Claude Desktop.
Error Messages/Logs
0x80070490
Steps to Reproduce
Try to install Claude desktop on an Atlas playbook Win11
Is this a regression?
No, this never worked
Platform
AMD X64 PC
Operating System
Windows
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗