1082
What a joke, can't believe people still voluntarily use this OS (sh.itjust.works)
submitted 9 months ago by to c/programmer_humor@programming.dev
171 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 31 points 9 months ago (8 children)

The Microsoft Store is impressively bad. So many random errors that don't give any helpful information that are impossible to fix.

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 11 points 9 months ago (4 children)

    Couldn't install iTunes because my clock was wrong. That certainly wasn't the ERROR I was presented with, but was ultimately the root cause.

    That, coincidentally, was the very same evening that I decided to and did uninstall windows on that machine.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 7 points 9 months ago (3 children)

    It’s probably because TLS uses your system clock to validate certificates. If your clock doesn’t match the server you’re connecting to, TLS fails and you get an “https failed/connection is insecure” error. And Windows likely uses https in the store to ensure MITM attacks can’t replace valid downloads with malicious ones.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 6 points 9 months ago* (2 children)

    I understand the mechanism, and why it is important.

    I don't understand why the error message from the store was nothing more than an error code, and why the MSKB for that code had absolutely no mention of a failed ssl negotiation as a possible cause.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 9 months ago (1 child)

    Time->TLS errors aren't handled well anywhere.

    As critical as they are to 2fa and TLS, you'd think every OS out there would poke around a few time servers and scream bloody murder if the time was off.

    Honestly, I think we, as a society, have leaned a little too hard into time as a precise critical failure point. It's fine for things like GPS that actually require it. but our clocks don't need to be precisely the same to tell how recent a request and response are and we can certainly make better hashing algos

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 9 months ago

    wget will give you a sniff of what the problem is. Microsoft Store will not.

    I don't NEED an application to necessarily pinpoint the error. Just even a rough direction. Any browser will explicitly tell you if there is a cert issue. That's more than enough to go on.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 7 points 9 months ago* (1 child)

    I have no idea who thought it would be a good idea to give an error code to a user in Hexadecimal form, with no other information.

    An error occurred: 0x 80070003

    is hardly helpful at all.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 9 months ago

    Oddly enough, giving the general public exact error messages ends up costing you in support and reputation.

    They obscure the messages because the inexperienced masses start digging up red herrings. Knowledge to someone with zero experience causes a lot of confusion.

    The experienced and capable users look up the codes and think about it for a minute, check their vpn, maybe a health dashboard, maybe reboot.

    Just about every complex machine out there give error codes instad of real messages, even when they have large displays capable of telling you exactly what the condition is.

  • permalink
  • fedilink
  • source
  • parent