CodeFrog
Windows Troubleshooting
← Back to CodeFrog

Windows Troubleshooting

This guide helps you resolve common issues when using CodeFrog on Windows.

Missing DLL Errors

libgmp-10.dll Missing

Problem: CodeFrog shows an error about missing libgmp-10.dll when running code analysis.

Error Message:

OpenGrep binary failed to start: Missing required DLL (libgmp-10.dll)

Solution:

  1. Check DLL Location
    • The DLL should be in the same directory as opengrep.exe
    • Expected location: {CodeFrog Data Directory}\binaries\opengrep\libgmp-10.dll
    • Check if the DLL file exists alongside the executable
  2. Re-extract Binaries
    • CodeFrog should automatically extract required DLLs when extracting the OpenGrep binary
    • If DLLs are missing, try:
      • Close CodeFrog completely
      • Delete the binaries cache folder (usually in AppData)
      • Restart CodeFrog - it will re-extract binaries and DLLs
  3. Manual DLL Installation (if automatic extraction fails)
    • Download libgmp-10.dll from MinGW-w64: https://www.mingw-w64.org/downloads/
    • Or download from a trusted source
    • Place the DLL in the same directory as opengrep.exe
    • Ensure the DLL version matches your system architecture (32-bit or 64-bit)
  4. Verify Other Required DLLs
    • OpenGrep may also require:
      • libstdc++-6.dll
      • libgcc_s_seh-1.dll
    • These should be extracted automatically with the binary
    • If missing, download from MinGW-w64 and place in the same directory

Other DLL Errors

Problem: Other DLL-related errors when running CodeFrog tools.

Solutions:

Windows Store Issues

Installation Problems

Problem: CodeFrog won’t install from Microsoft Store.

Solutions:

Update Issues

Problem: CodeFrog won’t update from Microsoft Store.

Solutions:

Permission Issues

Problem: CodeFrog requests permissions but they’re not granted.

Solutions:

File Permissions

Access Denied Errors

Problem: “Access Denied” when trying to access files or folders.

Solutions:

  1. Check Folder Permissions
    • Right-click the folder → Properties → Security tab
    • Ensure your user account has “Full control” or “Modify” permissions
    • Click “Edit” to change permissions if needed
  2. UAC Settings
    • Lower UAC settings may help (not recommended for security)
    • Settings → Accounts → Family & other users → Change account type
  3. Run as Administrator (temporary workaround)
    • Right-click CodeFrog → Run as administrator
    • Not recommended for regular use due to security concerns
  4. Move Project Folder
    • Move your project to a location with standard permissions (e.g., C:\Users\YourName\Documents\Projects)
    • Avoid system-protected folders

Long Path Issues

Problem: “Path too long” errors when accessing files.

Solutions:

  1. Enable Long Path Support (Recommended)
    • Run PowerShell as Administrator
    • Execute: New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force
    • Restart your computer
    • See Windows Setup Guide for detailed instructions
  2. Move Project to Shorter Path
    • Move project to a shorter path (e.g., C:\Projects instead of C:\Users\YourName\Documents\GitHub\VeryLongProjectName)
    • Update any references to the old path
  3. Use UNC Paths (for network drives)
    • Use \\Server\Share\Path format for network locations
    • Note: UNC paths have their own length limits

SSH Connectivity

OpenSSH Not Installed

Problem: CodeFrog can’t connect via SSH because OpenSSH is not available.

Solutions:

  1. Install OpenSSH Client
    • Open Settings → Apps → Optional Features
    • Click “Add a feature”
    • Search for “OpenSSH Client”
    • Install it
  2. Install via PowerShell (as Administrator) 
    Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
  3. Verify Installation 
    ssh -V
    • Should display version information

SSH Connection Failures

Problem: Cannot connect to localhost or remote servers via SSH.

Solutions:

  1. Check OpenSSH Server (for localhost connections) 
    Get-Service sshd
    • Should show “Running” status
    • If not running: Start-Service sshd
    • Set to auto-start: Set-Service -Name sshd -StartupType 'Automatic'
  2. Install OpenSSH Server (if not installed) 
    Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
Start-Service sshd
Set-Service -Name sshd -StartupType 'Automatic'
  3. Check Windows Firewall
    • Open Windows Security → Firewall & network protection
    • Ensure “OpenSSH SSH Server” is allowed
    • If not, click “Allow an app through firewall” and enable OpenSSH Server
  4. Test SSH Connection 
    ssh localhost
    • Should connect (may require password or key)
  5. Check SSH Service Status 
    Get-Service sshd | Select-Object Status, StartType

SSH Key Issues

Problem: SSH authentication fails even with correct credentials.

