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

'Parameter is Incorrect' on Azure Virtual Desktop with FSLogix #19298

New Issue
Closed
opened 2026-01-31 06:39:19 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 06:39:19 +00:00
Owner
Copy Link

Originally created by @lcondliffe on GitHub (Feb 1, 2023).

Windows Terminal version

1.15.3466.0

Windows build number

10.0.22621.0

Other Software

FSlogix 2.9.8171.14983

Steps to reproduce

Create a session host pool based on Azure image which has Windows Terminal as the default shell:

publuisher = "MicrosoftWindowsDesktop"
offer = "windows-11"
sku = "win11-22h2-avd"

First login as a new user creates an FSLogix profile and Terminal works just fine.

Sign out and back in again, try to launch Terminal and we received a 'parameter is incorrect' error.

Signing out and back in again SOMETIMES allows the app to launch again, as does restarting the session host and signing in again. I've also observed this happen mid-session just by closing Terminal and trying to open it again.

I believe this is somehow related to the use of FSlogix profile containers, as deleting 'C:\Users\USERNAME\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe' when the issue is re-created and then re-launching allows the app to launch again, however we need to persist this directory I believe to maintain Terminal settings across AVD sessions.

Other Windows Store / APPx applications included with the OS like Calculator and Clock seem unaffected by the same issue, it seems to be limited to Terminal.

Expected Behavior

Error free launch of Windows Terminal.

Actual Behavior

image

Originally created by @lcondliffe on GitHub (Feb 1, 2023). ### Windows Terminal version 1.15.3466.0 ### Windows build number 10.0.22621.0 ### Other Software FSlogix 2.9.8171.14983 ### Steps to reproduce Create a session host pool based on Azure image which has Windows Terminal as the default shell: publuisher = "MicrosoftWindowsDesktop" offer = "windows-11" sku = "win11-22h2-avd" First login as a new user creates an FSLogix profile and Terminal works just fine. Sign out and back in again, try to launch Terminal and we received a 'parameter is incorrect' error. Signing out and back in again SOMETIMES allows the app to launch again, as does restarting the session host and signing in again. I've also observed this happen mid-session just by closing Terminal and trying to open it again. I believe this is somehow related to the use of FSlogix profile containers, as deleting 'C:\Users\USERNAME\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe' when the issue is re-created and then re-launching allows the app to launch again, however we need to persist this directory I believe to maintain Terminal settings across AVD sessions. Other Windows Store / APPx applications included with the OS like Calculator and Clock seem unaffected by the same issue, it seems to be limited to Terminal. ### Expected Behavior Error free launch of Windows Terminal. ### Actual Behavior ![image](https://user-images.githubusercontent.com/51878981/215992872-11a3328e-19d6-425d-b502-e82df43aa11a.png)
claunia added the Needs-TriageIssue-BugResolution-ExternalTracking-External labels 2026-01-31 06:39:20 +00:00
claunia commented 2026-01-31 06:39:22 +00:00
Author
Owner
Copy Link

@lcondliffe commented on GitHub (Feb 6, 2023):

I believe that FSLogix version 2.9.8361.52326 fixes this problem since the addition of the feature to include a new AppX process on sign-out detailed in the release notes:

https://learn.microsoft.com/en-us/fslogix/whats-new#fslogix-2210-29836152326

So far I've not been able to re-create the issue after updating FSlogix on a test session host.

@lcondliffe commented on GitHub (Feb 6, 2023): I believe that FSLogix version 2.9.8361.52326 fixes this problem since the addition of the feature to include a new AppX process on sign-out detailed in the release notes: https://learn.microsoft.com/en-us/fslogix/whats-new#fslogix-2210-29836152326 So far I've not been able to re-create the issue after updating FSlogix on a test session host.
claunia commented 2026-01-31 06:39:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 6, 2023):

Thanks for following up! You beat us to finding the duplicate in our backlog. It'll be great to have this info in case somebody else asks. 😄

