Microsoft has closed a surprisingly simple way to create a local account during Windows 11 setup: the small “Learn more” link that briefly let users move past Microsoft account sign-in without command-line workarounds. Windows Latest reports that the link now behaves like a normal information page on a fresh Windows 11 26H2 ISO, returning users to the sign-in flow instead of moving them to local account creation.

For everyday users, this may look like a minor setup change. For IT admins, PC repair shops, testers, and Windows enthusiasts, it is another sign that Microsoft is continuing to tighten the out-of-box experience around online accounts. That matters for labs, repair benches, and privacy-conscious home users.

What changed in Windows 11 setup

According to Windows Latest, the previous behavior appeared on the Microsoft account sign-in screen during Windows 11 setup. The screen included explanatory text about syncing data and backing up files to OneDrive, ending with a small “Learn more” link. For a short period, clicking that link opened a data-management page and then advanced the setup process to the local user creation screen.

The important point is that this was not a polished, documented local-account option. It looked more like an unintended path through the setup flow. There were no registry edits, no fake email address trick, no unplugging the network cable, and no command prompt sequence. That made it attractive because it was understandable for non-technical users and fast for technicians preparing many machines.

Windows Latest says the behavior has now changed on fresh Windows 11 26H2 installation media. The same link still opens a page explaining how Microsoft manages data, but setup no longer advances to “Who’s going to use this device?” The available route is back to Microsoft account sign-in.

Why Microsoft keeps closing these routes

Microsoft has been moving in this direction for years. Windows 11 Home has long pushed Microsoft account sign-in during setup, and Windows 11 Pro has also become less friendly to local-first setup in consumer-style flows. Older bypasses such as oobe\bypassnro, fake account entries, registry toggles, or URI-based local-account commands have been blocked or limited in newer Insider and public builds.

Microsoft’s stated argument is that some bypasses skip setup screens that configure important features. From a product-management perspective, that may include device encryption recovery, OneDrive backup prompts, Microsoft Store identity, Find my device, Windows settings sync, and subscription offers. From an administrator’s perspective, however, the result is often extra friction before a PC can be tested, imaged, repaired, resold, or handed to a user who does not want cloud sign-in.

Both views can be true. A Microsoft account can be useful for many people, especially on personal PCs where cloud recovery and syncing are expected. But the lack of a visible “Use a local account” option makes Windows setup feel less like configuration and more like enrollment.

Practical impact for IT users and enthusiasts

The impact depends on how you deploy Windows.

If you manage business devices through Entra ID, Autopilot, Intune, or traditional imaging, this specific consumer setup loophole may not matter. Your deployment process should already define identity, management, policy, and user provisioning.

If you frequently reinstall Windows on test hardware, virtual machines, lab PCs, or customer systems, the change matters more. Local accounts remain useful when a machine should not be tied to a technician’s Microsoft account, when internet access is unavailable or intentionally isolated, or when the final owner has not yet been assigned.

Repair shops and refurbishers should be especially careful. Signing in with the wrong online account during setup can create cleanup work, privacy concerns, and licensing confusion. A clean local account is often the safest temporary state until the customer takes ownership.

What still works

Windows Latest notes that Windows 11 Pro still offers clunkier options such as domain join paths in some setup scenarios, and third-party installation media tools such as Rufus can prepare Windows media with local-account-friendly options. Those routes are more technical than the removed link behavior, but they are also more intentional and repeatable.

For organizations, the better answer is not to depend on loopholes at all. Use supported deployment tooling, documented unattended installation settings where appropriate, and a clear policy for whether devices should be joined to Entra ID, Active Directory, a workgroup, or a temporary local setup account.

For home users, the practical advice is simple: expect Microsoft to keep changing setup behavior. A bypass that works this month may disappear in the next ISO, cumulative update, or server-side setup change.

The bigger signal

The notable part is not only that Microsoft closed this path. It is how quickly it happened. Microsoft executives have acknowledged complaints about forced online sign-in and have also talked publicly about making Windows calmer and less cluttered. Closing a local-account escape route while setup still promotes cloud services will reinforce the view that Microsoft account growth remains a priority.

Windows would be better served by a clearer choice: recommend a Microsoft account, explain the benefits, but keep a visible local-account option for people who need it. That would reduce the cat-and-mouse game, help legitimate technicians, and make Windows setup feel more trustworthy.

Until then, Windows 11 local account setup remains a moving target. If local-first installation matters to your workflow, document the method you use, keep installation media under version control, and retest the process before you need it on a production or customer machine.

Source: Windows Latest