• mech@feddit.org
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    16 days ago

    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).

    • LainTrain@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      God where do you people even come from? Coming out of the woodwork to free-associate about some incompetence of an imagined IT department when Microsoft fucks up this OS every other day and when Teams and Sheets Web (or whatever the M$ version of Google Sheets is called) and Windows 11 is the way it is.

      • shalafi@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        16 days ago

        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
          link
          fedilink
          English
          arrow-up
          1
          ·
          15 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

    • WanderingThoughts@europe.pub
      link
      fedilink
      arrow-up
      1
      ·
      16 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.

    • calcopiritus@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      16 days ago

      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.

    • grandma@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      0
      ·
      16 days ago

      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.