Its possible the IT admin misconfigured but blocking the terminal or the store would not make sense at this company since most employees need them on a daily basis.
In a previous company, they roled out their update every few months. Every time, it closed all the ports we need to actually work. Make ticket, wait until IT got around to it, tell people no connection means no work. Those were the days to update documentation.
Could be part of an ISMS framework for ISO 27001, too. Just went through the latest round of audits at my workplace, with SOC 2 and ISO 27001 being the most recent. Think I aged 15 years this time around.
I’m a Windows sysadmin, this is the exact explanation. The only other thing, and this is going way out on a limb, is that terminal was installed through the Windows Store and something related is busted. I’ve never even heard of a company utilizing the Store for installations.
Others have already provided links to the GitHub issue detailing this bug and a Microsift employee confirming this indeed seems to be a micrsoft error although another team than the terminal one as it also affects multiple other programs such as the screengrab tool and notepad.
Then your IT has blocked use of the terminal for your account.
This isn’t a Microsoft issue (except for the useless error message).
Its possible the IT admin misconfigured but blocking the terminal or the store would not make sense at this company since most employees need them on a daily basis.
Update: most definitely a microsoft issue https://github.com/microsoft/terminal/issues/19764
Beautiful bug report
Never! Couldn’t possibly be M$’s fault! It’s definitely somehow your IT department!
I mean, it is.
They should have used Linux.
/s
That’s definitely an issue with your IT department. My work Windows laptop came with the terminal accessible.
Yea and Usain Bolt can run real fast and you can’t
You got problems buddy
I mean I was able to open the terminal just fine a few hours ago
Maybe they’ve updated their security policies? Could be to prevent users from installing unapproved software via winget, etc.
I have definitely never done that myself, if anyone asks …
It’s a MS issue, not isolated
In a previous company, they roled out their update every few months. Every time, it closed all the ports we need to actually work. Make ticket, wait until IT got around to it, tell people no connection means no work. Those were the days to update documentation.
deleted by creator
Could be part of an ISMS framework for ISO 27001, too. Just went through the latest round of audits at my workplace, with SOC 2 and ISO 27001 being the most recent. Think I aged 15 years this time around.
That’s an assumption
I’m a Windows sysadmin, this is the exact explanation. The only other thing, and this is going way out on a limb, is that terminal was installed through the Windows Store and something related is busted. I’ve never even heard of a company utilizing the Store for installations.
Others have already provided links to the GitHub issue detailing this bug and a Microsift employee confirming this indeed seems to be a micrsoft error although another team than the terminal one as it also affects multiple other programs such as the screengrab tool and notepad.
One of those comments can be found here: https://lemmy.dbzer0.com/comment/23913723
Nope, there’s official confirmation that it is.
Not really. Today at work that error appeared to me. As a software developer of course I have access to terminal, I use it every day.
I just closed the message and opened the terminal again, and it worked.
This is Microsoft’s fault, not any other’s.
What do you get when your search “terminal”? My home rig defaults to PowerShell, but I likely changed something years ago.
The terminal