Auto adding Azure Cloud Shell profile #23144

Closed
opened 2026-01-31 08:33:36 +00:00 by claunia · 4 comments
Owner

Originally created by @inoperable on GitHub (Apr 13, 2025).

Windows Terminal version

1.24.250409001-llm

Windows build number

10.0.27823.1000

Other Software

Windows Terminal keeps adding the Azure Cloud Shell profile despite me deleting it manually.
I don't appreciate M$ typical enforcement tactics. I need to delete this twice, then it gives up and
won't do it- but with every update it does this again.

Please, stop spilling your corporate strategies into everything

Steps to reproduce

Delete profile
Magic
Its here again!

Expected Behavior

Not it pop up automatically EVERY SINGLE TIME i update the WT

Actual Behavior

Auto addition of the profile despite my choice to delete it.

Originally created by @inoperable on GitHub (Apr 13, 2025). ### Windows Terminal version 1.24.250409001-llm ### Windows build number 10.0.27823.1000 ### Other Software Windows Terminal keeps adding the **Azure Cloud Shell** profile despite me deleting it manually. I don't appreciate M$ typical enforcement tactics. I need to delete this twice, then it gives up and won't do it- but with every update it does this again. Please, stop spilling your corporate strategies into everything ### Steps to reproduce Delete profile Magic Its here again! ### Expected Behavior Not it pop up automatically EVERY SINGLE TIME i update the WT ### Actual Behavior Auto addition of the profile despite my choice to delete it.
claunia added the Needs-TriageIssue-BugNeeds-AttentionResolution-Won't-Fix labels 2026-01-31 08:33:37 +00:00
Author
Owner

@DHowett commented on GitHub (Apr 14, 2025):

I don't appreciate M$ typical enforcement tactics.
Please, stop spilling your corporate strategies into everything

You may not be aware that we've worked1 pretty2 hard3 to make sure Terminal remembers that you've deleted an autogenerated profile. I would appreciate it if you didn't assume negative intent on behalf of my team.

Most of the above work requires that state.json (lives next to settings.json) be writable, and for it to be preserved across upgrades.

I can't help but notice that you're using the unpackaged or portable version of Terminal.

If you're using the unpackaged one, can you check the permissions on %LOCALAPPDATA%\Microsoft\Windows Terminal?

If you're using the portable one, are you migrating the .portable marker file and the settings directory from build to build/?

@DHowett commented on GitHub (Apr 14, 2025): > _I don't appreciate_ M$ typical enforcement tactics. > Please, stop spilling your corporate strategies into everything You may not be aware that we've worked[^1] pretty[^2] hard[^3] to make sure Terminal remembers that you've deleted an autogenerated profile. I _would_ appreciate it if you didn't assume negative intent on behalf of my team. Most of the above work requires that `state.json` (lives next to `settings.json`) be writable, and for it to be preserved across upgrades. I can't help but notice that you're using the unpackaged or portable version of Terminal. If you're using the unpackaged one, can you check the permissions on `%LOCALAPPDATA%\Microsoft\Windows Terminal`? If you're using the portable one, are you migrating the `.portable` marker file and the `settings` directory from build to build/? [^1]: #10910 [^2]: #8324 #10513 [^3]: #11007
Author
Owner

@DHowett commented on GitHub (Apr 14, 2025):

And can you, by chance, share a copy of state.json?

@DHowett commented on GitHub (Apr 14, 2025): And can you, by chance, share a copy of `state.json`?
Author
Owner

@inoperable commented on GitHub (Apr 14, 2025):

You turn this into some imaginary personal attack, it's not - If you have
to work hard to implement features that are questionable and maybe illegal
in some jurisdictions then maybe consider legal advice or career paths. I
use corporate software on my hardware from the company you work at, a
company that use policies with so many questionable tactics at the edge of
legal, sane and or just simply spindoctor human decency to an absurdity
levels which undeniable examples could fill a decent sized book sounds very
plausible. I don't question your work, I question the corporate wrapper
around it.

Dustin L. Howett @.***> schrieb am Mo., 14. Apr. 2025,
19:41:

And can you, by chance, share a copy of state.json?


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/18788#issuecomment-2802427140,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL7SAXLDBLLX67ZNAUPU4D2ZPXLLAVCNFSM6AAAAAB3A2ZXLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBSGQZDOMJUGA
.
You are receiving this because you authored the thread.Message ID:
@.***>
DHowett left a comment (microsoft/terminal#18788)
https://github.com/microsoft/terminal/issues/18788#issuecomment-2802427140

And can you, by chance, share a copy of state.json?


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/18788#issuecomment-2802427140,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL7SAXLDBLLX67ZNAUPU4D2ZPXLLAVCNFSM6AAAAAB3A2ZXLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBSGQZDOMJUGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@inoperable commented on GitHub (Apr 14, 2025): You turn this into some imaginary personal attack, it's not - If you have to work hard to implement features that are questionable and maybe illegal in some jurisdictions then maybe consider legal advice or career paths. I use corporate software on my hardware from the company you work at, a company that use policies with so many questionable tactics at the edge of legal, sane and or just simply spindoctor human decency to an absurdity levels which undeniable examples could fill a decent sized book sounds very plausible. I don't question your work, I question the corporate wrapper around it. Dustin L. Howett ***@***.***> schrieb am Mo., 14. Apr. 2025, 19:41: > And can you, by chance, share a copy of state.json? > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/18788#issuecomment-2802427140>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAL7SAXLDBLLX67ZNAUPU4D2ZPXLLAVCNFSM6AAAAAB3A2ZXLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBSGQZDOMJUGA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > *DHowett* left a comment (microsoft/terminal#18788) > <https://github.com/microsoft/terminal/issues/18788#issuecomment-2802427140> > > And can you, by chance, share a copy of state.json? > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/18788#issuecomment-2802427140>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAL7SAXLDBLLX67ZNAUPU4D2ZPXLLAVCNFSM6AAAAAB3A2ZXLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBSGQZDOMJUGA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@DHowett commented on GitHub (Apr 14, 2025):

Marking as won't fix.

@DHowett commented on GitHub (Apr 14, 2025): Marking as won't fix.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23144