A Windows user downloads the Claude desktop installer, clicks the executable, and encounters a message stating “installer corrupted” or “unsigned driver detected.” The installation halts. The browser version works fine on the same machine, but the desktop application—which offers faster performance, keyboard shortcuts, and seamless file management—remains inaccessible. This is not a rare edge case. Windows installation blockers stem from predictable causes: antivirus interference, missing administrator privileges, corrupted downloads, or security policy restrictions. Each has a specific diagnostic and resolution path.

The desktop application for Windows and macOS accelerates workflow by eliminating browser tab overhead and enabling offline-first file management, yet the installation process is also the first point where system-level settings can interfere. Understanding the structure of these errors, rather than retrying the installer or reinstalling Windows, saves time and restores access. A systematic diagnostic approach identifies the blocker within minutes and points to the correct fix.

Start with the download and file integrity

The first diagnostic step is to confirm that the downloaded installer is complete and uncorrupted. Many “installer corrupted” errors result not from a problem with Anthropic’s servers, but from incomplete file transfers, interrupted downloads, or filesystem errors during the download process. If a download was interrupted—due to a network disconnection, browser crash, or system sleep—the resulting .exe file will be incomplete and invalid, yet appear to exist in the Downloads folder.

Delete the current installer file completely. Open File Explorer, navigate to your Downloads folder, select the Claude installer, and press Delete. Then visit the official Anthropic download page to retrieve a fresh copy. Do not simply re-run the existing file. If your browser resumes downloads by default, ensure the download completes fully and shows a “download complete” notification before proceeding. For users with unstable connections, using a download manager with resume capability can prevent this blocker entirely.

A secondary check is to verify the file size after download. The Claude desktop installer is typically 150–200 MB in size. If the file you downloaded is significantly smaller (for example, under 50 MB), the download was interrupted. Delete it and download again. This simple verification prevents hours of troubleshooting misattributed to driver or permission issues when the actual problem is an incomplete file transfer. Only after confirming that the installer is the correct size should you proceed to the next diagnostic step.

Verify administrator privileges and UAC behavior

Claude desktop installation on Windows requires administrator-level privileges because the installer needs to write to protected system directories and, in some configurations, register drivers. If your user account lacks administrator rights, or if User Account Control (UAC) is blocking the installation silently, the error message may appear to reference file corruption when the actual cause is permission denial.

To verify your account privilege level, right-click the installer executable and select “Run as administrator” from the context menu. This forces a UAC prompt (if UAC is enabled) and grants elevated permissions for that single execution. If the installation proceeds without error after using “Run as administrator,” the issue was insufficient privileges on your standard user account. In that case, contact your system administrator if you do not have permission to elevate, or create a local administrator account if your device is personal.

If you still encounter an error even when running as administrator, make a note of the exact error message and proceed to the antivirus diagnostic. However, if the installation succeeds when run as administrator, you have confirmed the cause. For future ease, you can configure the installer to always run as administrator by right-clicking it, selecting Properties, navigating to the Advanced tab, and checking “Run this program as an administrator.” This avoids repeated UAC prompts for subsequent installations or updates.

Identify and temporarily disable security software interference

Windows Defender, third-party antivirus software, and behavioral detection tools often flag executable installers as suspicious because they perform system-level modifications. These tools may quarantine the installer, block file writes, or prevent the installer from launching—sometimes without displaying a clear notification to the user. The error message may then incorrectly reference file corruption or driver issues rather than stating that security software blocked the action.

Start by disabling antivirus scanning temporarily. In Windows Security (built-in Windows Defender), open Settings > Privacy & Security > Windows Security > Virus & threat protection. Click “Manage settings” and toggle off “Real-time protection” for 10 minutes. If you use third-party antivirus software such as Norton, McAfee, Kaspersky, or Avast, open its settings and select “Disable temporarily” or “Exit.” Allow the timer to expire (usually 10–15 minutes) rather than permanently disabling, as this is safer for your system.

Once antivirus is temporarily disabled, right-click the Claude installer and select “Run as administrator” again. Attempt the installation. If it succeeds, antivirus interference was the cause. After installation completes, re-enable your security software immediately. Then add Claude to your antivirus software’s exclusion list so future updates do not trigger the same block. In Windows Defender, this means navigating to Virus & threat protection > Manage settings > Add exclusions and selecting the Claude installation folder (typically C:\Users\[YourUsername]\AppData\Local\Claude or Program Files\Claude, depending on installation location).

Check system driver signing requirements and driver installation errors

An “unsigned driver” error is distinct from an “installer corrupted” error, and it indicates that Windows is blocking a driver component because it lacks Microsoft’s digital signature. Claude desktop sometimes installs auxiliary drivers for optimized performance or system integration, depending on your Windows version and hardware configuration. If Windows Secure Boot or driver signature enforcement is enabled—which is the default on modern Windows systems—an unsigned driver will be rejected.

