Windows 11 Home OOBE ‘Learn More’ Local Account Bypass Reportedly Closed

What was reportedly blocked​

On October 9, Neowin reported that Redmond has quietly patched the trick as X user and Windows enthusiast Bob Pony discovered that this loophole no longer works on the more recent builds. Neowin quoted his update, which said the workaround "by clicking on the tiny "Learn more" hyperlink in the Microosft [sic] account sign in page during the Windows 11 OOBE has been recently quietly patched server side."

Neowin also suggested that perhaps it was done in such a hurry that it was not even mentioned in any of the recently released cumulative update changelogs.

Here is how solid each part of the claim is:

• Confirmed by more than one source: the trick existed, and several outlets independently reproduced it in September.
• Bob Pony's claim only: the trick now fails on newer builds, and the fix was made server side.
• Not established: the exact build or edition where it fails, the date it changed, or any comment from Microsoft. We found no Microsoft statement about this.

Microsoft's own Windows 11 version 26H2 release-health page lists current known issues, including a Credential Guard domain-trust problem, USB Audio Class 1.0 failures and an AC-3 decoding crash. It says nothing about this setup behavior. That proves very little either way. OOBE (out-of-box experience, the first-run setup screens) loads much of its content from the web, so a change to it would not necessarily appear in a release note.

It was an account bypass, not a hardware bypass​

The headline says "requirements bypass," but the "Learn more" trick never got around Windows 11's hardware checks. It got around one thing: the requirement to sign in with a Microsoft account (MSA) during setup on Windows 11 Home.

Neowin's article mixes the two. It mentions that using third-party apps like Ventoy and Rufus, users can bypass the system requirements enforced by Microsoft, but those tools are a separate matter from this OOBE link. Nothing in the reporting suggests that the TPM, Secure Boot or CPU checks changed, or that Rufus and Ventoy stopped working. This story is about one link on one setup screen.

There is a second discrepancy. Neowin described the trick as setting up Windows 11 without internet and Microsoft Account (MSA). The people who tested it said the opposite about the network. Windows Latest wrote that you don't have to disconnect your Wi-Fi, either, and BetaNews noted that the PC can also stay connected to the internet throughout setup. The trick skipped the account. It did not skip the network.

How the trick worked​

Bob Pony first posted the method on September 12, 2026. His post said that a new method for skipping the mandatory Microsoft Account login in Windows 11 Home Edition has been discovered... just simply click on the small Learn more hyperlink on the Microsoft Account login page.

The steps, as Windows Latest documented them:

1. Start a fresh Windows 11 Home installation and go through the usual OOBE screens.
2. Connect to the internet and continue until you reach "Let's add your Microsoft account."
3. Look for the small "Learn more" link in the long paragraph under "Sign-in options". Do not click the big Learn More button near the bottom of the page.
4. If it worked, Windows moves to "Who's going to use this device?" Enter a local username and continue.
5. Setup then asked for a password, a confirmation of that password and three security questions.

Several outlets checked it before the reported block:

• Windows Latest tested it in a virtual machine using the then-latest Windows 11 Home ISO.
• The Register said it tried the method and that it behaved exactly as Bob Pony's video showed.
• PC Gamer said it tested the process as detailed by Windows Latest on a fresh installation of a non-Insider Preview build of Windows 11, and were able to replicate the bypass.
• BetaNews reported that it has been confirmed on retail Windows 11 Home installation media and on Windows 11's Insider Experimental channel, build 29677.

None of these outlets has published a retest since Bob Pony's update. Their September results show the trick once worked. They do not confirm that it has stopped working.

What we know so far: the trick was real and reproducible on Home in September. The claim that it is now blocked comes from Bob Pony's later observation, which Neowin reported.

Was this a bug or an exit Microsoft left open?​

Most observers called it a bug. SecurityOnline noted that under normal circumstances, OOBE itself fetches content online, and the Learn More hyperlink ought to display additional information before offering a return button. Windows Latest also said this was not an officially supported way to create a local account.

That fits the claim of a server-side fix. If the help link loads web content and that content accidentally sent setup to the local-account screen, Microsoft could correct it on the web side without shipping a cumulative update. To be clear, that is our inference from how OOBE is built. Microsoft has not confirmed the mechanism.

The Register offered another theory. Because Pro users and administrators already have other ways to avoid a Microsoft account, it suggested that might be why the loophole existed at all. That is interesting, but it is speculation.

A long line of closed workarounds​

This fix continues a long pattern. Neowin notes that Microsoft has blocked off various bypass tricks like those using OOBE\bypassnro and start ms-cxh:localonly commands.

According to Windows Latest:

• The oobe\bypassnro script was removed from Insider builds in early 2025. A related registry value kept working for a while afterward.
• In October 2025, Insider build 26120.6772 blocked several methods: the BypassNRO registry value, start ms-cxh:localonly, start ms-cxh://setaddlocalonly, entering fake credentials to force an account failure, and the old oobenetworkconnectionflow trick.
• Microsoft's stated reason was that these methods let people "exit OOBE with a device that is not fully configured for use."

Windows Latest added an important caveat: those restrictions were tested in Insider builds and had not been confirmed in production releases. Microsoft's explanation was about those earlier methods. It has not said anything about the "Learn more" link.

Some people inside Microsoft don't like the requirement either. PC Gamer noted that Vice president Scott Hanselman has previously said on X that he hates it, and that he's "working on it". So far, no policy change has followed.

Version 26H2​

Microsoft's release-health page says Windows 11 version 26H2 reached general availability on September 29, 2026. The rollout is phased and will widen over the coming months. The page says 26H2 contains the features recently announced for 25H2 and 24H2 and is delivered using servicing technology so it installs quickly.

The 26H2 label in the headline is mostly about timing. No source we found ties the reported OOBE change to a particular 26H2 build or update, or shows that only 26H2 is affected. If the fix really was server side, it could affect setup on any build whose OOBE loads that content. That is also inference, not something anyone has confirmed.

What this means if you're setting up a PC​

• Don't count on the link. Treat the "Learn more" route as unreliable at best. It was never supported, and Bob Pony now says it has been closed.
• Home users: plan for a Microsoft account during setup. Some people create a local account later in Settings, but check how that works on your build before relying on it.
• Pro users: The Register said Pro users and administrators have other options and are not forced into a Microsoft account. Windows Latest mentioned one user's report that Pro's "Set up for work or school" path still reaches a local-account screen. We haven't verified that on 26H2.
• Hardware checks are a separate issue. Nothing here shows a change to tools such as Rufus or Ventoy that change installation media.
• Help desks and people who set up PCs for family: update any setup notes that point to this link, and try any workaround on your exact installation media before you rely on it.

The bottom line​

A one-click shortcut around Windows 11 Home's Microsoft account requirement appeared on September 12. Several outlets confirmed it worked, and within a month its finder said Microsoft had quietly closed it on the server side. The direction is consistent with Microsoft's history of closing these workarounds. The details are still unconfirmed: no build number, no published retest by an outlet and no statement from Microsoft.

Until one of those turns up, it is safest to assume the link no longer works. Calling this a broad "requirements bypass" block goes beyond the evidence. Only the account-sign-in shortcut is reported closed.