Skip to main content
Fix common issues related to system environment, shell, and dependencies.

PowerShell not recognized

Problem: Error message “PowerShell is not recognized as an internal or external command”. Solutions:
  • Windows users:
    • Add PowerShell to system PATH
    • Open Settings → System → About → Advanced system settings → Environment Variables
    • Add PowerShell path: C:\Windows\System32\WindowsPowerShell\v1.0\
    • Restart SoloEnt after changing PATH
  • Alternative:
    • Use Command Prompt (cmd) instead
    • Change default terminal in Settings
    • Reinstall PowerShell if missing

Command not found

Problem: Terminal shows “command not found” or similar errors. Solutions:
  • Verify the command/tool is installed on your system
  • Check if command is in system PATH
  • Restart terminal after installing new tools
  • Use full path to executable if needed
  • Install missing dependencies

Python/Node not found

Problem: Python or Node.js commands don’t work. Solutions:
  • Install Python from python.org or Node.js from nodejs.org
  • Verify installation: python --version or node --version
  • Add to PATH if installed but not recognized
  • Restart SoloEnt after installation
  • Check for version conflicts (multiple Python/Node versions)

Permission denied errors

Problem: “Permission denied” or “Access denied” errors. Solutions:
  • macOS/Linux:
    • Use sudo if appropriate
    • Check file permissions with ls -la
    • Grant Full Disk Access in System Settings
  • Windows:
    • Run SoloEnt as Administrator if needed
    • Check folder security settings
    • Disable User Account Control temporarily

Path with spaces causes errors

Problem: Commands fail when file paths contain spaces. Solutions:
  • Wrap paths in quotes: "C:\My Documents\project"
  • Use escape characters in terminal
  • Avoid spaces in project folder names
  • Use hyphens or underscores instead: my-project not my project

Git not available

Problem: Git commands don’t work or Git is not found. Solutions:
  • Install Git from git-scm.com
  • Verify installation: git --version
  • Add Git to system PATH
  • Restart terminal/SoloEnt after installation
  • Use GitHub Desktop as alternative

Environment variables not set

Problem: Application can’t find required environment variables. Solutions:
  • Set variables in system settings (not just terminal session)
  • Windows: System Properties → Environment Variables
  • macOS/Linux: Add to ~/.zshrc or ~/.bashrc
  • Restart SoloEnt after setting variables
  • Verify with echo $VARIABLE_NAME (Unix) or echo %VARIABLE_NAME% (Windows)

Shell compatibility issues

Problem: Commands work in one shell but not another. Solutions:
  • Check which shell you’re using: echo $SHELL
  • Switch to compatible shell (bash, zsh, PowerShell)
  • Configure default shell in SoloEnt settings
  • Use cross-platform commands when possible

System architecture mismatch

Problem: Tools or binaries incompatible with your system. Solutions:
  • Check system architecture: uname -m (Unix) or systeminfo (Windows)
  • Download correct version (x64, ARM64, etc.)
  • Use compatible alternatives
  • Enable Rosetta 2 on Apple Silicon Macs if needed

Antivirus blocking operations

Problem: Antivirus software interferes with SoloEnt operations. Solutions:
  • Add SoloEnt to antivirus whitelist/exceptions
  • Temporarily disable antivirus to test
  • Check antivirus logs for blocked actions
  • Contact antivirus support for proper configuration

Disk space issues

Problem: Operations fail due to insufficient disk space. Solutions:
  • Check available disk space
  • Clear temporary files and caches
  • Move project to drive with more space
  • Delete unnecessary files

Network/firewall issues

Problem: Cannot connect to API services or download updates. Solutions:
  • Check firewall settings
  • Allow SoloEnt through firewall
  • Configure proxy settings if behind corporate firewall
  • Test connection with different network
  • Contact IT department for enterprise environments
Many environment issues are resolved by restarting SoloEnt after making system changes like PATH updates or installing new tools.

Still having issues?

Reporting environment issues

When reporting environment problems, include:
  • Operating system: Windows 10/11, macOS version, Linux distribution
  • System architecture: x64, ARM64, Apple Silicon
  • Shell type: PowerShell, CMD, bash, zsh
  • Error messages: Full text of any errors
  • Steps taken: What you tried before reporting
This information helps us diagnose and resolve issues faster.