Deploy Git Credential Manager (User) to Microsoft Intune
GitHubWindowsversion 2.9.1, 14 July 2026
Git Credential Manager (User) is in the PatchBee catalog as a Windows app from GitHub, synced from the Windows Package Manager community repository (winget). Pick it in the App Library and PatchBee writes the deployment plan below, builds the package, publishes it to your Intune tenant and assigns it to the Entra groups you choose. New versions then follow through your update rings.
Install from the command line
winget install --id Git.GCM -e --silentPatchBee runs the same silent install of Git Credential Manager (User) for you in Intune: the installer winget points at, verified, packaged with the switches and detection rule below, and published to your tenant.
The plan PatchBee writes
Git Credential Manager (User) as an Intune app
The standard form for a Inno Setup (x64, per machine). The real plan is generated from the installer when you package, and shown in full before anything is published; every field can be changed.
- Intune app type
- Windows app (Win32), .intunewin
- Install
- "GitCredentialManagerUser.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-
- Uninstall
- "unins000.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART
- Detection
- Registry: the Inno Setup uninstall key. Uninstall key {fdfae50a-1bc1-4ead-9228-1e1c275e8d12}}_is1, DisplayVersion 2.9.1 or newer.
- Requirements
- x86 (32-bit), x64, ARM64 · per user or per machine
Why these values: silent install switches and detection rules, explained.
Installers in version 2.9.1
| Architecture | Type | Scope | Hash |
|---|---|---|---|
| x86 (32-bit) | Zip archive | scope decided at plan time | SHA-256 published |
| x86 (32-bit) | Inno Setup | per user | SHA-256 published |
| x86 (32-bit) | Inno Setup | per machine | SHA-256 published |
| x64 | Zip archive | scope decided at plan time | SHA-256 published |
| x64 | Inno Setup | per user | SHA-256 published |
| x64 | Inno Setup | per machine | SHA-256 published |
| ARM64 | Zip archive | scope decided at plan time | SHA-256 published |
| ARM64 | Inno Setup | per user | SHA-256 published |
| ARM64 | Inno Setup | per machine | SHA-256 published |
PatchBee downloads the installer from the publisher's own URL and verifies its SHA-256 against the catalog before packaging. "None published" means the source carries no hash for this download, so that check has nothing to compare against; packaging still works.
About Git Credential Manager (User)
Git Credential Manager (GCM) is a secure Git credential helper built on .NET that runs on
Windows, macOS, and Linux. It aims to provide a consistent and secure authentication experience,
including multi-factor auth, to every major source control hosting service and platform.
GCM supports (in alphabetical order) Azure DevOps, Azure DevOps Server (formerly Team Foundation
Server), Bitbucket, GitHub, and GitLab. Compare to Git's built-in credential helpers (Windows:
wincred, macOS: osxkeychain, Linux: gnome-keyring/libsecret), which provide single-factor
- Publisher
- GitHub
- License
- MIT
- Source
- winget · Git.GCM
- Versions in catalog
- 5
How this becomes an app in your tenant
Sign in with your Microsoft work account and connect your Intune tenant once. Find Git Credential Manager (User) in the App Library, open its plan (the commands, detection rule and requirements above, editable) and publish: PatchBee downloads and verifies the installer, builds the package, creates the Intune app and assigns your groups. When GitHub ships a new version, PatchBee detects it and rolls it out through your rings, with supersedence and rollback.
Read the step-by-step guideMore Windows apps
Catalog data as of 11 October 2026, from the Windows Package Manager community repository (winget). The product re-reads the source every night and plans against the live catalog, so the version here may already be one behind. Nothing is published to a tenant without an administrator approving the plan.