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

[on start] "Incorrect Function" #12737

New Issue
Closed
opened 2026-01-31 03:23:28 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 03:23:28 +00:00
Owner
Copy Link

Originally created by @Lagicrus on GitHub (Feb 25, 2021).

https://aka.ms/AAbc3m9

Environment

Windows build number: Win32NT             10.0.21322.0 Microsoft Windows NT 10.0.21322.0
Windows Terminal version (if applicable): 1.5.10411.0

Any other software?

Steps to reproduce

  1. Click the Icon in Taskbar or Start menu
  2. Wait a few seconds for it to "Load"
  3. Have a popup appear in your face telling you it is an "Incorrect function."
    image

Expected behaviour

It should load

Actual behaviour

It isn't loading

Originally created by @Lagicrus on GitHub (Feb 25, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> https://aka.ms/AAbc3m9 # Environment ```none Windows build number: Win32NT 10.0.21322.0 Microsoft Windows NT 10.0.21322.0 Windows Terminal version (if applicable): 1.5.10411.0 Any other software? ``` # Steps to reproduce 1. Click the Icon in Taskbar or Start menu 2. Wait a few seconds for it to "Load" 3. Have a popup appear in your face telling you it is an "Incorrect function." ![image](https://user-images.githubusercontent.com/24227350/109150179-6af5ee00-7760-11eb-9b90-efc31f58c05a.png) # Expected behaviour It should load # Actual behaviour It isn't loading
claunia commented 2026-01-31 03:23:30 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Feb 25, 2021):

So you are using insider preview? I’m not sure the core team’s goal about WT running on insider builds.

@skyline75489 commented on GitHub (Feb 25, 2021): So you are using insider preview? I’m not sure the core team’s goal about WT running on insider builds.
claunia commented 2026-01-31 03:23:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 25, 2021):

I mean, we're all on Insiders builds ourselves, so that shouldn't have anything to do with it 😄. We'll have to dig in on the feedback link, but I'm worried that it's crashing before even loading the terminal, so that might not be useful...

@zadjii-msft commented on GitHub (Feb 25, 2021): I mean, we're all on Insiders builds ourselves, so that _shouldn't_ have anything to do with it 😄. We'll have to dig in on the feedback link, but I'm worried that it's crashing before even loading the terminal, so that might not be useful...
claunia commented 2026-01-31 03:23:30 +00:00
Author
Owner
Copy Link

@Lagicrus commented on GitHub (Feb 25, 2021):

I mean, we're all on Insiders builds ourselves, so that shouldn't have anything to do with it 😄. We'll have to dig in on the feedback link, but I'm worried that it's crashing before even loading the terminal, so that might not be useful...

Ye.. I have even ran the "Repair" function from the Windows App view or whatever it is called if that helps
If you can point me at ways to get more logs or dumps, feel free to ping, I want this working again 😄 I use it way too much

@Lagicrus commented on GitHub (Feb 25, 2021): > I mean, we're all on Insiders builds ourselves, so that _shouldn't_ have anything to do with it 😄. We'll have to dig in on the feedback link, but I'm worried that it's crashing before even loading the terminal, so that might not be useful... Ye.. I have even ran the "Repair" function from the Windows App view or whatever it is called if that helps If you can point me at ways to get more logs or dumps, feel free to ping, I want this working again 😄 I use it way too much
claunia commented 2026-01-31 03:23:31 +00:00
Author
Owner
Copy Link

@Lagicrus commented on GitHub (Feb 27, 2021):

Minor update, after my PC crashed which caused me to reboot, I tried to reopen Terminal
I couldn't printscreen due to it being a Windows popup, but it mentioned something about it not being able to open it due to the storage being offline?
I will see if i can get this to happened again later

@Lagicrus commented on GitHub (Feb 27, 2021): Minor update, after my PC crashed which caused me to reboot, I tried to reopen Terminal I couldn't printscreen due to it being a Windows popup, but it mentioned something about it not being able to open it due to the storage being offline? I will see if i can get this to happened again later
claunia commented 2026-01-31 03:23:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 1, 2021):

FYI on a MessageBox like that, you can just hit ctrl+c and it'll actually copy the text of that dialog. Handy for bug reports like this ☺️

The specific text that it shows you might be helpful in narrowing down the cause of this.

@zadjii-msft commented on GitHub (Mar 1, 2021): FYI on a `MessageBox` like that, you can just hit <kbd>ctrl+c</kbd> and it'll actually copy the text of that dialog. Handy for bug reports like this ☺️ The specific text that it shows you might be helpful in narrowing down the cause of this.
claunia commented 2026-01-31 03:23:31 +00:00
Author
Owner
Copy Link

