this post was submitted on 08 Oct 2025
543 points (92.9% liked)

Linux

13501 readers
160 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
 

Note: the MacOS part is false

you are viewing a single comment's thread
view the rest of the comments
[–] AbsolutelyClawless@piefed.social 1 points 4 days ago* (last edited 4 days ago) (1 children)

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 3 points 4 days ago (2 children)

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

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.

[–] Ftumch@lemmy.dbzer0.com 3 points 4 days ago* (last edited 4 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.