Claude Desktop Won’t Install? Windows & Mac Fixes That Worked (2026)

Claude Desktop Installation Troubleshooting: Fixes for Windows and Mac (2026)

Last checked: April 2026

📑Table of Contents

1. Claude Desktop Installation Troubleshooting: Fixes for Windows and Mac (2026)
2. Quick symptom dictionary
3. Start with this Windows troubleshooting order
4. Windows fixes
5. macOS flow: Gatekeeper, architecture, permissions
6. Shared failures: config JSON and Node.js
7. Frequently asked questions
8. Summary

Claude Desktop installation troubleshooting usually comes down to four causes: Windows MSIX conflicts, virtualization settings, macOS Gatekeeper blocks, or a broken claude_desktop_config.json. During our rollout in January and February 2026, I personally hit 0x80073D28, 0x80073CFA, Cowork virtualization errors on Windows 11 Pro, and later a Store redirect caused by a broken app registration.

The practical fix order is simple. On Windows, clean up Appx registrations and leftover package folders first, then check virtualization. On macOS, start with Gatekeeper, architecture, and permissions. This guide combines official Claude Help Center documentation with community fixes from GitHub issue #28892 and Reddit, plus what actually worked in our team deployment.

If you have not downloaded the app yet, start with the official Claude download page. The baseline setup steps are in Installing Claude Desktop. If you need a Linux fallback, the CLI vs Web vs Desktop comparison is the right next read.

Quick symptom dictionary

Symptom	HRESULT / Error	Primary cause	First fix	Section
Trusted app installs must be enabled	–	Developer Mode disabled	winget install Anthropic.Claude	Windows #1
Install fails	0x80073D28 / 0x80073CFA	Old package leftovers	Remove Appx + ProgramData leftovers	Windows #2
Install fails	0x80073CF3	Dependency or registration damage	--force reinstall	Windows #2
Cowork will not start	Virtualization is not available	BIOS or Windows virtualization missing	Enable VT-x / SVM + Hypervisor	Windows #3
Installer opens Microsoft Store	claude:// handler missing	Protocol registration broken	Reinstall or pin older version	Windows #5
Cowork tab missing / VM fails	0x80370102 and similar	Hypervisor or VM bundle issue	bcdedit /set hypervisorlaunchtype auto	Windows #4
App is Damaged / blocked at launch	–	Gatekeeper	Open Anyway / remove quarantine	macOS #1
Blank or slow UI	–	Cache corruption or Intel build	Clear cache / reinstall arm64 build	macOS #2-3

Sources: Claude Help Center, Deploy Claude Desktop for Windows, GitHub issue #28892, Reddit r/ClaudeAI (checked April 2026)

---

Start with this Windows troubleshooting order

If you are on Windows, use this order before you chase edge cases. It saved us the most time during rollout.

1. Reboot and make sure no Claude process is still running
2. Remove existing Appx registrations from an elevated PowerShell
3. Delete C:\ProgramData\Packages\Claude_* and %LOCALAPPDATA%\Temp\Claude-*.msix
4. Check older versions with winget show --id Anthropic.Claude --versions and install a stable build if needed
5. Only if Store redirects or Cowork corruption remain, use PsExec as the last resort for CoworkVMService

Get-AppxPackage -Name "*Claude*" -AllUsers | Remove-AppxPackage -AllUsers
winget show --id Anthropic.Claude --versions
winget install --id Anthropic.Claude --version 1.1.4173 --force --accept-package-agreements --accept-source-agreements

---

Windows fixes

#1 Developer Mode block

This is the most common Windows installation blocker. Claude Desktop ships as an MSIX package, and Windows treats it as a sideloaded app unless it comes from the Microsoft Store.

In our rollout, Developer Mode was locked on several managed devices. The fastest workaround was not policy escalation. It was using winget directly.

winget install Anthropic.Claude --accept-package-agreements --accept-source-agreements

---

#2 MSIX conflicts and leftover package folders

The first real breakage we hit was 0x80073D28 and 0x80073CFA. In both cases, the winning fix was removing all Appx registrations and then deleting leftover package folders under C:\ProgramData\Packages\Claude_*.

If you see 0x80073CF3, treat it as the same family of problem. Remove the old installation first, then reinstall with --force.

Get-AppxPackage -Name "*Claude*" -AllUsers | Remove-AppxPackage -AllUsers
rmdir /s /q "%LOCALAPPDATA%\AnthropicClaude"
rmdir /s /q "%APPDATA%\Claude"
del /q "%LOCALAPPDATA%\Temp\Claude-*.msix"

If Windows refuses to delete the ProgramData folder, close all Claude processes first. If the folder is still locked, use Sysinternals handle.exe or Process Explorer to find the locking process.

---

#3 Virtualization is not available

On our Windows 11 Pro 23H2 test machine, Cowork would not start until both Windows features and BIOS virtualization were enabled. The exact labels we saw in BIOS were Intel Virtualization Technology and VT-x on Lenovo ThinkPad and Dell Latitude hardware.

Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -All
Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -All
bcdedit /set hypervisorlaunchtype auto

