The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →You can deploy Git for Windows as a managed Win32 application from the Microsoft Intune Enterprise App Catalog—without building an .intunewin package—if the package is available in your tenant. In the Intune admin center, create a Windows Enterprise App Catalog app, search for the current Git package, retain its preconfigured commands and detection rules, then assign it to a pilot group before wider deployment.
This procedure installs the Git for Windows distribution (Git, Git Bash, Git GUI and Windows integrations), not GitHub Desktop. Catalog availability, package architecture, language and version must be checked live because they can vary by tenant and change over time.
Before you begin
- An Intune tenant with Windows devices enrolled and managed.
- Enterprise Application Management access. Microsoft lists it as a $2 per user per month annual add-on requiring Intune Plan 1, while it is also included in Intune Suite; qualifying Microsoft 365 licenses may include selected advanced Intune capabilities. Check your tenant’s entitlement at Microsoft Intune pricing.
- Permission to create and assign applications, plus a user or device group for testing.
- Managed 64-bit Windows devices, unless you have confirmed that the selected package supports another architecture. Microsoft’s catalog documentation identifies 64-bit managed Windows support; the package’s Requirements page is authoritative.
- Internet access to Microsoft-hosted application content, including the catalog infrastructure under
*.manage.microsoft.com. - A pilot device or group and a decision about what to do with existing per-user or machine-wide Git installations.
Git for Windows is separate from GitHub Desktop, Git LFS and GitHub CLI. LFS or CLI availability must be validated separately for your selected package and developer workflow. The upstream installer and release information are at git-scm.com/install/windows.
Confirm that Git is in your tenant’s catalog
Do not assume that an article, a different cloud or another tenant exposes the same package. Verify the live catalog first.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
- Sign in to the Intune admin center.
- Open Apps, then All Apps, and select Create.
- Choose Windows platform.
- Choose Enterprise App Catalog app, then select Select.
- On App information, select Search the Enterprise App Catalog.
- Search for
GitandGit for Windows. Try the publisher shown by the catalog if a publisher filter is available. - Compare the package name, publisher, language, architecture and version. Select the newest approved variant that matches your devices.
If no suitable entry appears, confirm Enterprise Application Management licensing and search terms, then check the catalog again later. Microsoft accepts requests for additions but provides no guaranteed timeline. Use a custom Win32 app as the interim method.
Add the Git package
1. Accept the catalog metadata
After selecting a package, Intune populates the application information. Review the name, description, publisher, version, category, information URL, privacy URL (if present) and logo. Keep Microsoft’s values unless you have a specific administrative reason to change them; catalog metadata is validated for that package.
2. Keep the supplied program settings
On Program, Intune normally supplies the install command, uninstall command, install behavior, restart behavior and return codes. Keep those values and leave the installer type as Command line. Do not copy a command from the Git website: the catalog may use a particular installer build, wrapper or syntax. Microsoft warns that unnecessary changes can cause installation or update failures. A Win32 installation must run silently; interactive prompts and dialogs are not supported. See Microsoft’s catalog app procedure and Win32 app guidance.
For a machine-wide developer-tool deployment, use System installation behavior when that is what the selected package specifies. Test the result on a clean device before changing context.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors3. Review requirements
Check the prefilled architecture, minimum operating-system version, disk space, memory, CPU and any additional rules. Do not loosen a requirement just to make a device eligible. A 32-bit device or an unsupported Windows edition may require another package or a custom deployment.
4. Retain detection rules
Detection determines whether Intune considers Git installed and whether an update is needed. Keep the catalog-provided rule by default. A file can exist while detection fails if it is in a different context or location; conversely, an overly broad rule can report success for an old or unrelated installation.
5. Apply scope tags when needed
Scope tags limit which delegated administrators can view or manage the app. Use them for business-unit, geography or support-team administration; otherwise leave them unchanged.
6. Review and create
Review app information, program settings, requirements, detection, scope tags and assignments, then select Create.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChoose an assignment strategy
| Assignment | Result | Best use |
|---|---|---|
| Required | Installs automatically for targeted users or devices | Approved standard image or developer-device baseline |
| Available for enrolled devices | Shows in Company Portal for user-initiated installation | Pilot, optional developer tooling or staged validation |
| Uninstall | Removes Git from targeted users or devices | Retirement or removal of unmanaged copies after testing |
A practical rollout is to assign Available to a pilot, validate Git Bash, PATH, credential helpers and IDE integrations, then move the approved group to Required. Prefer device targeting and system context when Git must be present for every user. A user-targeted machine-wide install can fail for a standard user who lacks device-administrator rights.
Verify the installation
Monitor the app’s Overview, device and user installation status, per-device status and Managed Apps reports. The Enterprise App Catalog training module covers monitoring at Microsoft Learn.
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
On a test device, open a new PowerShell session and run:
git --version
where.exe git
Test-Path "C:Program FilesGitcmdgit.exe"
Test-Path "C:Program FilesGitbingit.exe"
git config --global --listThe common paths are validation examples, not guarantees. Close and reopen terminals after installation so a new PATH is loaded. Verify the shell and context in which developers will work. A successful Git command does not configure repository permissions, SSH keys, tokens or hosted-provider authentication.
Understand versions and updates
The upstream Git release and the Intune catalog version are separate. The Git for Windows page showed Git 2.55.0, with x64 build 2.55.0(3) released July 14, 2026, when checked for this article; your catalog may expose an older or different build.
When a newer catalog package appears, use the available catalog update workflow or create a new app and configure supersedence. Pilot it, decide whether the previous version should be uninstalled, and expand assignments after validation. Catalog updates are not automatically deployed merely because an upstream release exists. Microsoft says most catalog updates complete automated validation within 24 hours, while manually tested updates can take up to seven days; these are service objectives, not guarantees. See Enterprise App Catalog update guidance. Custom PowerShell scripts are not automatically carried into a superseding app.
Troubleshoot common failures
Git is not listed
- Search both
GitandGit for Windowsand inspect the publisher. - Confirm Enterprise Application Management access and the correct cloud environment.
- If the package is absent, request it through Microsoft’s feedback process and deploy a custom Win32 package meanwhile.
Installation remains pending
Check the device’s last check-in, assignment inclusion and exclusions, storage, network access, Delivery Optimization and whether another installation is occupying the Intune Management Extension. Microsoft says the extension checks for new Win32 assignments about hourly or after a service/device restart; see Win32 deployment documentation.
Standard-user deployment fails
Machine-wide installation may require elevated rights. Target devices and use the package’s system context rather than relying on a standard user’s permissions.
Recommended Free Tools
Git is installed but not recognized
Run where.exe git, inspect the actual installation path and reopen the terminal. Check whether Git was installed per-user, whether PATH integration was selected, and whether the shell uses a different environment context.
Detection fails although files exist
Record the installed version, executable path and installation context. Check for an older or per-user copy and collect Intune Management Extension logs before replacing the catalog rule. Changing catalog detection can disrupt upgrades.
An existing manual installation causes conflicts
Test clean devices, older and newer Git versions, per-user installs and machine-wide installs. Define whether Intune should preserve, upgrade, replace or remove unmanaged copies before broad assignment.
A Git upgrade changes developer behavior
Pilot changes to branch defaults, Credential Manager, PATH, bundled OpenSSH, Git Bash, hooks, CI scripts, SSH keys and IDE integrations. Installing Git does not guarantee that those workflows remain unchanged.
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
A custom script fails
If you replace catalog commands with a script, keep it within Microsoft’s 50 KB limit, install silently, return exit code 0 only on success, write useful output, test in the same context as Intune and follow Microsoft’s encoding guidance. Incorrect scripts or unsupported Graph modifications can break scripted catalog apps.
When a custom Win32 app is better
| Criterion | Enterprise App Catalog | Custom Win32 app |
|---|---|---|
| Packaging effort | Low | Higher; create an .intunewin package |
| Installer control | Limited | Full command, parameters and scripts |
| Detection | Microsoft-provided defaults | Administrator-defined |
| Version timing | Depends on catalog processing | Organization chooses the build |
| Best fit | Standard software with supported catalog metadata | Custom configuration, urgent releases or bespoke logic |
Choose a custom package when Git is unavailable, a specific build is required immediately, custom installer parameters or pre/post-install actions are essential, 32-bit devices must be supported, or multiple side-by-side versions are needed. Follow Microsoft’s Win32 packaging guidance.
Catalog alternatives
The Microsoft Store may be suitable if the required Git package and installation context are available, but Store assignment and update behavior differ; some Win32 Store apps require a user to initiate installation from Company Portal. Details are in Microsoft Store app deployment.
Git documents this winget command:
winget install --id Git.Git -e --source wingetwinget is useful for scripts and administrator-driven installs, but it does not by itself provide Intune targeting, managed-app inventory, deployment reporting, detection governance or rollback controls. Compare it with the managed lifecycle you require.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Frequently Asked Questions
Can Intune install Git for every user on a computer?
Yes, when the selected package supports machine-wide system installation. Target devices and validate the result on a clean test machine; a user-targeted install can fail for standard users without elevation.
Does installing Git for Windows install GitHub Desktop?
No. GitHub Desktop is a separate application. Git LFS and GitHub CLI also require separate validation or deployment.
Does Intune automatically update Git whenever Git releases?
No. A newer catalog package must be reviewed and deployed through the available update or supersedence workflow, unless an applicable auto-update capability is configured.
Do I need a Git license?
Git for Windows is open-source software. Your organization may still need Intune Enterprise Application Management or other Microsoft licensing, plus any separate repository-service subscriptions.
Can I customize the catalog install command?
Only when there is a documented requirement and you have tested the result. Microsoft recommends retaining the catalog-provided commands, requirements and detection settings.
Why does Intune report success but git –version fail?
The shell may have a stale PATH, Git may be installed in another user or system context, or the catalog detection rule may have matched a different installation. Reopen the shell and inspect with where.exe git.
The Bottom Line
Use the Enterprise App Catalog when your tenant exposes a suitable Git for Windows package and you want Microsoft-prepared packaging, detection and reporting. Verify the live package, preserve its defaults, deploy to a pilot, and promote only after testing PATH and developer workflows. If the catalog lacks the required build or control, a custom Win32 package is the more predictable choice.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
