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

Support to execute 32-bit executables in a 64-bit system #4548

New Issue
Closed
opened 2026-01-30 23:50:11 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:50:11 +00:00
Owner
Copy Link

Originally created by @srinivasanc22071986 on GitHub (Oct 19, 2019).

Environment

Hi, Recently I installed to PL/1 compiler from Iron-Spring http://www.iron-spring.com/index.html for Linux in the New Windows Terminal under WSL(Windows Subsystem for Linux), But I heard from certain online forums that the WSL of Windows will support only 64-bit executables and no 32-bit executables, Unfortunately the above-mentioned PL/1 compiler is a 32-bit compiler, so I tried to many times to get that working, but unable to do so, and I kept on getting the below error,

-bash: ./plic: cannot execute binary file: Exec format error

image

To you have any plans to implement the feature to support 32-bit executables in WSL and also in the final version of Windows New Terminal 1.0? If so when?

Also technically we cannot execute a 64-bit executable on a 32-bit operating system, but the other way round should be possible with certain minor changes in the system,

At last, I achieved the above action using some additional installation given in the below link,

https://github.com/microsoft/wsl/issues/2468#issuecomment-374904520

Steps to reproduce

Try to execute a 32-bit executable you will get this error.

Expected behavior

The windows terminal should execute 32-bit executables without throwing any error

Actual behavior

The windows terminal throws a blank error without proper error descritption when a 32-bit executable is tried

Originally created by @srinivasanc22071986 on GitHub (Oct 19, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Hi, Recently I installed to PL/1 compiler from Iron-Spring http://www.iron-spring.com/index.html for Linux in the New Windows Terminal under WSL(Windows Subsystem for Linux), But I heard from certain online forums that the WSL of Windows will support only 64-bit executables and no 32-bit executables, Unfortunately the above-mentioned PL/1 compiler is a 32-bit compiler, so I tried to many times to get that working, but unable to do so, and I kept on getting the below error, -bash: ./plic: cannot execute binary file: Exec format error ![image](https://user-images.githubusercontent.com/49483717/67143141-e8b10c00-f285-11e9-8c31-497835c9c80d.png) To you have any plans to implement the feature to support 32-bit executables in WSL and also in the final version of Windows New Terminal 1.0? If so when? Also technically we cannot execute a 64-bit executable on a 32-bit operating system, but the other way round should be possible with certain minor changes in the system, At last, I achieved the above action using some additional installation given in the below link, https://github.com/microsoft/wsl/issues/2468#issuecomment-374904520 # Steps to reproduce Try to execute a 32-bit executable you will get this error. # Expected behavior The windows terminal should execute 32-bit executables without throwing any error # Actual behavior The windows terminal throws a blank error without proper error descritption when a 32-bit executable is tried
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-30 23:50:11 +00:00
claunia commented 2026-01-30 23:50:12 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 21, 2019):

There's nothing Terminal can do about this. Please continue to follow microsoft/wsl#2468.

@DHowett-MSFT commented on GitHub (Oct 21, 2019): _There's nothing Terminal can do about this._ Please continue to follow microsoft/wsl#2468.
claunia commented 2026-01-30 23:50:12 +00:00
Author
Owner
Copy Link

@srinivasanc22071986 commented on GitHub (Oct 23, 2019):

Yes, I expected this reply, thank you for your support, and I will continue to follow this issue.

@srinivasanc22071986 commented on GitHub (Oct 23, 2019): Yes, I expected this reply, thank you for your support, and I will continue to follow this issue.
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 Needs-Tag-Fix Resolution-External
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#4548
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?