Check your Secure Boot and driver signature enforcement status. Restart your computer and enter the BIOS or UEFI settings (typically by pressing F2, F10, F12, or Del during the boot screen, depending on your manufacturer). Look for options named “Secure Boot,” “UEFI Secure Boot,” or similar. If it is enabled, you have two choices: disable Secure Boot entirely (less secure, but permits unsigned drivers), or check whether Anthropic publishes a signed driver version for your Windows build and update your download. You can also learn more about verified Windows versions and driver compatibility by reviewing the system requirements on the official Anthropic site.

For many users, the simpler path is to disable Secure Boot if your organization’s policies permit it. After disabling Secure Boot in BIOS, save settings, exit, and allow the computer to restart. Then attempt the Claude installation again by right-clicking the installer and running as administrator. If the installation succeeds, Secure Boot enforcement was the blocker. For enterprise users or those in heavily managed environments, contact your IT department before modifying these settings; they may have specific driver and security policies that require coordination.

Clear the installer cache and resolve conflicting partial installations

If you have attempted the installation multiple times without addressing the root cause, temporary installation files and registry entries may accumulate, causing subsequent attempts to fail even after the original blocker is fixed. Windows installer (MSI) processes can also leave behind cached data that conflicts with fresh installations.

To clear the installer cache, open a Command Prompt as administrator. Press Windows+R, type “cmd”, right-click “Command Prompt” in the results, and select “Run as administrator.” Then type the following command and press Enter: `msiexec /unregister`. This clears the MSI cache. Next, navigate to the temporary files folder by typing `cd %temp%` and pressing Enter. Look for folders named something like “Claude” or beginning with an underscore followed by random characters. Delete these folders by typing `rmdir /s /q [FolderName]`. These temporary files are remnants of failed installations and do not affect the normal operation of Windows or other software.

If Claude was partially installed, you can also uninstall it cleanly before reinstalling. Go to Settings > Apps > Apps & features, search for “Claude,” click it, and select “Uninstall.” Follow the uninstall wizard completely. After uninstallation is finished, delete the main installation folder if it still exists: typically `C:\Users\[YourUsername]\AppData\Local\Claude`. Only after these cleanup steps should you download a fresh installer and attempt installation again, using the diagnostics above (administrator privileges and antivirus checks) to prevent recurrence.

Hardware resource and system compatibility checks

Rarely, installation failures on Windows can result from low disk space, insufficient RAM, or hardware incompatibility rather than software blockers. Claude’s cloud-based architecture means most processing occurs on Anthropic’s servers, so local hardware requirements are modest, but the installer itself and initial setup do require some resources.

Verify that you have at least 2 GB of free disk space on your C: drive (or wherever Windows is installed). Open File Explorer, right-click the drive, and select “Properties” to see free space. If free space is below 1 GB, delete unnecessary files or uninstall unused programs to free up capacity. The installer will fail or stall without sufficient space. Also check that your system has at least 4 GB of RAM available. If your system is running slowly or showing “low memory” warnings, close background applications and restart your computer before attempting installation again.

Finally, confirm your Windows version compatibility. Claude desktop runs on Windows 10 (version 1909 or later) and Windows 11. If you are running an older build of Windows 10, you may need to manually update Windows. Open Settings > Update & Security > Windows Update and click “Check for updates.” Install all available updates and restart. After updates complete, verify your Windows version by pressing Windows+R, typing “winver,” and confirming that your version number meets the minimum requirement.

Escalation and support when standard diagnostics do not resolve the issue

If you have worked through all of the above diagnostics—verified the download, run as administrator, disabled antivirus, checked Secure Boot, cleared the cache, confirmed hardware resources, and updated Windows—and the installation still fails, the issue may be specific to your system configuration or a rare hardware-software interaction. At this point, documentation of your steps and error messages becomes essential for support.

Record the exact error message by taking a screenshot or typing it down verbatim. Note your Windows version, antivirus software name, and any recent system changes (driver updates, Windows updates, new hardware). If the error occurs during installation, attempt to capture it again while a support representative observes if possible. Then contact Anthropic support with this information, or check the official installation guide to see if a workaround for your specific hardware configuration has been published.

An alternative approach for users who need immediate access is to use the web version of Claude through your browser. While the desktop application offers speed and convenience benefits—offline file management, keyboard shortcuts, and faster responsiveness—the browser version provides identical functionality and is unaffected by installation issues. You can continue using the web version while troubleshooting the desktop installation at a slower pace, ensuring no disruption to your workflow.