• TheTechnician27@lemmy.world
    link
    fedilink
    English
    arrow-up
    88
    arrow-down
    2
    ·
    13 hours ago

    Technically the numerical code still gives you a precise search key to find other people discussing the same issue.

    … You know, as would be useful for a serious operating system where online support doesn’t mean trawling the bowels of Reddit praying somebody’s had the same issue and found a reproducible solution.

    • JoshCodes@programming.dev
      link
      fedilink
      English
      arrow-up
      4
      ·
      4 hours ago

      “Question: I am getting error with code 0xblahblahblah. How to fix?”

      “Deleted response”

      Reply 1: “Youre a life saver mate, thank you.”

      Reply 2: “I would kiss you if you were here”

      Reply 3: “Absolute legend, this fix is so obvious, thank you for pointing it out!”

    • cals11@programming.dev
      link
      fedilink
      arrow-up
      57
      ·
      10 hours ago

      Hello I’m a 12 year Microsoft MVP and Certified independent advisor here to help.

      Please type “CMD” into the start menu then type “ckdsk /f /r”

      If this solved your issue please click on “Accept as solution”!

    • TrickDacy@lemmy.world
      link
      fedilink
      arrow-up
      29
      ·
      12 hours ago

      I have copied down and manually typed out numbers like that many times when using windows. I’m not sure it ever once helped me in the slightest.

    • marcos@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      10 hours ago

      The problem is that “the same issue” here means “there’s any error at all with the MS Store”. Any discussion about there will be useless.

    • stevestevesteve@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      11 hours ago

      Except the code covers SUCH a vague issue that it’s useless. Not very precise when any issue with the store gives you the same code. Maybe it couldn’t find a DNS record for the online store. Maybe its local db is corrupt. Maybe it’s been locked out administratively. Doesn’t matter which root cause, same error code, so it’s not a “precise” error code.

      These may not be the case in this instance, but in many, many other instances, it sure has been