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 crashes when run inside terminal #21008

New Issue
Closed
opened 2026-01-31 07:30:26 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 07:30:26 +00:00
Owner
Copy Link

Originally created by @gilknyaz on GitHub (Dec 21, 2023).

Originally assigned to: @rainersigwald on GitHub.

Windows Terminal version

1.18.3181

Windows build number

10.0.22621.0

Other Software

MSBuild (VS 2022)

Steps to reproduce

  1. Open the Developer Command Prompt for VS 2022 profile.
  2. go to a C# solution folder
  3. Run MSbuild to compile. (Or run msbuild /t:Restore to restore some nuget packages)

Expected Behavior

MSbuild to succeed

Actual Behavior

MSBuild starts working but stops very early. No error is written to the console.
In Event Viewer -> Application, the following error appears:

Faulting application name: MSBuild.exe, version: 17.8.3.51904, time stamp: 0xe31ab667
Faulting module name: combase.dll, version: 10.0.22621.2792, time stamp: 0xd9671289
Exception code: 0xc0000409
Fault offset: 0x00000000001522b2
Faulting process id: 0x0x6380
Faulting application start time: 0x0x1DA34154F6EE43B
Faulting application path: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\MSBuild.exe
Faulting module path: C:\WINDOWS\System32\combase.dll
Report Id: 4af61e29-3040-4862-b67c-0fb2c7a14aef
Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Originally created by @gilknyaz on GitHub (Dec 21, 2023). Originally assigned to: @rainersigwald on GitHub. ### Windows Terminal version 1.18.3181 ### Windows build number 10.0.22621.0 ### Other Software MSBuild (VS 2022) ### Steps to reproduce 1. Open the Developer Command Prompt for VS 2022 profile. 2. go to a C# solution folder 3. Run MSbuild to compile. (Or run msbuild /t:Restore to restore some nuget packages) ### Expected Behavior MSbuild to succeed ### Actual Behavior MSBuild starts working but stops very early. No error is written to the console. In Event Viewer -> Application, the following error appears: Faulting application name: MSBuild.exe, version: 17.8.3.51904, time stamp: 0xe31ab667 Faulting module name: combase.dll, version: 10.0.22621.2792, time stamp: 0xd9671289 Exception code: 0xc0000409 Fault offset: 0x00000000001522b2 Faulting process id: 0x0x6380 Faulting application start time: 0x0x1DA34154F6EE43B Faulting application path: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\MSBuild.exe Faulting module path: C:\WINDOWS\System32\combase.dll Report Id: 4af61e29-3040-4862-b67c-0fb2c7a14aef Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
claunia added the Needs-TriageIssue-BugResolution-External labels 2026-01-31 07:30:26 +00:00
claunia commented 2026-01-31 07:30:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 3, 2024):

@rainersigwald any ideas? Or any idea how to investigate? Does this work just fine in the vintage console/?

@zadjii-msft commented on GitHub (Jan 3, 2024): @rainersigwald any ideas? Or any idea how to investigate? Does this work just fine in the vintage console/?
claunia commented 2026-01-31 07:30:28 +00:00
Author
Owner
Copy Link

@rainersigwald commented on GitHub (Jan 4, 2024):

I haven't heard of this before. Since you have VS installed, you might be able to get more information by setting the environment variable MSBUILDDEBUGONSTART=1 before running MSBuild, which should pop up a JIT debugger prompt. Then the crash might have a bit more actionable information?

@rainersigwald commented on GitHub (Jan 4, 2024): I haven't heard of this before. Since you have VS installed, you might be able to get more information by setting the environment variable `MSBUILDDEBUGONSTART=1` before running MSBuild, which should pop up a JIT debugger prompt. Then the crash might have a bit more actionable information?
claunia commented 2026-01-31 07:30:28 +00:00
Author
Owner
Copy Link

@gilknyaz commented on GitHub (Jan 5, 2024):

@zadjii-msft @rainersigwald
MSBuild.001.zip
MSBuild.002.zip

I've uploaded the dump created with MSBUILDDEBUGONSTART
It's split because github doesn't allow more than 25MB per-file. Please rename them to MSBuild.zip.001 and MSBuild.zip.002 to open.

Another thing that might explain the difference - it happens to me on a Virtual Desktop machine. (VMWare VDI). Doesn't happen on a regular PC.

@gilknyaz commented on GitHub (Jan 5, 2024): @zadjii-msft @rainersigwald [MSBuild.001.zip](https://github.com/microsoft/terminal/files/13843107/MSBuild.001.zip) [MSBuild.002.zip](https://github.com/microsoft/terminal/files/13843110/MSBuild.002.zip) I've uploaded the dump created with MSBUILDDEBUGONSTART It's split because github doesn't allow more than 25MB per-file. Please rename them to MSBuild.zip.001 and MSBuild.zip.002 to open. Another thing that might explain the difference - it happens to me on a Virtual Desktop machine. (VMWare VDI). Doesn't happen on a regular PC.
claunia commented 2026-01-31 07:30:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 10, 2024):

@rainersigwald Hey can you investigate this more on your side? Or move this to the msbuild repo? I can't imagine that this is something that is really caused by Terminal code... but if this is something that explodes in msbuild cause we're running, I think you'd be best equipped to find out why

@zadjii-msft commented on GitHub (Jan 10, 2024): @rainersigwald Hey can you investigate this more on your side? Or move this to the msbuild repo? I can't imagine that this is something that is really caused by Terminal code... but if this is something that explodes in msbuild cause we're running, I think you'd be best equipped to find out why
claunia commented 2026-01-31 07:30:29 +00:00
Author
Owner
Copy Link

@rainersigwald commented on GitHub (Jan 10, 2024):

This issue was moved to dotnet/sdk#38742

@rainersigwald commented on GitHub (Jan 10, 2024): This issue was moved to dotnet/sdk#38742
claunia commented 2026-01-31 07:30:29 +00:00
Author
Owner
Copy Link

@rainersigwald commented on GitHub (Jan 10, 2024):

@zadjii-msft I copied this to dotnet/msbuild, feel free to close this one.

@rainersigwald commented on GitHub (Jan 10, 2024): @zadjii-msft I copied this to dotnet/msbuild, feel free to close this one.
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 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#21008
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?