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

Terminal failed to build with error MSB8020 on MSVC #18561

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

Originally created by @nnfdnkns on GitHub (Sep 28, 2022).

Windows Terminal version

No response

Windows build number

No response

Other Software

No response

Steps to reproduce

Terminal failed to build with error MSB8020:The build tools for v143 (Platform Toolset = 'v143') cannot be found. add /p:PlatformToolset=v142, It also failed.

repro steps:
1.git -C "F:\gitP" clone https://github.com/microsoft/terminal microsoft\terminal
2.cd F:\gitP\microsoft\terminal
3.set path=F:\gitP\microsoft\terminal\dep\nuget;%PATH%
4.nuget restore OpenConsole.sln 2>&1
5.set CL=/wd4189 /wd5104 /D_SILENCE_STDEXT_HASH_DEPRECATION_WARNINGS %CL%
6.msbuild /m /p:Platform=x64 /p:Configuration=Release /p:WindowsTargetPlatformVersion=10.0.22000.0 /p:PlatformToolset=v142 OpenConsole.sln /t:Restore /t:Rebuild 2>&1

Expected Behavior

Terminal could build successfully

Actual Behavior

2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(331,5): error MSB4036: The "GetFrameworkSdkPackages" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with in the project file, or in the *.tasks files located in the "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin" directory. [F:\gitP\microsoft\terminal\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj]

Originally created by @nnfdnkns on GitHub (Sep 28, 2022). ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce Terminal failed to build with error MSB8020:The build tools for v143 (Platform Toolset = 'v143') cannot be found. add /p:PlatformToolset=v142, It also failed. **repro steps:** 1.git -C "F:\gitP" clone https://github.com/microsoft/terminal microsoft\terminal 2.cd F:\gitP\microsoft\terminal 3.set path=F:\gitP\microsoft\terminal\dep\nuget;%PATH% 4.nuget restore OpenConsole.sln 2>&1 5.set _CL_=/wd4189 /wd5104 /D_SILENCE_STDEXT_HASH_DEPRECATION_WARNINGS %_CL_% 6.msbuild /m /p:Platform=x64 /p:Configuration=Release /p:WindowsTargetPlatformVersion=10.0.22000.0 /p:PlatformToolset=v142 OpenConsole.sln /t:Restore /t:Rebuild 2>&1 ### Expected Behavior Terminal could build successfully ### Actual Behavior 2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(331,5): error MSB4036: The "GetFrameworkSdkPackages" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin" directory. [F:\gitP\microsoft\terminal\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj]
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 06:17:44 +00:00
claunia commented 2026-01-31 06:17:45 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 28, 2022):

I think the problem is that you're using Visual Studio 2019, while Terminal requires Visual Studio 2022. See the prerequisites here: https://github.com/microsoft/terminal#prerequisites

@j4james commented on GitHub (Sep 28, 2022): I think the problem is that you're using Visual Studio 2019, while Terminal requires Visual Studio 2022. See the prerequisites here: https://github.com/microsoft/terminal#prerequisites
claunia commented 2026-01-31 06:17:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 3, 2022):

@nnfdnkns can you confirm which version of VS you're using to build/?

@zadjii-msft commented on GitHub (Oct 3, 2022): @nnfdnkns can you confirm which version of VS you're using to build/?
claunia commented 2026-01-31 06:17:45 +00:00
Author
Owner
Copy Link

@duggi-9977 commented on GitHub (Oct 4, 2022):

I guess you should upgrade the project to use the current Visual Studio toolset, or use the Visual Studio Installer to install the specified build toolset. Check this link to modify your VS: https://learn.microsoft.com/en-us/visualstudio/install/modify-visual-studio?view=vs-2022.

Additionally: In Visual Studio, in Solution Explorer:
(1) open the shortcut menu for your project (not for your solution) and then choose Properties to open your project Property
Pages dialog box.
(2) In the Property Pages dialog box, open the Configuration drop-down list and then select All Configurations.
(3) In the left pane of the dialog box, expand Configuration Properties and then select General.
(4) In the right pane, select Platform Toolset and then select the toolset you want from the drop-down list (2022_
(5) Click OK

@duggi-9977 commented on GitHub (Oct 4, 2022): I guess you should upgrade the project to use the current Visual Studio toolset, or use the Visual Studio Installer to install the specified build toolset. Check this link to modify your VS: https://learn.microsoft.com/en-us/visualstudio/install/modify-visual-studio?view=vs-2022. Additionally: In Visual Studio, in Solution Explorer: (1) open the shortcut menu for your project (not for your solution) and then choose Properties to open your project Property Pages dialog box. (2) In the Property Pages dialog box, open the Configuration drop-down list and then select All Configurations. (3) In the left pane of the dialog box, expand Configuration Properties and then select General. (4) In the right pane, select Platform Toolset and then select the toolset you want from the drop-down list (2022_ (5) Click OK
claunia commented 2026-01-31 06:17:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 8, 2022):

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 (Oct 8, 2022): 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-31 06:17:45 +00:00
Author
Owner
Copy Link

@nnfdnkns commented on GitHub (Oct 13, 2022):

@zadjii-msft version of VS is vs2019

@nnfdnkns commented on GitHub (Oct 13, 2022): @zadjii-msft version of VS is vs2019
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-Attention 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#18561
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?