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

The data area passed to a system call is too small. #4075

New Issue
Closed
opened 2026-01-30 23:37:24 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 23:37:24 +00:00
Owner
Copy Link

Originally created by @jdudleyintelliflo on GitHub (Sep 26, 2019).

Environment

Microsoft Windows NT 10.0.18362.0

Steps to reproduce

Install app from windows store OR build from source and deploy Cascadia package.

Expected behavior

Terminal runs successfully.

Actual behavior

Error "The data area passed to a system call is too small." is shown and terminal does not open.

image

Originally created by @jdudleyintelliflo on GitHub (Sep 26, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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. --> # Environment Microsoft Windows NT 10.0.18362.0 # Steps to reproduce Install app from windows store OR build from source and deploy Cascadia package. # Expected behavior Terminal runs successfully. # Actual behavior Error "The data area passed to a system call is too small." is shown and terminal does not open. ![image](https://user-images.githubusercontent.com/48676819/65696894-f225ca80-e071-11e9-8c71-5b6f5f448329.png)
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-30 23:37:24 +00:00
claunia commented 2026-01-30 23:37:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 26, 2019):

By any chance is this page relevant to your scenario?

For the record, the Windows Terminal is a "Desktop Bridge" application.

@zadjii-msft commented on GitHub (Sep 26, 2019): By any chance is [this page](https://support.microsoft.com/en-us/help/4073393/fix-the-data-area-passed-to-a-system-call-is-too-small-error-when-you) relevant to your scenario? For the record, the Windows Terminal _is_ a "Desktop Bridge" application.
claunia commented 2026-01-30 23:37:25 +00:00
Author
Owner
Copy Link

@jdudleyintelliflo commented on GitHub (Sep 26, 2019):

Ah thanks, yes I saw that page before but somehow I didn't think it was relevant. Will try that and hopefully it will resolve it.

@jdudleyintelliflo commented on GitHub (Sep 26, 2019): Ah thanks, yes I saw that page before but somehow I didn't think it was relevant. Will try that and hopefully it will resolve it.
claunia commented 2026-01-30 23:37:25 +00:00
Author
Owner
Copy Link

@jdudleyintelliflo commented on GitHub (Sep 26, 2019):

This resolves it - thanks.

@jdudleyintelliflo commented on GitHub (Sep 26, 2019): This resolves it - thanks.
claunia commented 2026-01-30 23:37:26 +00:00
Author
Owner
Copy Link

@keithdw1973 commented on GitHub (Jun 2, 2020):

I've just installed Windows Terminal from the Windows Store onto my Windows 10Pro (v 1909, OS Build 18363.836) Ryzen machine and am getting this same error when trying to run the software.
image

@keithdw1973 commented on GitHub (Jun 2, 2020): I've just installed Windows Terminal from the Windows Store onto my Windows 10Pro (v 1909, OS Build 18363.836) Ryzen machine and am getting this same error when trying to run the software. ![image](https://user-images.githubusercontent.com/40072536/83548935-6f0c1c80-a4fc-11ea-856b-8c83069a2130.png)
claunia commented 2026-01-30 23:37:26 +00:00
Author
Owner
Copy Link

@manugonzalez commented on GitHub (Jan 21, 2021):

Hi folks,

I've been running the same error for a while now.
How can this error be fixed?

@manugonzalez commented on GitHub (Jan 21, 2021): Hi folks, I've been running the same error for a while now. How can this error be fixed?
claunia commented 2026-01-30 23:37:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 21, 2021):

If you're hitting the same thing as OP, then

For more information about Desktop Bridge and workarounds for this issue, see this MSSQL Tiger Team Blog article.

From that link:

The hotfix for this issue for SQL Server 2017, SQL Server 2016 SP1 and SQL Server 2014 SP2 branches was included in following cumulative update.

https://support.microsoft.com/en-us/help/4073393/fix-the-data-area-passed-to-a-system-call-is-too-small-error-when-you

Fix for other versions of SQL Server is in progress. I'll update the article as and when additional details are available.

@zadjii-msft commented on GitHub (Jan 21, 2021): If you're hitting the same thing as OP, then > For more information about Desktop Bridge and workarounds for this issue, see [this MSSQL Tiger Team Blog article](https://docs.microsoft.com/en-us/archive/blogs/sql_server_team/centennial-appsdesktop-bridge-sql-server-and-error-the-data-area-passed-to-a-system-call-is-too-small). From that link: > The hotfix for this issue for SQL Server 2017, SQL Server 2016 SP1 and SQL Server 2014 SP2 branches was included in following cumulative update. > > https://support.microsoft.com/en-us/help/4073393/fix-the-data-area-passed-to-a-system-call-is-too-small-error-when-you > > Fix for other versions of SQL Server is in progress. I'll update the article as and when additional details are available.
claunia commented 2026-01-30 23:37:27 +00:00
Author
Owner
Copy Link

@keithdw1973 commented on GitHub (May 20, 2021):

I am having this exact problem with the "Windows Terminal" application in the Windows App Store and with the nVidia control pannel. I'm not sure how to resolve it as I am running Windows 10 and unless SQL server is part of the Windows 10 install, I have never installed it, I've never used it, I'm not even sure what it is.

@keithdw1973 commented on GitHub (May 20, 2021): I am having this exact problem with the "Windows Terminal" application in the Windows App Store and with the nVidia control pannel. I'm not sure how to resolve it as I am running Windows 10 and unless SQL server is part of the Windows 10 install, I have never installed it, I've never used it, I'm not even sure what it is.
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-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#4075
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?