Some of our test devices also behaved better with WSL2 enabled. On Home edition, we stayed with Virtual Machine Platform and Windows Hypervisor Platform. On Pro, Hyper-V was also viable.

---

#4 Cowork tab missing or VM will not launch

If installation succeeds but Cowork is missing, look at Windows edition, hypervisor startup, and corrupted VM bundles. That is where we found most post-install failures.

bcdedit /set hypervisorlaunchtype auto
rmdir /s /q "%APPDATA%\Claude\vm_bundles"

If you mainly need the app itself, not Cowork, it is still worth getting Desktop running first. For the broader product split, see the Claude autonomous agent features guide.

---

#5 Broken claude:// handler and downgrade strategy

GitHub issue #28892 surfaced a different failure mode: the app’s claude:// protocol handler was not registered, so Windows kept redirecting users to Microsoft Store. That is not the same issue as a silent launch failure.

winget show --id Anthropic.Claude --versions
winget install --id Anthropic.Claude --version 1.1.4173 --force --accept-package-agreements --accept-source-agreements

The tradeoff matters. Older builds like 1.1.4173 can get Desktop installed, but they do not include newer Cowork capabilities. In practice, this means “get the app working first, wait on Cowork later.” That was still the best move for machines where the current build repeatedly failed.

If the problem survives reinstall attempts, the last-resort community fix is PsExec with SYSTEM privileges to remove the broken CoworkVMService registration:

PsExec.exe -i -s cmd.exe
whoami
reg delete HKLM\SYSTEM\CurrentControlSet\Services\CoworkVMService /f

Use this carefully and preferably with IT involvement on managed machines. It is not the normal official support path.

---

macOS flow: Gatekeeper, architecture, permissions

Mac problems were much lighter in our experience. The winning order was always the same: clear the launch block, verify the correct build, then grant the right permissions.

1. Check Gatekeeper and use Open Anyway if needed
2. Confirm you are on the arm64 build if you use Apple Silicon
3. If the app is blank, clear Cache and vm_bundles
4. If MCP or Computer Use fails, grant Accessibility, Screen Recording, and Full Disk Access

#1 Gatekeeper block

On macOS Sequoia 15, we saw a first-launch block that was resolved by opening Claude from Privacy & Security. If that does not appear, remove the quarantine flag and try again.

xattr -d com.apple.quarantine /Applications/Claude.app
brew install --cask claude

---

#2 Blank UI, wrong build, and MCP permissions

We also ran into the classic Apple Silicon mistake: installing the Intel build on an arm64 machine. Reinstalling the native build fixed the startup lag immediately. On a separate machine, MCP only started working after enabling Screen Recording and Accessibility.

rm -rf ~/Library/Application\ Support/Claude/Cache
rm -rf ~/Library/Application\ Support/Claude/vm_bundles
brew install --cask claude

After granting permissions, restart the app. If you need the security angle explained for teammates, the Claude security settings guide is a good companion article.

---

Shared failures: config JSON and Node.js

The fastest way to diagnose a sudden post-install launch failure is to test claude_desktop_config.json. A single JSON syntax error can stop the app cold on both platforms.

ren "%APPDATA%\Claude\claude_desktop_config.json" "claude_desktop_config.json.bak"

On Windows, the file lives in %APPDATA%\Claude\claude_desktop_config.json. On macOS, it is in ~/Library/Application Support/Claude/claude_desktop_config.json. Validate the file before restoring it.

If MCP servers still fail, check Node.js and npx. Desktop apps do not always inherit your terminal PATH, which is why MCP can work in CLI but fail in Desktop. The broader version tradeoffs are in the CLI, Web, and Desktop comparison.

---

Frequently asked questions

Q1. Claude Desktop suddenly stopped launching. Where should I look first?

Start with claude_desktop_config.json, then look for MSIX leftovers, then check for multiple stuck processes. On Windows, Appx cleanup is usually the best first reset. On macOS, cache cleanup is often enough.

Q2. Why does the installer redirect me to Microsoft Store?

The claude:// protocol handler may be broken. Remove the existing package registration, reinstall, and if needed pin an older build with winget.

Q3. Are PowerShell and PsExec safe?

PowerShell is standard Windows tooling. PsExec is much more powerful because it can run as SYSTEM, so treat it as a last-resort repair tool. On managed devices, involve IT before you use it.

Q4. Why does Windows still think Claude is installed after I removed it?

You probably still have Appx registration data or a leftover C:\ProgramData\Packages\Claude_* folder. Remove both before reinstalling.

Q5. Where can I monitor current known issues?

Watch anthropics/claude-code issues, r/ClaudeAI, the release notes, and the status page.

Q6. What should Linux users do?

There is no native Claude Desktop build for Linux as of April 2026. Use Claude Code CLI instead.

---

Summary

From our rollout experience, the most common blocker was Windows MSIX conflict, not the installer itself. Appx cleanup plus a forced winget reinstall solved more machines than anything else. On Mac, most friction came from permissions and build selection, not deep system breakage.

If you are still stuck after the steps above, gather your OS version, exact error code, and the commands you already ran, then compare them against Deploy Claude Desktop for Windows and the official install guide.