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

Crash on launch with no Azure tools installed #3955

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

Originally created by @zb140 on GitHub (Sep 20, 2019).

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): Custom build, b84a073

Any other software?

Steps to reproduce

  1. On a system that does not have any Azure tools or components installed, fetch commit b84a073.
  2. Clean and then rebuild the solution
  3. Rename profiles.json to profiles.json.old (not sure if this is important, but when I update to a new build of Terminal I like to start with a completely fresh profiles.json and merge in all my customizations)
  4. Attempt to launch Windows Terminal

Expected behavior

Terminal launches 😄

Actual behavior

Terminal crashes ☹️

Ironically, it's crashing while trying to determine whether Azure stuff is in fact installed. The exact line that's crashing is apparently in a generated file (...\src\cascadia\TerminalApp\lib\Generated Files\winrt\base.h) where it calls WINRT_RoGetActivationFactory and unexpectedly gets ERROR_MOD_NOT_FOUND (0x8007007e). Going up the stack ultimately leads to this line: 0df02343f1/src/cascadia/TerminalApp/AzureCloudShellGenerator.cpp (L34)

Everything further down the stack than that line appears to be in generated code, so I guess it's possible that generation isn't going well. But I would expect the build process I use to pretty much rule that out since it always starts with a completely fresh checkout (no local changes at all) and a complete clean and rebuild of everything. I have also tried with a completely new, fresh clone (rather than updating an existing clone) with the same results.

Originally created by @zb140 on GitHub (Sep 20, 2019). # Environment ```none Windows build number: 10.0.18362.0 Windows Terminal version (if applicable): Custom build, b84a073 Any other software? ``` # Steps to reproduce 1. On a system that does not have any Azure tools or components installed, fetch commit b84a073. 1. Clean and then rebuild the solution 1. Rename `profiles.json` to `profiles.json.old` (not sure if this is important, but when I update to a new build of Terminal I like to start with a completely fresh `profiles.json` and merge in all my customizations) 1. Attempt to launch Windows Terminal # Expected behavior Terminal launches 😄 # Actual behavior Terminal crashes ☹️ Ironically, it's crashing while trying to determine whether Azure stuff is in fact installed. The exact line that's crashing is apparently in a generated file (`...\src\cascadia\TerminalApp\lib\Generated Files\winrt\base.h`) where it calls `WINRT_RoGetActivationFactory` and unexpectedly gets `ERROR_MOD_NOT_FOUND` (0x8007007e). Going up the stack ultimately leads to this line: https://github.com/microsoft/terminal/blob/0df02343f13059640f57042b8c1d8c113ac4bae5/src/cascadia/TerminalApp/AzureCloudShellGenerator.cpp#L34 Everything further down the stack than that line appears to be in generated code, so I guess it's possible that generation isn't going well. But I would expect the build process I use to pretty much rule that out since it always starts with a completely fresh checkout (no local changes at all) and a complete clean and rebuild of everything. I have also tried with a completely new, fresh clone (rather than updating an existing clone) with the same results.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-30 23:34:12 +00:00
claunia commented 2026-01-30 23:34:13 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 20, 2019):

This looks suspiciously similar to (bug number where Visual Studio 2019 Update 3 was broken), but that has since been fixed. It’s looking for a DLL that the packaging project has conveniently forgotten to place in the package.

Fortunately, it’s not about having any azure tools installed :)

Can you share some more info about your environment? What VS version are you using, and can you share a Detailed or Diagnostic level build log?

@DHowett-MSFT commented on GitHub (Sep 20, 2019): This looks suspiciously similar to (bug number where Visual Studio 2019 Update 3 was broken), but that has since been fixed. It’s looking for a DLL that the packaging project has conveniently forgotten to place in the package. Fortunately, it’s not about having any azure tools installed :) Can you share some more info about your environment? What VS version are you using, and can you share a Detailed or Diagnostic level build log?
claunia commented 2026-01-30 23:34:13 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 20, 2019):

(That was #2625. Sorry, I’m on my phone :))

@DHowett-MSFT commented on GitHub (Sep 20, 2019): (That was #2625. Sorry, I’m on my phone :))
claunia commented 2026-01-30 23:34:13 +00:00
Author
Owner
Copy Link

@zb140 commented on GitHub (Sep 20, 2019):

Thanks for the quick response! My Visual Studio version is 16.3.0 Preview 1. I didn't previously realize I was using a preview version, so I guess that might be related. I can try to switch to a released version and see if that helps.

I've also attached the diagnostic level build log (zipped for file size). It's in two parts because the build actually doesn't succeed the first time. When I build from a fresh checkout it builds for a while then errors out with:

Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3272	There was a problem reading the implementation file "C:\Users\zb\stuff\Terminal\x64\Release\TerminalAppLib\TerminalAppLib.lib". "Unable to read beyond the end of the stream."	LocalTests_TerminalApp	C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets	2106

Starting an incremental build at that point then succeeds. This has been happening since well before yesterday so I don't think it's the problem, but it might be.

Output-Build.zip

@zb140 commented on GitHub (Sep 20, 2019): Thanks for the quick response! My Visual Studio version is 16.3.0 Preview 1. I didn't previously realize I was using a preview version, so I guess that might be related. I can try to switch to a released version and see if that helps. I've also attached the diagnostic level build log (zipped for file size). It's in two parts because the build actually doesn't succeed the first time. When I build from a fresh checkout it builds for a while then errors out with: ```none Severity Code Description Project File Line Suppression State Error MSB3272 There was a problem reading the implementation file "C:\Users\zb\stuff\Terminal\x64\Release\TerminalAppLib\TerminalAppLib.lib". "Unable to read beyond the end of the stream." LocalTests_TerminalApp C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets 2106 ``` Starting an incremental build at that point then succeeds. This has been happening since well before yesterday so I don't think it's the problem, but it might be. [Output-Build.zip](https://github.com/microsoft/terminal/files/3636778/Output-Build.zip)
claunia commented 2026-01-30 23:34:13 +00:00
Author
Owner
Copy Link

@zb140 commented on GitHub (Sep 20, 2019):

I just had a chance to look at #2625 and yeah, this definitely looks highly similar, although oddly my build does include the fix for that one.

@zb140 commented on GitHub (Sep 20, 2019): I just had a chance to look at #2625 and yeah, this definitely looks highly similar, although oddly my build does include the fix for that one.
claunia commented 2026-01-30 23:34:14 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 20, 2019):

It definitely looks like the same issue from the logs. Have you tried after "preview 1"?

@DHowett-MSFT commented on GitHub (Sep 20, 2019): It definitely looks like the same issue from the logs. Have you tried after "preview 1"?
claunia commented 2026-01-30 23:34:14 +00:00
Author
Owner
Copy Link

@zb140 commented on GitHub (Sep 21, 2019):

Updating to Preview 4 did indeed fix it. Sorry for the noise 😄

@zb140 commented on GitHub (Sep 21, 2019): Updating to Preview 4 did indeed fix it. Sorry for the noise 😄
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-Attention Needs-Tag-Fix 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#3955
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?