UTF-8 ACP seems to hork the Terminal store app forever? "The parameter is incorrect" #4227

Closed
opened 2026-01-30 23:41:27 +00:00 by claunia · 6 comments
Owner

Originally created by @aliozgur on GitHub (Oct 3, 2019).

Environment

Windows build number: 10.0.18362.0
Windows Terminal version: v0.5.2681.0

Steps to reproduce

Find the Windows Terminal (Preview) app and click.

Expected behavior

Windows Terminal should launch.

Actual behavior

image

Originally created by @aliozgur on GitHub (Oct 3, 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 ```none Windows build number: 10.0.18362.0 Windows Terminal version: v0.5.2681.0 ``` # Steps to reproduce Find the Windows Terminal (Preview) app and click. <!-- A description of how to trigger this bug. --> # Expected behavior Windows Terminal should launch. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior ![image](https://user-images.githubusercontent.com/799194/66106817-796dc380-e5c7-11e9-8a69-6d181b916ab8.png) <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-ReproNeeds-Attention labels 2026-01-30 23:41:27 +00:00
Author
Owner

@aliozgur commented on GitHub (Oct 3, 2019):

This problem popped up after I turned on the "Use Unicode UTF-8 for worldwide lanugage support".
image

The interesting thing is, the problem still exists even if I turn off the "Use Unicode UTF-8 for worldwide lanugage support" feature.

@aliozgur commented on GitHub (Oct 3, 2019): This problem popped up after I turned on the "Use Unicode UTF-8 for worldwide lanugage support". ![image](https://user-images.githubusercontent.com/799194/66107056-07e24500-e5c8-11e9-9701-38a918542186.png) The interesting thing is, the problem still exists even if I turn off the "Use Unicode UTF-8 for worldwide lanugage support" feature.
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 8, 2019):

So wait -- you turned on this feature, rebooted, the problem began, and now you've turned it off and rebooted again and it still fails? The globalization team (who owns the UTF-8 ACP feature(!)) is going to find this extremely interesting. Thanks!

@DHowett-MSFT commented on GitHub (Oct 8, 2019): So wait -- you turned on this feature, rebooted, the problem began, and now you've turned it off and rebooted again _and it still fails_? The globalization team (who owns the UTF-8 ACP feature(!)) is going to find this extremely interesting. Thanks!
Author
Owner

@aliozgur commented on GitHub (Oct 8, 2019):

Yes that’s exactly the case. Turned on the feature, restarted Windows and terminal failed. Turned off the feature, restarted Windows again and terminal still fails.

@aliozgur commented on GitHub (Oct 8, 2019): Yes that’s exactly the case. Turned on the feature, restarted Windows and terminal failed. Turned off the feature, restarted Windows again and terminal still fails.
Author
Owner

@aliozgur commented on GitHub (Oct 11, 2019):

This happende for another Microsoft AppStore app Trello as well.

First I got this error (A different one)
C:\Program Files\WindowsApps\45273LiamForsyth.PawsforTrello_2.11.1.0_x64__7pb5ddty8z1pa\app\Trello.exe
The data area passed to a system call is too small.

On subsequent attempts to run the app again I got "The parameter is incorrect" error.

@aliozgur commented on GitHub (Oct 11, 2019): This happende for another Microsoft AppStore app Trello as well. First I got this error (A different one) C:\Program Files\WindowsApps\45273LiamForsyth.PawsforTrello_2.11.1.0_x64__7pb5ddty8z1pa\app\Trello.exe The data area passed to a system call is too small. On subsequent attempts to run the app again I got "The parameter is incorrect" error.
Author
Owner

@aliozgur commented on GitHub (Oct 11, 2019):

Ok, I think I've resolved the problem. Here are the steps I've followed to resolve the issue

  • I've noticed some ESENT related errors in Event Log
  • Then I Googled for the logged ESENT errors.
  • I could not find any direct solution for those errors, but some guys advised to update SQL Server
  • Then I updaded my local SQL Server 2014 to lates service pack (SP3) and then installed the latest Cummulative Update (CU4)

After couple of restarts Widows Terminal and the other app (Trello) seems to work.

@aliozgur commented on GitHub (Oct 11, 2019): Ok, I think I've resolved the problem. Here are the steps I've followed to resolve the issue * I've noticed some ESENT related errors in Event Log * Then I Googled for the logged ESENT errors. * I could not find any direct solution for those errors, but some guys advised to update SQL Server * Then I updaded my local SQL Server 2014 to lates service pack (SP3) and then installed the latest Cummulative Update (CU4) After couple of restarts Widows Terminal and the other app (Trello) seems to work.
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 23, 2019):

That's really interesting. Thanks for following up! It might be worth filing an issue on the "App installation/deployment" node in feedback hub if you hit this issue again. 😄

@DHowett-MSFT commented on GitHub (Oct 23, 2019): That's really interesting. Thanks for following up! It might be worth filing an issue on the "App installation/deployment" node in feedback hub if you hit this issue again. :smile:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4227