Review prerequisites (IT)¶
The GitM installer detects .NET 4.8, Git, and Git LFS and aborts if any is missing. It does not install them. For a fleet rollout, get these onto machines first or your install will stop on the prerequisite screen.
The single-machine version of this page is Review prerequisites.
What the installer checks (and what happens if missing)¶
| Prerequisite | Check | If missing |
|---|---|---|
| .NET Framework 4.8 | Registry …\NDP\v4\Full Release ≥ 528040 |
Installer shows an error and exits. |
| Git for Windows | git --version |
Installer shows an error and exits. |
| Git LFS | git lfs version |
Installer shows an error and exits. |
The installer's [Files] and [Run] sections only deploy the add-in and run RegAsm — there
are no bundled vendor installers in the package.
Recommended fleet approach¶
Deploy the prerequisites with your existing software management before (or alongside) GitM:
- .NET Framework 4.8 — present on current Windows 10/11; include in your base image if not.
- Git for Windows — deploy silently, e.g.
Git-<ver>-64-bit.exe /VERYSILENT /NORESTART. This also provides Git Credential Manager (recommended auth). - Git LFS — deploy, then ensure
git lfs installhas run for the user context so LFS hooks are registered.
Verify on a machine:
git --version
git lfs version
Other requirements¶
- Windows 10/11, 64-bit.
- SolidWorks 2022–2025 installed.
- Administrator rights for the GitM install (writes COM + SolidWorks registry keys).
Expected result¶
- All three prerequisites report present on target machines, so GitM installs without hitting the abort screen.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| Mass install stops on the prerequisite error | Git/LFS/.NET not on the image. | Deploy prerequisites first; re-run GitM setup. |
| LFS check fails though Git is present | git lfs install not run in the user context. |
Run it per user, or via login script. |
Known limitations¶
- Not bundled — the PRD's bundled-silent-prerequisites design is unimplemented. Plan to provide Git/LFS/.NET through your own deployment. See Known limitations and discrepancies.