Fixing the ANSI Output Bug in Freebuff on Windows
Many Windows users have encountered this ANSI output bug in Freebuff. If you're seeing raw escape sequences like the screenshot below, this guide should help.
James (Freebuff owner): If you happen to read this, please consider pinning this guide. This is one of the most common Windows issues, and having a single reference would make it much easier for users to find the solution.
Step 1 — Check Your PowerShell Version
If you're still using Command Prompt (cmd), I highly recommend switching to PowerShell. It provides significantly better terminal compatibility and ANSI support.
Open PowerShell and run:
$PSVersionTable.PSVersion
This command shows the version of PowerShell you're currently using.
Example:
If you're using Windows PowerShell 5.1, that's most likely the cause of the problem.
PowerShell 5.1 has limited ANSI/VT100 support, which may cause Freebuff to print escape sequences such as:
instead of displaying colored output correctly.
Step 2 — Install the Latest Version of PowerShell
Install the latest stable version of PowerShell using WinGet:
winget install --id Microsoft.PowerShell --source winget
At the time of writing (July 2026), this installs PowerShell 7.6.3.
If you're reading this later, simply install the latest available version rather than looking for a specific release number.
PowerShell 7 includes a modern terminal engine with much better ANSI support than Windows PowerShell 5.1.
Step 3 — Set PowerShell 7 as Your Default Terminal Profile
If you're using Windows Terminal, make PowerShell 7 your default profile.
Open:
Windows Terminal → Settings → Startup
Then change Default profile to PowerShell 7.
Save the settings and restart Windows Terminal.
If You Can't Set PowerShell 7 as the Default
Do not try to replace Windows PowerShell 5.1.
Windows PowerShell is a built-in Windows component, and replacing or modifying it can cause compatibility issues with Windows or other applications.
Instead, simply launch PowerShell 7 directly.
Search for:
or PowerShell 7
You can also launch it using Win + R:
Still Seeing the ANSI Bug?
If you've already switched to PowerShell 7 and you're still seeing ANSI escape sequences, the issue is most likely within Freebuff/Codebuff itself, not your terminal.
The developers are already aware of some Windows-specific ANSI rendering issues, so in that case you'll need to wait for a future update.
macOS & Linux
Most modern terminals on macOS and Linux already have excellent ANSI support.
If you're seeing this issue:
- Make sure your operating system is up to date.
- Update your terminal emulator to the latest version.
- Try running Freebuff from a different modern terminal (such as iTerm2, Ghostty, Kitty, or WezTerm).
- As a final troubleshooting step, try running Freebuff in PowerShell 7, which is available on Windows, macOS, and Linux.
If the issue still persists, it's most likely a Freebuff/Codebuff bug rather than a terminal issue.
Hopefully this guide saves someone a bit of time.
Fixing the ANSI Output Bug in Freebuff on Windows
Many Windows users have encountered this ANSI output bug in Freebuff. If you're seeing raw escape sequences like the screenshot below, this guide should help.
Step 1 — Check Your PowerShell Version
If you're still using Command Prompt (cmd), I highly recommend switching to PowerShell. It provides significantly better terminal compatibility and ANSI support.
Open PowerShell and run:
$PSVersionTable.PSVersionThis command shows the version of PowerShell you're currently using.
Example:
If you're using Windows PowerShell 5.1, that's most likely the cause of the problem.
PowerShell 5.1 has limited ANSI/VT100 support, which may cause Freebuff to print escape sequences such as:
instead of displaying colored output correctly.
Step 2 — Install the Latest Version of PowerShell
Install the latest stable version of PowerShell using WinGet:
At the time of writing (July 2026), this installs PowerShell 7.6.3.
If you're reading this later, simply install the latest available version rather than looking for a specific release number.
PowerShell 7 includes a modern terminal engine with much better ANSI support than Windows PowerShell 5.1.
Step 3 — Set PowerShell 7 as Your Default Terminal Profile
If you're using Windows Terminal, make PowerShell 7 your default profile.
Open:
Windows Terminal → Settings → Startup
Then change Default profile to PowerShell 7.
Save the settings and restart Windows Terminal.
If You Can't Set PowerShell 7 as the Default
Do not try to replace Windows PowerShell 5.1.
Windows PowerShell is a built-in Windows component, and replacing or modifying it can cause compatibility issues with Windows or other applications.
Instead, simply launch PowerShell 7 directly.
Search for:
or PowerShell 7
You can also launch it using Win + R:
Still Seeing the ANSI Bug?
If you've already switched to PowerShell 7 and you're still seeing ANSI escape sequences, the issue is most likely within Freebuff/Codebuff itself, not your terminal.
The developers are already aware of some Windows-specific ANSI rendering issues, so in that case you'll need to wait for a future update.
macOS & Linux
Most modern terminals on macOS and Linux already have excellent ANSI support.
If you're seeing this issue:
If the issue still persists, it's most likely a Freebuff/Codebuff bug rather than a terminal issue.
Hopefully this guide saves someone a bit of time.