• Liam Mayfair
    link
    fedilink
    English
    arrow-up
    29
    ·
    edit-2
    3 days ago

    A few weeks ago I helped one of my client’s employees set up their brand new laptop, which came with Win11 installed, of course. They just need it for basic work stuff and there’s no chance in hell anything other than Windows is a viable option here.

    We work remotely so I would help them get set up to a point where they could at least share their screen to me, or I could take over via remote access myself, to finish the installation process. I just needed to guide them through the steps “blind” for a short while. Easy peasy, right?

    So we go through the Windows 11 first time setup together. All seems to go ok until Windows asks them to log into their MS account or create one. No problem, we should be able to do that, right? Only that we can’t. We’re connected to the WiFi, etc., yet they get some generic ass error message like “Sorry, something went wrong” and that’s that.

    Ok, so we can’t log in with an online account. Let’s try offline as a fallback! We set the username, password… “Sorry, something went wrong” again. We try to guess maybe it’s the password, it doesn’t match! Or it’s not strong enough! So we try all these different things for ages. Again, we’re getting no feedback whatsoever from Windows. Just “Something went wrong fuck you lol”.

    I don’t use Windows myself, I’ve been a Linux user for years now, I don’t have any freaking clue how to remotely diagnose a vague issue that literally prevents them from getting the laptop to a functional state. So I Google the problem and the recommended answer is to run this magic “bypassnro” command. It will cut all the mandatory online account bullshit, move straight to a reliable offline account setup screen, and allow us to, you know, actually do work? And it worked!

    If I hadn’t had that command at my disposal, that I was forced to use by Microsoft’s broken ass setup UX, I would’ve probably spent twice or three times longer coaching my non-tech-savvy client through booting into fail safe mode and doing all kinds of arcane sysadmin shit that I don’t even have to ever think about in Linux. All this just to get them into the desktop, on a brand new laptop.

    And Microsoft have now decided to take it away. Nice one.

    • AlphaOmega@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 days ago

      I was trying to set up win 11 laptop for my mom and ran into S mode, that took like an hour to walk my elderly mom through the steps to disable it so I could remote in. Finally gave up and grab a MS approved remote desktop app to remote in a disable the S mode, its s for Shit. Of course the other remote desktop app crashed. Sorry family, no more windows PCs for you

      • endeavor@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        3 days ago

        You could’ve just had your mom install linux and you wouldn’t have to remote in since theres nothing to do. Everything just works.