@DHowett commented on GitHub (Feb 6, 2023): Thanks for following up! You beat us to finding the duplicate in our backlog. It'll be great to have this info in case somebody else asks. :smile:
claunia commented 2026-01-31 06:39:23 +00:00
Author
Owner
Copy Link

@lcondliffe commented on GitHub (Feb 28, 2023):

I've since managed to re-produce this issue on FSLogix version 2.9.8361.52326

It seems a lot less frequent than when we were using the previous FSLogix version, it seems to happen more when other users are logged into the AVD session host.

image

Other inbox apps seem consistently ok so I'm not sure it's a specific interoperability issue between FSlogix and Terminal.

@lcondliffe commented on GitHub (Feb 28, 2023): I've since managed to re-produce this issue on FSLogix version 2.9.8361.52326 It seems a lot less frequent than when we were using the previous FSLogix version, it seems to happen more when other users are logged into the AVD session host. ![image](https://user-images.githubusercontent.com/51878981/221827177-5badae33-1cdf-428f-a1bc-cdac204062cd.png) Other inbox apps seem consistently ok so I'm not sure it's a specific interoperability issue between FSlogix and Terminal.
claunia commented 2026-01-31 06:39:23 +00:00
Author
Owner
Copy Link

@msft-jasonparker commented on GitHub (Mar 9, 2023):

We just released HF1 for 2210 which has some fixes for the InstallAppxPackages feature flag.

As Terminal is an inbox app, we expect it to work. Not all AppX package and apps are equal and there could be an interop issue that we are unaware of. We have not seen this issue in our test environments.

UPDATE:
In order to fully investigate, please open a support ticket selecting FSLogix as the support type and Apps: Appx or UWP application issues as the subtype. We'll want to have support help you run a procmon and then have it reviewed by an FSLogix SME.

@msft-jasonparker commented on GitHub (Mar 9, 2023): We just released [HF1 for 2210](https://learn.microsoft.com/en-us/fslogix/whats-new#fslogix-2210-hotfix-1-29844042104) which has some fixes for the InstallAppxPackages feature flag. As Terminal is an inbox app, we expect it to work. Not all AppX package and apps are equal and there could be an interop issue that we are unaware of. We have not seen this issue in our test environments. **UPDATE:** In order to fully investigate, please open a [support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) selecting FSLogix as the support type and Apps: Appx or UWP application issues as the subtype. We'll want to have support help you run a procmon and then have it reviewed by an FSLogix SME.
claunia commented 2026-01-31 06:39:24 +00:00
Author
Owner
Copy Link

@lcondliffe commented on GitHub (Mar 10, 2023):

Thanks Jason,

I'll see if I can complete a new build with the hotfix version asap and see if the issue can still be re-created there.

I already have a Microsoft support case open alongside this issue with the FSLogix team under ref:

#2302280040003958

I will be difficult to run a procmon as so far I've not managed to determine some exact steps to re-create the issue, it just appears seemingly at random.

@lcondliffe commented on GitHub (Mar 10, 2023): Thanks Jason, I'll see if I can complete a new build with the hotfix version asap and see if the issue can still be re-created there. I already have a Microsoft support case open alongside this issue with the FSLogix team under ref: #2302280040003958 I will be difficult to run a procmon as so far I've not managed to determine some exact steps to re-create the issue, it just appears seemingly at random.
claunia commented 2026-01-31 06:39:24 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 10, 2023):

FWIW, I'm gonna close this out since this seems like it's an external issue. If the investigation comes back pointing the finger at the Terminal, we'd be more than happy to re-open and take another look.

Thanks everyone!

@zadjii-msft commented on GitHub (Mar 10, 2023): FWIW, I'm gonna close this out since this _seems_ like it's an external issue. If the investigation comes back pointing the finger at the Terminal, we'd be more than happy to re-open and take another look. Thanks everyone!
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 Tracking-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#19298
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?