@Lagicrus commented on GitHub (Mar 1, 2021):

FYI on a MessageBox like that, you can just hit ctrl+c and it'll actually copy the text of that dialog. Handy for bug reports like this ☺️

The specific text that it shows you might be helpful in narrowing down the cause of this.

I had no idea that was a thing.. Everyday you learn something new 👍

[Window Title]
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10411.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

[Content]
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10411.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

Incorrect function.


[OK]
@Lagicrus commented on GitHub (Mar 1, 2021): > FYI on a `MessageBox` like that, you can just hit ctrl+c and it'll actually copy the text of that dialog. Handy for bug reports like this ☺️ > > The specific text that it shows you might be helpful in narrowing down the cause of this. I had no idea that was a thing.. Everyday you learn something new :+1: ``` [Window Title] C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10411.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe [Content] C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10411.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Incorrect function. [OK] ```
claunia commented 2026-01-31 03:23:31 +00:00
Author
Owner
Copy Link

@Lagicrus commented on GitHub (Mar 8, 2021):

I got the window to appear on windows start again

Windows Terminal can’t open because it is offline. The storage device might be missing or disconnected.

That is what I get when I hit the copy button, this was after a Green screen with it working fine

@Lagicrus commented on GitHub (Mar 8, 2021): I got the window to appear on windows start again ``` Windows Terminal can’t open because it is offline. The storage device might be missing or disconnected. ``` That is what I get when I hit the copy button, this was after a Green screen with it working fine
claunia commented 2026-01-31 03:23:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 26, 2021):

Weird. This is another feedback that ended up getting bucketed to utc_feedbacc_diagtrack.dll, which is totally useless 😕 On the bright side, it doesn't seem to think that the Terminal is actually involved in the crash at all. On the down side, that kinda means there's nothing left for me to be able to investigate. I can't track down the crash outside our codebase ☹️

Does re-installing the app from the store help? (make sure to back up your settings from %localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json first!)

@zadjii-msft commented on GitHub (Mar 26, 2021): Weird. This is another feedback that ended up getting bucketed to `utc_feedbacc_diagtrack.dll`, which is totally useless 😕 On the bright side, it doesn't seem to think that the Terminal is actually involved in the crash at all. On the down side, that kinda means there's nothing left for me to be able to investigate. I can't track down the crash outside our codebase ☹️ Does re-installing the app from the store help? (make sure to back up your settings from `%localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json` first!)
claunia commented 2026-01-31 03:23:32 +00:00
Author
Owner
Copy Link

@Lagicrus commented on GitHub (Mar 26, 2021):

Weird. This is another feedback that ended up getting bucketed to utc_feedbacc_diagtrack.dll, which is totally useless 😕 On the bright side, it doesn't seem to think that the Terminal is actually involved in the crash at all. On the down side, that kinda means there's nothing left for me to be able to investigate. I can't track down the crash outside our codebase ☹️

Does re-installing the app from the store help? (make sure to back up your settings from %localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json first!)

I'll try that later, so far I have found that waiting and then trying again seems to fix it?
I haven't bothered to time it as that is too variable, but ye. If I get the warning, wait a bit, then try again, "when everything has calmed down". And it seems to work again?

@Lagicrus commented on GitHub (Mar 26, 2021): > Weird. This is another feedback that ended up getting bucketed to `utc_feedbacc_diagtrack.dll`, which is totally useless 😕 On the bright side, it doesn't seem to think that the Terminal is actually involved in the crash at all. On the down side, that kinda means there's nothing left for me to be able to investigate. I can't track down the crash outside our codebase ☹️ > > Does re-installing the app from the store help? (make sure to back up your settings from `%localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json` first!) I'll try that later, so far I have found that waiting and then trying again seems to fix it? I haven't bothered to time it as that is too variable, but ye. If I get the warning, wait a bit, then try again, "when everything has calmed down". And it seems to work again?
claunia commented 2026-01-31 03:23:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 13, 2021):

Sorry this one's stayed hidden on the backlog so long - @Lagicrus you still seeing this? Is there anything that gets logged in Event Viewer when this happens? I honestly have no idea what's going on here, or why letting the OS "settle down" would fix this...

@zadjii-msft commented on GitHub (Dec 13, 2021): Sorry this one's stayed hidden on the backlog so long - @Lagicrus you still seeing this? Is there anything that gets logged in Event Viewer when this happens? I honestly have no idea what's going on here, or why letting the OS "settle down" would fix this...
claunia commented 2026-01-31 03:23:32 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 17, 2021):

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 (Dec 17, 2021): 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**.
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-Author-Feedback Needs-Repro Needs-Tag-Fix Needs-Triage No-Recent-Activity Product-Terminal Severity-Crash
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#12737
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?