• u/lukmly013 💾 (lemmy.sdf.org)@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 day ago

    You can still force local account. Edit: nevermind, first sentence of the article:

    Earlier today, we published an article regarding Microsoft’s recent removal of the BYPASSNRO script and how it has irked Windows 11 users

    Well, fuck.

    On setup: Shift + F10 -> click into the CMD window (it opens unfocused)

    cd oobe
    bypassnro
    

    And do not connect to network until you finish setup.

    Disabling auto updates was also very simple and intuitive. Couldn’t be easier.

    Meta + R -> Type gpedit.msc and press enter -> On left click Administrative templates -> All settings -> Configure Automatic Updates -> Select option 2, Enabled and Apply

    • kernelle@0d.gs
      link
      fedilink
      English
      arrow-up
      6
      ·
      23 hours ago

      Bypassnro is the old method, no longer working since 24H2. I’ve tested this method on GitHub and it works for normal AND S-mode devices.

      • Ctrl + Shift + J before selecting secondary keyboard layout (sometimes you need to click on the outside borders of the form so the dev console pops up)
      • Type this (can use autocomplete): WinJS.Application.restart(“ms-cxh://LOCALONLY”)
      • Setup with local account
    • SpikesOtherDog@ani.social
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 day ago

      I’m still creating local accounts using the bypass in the auto unattend file.

      If a drive is crypto locked and there is only a local account, it might as well be wiped if nobody has a password.