Note: the MacOS part is false

  • AbsolutelyClawless@piefed.social
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    7 days ago

    Isn’t the second sentence incorrect? You can force local account creation by running oobe\bypassnro to bypass the internet connection requirement which lets you create a local account instead. And at least on the Pro(?) version it can be bypassed by choosing the Domain account option even if the PC won’t be joined to any domain. It just creates a local account. I have to deal with Win 11 installations as part of my job and this is the way I’ve been doing it.

    All this is not to defend M$’ attempt to force this bullshit on the users. I’m a Linux user and steer clear of M$ products whenever and wherever I can. Just wanted to point out an M$ account isn’t necessary to setup Win 11. (Unless these workarounds are only possible in the Pro version?)

    • BanMe@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 days ago

      oobe\bypassnro was disabled in Windows 10 by an update 2-3 years ago, it doesn’t work in Windows 11 at all.

      • Ftumch@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        6 days ago

        I installed Windows 11 Pro 24H2 yesterday and the oobe\bypassnro trick worked for me. You just have to make sure no ethernet cable is connected. Then if you tell the installer you have no internet, it’ll let you create a local account.

      • AbsolutelyClawless@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 days ago

        What the other person said. But I gotta say it’s a bit weird to reply to me that something doesn’t work when I’ve been doing it that way in present day on present OS.