starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

RAR.exe (version 7.01 x64) won't start with the error "ERROR: '-' is expected in the beginning of: C:\Program Files\WinRAR\RAR.exe" from Command Prompt #22009

New Issue
Closed
opened 2026-01-31 08:00:47 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:00:47 +00:00
Owner
Copy Link

Originally created by @gschizas on GitHub (Jul 25, 2024).

Windows Terminal version

1.21.1772.0

Windows build number

10.0.22631.3880

Other Software

rar.exe version 7.01 x64 (from win-rar.com

Steps to reproduce

  1. Download WinRAR from https://www.win-rar.com/.
  2. Open Command Prompt
  3. Run "C:\Program Files\WinRAR\Rar.exe" (or cd "C:\Program Files\WinRAR" and then run Rar.exe)

Expected Behavior

Expected to see the help text (command line switches) for RAR.exe

Actual Behavior

I'm getting "ERROR: '-' is expected in the beginning of: C:\Program Files\WinRAR\RAR.exe"

Originally created by @gschizas on GitHub (Jul 25, 2024). ### Windows Terminal version 1.21.1772.0 ### Windows build number 10.0.22631.3880 ### Other Software rar.exe version 7.01 x64 (from [win-rar.com](https://www.win-rar.com/) ### Steps to reproduce 1. Download WinRAR from https://www.win-rar.com/. 2. Open Command Prompt 3. Run `"C:\Program Files\WinRAR\Rar.exe"` (or `cd "C:\Program Files\WinRAR"` and then run `Rar.exe`) ### Expected Behavior Expected to see the help text (command line switches) for RAR.exe ### Actual Behavior I'm getting "ERROR: '-' is expected in the beginning of: C:\Program Files\WinRAR\RAR.exe"
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:00:47 +00:00
claunia commented 2026-01-31 08:00:48 +00:00
Author
Owner
Copy Link

@gschizas commented on GitHub (Jul 25, 2024):

These combinations work:

  • Windows Terminal 1.20.11781.0 with any shell (Command Prompt (cmd.exe), Windows PowerShell (5), PowerShell (7))
  • Windows Terminal 1.21.1772.0 with any PowerShell (5 or 7)
  • Console Host with any shell (cmd.exe or PowerShell 5/7)

It's only the combination of Windows Terminal Preview (1.21.1772.0) with Command Prompt that doesn't work.

@gschizas commented on GitHub (Jul 25, 2024): These combinations work: * Windows Terminal 1.20.11781.0 with any shell (Command Prompt (cmd.exe), Windows PowerShell (5), PowerShell (7)) * Windows Terminal 1.21.1772.0 with any PowerShell (5 or 7) * Console Host with any shell (cmd.exe or PowerShell 5/7) It's only the combination of Windows Terminal Preview (1.21.1772.0) with Command Prompt that doesn't work.
claunia commented 2026-01-31 08:00:48 +00:00
Author
Owner
Copy Link

@gschizas commented on GitHub (Jul 25, 2024):

After all, the problem was with an environment variable. No problem at all with either Windows Terminal or RAR.exe (technically, the problem is with RAR.exe, but it was being abused).

Apparently the environment variable RAR has some special usage from RAR.exe

@gschizas commented on GitHub (Jul 25, 2024): After all, the problem was with an environment variable. No problem at all with either Windows Terminal or RAR.exe (technically, the problem is with RAR.exe, but it was being abused). Apparently the environment variable RAR has some special usage from RAR.exe
claunia commented 2026-01-31 08:00:48 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 25, 2024):

Wow, that’s a weird one! Thanks for following up!

@DHowett commented on GitHub (Jul 25, 2024): Wow, that’s a weird one! Thanks for following up!
claunia commented 2026-01-31 08:00:48 +00:00
Author
Owner
Copy Link

@strawberryfield commented on GitHub (Sep 10, 2024):

I don't understand as you solved the problem.

@strawberryfield commented on GitHub (Sep 10, 2024): I don't understand as you solved the problem.
claunia commented 2026-01-31 08:00:49 +00:00
Author
Owner
Copy Link

@gschizas commented on GitHub (Sep 10, 2024):

I don't understand as you solved the problem.

It wasn't a problem with Windows Terminal, it was a problem with RAR.exe. If you set an environment variable RAR (e.g. SET RAR=abcd), the latest version of the RAR.exe command line uses it as the default options.

@gschizas commented on GitHub (Sep 10, 2024): > I don't understand as you solved the problem. It wasn't a problem with Windows Terminal, it was a problem with RAR.exe. If you set an environment variable RAR (e.g. `SET RAR=abcd`), the latest version of the RAR.exe command line uses it as the default options.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22009
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?