Modified, NeedsRemediation / PackageUserInformation

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?

Hi,

Claude Desktop consistently crashes on launch on my Windows 10 machine. I've done extensive diagnostics and have log files to attach.

Environment:

• OS: Windows 10 Enterprise, Build 19045 (19041.1.amd64fre.vb_release.191206-1406)
• App Version: 1.17377.2
• Electron: 42.5.1 / Chrome 148.0.7778.271 / Node 24.17.0
• Package: Claude_pzs8sxrjxfjjc
• WiFi adapter: Intel(R) Dual Band Wireless-AC 7260

Core issue found in logs (attached):
The app's internal Chromium network stack fails all startup API calls with net::ERR_NAME_NOT_RESOLVED - e.g.:

• "Health check fetch failed: Error: net::ERR_NAME_NOT_RESOLVED"
• "[account] Bootstrap API fetch failed: net::ERR_NAME_NOT_RESOLVED"
• "[growthbook] network error: net::ERR_NAME_NOT_RESOLVED"

This happens even though the OS-level network stack works fine (Test-NetConnection claude.ai -Port 443 succeeds, browser works normally, no proxy configured). This strongly suggests Claude's Electron/Chromium networking layer is failing to resolve DNS independently of the OS resolver.

After each crash, Get-AppxPackage shows the package status as "Modified, NeedsRemediation" - this appears to be a side effect of the crash occurring mid-write of session/account data, not a pre-existing corruption, since it recurs identically after every clean reinstall.

Steps already tried, all without resolving the issue:

1. Full uninstall/reinstall cycles (multiple times, across versions 1.17377.1.0 and 1.17377.2.0)
2. Deleted %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc and %LOCALAPPDATA%\AnthropicClaude before each reinstall
3. Disabled Windows Defender real-time protection, Controlled Folder Access, and Network Protection
4. Disabled Windows Firewall entirely
5. Confirmed no VPN or proxy in use (netsh winhttp show proxy: "Direct access, no proxy server")
6. Confirmed hosts file is clean
7. Ran sfc /scannow (no violations), DISM /Online /Cleanup-Image /RestoreHealth (completed successfully), chkdsk C: /f (disk healthy)
8. Reset Winsock (netsh winsock reset), reset TCP/IP stack (netsh int ip reset), flushed DNS - no change
9. Manually set DNS to 1.1.1.1/8.8.8.8 on the WiFi adapter and disabled IPv6 - no change
10. Disabled the Hyper-V vEthernet (Default Switch) virtual adapter in case it was intercepting routing - no change
11. Confirmed via Get-AppxPackage -AllUsers | Where-Object {$_.Status -ne "Ok"} that Claude is the ONLY package on the system with a non-Ok status
12. Confirmed this is a personal, non-managed device

Given that the OS network stack works correctly for every other application (including the browser) and only Claude's Electron process fails DNS resolution, and this reproduces identically across multiple clean reinstalls and network configurations, this looks like an application-level issue with this specific build rather than something fixable on my end.

I have full log zips (main.log, system-info.txt, and others) from two crash instances ready to attach. Please let me know if there's a known issue with this version on Windows 10, or what further diagnostics I can provide.

Thanks,
[Your name]

What Should Happen?

should work

Error Messages/Logs

Modified, NeedsRemediation / PackageUserInformation

Steps to Reproduce

install claude
and error comes on widows 10

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

5

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_