Claude

For managed Windows deployments of Claude Desktop, treat the official desktop download path as a user-context/bootstrapper-style install rather than a conventional machine-wide MSI. Pilot required deployments separately from ordinary MSI packages, because the user-facing app may be delivered through package/MSIX-style setup and may not leave the same HKLM product-code evidence that traditional installers create.

If your management tool deploys as SYSTEM, validate the install in a signed-in user session before assigning it broadly: confirm the user can launch Claude Desktop, confirm whether local-admin rights are required in your environment, and record the actual installed-package or file/version evidence that appears after setup. Use that evidence for Intune/ConfigMgr detection so a failed bootstrapper run is not reported as a successful install.

For environments evaluating Claude desktop/Cowork features, do not assume an EXE bootstrapper can install every package-based component silently for all users. Keep detection and remediation scoped to the official Claude Desktop package that is actually installed on the target Windows build, then test updates in the same user context used for deployment.

Official sources: Claude Desktop downloads and Claude Desktop install documentation.