Getting Started
Licensing
System Requirements
Command-Line Interface / Installing Forge / Troubleshooting Installation Problems
New to FORGE? Start a free 30-day trial

Troubleshooting Installation Problems

Updated on Oct 5, 2026

This article collects installation issues and verification steps for Forge. For platform-specific installation procedures, see Installing on Windows, Installing on macOS, and Installing on Linux. For additional installation cases, see Installation Issues.

Verify the download

Use GPG signatures and SHA256 checksums to confirm that a release asset is authentic and complete. The installers check SHA256 automatically. They don't check GPG signatures.

  1. Download the asset together with the checksum and key files:
bash
gh release download v<version> --repo telerik/forge \
 --pattern 'frg-<version>-x86_64-linux' --pattern 'frg-<version>-x86_64-linux.asc' \
 --pattern 'SHA256SUMS' --pattern 'SHA256SUMS.asc' --pattern 'public-key.asc'
  1. Import the Forge public key and check the signatures:
bash
gpg --import public-key.asc
gpg --verify SHA256SUMS.asc
gpg --verify frg-<version>-x86_64-linux.asc frg-<version>-x86_64-linux

Each command must report Good signature.

  1. Check the SHA256 checksum:
bash
sha256sum --check --ignore-missing SHA256SUMS # Linux
shasum -a 256 --check --ignore-missing SHA256SUMS # macOS

On Windows, compare the hash with the matching line in SHA256SUMS, and check the Authenticode signature:

powershell
Get-FileHash .\frg-<version>-x86_64-windows.exe -Algorithm SHA256
Get-AuthenticodeSignature .\frg-<version>-x86_64-windows.exe

On macOS, you can also check the code signature of the installed binary with:

bash
codesign --verify --verbose /usr/local/bin/frg

frg: command not found

Cause: The install folder isn't on your PATH, or the terminal started before the PATH changed.

Solution:

  1. Open a new terminal.
  2. Check where Forge is installed: ls -l /usr/local/bin/frg. On Windows, run Get-Command frg.exe.
  3. If the folder isn't on your PATH, add it to your shell profile, for example:
bash
echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.zshrc

Installation to C:\Program Files\Forge requires administrator privileges

Cause: You ran install.ps1 with the default install folder in a non-Administrator session.

Solution: Run PowerShell as Administrator, or install to your user profile:

powershell
.\install.ps1 -InstallDir "$env:LOCALAPPDATA\Programs\Forge"

No installable content found in Arch package

Cause: The v

Solution: Run the installer with --force-binary, or install the binary manually. See Installing on Linux.

Installer reports an unsupported platform (exit code 2)

Cause: Forge publishes builds for Linux x86_64 and aarch64, macOS x86_64 and aarch64, and Windows x86_64 only.

Solution: Check your platform with uname -s -m, or $env:PROCESSOR_ARCHITECTURE on Windows. On an unsupported platform, use a supported machine or container.

Both installers use these exit codes:

CodeMeaning
0Success
1General error, such as an invalid argument
2Unsupported platform
3Authentication failure
4Network or download failure
5Verification failure
6Installation failure, such as missing permissions

Checksum or signature verification fails

Cause: The download is incomplete or corrupted, or the asset doesn't match the signature or checksum file.

Solution:

  1. Delete the downloaded files and download them again from the same release.
  2. For GPG, import public-key.asc from that release before you run gpg --verify.
  3. If verification still fails, don't install the file. Report the problem to your Progress representative. Use --skip-verify or -SkipVerify only when you have verified the file another way.

PowerShell version error on Windows

Cause: install.ps1 doesn't run in Windows PowerShell 5.1. It needs PowerShell 7.

Solution: Install PowerShell 7 with winget install Microsoft.PowerShell, open pwsh, and run the installer again. To check your version, run $PSVersionTable.PSVersion.Major.

Download fails or hits GitHub API rate limits (exit code 3 or 4)

Cause: Anonymous GitHub API requests are rate limited, or a proxy or firewall blocks github.com.

Solution: Sign in with gh auth login, or set GITHUB_TOKEN before you run the installer. Then try again. Check that your network allows github.com and api.github.com.

Binary doesn't run, or is slow on Apple silicon

Cause: You installed the binary for a different architecture.

Solution: Compare uname -m with file "$(command -v frg)". On Apple silicon, the output should include arm64. Install the matching asset.

macOS blocks the binary

Cause: macOS Gatekeeper blocks a file downloaded in a browser. Forge binaries are signed and notarized, so this is rare.

Solution: Remove the quarantine attribute (the installer does this for you):

bash
xattr -d com.apple.quarantine /usr/local/bin/frg

Or open System Settings > Privacy & Security and select Open Anyway.

Windows Server policies block Forge

If SmartScreen, the execution policy, or Group Policy blocks Forge, see the Windows Server installation guidance in Installing on Windows.

Verify the installation

Open a new terminal and run:

bash
frg --version

Expected output for this release:

text
frg <version>

Inside a configured project, frg status checks your configuration and agent.

See Also

In this article
Verify the downloadfrg: command not foundInstallation to C:\Program Files\Forge requires administrator privilegesNo installable content found in Arch packageInstaller reports an unsupported platform (exit code 2 )Checksum or signature verification failsPowerShell version error on WindowsDownload fails or hits GitHub API rate limits (exit code 3 or 4 )Binary doesn't run, or is slow on Apple siliconmacOS blocks the binaryWindows Server policies block ForgeVerify the installationSee Also