starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-09 02:26:45 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

How do I actually run the new terminal? #650

New Issue
Closed
opened 2026-01-30 21:58:01 +00:00 by claunia · 13 comments
claunia commented 2026-01-30 21:58:01 +00:00
Owner
Copy Link

Originally created by @Daniel15 on GitHub (May 6, 2019).

I compiled the terminal from this repo using

msbuild OpenConsole.sln /p:Configuration=Release

It compile fine, but when I run bin\x64\Release\OpenConsole.exe, it just loads regular cmd.exe, rather than the fancy terminal shown at https://devblogs.microsoft.com/commandline/introducing-windows-terminal/. Am I missing something?

Windows version 10.0.17763.437
Visual Studio 2017 Professional
MSBuild 15.9.21+g9802d43bc3

Originally created by @Daniel15 on GitHub (May 6, 2019). I compiled the terminal from this repo using ``` msbuild OpenConsole.sln /p:Configuration=Release ``` It compile fine, but when I run `bin\x64\Release\OpenConsole.exe`, it just loads regular `cmd.exe`, rather than the fancy terminal shown at https://devblogs.microsoft.com/commandline/introducing-windows-terminal/. Am I missing something? Windows version 10.0.17763.437 Visual Studio 2017 Professional MSBuild 15.9.21+g9802d43bc3
claunia commented 2026-01-30 21:58:03 +00:00
Author
Owner
Copy Link

@Gnbrkm41 commented on GitHub (May 6, 2019):

https://github.com/microsoft/Terminal/tree/master/tools
try using opencon?

@Gnbrkm41 commented on GitHub (May 6, 2019): https://github.com/microsoft/Terminal/tree/master/tools try using `opencon`?
claunia commented 2026-01-30 21:58:03 +00:00
Author
Owner
Copy Link

@jimblanchard commented on GitHub (May 6, 2019):

If you run the solution, making sure that you have CascadiaPackage set up as the startup project, it should sideload the app. It will now just be in your Start menu.

@jimblanchard commented on GitHub (May 6, 2019): If you run the solution, making sure that you have CascadiaPackage set up as the startup project, it should sideload the app. It will now just be in your Start menu.
claunia commented 2026-01-30 21:58:03 +00:00
Author
Owner
Copy Link

@jimblanchard commented on GitHub (May 6, 2019):

Oh, also something I picked up in one of the other threads. When you run it, it still looks like cmd.exe. Hit ctrl-T to show the tab bar. Then go into settings and set alwaysShowTabs to true.

@jimblanchard commented on GitHub (May 6, 2019): Oh, also something I picked up in one of the other threads. When you run it, it still _looks_ like cmd.exe. Hit ctrl-T to show the tab bar. Then go into settings and set alwaysShowTabs to true.
claunia commented 2026-01-30 21:58:03 +00:00
Author
Owner
Copy Link

@Daniel15 commented on GitHub (May 6, 2019):

@Gnbrkm41 opencon just seems to copy the binaries to a temp folder, then runs OpenConsole.exe:
35229a775d/tools/opencon.cmd (L19-L25)

Just tried it and it still appears to open a regular terminal for me:

(and pressing Ctrl+T doesn't work in this terminal, so I really do think it's a standard cmd.exe)

@jimblanchard - That sounds promising... I was compiling using MSBuild, but I'll try running that CascadiaPackage through Visual Studio. Currently it fails to compile that package in VS, seems like it doesn't like my Windows version:

DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher. You currently are running version 10.0.17763.437. Please update your OS, or change your deployment target to a device with the appropriate version

@Daniel15 commented on GitHub (May 6, 2019): @Gnbrkm41 `opencon` just seems to copy the binaries to a temp folder, then runs `OpenConsole.exe`: https://github.com/microsoft/Terminal/blob/35229a775d9e9908a8dfb102e01f49b494b29194/tools/opencon.cmd#L19-L25 Just tried it and it still appears to open a regular terminal for me: ![](https://d.sb/2019/05/explorer_06-15.40.16.png) (and pressing Ctrl+T doesn't work in this terminal, so I really do think it's a standard cmd.exe) @jimblanchard - That sounds promising... I was compiling using MSBuild, but I'll try running that `CascadiaPackage` through Visual Studio. Currently it fails to compile that package in VS, seems like it doesn't like my Windows version: > DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher. You currently are running version 10.0.17763.437. Please update your OS, or change your deployment target to a device with the appropriate version
claunia commented 2026-01-30 21:58:04 +00:00
Author
Owner
Copy Link

@jimblanchard commented on GitHub (May 6, 2019):

Yes. You definitely need the latest version of Win10 installed. I think there is another issue thread discussing that topic.

@jimblanchard commented on GitHub (May 6, 2019): Yes. You definitely need the latest version of Win10 installed. I think there is another issue thread discussing that topic.
claunia commented 2026-01-30 21:58:04 +00:00
Author
Owner
Copy Link

@Daniel15 commented on GitHub (May 6, 2019):

I tried hacking Package.appxmanifest to use my Windows version:

<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.17763.0" />