Solutions:

  1. Check SSH Key Location
    • User keys: C:\Users\YourUsername\.ssh\
    • Ensure private key is named id_rsa or id_ed25519
    • Public key should be id_rsa.pub or id_ed25519.pub
  2. Verify Key Permissions
    • Private key should have restricted permissions
    • Right-click private key → Properties → Security
    • Remove all users except your account
    • Ensure only you have “Full control”
  3. Generate New SSH Key (if needed) 
    ssh-keygen -t ed25519 -C "your_email@example.com"
    • Follow prompts to create new key pair
  4. Add Public Key to Server
    • Copy public key content
    • Add to server’s ~/.ssh/authorized_keys file

Terminal Configuration

Terminal Not Starting

Problem: Terminal doesn’t open or shows errors in CodeFrog.

Solutions:

  1. Check OpenSSH Installation
    • Ensure OpenSSH Client is installed (see SSH Connectivity section)
  2. Verify Terminal Application
    • Windows Terminal (recommended): Available from Microsoft Store
    • PowerShell: Pre-installed on Windows 10/11
    • Command Prompt: Pre-installed
  3. Check PATH Environment Variable
    • Press Win + X → System → Advanced system settings → Environment Variables
    • Verify PATH includes: C:\Windows\System32\WindowsPowerShell\v1.0\
    • Also check: C:\Windows\System32\
  4. Test Terminal Manually
    • Open PowerShell or Command Prompt directly
    • If it works outside CodeFrog, the issue may be with CodeFrog’s terminal integration
    • Try restarting CodeFrog

PowerShell Issues

Problem: PowerShell commands don’t work or show errors.

Solutions:

  1. Check Execution Policy 
    Get-ExecutionPolicy
    • Should be “RemoteSigned” or “Unrestricted”
    • If “Restricted”, change it: 
      Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
  2. Update PowerShell
    • Install PowerShell 7+ from Microsoft Store or GitHub
    • PowerShell 7 is more modern and compatible
  3. Check PATH Configuration
    • Ensure PowerShell is in your PATH
    • Default location: C:\Windows\System32\WindowsPowerShell\v1.0\

Windows Terminal Issues

Problem: Windows Terminal doesn’t work or isn’t detected.

Solutions:

  1. Install Windows Terminal
    • Download from Microsoft Store
    • Or from: https://aka.ms/terminal
  2. Set as Default
    • Open Windows Terminal
    • Settings → Startup → Default profile
    • Choose PowerShell or Command Prompt
  3. Check Installation
    • Windows Terminal should be in: C:\Users\YourUsername\AppData\Local\Microsoft\WindowsApps\
    • Verify it’s accessible from Start menu

Multi-Window Management

Windows Not Opening

Problem: New windows don’t open when using “File → New Window”.

Solutions:

  1. Check Window Limits
    • CodeFrog may have limits on number of open windows
    • Close some windows and try again
  2. Restart CodeFrog
    • Close all CodeFrog windows
    • Restart the application
    • Try opening a new window
  3. Check System Resources
    • Open Task Manager (Ctrl + Shift + Esc)
    • Check memory and CPU usage
    • Close other applications if resources are low

Window Management Issues

Problem: Windows behave unexpectedly or don’t respond.

Solutions:

  1. Window Focus Issues
    • Click on the window to bring it to focus
    • Use Alt + Tab to switch between windows
    • Check if window is minimized
  2. Window Positioning
    • Drag windows to reposition
    • Use Win + Arrow keys to snap windows
    • Reset window layout in CodeFrog settings
  3. Multiple Monitors
    • Ensure windows aren’t on disconnected monitors
    • Use Win + Shift + Arrow keys to move windows between monitors

Chrome Detection Issues

Problem: CodeFrog can’t detect Chrome for web testing.

Solutions:

  1. Check Chrome Installation
    • Verify Chrome is installed in default location:
      • C:\Program Files\Google\Chrome\Application\chrome.exe
      • C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
    • Or user installation:
      • C:\Users\YourUsername\AppData\Local\Google\Chrome\Application\chrome.exe
  2. Reinstall Chrome
    • Uninstall Chrome completely
    • Download and reinstall from: https://www.google.com/chrome/
    • Install to default location
  3. Check PATH
    • Chrome should be accessible from PATH
    • Or CodeFrog should detect it automatically
  4. Manual Chrome Path
    • Some CodeFrog features may allow manual Chrome path specification
    • Check settings for Chrome path configuration

General Issues

CodeFrog Won’t Start

Solutions:

Performance Issues

Solutions:

Crashes or Freezes

Solutions:

Getting More Help

If you’re still experiencing issues:

  1. Check Other Guides
  2. Collect Information
    • Note the exact error message
    • Check CodeFrog logs (if available)
    • Note what you were doing when the issue occurred
    • Check Windows Event Viewer for system errors
  3. Contact Support
    • Visit CodeFrog support website
    • Include error messages and steps to reproduce
    • Mention you’re using Windows and include your Windows version

Next Steps