Windows PowerShell 5.1 - Unicode Display Issues

[GordonBeeming]

Summary

Windows PowerShell 5.1 has limited Unicode character support, causing emojis and special box-drawing characters to display as ? instead of the intended symbols. This affects the visual appearance of the dependency check output and other UI elements.

Environment

• Windows PowerShell 5.1 (default on Windows 10/11)
• Console/terminal with limited Unicode font support

Steps to Reproduce

1. Run copilot_here or copilot_yolo in Windows PowerShell 5.1
2. Observe the dependency check output
3. Special characters display as ? instead of proper Unicode symbols

Example Output

?? Dependency Check:
????????????????????????????????????????????????????????????????
? GitHub CLI (gh)
   ?? Install: winget install --id GitHub.cli --source winget
? Docker
   ?? Install: https://docs.docker.com/desktop/install/windows-install/
????????????????????????????????????????????????????????????????

Expected Output

Should display with proper box-drawing characters and icons (as seen in PowerShell Core 7+).

Impact

• Severity: Low (cosmetic only)
• Functionality: Not affected - all features work correctly
• User Experience: Slightly degraded visual appearance

Workaround

Use PowerShell Core (PowerShell 7+) instead of Windows PowerShell 5.1:

# Install PowerShell Core
winget install --id Microsoft.PowerShell --source winget

# Or download from: https://aka.ms/powershell-release?tag=stable

[GordonBeeming]

Resolution: Won't Fix

Reason:

1. Easy Upgrade Available: PowerShell Core 7+ is free, officially supported by Microsoft, and recommended for modern Windows development
2. Not a Breaking Issue: All functionality works correctly; this is purely cosmetic
3. Windows PowerShell 5.1 Limitation: This is an inherent limitation of the older PowerShell version, not our codebase
4. Microsoft's Direction: Microsoft recommends PowerShell Core for new projects and cross-platform compatibility
5. Minimal Impact: Users can still use the tool successfully despite the visual difference

Note: We've already invested significant effort ensuring the tool functions correctly on Windows PowerShell 5.1 (handling regex patterns, encoding, etc.). Fixing the cosmetic Unicode display would require replacing all special characters with ASCII alternatives, reducing the UX for 99% of users who use modern shells.

Workaround

Use PowerShell Core (PowerShell 7+) instead of Windows PowerShell 5.1 for the full visual experience with proper Unicode character display.

Installation Options

Option 1: Using winget (Recommended)

winget install -e --id Microsoft.PowerShell --source winget

Option 2: Direct Download

• Download from: https://aka.ms/powershell-release?tag=stable
• Run the MSI installer

After Installation

1. Open PowerShell (not Windows PowerShell) from your Start menu
2. Run the copilot_here installation command again
3. Unicode characters will now display correctly ✨

Note

The functionality is NOT affected in Windows PowerShell 5.1 - only the visual display. All features work correctly despite the ? characters appearing instead of proper Unicode symbols.

[GordonBeeming]

Resolution

This issue has been FIXED as of version 2025.12.29.10 (or the next release after 2025.12.29.9).

What Changed

Added UTF-8 console output encoding to both:

• Native binary (Program.cs) - Sets Console.OutputEncoding = UTF8
• PowerShell script (copilot_here.ps1) - Sets [Console]::OutputEncoding = UTF8

Result

Unicode characters now display correctly in all Windows terminals:

• Windows PowerShell 5.1 ✅
• PowerShell Core 7+ ✅
• Windows Terminal ✅
• Command Prompt ✅

The dependency check output now shows proper Unicode characters (boxes, arrows, icons) instead of ? symbols.

For Users on Older Versions

If you're still seeing ? characters, update to the latest version:

# Update the shell functions
. "$env:USERPROFILE\Documents\PowerShell\copilot_here.ps1"
copilot_here --update

# Or reinstall from scratch
$scriptPath = "$env:USERPROFILE\Documents\PowerShell\copilot_here.ps1"; New-Item -ItemType Directory -Force -Path (Split-Path $scriptPath) | Out-Null; Invoke-WebRequest -Uri "https://github.com/GordonBeeming/copilot_here/releases/download/cli-latest/copilot_here.ps1" -OutFile $scriptPath; if (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Force -Path $PROFILE | Out-Null }; if (-not (Select-String -Path $PROFILE -Pattern "copilot_here.ps1" -Quiet -ErrorAction SilentlyContinue)) { Add-Content $PROFILE "`n. $scriptPath" }; . $PROFILE