Share via

Claude App Intune Packaging

Wilson Liew 0 Reputation points
2026-05-18T06:35:04.9+00:00

Hi All,

The admin attempted to package Claude Enterprise for Windows via Intune, but the installation failed on the devices.

Kindly refer to the installation script below for further checking.

===============================================

Claude non-admin installation script

$Installer = "Claude-Setup.exe"

$CurrentPath = Split-Path -Parent $MyInvocation.MyCommand.Path

$InstallerPath = Join-Path $CurrentPath $Installer

$LogPath = "$env:TEMP\ClaudeInstall.log"

Start-Transcript -Path $LogPath -Force

try {

    Write-Host "Starting Claude installation..."

    if (!(Test-Path $InstallerPath)) {

        Write-Host "Installer not found."

        exit 1

    }

    # Silent install

    Start-Process `

        -FilePath $InstallerPath `

        -ArgumentList "/S" `

        -Wait `

        -NoNewWindow

    Start-Sleep -Seconds 10

    # Verify installation

    $ClaudePath = "$env:LocalAppData\Programs\Claude\Claude.exe"

    if (Test-Path $ClaudePath) {

        Write-Host "Claude installed successfully."

        exit 0

    }

    else {

        Write-Host "Claude installation failed."

        exit 1

    }

}

catch {

    Write-Host $_.Exception.Message

    exit 1

}

finally {

    Stop-Transcript

}

======================================================

Screenshot 2026-05-18 at 14.29.05

Screenshot 2026-05-18 at 14.25.39Screenshot 2026-05-18 at 14.26.56

Thanks and regards

Wilson

Microsoft Security | Intune | Application management
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-05-18T06:35:30.27+00:00

    Error 0x80070001 is a generic installation failure. From the provided information, the key Intune‑specific checks and troubleshooting steps are:

    1. Verify that the Win32 app actually reaches the device
      • In the Microsoft Intune admin center, go to Apps > All apps > Claude > Device install status and confirm that the targeted devices show as Installed / Failed with the same error.
      • If the app does not appear on the device at all (for user‑group targeting), follow the guidance for user‑targeted apps:
        • Ensure the app is assigned with Available intent if it should appear in Company Portal.
        • For BYOD Windows devices, ensure the user has added a work account.
        • Confirm the user is not over the Microsoft Entra Maximum devices per user limit and remove stale device records if necessary.
    2. Use Intune Management Extension (IME) logs to see what fails
      • On an affected device, open C:\ProgramData\Microsoft Intune Management Extension\Logs and review the IME logs.
      • Follow the Win32 app flow:
        • Check that the app is discovered (ExecManager identifies app and intent).
        • Confirm dependencies and detection rules are evaluated.
        • Confirm content is downloaded to C:\Program Files (x86)\Microsoft Intune Management Extension\Content\Incoming and unzipped to C:\Windows\IMECache.
        • Look for the step where the installer is executed (the command that runs Claude-Setup.exe via the PowerShell script) and note the lpExitCode returned by the installer.
      • If lpExitCode is non‑zero, the failure is coming from the Claude installer or script, not Intune. Use that exit code and the transcript log ($env:TEMP\ClaudeInstall.log) to debug the script/installer.
    3. Validate detection rules
      • Intune may report failure even if the app installed, or success even if it did not, when detection rules are incorrect.
      • Confirm that the detection rule matches what the script checks (for example, file "$env:LocalAppData\Programs\Claude\Claude.exe").
      • If the app installs per‑user but the Win32 app is assigned in system context, adjust detection so it evaluates correctly for that context.
    4. Confirm installation on the device
      • On a target device, manually check Settings > Apps > Installed apps to see whether Claude is present.
      • Also check the expected installation directory (for example under C:\Program Files, C:\Program Files (x86), or the user’s LocalAppData\Programs folder) and try launching the app.
    5. If the script is user‑context only
      • If the Win32 app assignment is in user context but the app requires elevated permissions or device admin rights, the installation can fail. In that case, adjust the deployment so that the Intune Management Extension runs the installer in system context, or use an installer that supports non‑admin per‑user installation.

    After these checks, use the specific installer exit code and transcript log from the device to refine the script or installer parameters, then redeploy and re‑check the IME logs and Intune device install status.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.