From 4b3e84e1e1f9d9117aef00ce7420dd30360030ca Mon Sep 17 00:00:00 2001 From: nordicnode Date: Tue, 16 Jun 2026 18:13:51 -0700 Subject: [PATCH] fix(windows): add UTF-8 BOM to PowerShell scripts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes #19 PowerShell 5.1 on Windows defaults to the system ANSI codepage when parsing .ps1 files and misreads the UTF-8 multibyte sequences used in the banner (━, ·, ║, etc.). Without a BOM the parser corrupts these bytes, producing cascading parse errors: Unexpected token '}' in expression or statement. The string is missing the terminator. Missing closing '}' in statement block or type definition. Adding a UTF-8 BOM (EF BB BF) tells PowerShell to decode the file as UTF-8, resolving the parse errors. The reporter confirmed this on Windows 11. Applied to both setup.ps1 and uninstall.ps1. The file body is unchanged — only the 3-byte BOM was prepended. --- setup.ps1 | 2 +- uninstall.ps1 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/setup.ps1 b/setup.ps1 index d08a62c..2bfa9a1 100644 --- a/setup.ps1 +++ b/setup.ps1 @@ -1,4 +1,4 @@ -<# +<# .SYNOPSIS TorBox Media Server - All-in-One Setup Script Automated setup for a debrid-powered media server using Docker on Windows diff --git a/uninstall.ps1 b/uninstall.ps1 index 9131b7f..3e09dcc 100644 --- a/uninstall.ps1 +++ b/uninstall.ps1 @@ -1,4 +1,4 @@ -<# +<# .SYNOPSIS TorBox Media Server - Uninstall Script Removes all containers, configs, and data on Windows.