• Katzastrophe@feddit.de
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    5 months ago

    Tried that a few months ago with a factory new machine and it did not work. Though it might work on Pro machines

    • echutaa@programming.dev
      link
      fedilink
      arrow-up
      9
      ·
      5 months ago

      You just need quotes on it, ms fucked up the directory traversal “oobe/bypassnro.cmd” worked for me setting up a user machine yesterday

    • A Mouse@midwest.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      That’s interesting! I wonder if they are locking down factory installations.

      About a month ago I was able to do it with a fresh install of Pro in a VM, I’ll do a quick test and see if it works on Home…and it works too. I had to disconnect the network and then run the OOBE\BYPASSNRO command, it rebooted and gave me the continue without network and limited setup options.

      • Katzastrophe@feddit.de
        link
        fedilink
        arrow-up
        4
        ·
        5 months ago

        That’s super weird, but disconnecting the network is the only way that you can reliably setup the machine without an account in my experience

    • BigDev@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      I had to refresh a pc with Windows 11 recently (unfortunately) and I can confirm it works, but I found it only works on a completely clean install, and you have to run the command IMMEDIATELY when starting setup. I had to re-install twice, because the first time I connected to Wi-Fi, and even running the command and disabling wifi, it still demanded an account. I had to wipe the drive an install a second time, then run the command right at the start of the setup process, before doing anything. THEN it let me skip connecting to internet and logging into an account.