Now it compiles, but when I run it, it starts then immediately exits:

The program '[25624] WindowsTerminal.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'.

I guess it probably actually does need the newer Windows version. Oh well.

Unfortunately I can't use any prerelease Windows versions on my work PC, so I'm stuck on 1809 (build 17763). Will try it again once 1903 is out as a stable release.

@Daniel15 commented on GitHub (May 6, 2019): I tried hacking `Package.appxmanifest` to use my Windows version: ``` <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.17763.0" /> ``` Now it compiles, but when I run it, it starts then immediately exits: ``` The program '[25624] WindowsTerminal.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'. ``` I guess it probably actually does need the newer Windows version. Oh well. Unfortunately I can't use any prerelease Windows versions on my work PC, so I'm stuck on 1809 (build 17763). Will try it again once 1903 is out as a stable release.
claunia commented 2026-01-30 21:58:04 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (May 7, 2019):

Yeah, 1903 is a hard requirement here.

@oising commented on GitHub (May 7, 2019): Yeah, 1903 is a hard requirement here.
claunia commented 2026-01-30 21:58:05 +00:00
Author
Owner
Copy Link

@Daniel15 commented on GitHub (May 7, 2019):

Thanks @oising. In that case, I'll close this issue and re-test it when 1903 is released.

@Daniel15 commented on GitHub (May 7, 2019): Thanks @oising. In that case, I'll close this issue and re-test it when 1903 is released.
claunia commented 2026-01-30 21:58:05 +00:00
Author
Owner
Copy Link

@hapylestat commented on GitHub (May 8, 2019):

@Daniel15 check the guides, if you running OpenTerminal.exe you doing wrong things. The application at the output called WindowsTerminal.exe, compile the CascadiaPackage instead of OpenConsolePackage

@hapylestat commented on GitHub (May 8, 2019): @Daniel15 check the guides, if you running OpenTerminal.exe you doing wrong things. The application at the output called WindowsTerminal.exe, compile the CascadiaPackage instead of OpenConsolePackage
claunia commented 2026-01-30 21:58:05 +00:00
Author
Owner
Copy Link

@thomthom commented on GitHub (May 8, 2019):

@hapylestat where in the guides is this described?

The root README file doesn't mention this. Nor does the tools/README. doc/building.md only mentions razzle, bcz and opencon.

With all the projects in the solution and no mention in the main README it's somewhat confusing if you have never touched the project. The minimum Windows version required is also something I found no mention of - other than in this issue.

@thomthom commented on GitHub (May 8, 2019): @hapylestat where in the guides is this described? The root README file doesn't mention this. Nor does the tools/README. doc/building.md only mentions razzle, bcz and opencon. With all the projects in the solution and no mention in the main README it's somewhat confusing if you have never touched the project. The minimum Windows version required is also something I found no mention of - other than in this issue.
claunia commented 2026-01-30 21:58:05 +00:00
Author
Owner
Copy Link

@hapylestat commented on GitHub (May 10, 2019):

@thomthom the readme describes the "default" way which "should" work. But as users have different environment, software versions and bunch of another "variables" - the end guide may vary for each of them.

As of now, the complete guide and links r maintained here #489, later it could be moved to a separate PR to form proper and full readme update,

@hapylestat commented on GitHub (May 10, 2019): @thomthom the readme describes the "default" way which "should" work. But as users have different environment, software versions and bunch of another "variables" - the end guide may vary for each of them. As of now, the complete guide and links r maintained here #489, later it could be moved to a separate PR to form proper and full readme update,
claunia commented 2026-01-30 21:58:06 +00:00
Author
Owner
Copy Link

@sourabhsomani commented on GitHub (Jun 18, 2019):

I tried hacking Package.appxmanifest to use my Windows version:

<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.17763.0" />

Now it compiles, but when I run it, it starts then immediately exits:

The program '[25624] WindowsTerminal.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'.

I guess it probably actually does need the newer Windows version. Oh well.

Unfortunately I can't use any prerelease Windows versions on my work PC, so I'm stuck on 1809 (build 17763). Will try it again once 1903 is out as a stable release.

Thank You. Finally done and Deployed :)

@sourabhsomani commented on GitHub (Jun 18, 2019): > I tried hacking `Package.appxmanifest` to use my Windows version: > > ``` > <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.17763.0" /> > ``` > > Now it compiles, but when I run it, it starts then immediately exits: > > ``` > The program '[25624] WindowsTerminal.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'. > ``` > > I guess it probably actually does need the newer Windows version. Oh well. > > Unfortunately I can't use any prerelease Windows versions on my work PC, so I'm stuck on 1809 (build 17763). Will try it again once 1903 is out as a stable release. Thank You. Finally done and Deployed :)
claunia commented 2026-01-30 21:58:06 +00:00
Author
Owner
Copy Link

@WaiYanMyintMo commented on GitHub (May 24, 2020):

I hope 17763 gets supported. It's not even old

@WaiYanMyintMo commented on GitHub (May 24, 2020): I hope 17763 gets supported. It's not even old
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
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#650
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?