Generated profiles of "Developer cmd/pwsh for VS" have different guid for even same distribution #17132

Open
opened 2026-01-31 05:33:04 +00:00 by claunia · 0 comments
Owner

Originally created by @hsupu on GitHub (Apr 1, 2022).

Windows Terminal version

1.12.10393.0

Windows build number

10.0.19044.0 or 10.0.22000.0

Other Software

No response

Steps to reproduce

I want to sync the settings of wt between PCs, hit this issue.

I installed VS 2022 Community and VSSetup (pwsh module). Get-VSSetupInstance reported different InstanceId.

I read the code and found wt uses VS InstanceId to generate guid.

Expected Behavior

Either VS InstanceId becomes identical for same distribution or WT generates profiles uses a independent way.

Actual Behavior

WT generates profiles from VS InstanceId which is different between PCs.

Originally created by @hsupu on GitHub (Apr 1, 2022). ### Windows Terminal version 1.12.10393.0 ### Windows build number 10.0.19044.0 or 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce I want to sync the settings of wt between PCs, hit this issue. I installed VS 2022 Community and VSSetup (pwsh module). `Get-VSSetupInstance` reported different `InstanceId`. I read the code and found wt uses VS InstanceId to generate guid. ### Expected Behavior Either VS InstanceId becomes identical for same distribution or WT generates profiles uses a independent way. ### Actual Behavior WT generates profiles from VS InstanceId which is different between PCs.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:33:04 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17132