this post was submitted on 21 Jan 2026
1061 points (97.1% liked)

Programmer Humor

28803 readers
343 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] grandma@sh.itjust.works 139 points 5 days ago (1 children)

Its a work device so I'm signed in like a good little corporate peon, still they manage to fuck it up.

[–] mech@feddit.org 75 points 5 days ago* (last edited 5 days ago) (6 children)

Then your IT has blocked use of the terminal and store for your account.
Which makes sense for regular users to reduce the chance of fuck-ups and rise of a shadow IT.
This isn't a Microsoft issue (except for the slightly unspecific error message).

[–] grandma@sh.itjust.works 51 points 5 days ago* (last edited 5 days ago) (2 children)

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.

[–] grandma@sh.itjust.works 71 points 5 days ago (2 children)
[–] Confused_Emus@lemmy.dbzer0.com 54 points 5 days ago (1 children)

Never! Couldn’t possibly be M$’s fault! It’s definitely somehow your IT department!

[–] msage@programming.dev 10 points 5 days ago

I mean, it is.

They should have used Linux.

/s

[–] craftrabbit@lemmy.zip 36 points 5 days ago

Beautiful bug report

Expected Behaviour:

It would be pretty nice, if the terminal would open

[–] 87Six@lemmy.zip 14 points 5 days ago (1 children)
[–] shalafi@lemmy.world -5 points 5 days ago (1 children)

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.

[–] GojuRyu@lemmy.world 3 points 4 days ago

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

[–] calcopiritus@lemmy.world 14 points 5 days ago (1 children)

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.

[–] shalafi@lemmy.world 1 points 5 days ago (1 children)

What do you get when your search "terminal"? My home rig defaults to PowerShell, but I likely changed something years ago.

[–] calcopiritus@lemmy.world 2 points 5 days ago
[–] WanderingThoughts@europe.pub 9 points 5 days ago

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.

[–] TheBat@lemmy.world 6 points 5 days ago (1 children)

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.