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

msbuild.exe is not recognized as the name of a cmdlet, function, script file, or operable program. #2095

New Issue
Closed
opened 2026-01-30 22:46:39 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 22:46:39 +00:00
Owner
Copy Link

Originally created by @Pcoric on GitHub (Jun 24, 2019).

Environment

Windows build number: [run "ver" at a command prompt] Microsoft Windows [Version 10.0.17763.557]
Windows Terminal version (if applicable): v0.2.1715.0

Any other software?

Steps to reproduce

Running the installation commands from vs 2019 preview. I am doing it in PowerShell, although I also tried in CMD and got errors at the bcz step. Import-Module .\tools\OpenConsole.psm1 &
Set-MsBuildDevEnvironment both worked for me.

NOTE: Found what seemed like a similar issue at #930 but I am using the merged update. I think I may just need to give up trying to do it with 2019, but I'm still filing this as a bug hoping someone will explain to me why the version is causing this issue if I'm just running PowerShell commands.

Expected behavior

I'd expect the Invoke-OpenConsoleBuild command to complete successfully, it's giving me an error.

Actual behavior

Build is failing: msbuild.exe : The term 'msbuild.exe' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\pacoric\source\repos\terminal\tools\OpenConsole.psm1:251 char:5

  • msbuild.exe "$env:OpenConsoleRoot\OpenConsole.sln" @args

  • ~~~~~~~~~~~
    • CategoryInfo : ObjectNotFound: (msbuild.exe:String) [], CommandNotFoundException
    • FullyQualifiedErrorId : CommandNotFoundException
Originally created by @Pcoric on GitHub (Jun 24, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run "ver" at a command prompt] Microsoft Windows [Version 10.0.17763.557] Windows Terminal version (if applicable): v0.2.1715.0 Any other software? ``` # Steps to reproduce Running the installation commands from vs 2019 preview. I am doing it in PowerShell, although I also tried in CMD and got errors at the bcz step. Import-Module .\tools\OpenConsole.psm1 & Set-MsBuildDevEnvironment both worked for me. NOTE: Found what seemed like a similar issue at #930 but I am using the merged update. I think I may just need to give up trying to do it with 2019, but I'm still filing this as a bug hoping someone will explain to me why the version is causing this issue if I'm just running PowerShell commands. # Expected behavior I'd expect the Invoke-OpenConsoleBuild command to complete successfully, it's giving me an error. # Actual behavior <!-- What's actually happening? --> Build is failing: msbuild.exe : The term 'msbuild.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Users\pacoric\source\repos\terminal\tools\OpenConsole.psm1:251 char:5 + msbuild.exe "$env:OpenConsoleRoot\OpenConsole.sln" @args + ~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (msbuild.exe:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
claunia added the Issue-QuestionNeeds-Author-FeedbackProduct-TerminalArea-Build labels 2026-01-30 22:46:39 +00:00
claunia commented 2026-01-30 22:46:40 +00:00
Author
Owner
Copy Link

@adiviness commented on GitHub (Jun 24, 2019):

it sounds like msbuild isn't getting added to your path correctly, what's your path look like after running Set-MsBuildDevEnvironment?

@adiviness commented on GitHub (Jun 24, 2019): it sounds like msbuild isn't getting added to your path correctly, what's your path look like after running `Set-MsBuildDevEnvironment`?
claunia commented 2026-01-30 22:46:40 +00:00
Author
Owner
Copy Link

@jpandersen87 commented on GitHub (Jun 29, 2019):

I also ran into this issue. You need to run Set-MsBuildDevEnvironment with the Prerelease parameter set to $true for the script to find VS2019.

@jpandersen87 commented on GitHub (Jun 29, 2019): I also ran into this issue. You need to run Set-MsBuildDevEnvironment with the Prerelease parameter set to $true for the script to find VS2019.
claunia commented 2026-01-30 22:46:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 3, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 3, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-30 22:46:41 +00:00
Author
Owner
Copy Link

@0x11DFE commented on GitHub (Nov 26, 2021):

I am having the same issue, DEV's bump?

@0x11DFE commented on GitHub (Nov 26, 2021): I am having the same issue, DEV's bump?
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 Area-Build Issue-Question Needs-Author-Feedback Product-Terminal
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#2095
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?