Network connection flow in Windows 11 and networks: a complete guide

If you're installing Windows 11 and you've come across the dreaded "Let's connect you to a network" screen, you've probably noticed that Microsoft is increasingly making it difficult to use the system without internet or an online account.And of course, if you don't have an internet connection at that moment or simply don't want to link your PC to a Microsoft account, things get complicated, making it advisable to review the Privacy tightening in Windows 11.

The good news is that, despite these limitations, there are still several ways to bypass the network connection flow requirement and create a local accountThis applies to both older and more recent versions of Windows 11. Furthermore, all of this intersects with the more technical concept of "flow" in networks, which also comes up when we talk about traffic, quality of service, and routers. And if you need to control how wireless networks connect, you can learn how to... disable automatic connection.

What is “network connection flow” in Windows 11

In the context of installing Windows 11, the so-called “Network Connection Flow” is the process that controls the screen where the system forces the computer to connect to the Internet. to be able to continue with the setup wizard (OOBE, Out Of Box Experience).

This connection flow is managed by a specific component of the system, whose process is called oobenetworkconnectionflow.exe within the installation environmentWhile that process is active, the assistant will repeatedly insist that you connect to Wi-Fi or a wired connection before letting you create the user.

Microsoft has been tightening these requirements over time: It was first implemented in Windows 10 Home, then in Windows 11 Home and, more recently, it has begun to extend the requirement to Pro editions in new system builds as well, even in corporate environments and mass deployments of Windows 11.

The objective is clear: force the use of Microsoft accounts and link the installation to online serversThis involves collecting data such as approximate location, IP addresses, login and logout habits, and other telemetry related to your activity.

For many users this is not a problem, but for those who want to maintain a more private profile, install equipment on isolated networks, or simply not have internet available during installation.This “network connection flow” becomes a major obstacle, especially when it is needed Block and hide Wi-Fi networks in controlled environments.

Classic methods for installing Windows 11 without a network connection

In the early versions of Windows 11, many users discovered relatively simple shortcuts to Complete the installation without connecting to the Internet and thus be able to create a local accountThese methods still work on many computers, especially on older builds.

One of the most straightforward tricks is to forcibly close the “Network Connection Flow” process during OOBEBy doing so, the installation wizard "gives up" and proceeds directly to the local user creation screen.

When you reach the "Let's connect you to a network" screen and the system won't let you proceed without Wi-Fi or a cable, you can open an advanced command window with Shift + F10 directly from the assistantThis works on both desktop and laptop computers.

From that console, you have two well-known options: Use Task Manager (taskmgr) to kill the process, or launch a specific command that directly closes oobenetworkconnectionflow.exe without going through graphical interfaces.

The key to these methods is that, Once the network connection flow stops running, the installer itself immediately displays the local account creation screen., as was the case in the past before the use of Microsoft accounts was so heavily enforced.

How to kill the Network Connection Flow process with Task Manager

One of the simplest methods for most users is to Use the Windows Task Manager during the installation processDespite being in the OOBE environment, it is still possible to open it and manage processes.

The basic steps are as follows, applicable mainly to Windows 11 Home and many slightly earlier Pro versions:

1. On the screen where the assistant insists that you connect to the Internet, Press Shift + F10 to open the command consoleYou will see a black CMD-type window with elevated privileges.

2. In that window, type taskmgr and press Enter. The Task Manager for the installation environment will open.

3. If it appears in simplified mode, Click on “More details” to see the full view with tabs and all active processes on the system.

4. On the Processes tab, scroll down until you find an entry called “Network Connection Flow” or similarIt may appear as part of the background processes associated with the OOBE.

5. Select that process and click on “End Task” to close oobenetworkconnectionflow.exeAs soon as you do this, you'll notice the assistant's background screen change automatically.

6. Close Task Manager (if you want) and the CMD window by typing exit and pressing Enter. When you return to the wizard, you will usually see the option to Create a local user without needing a network.

This method is especially useful if you prefer Avoid more “aggressive” commands and have a visual view of what you are closing.and it will help you when you need to change the network adapter priorityHowever, there are scenarios where Task Manager may not open correctly or may freeze, especially on somewhat problematic hardware.

Bypass the network connection flow with taskkill from the console

If you're having trouble with Task Manager or just want to get straight to the point, you can resort to taskkill, a command-line utility that directly terminates processesThis method has also been widely used by many users.

Again, the starting point is the Windows 11 mandatory connection screen. When the wizard asks you to connect to a network and won't let you continue, Press Shift + F10 to open an elevated command prompt.

In that window, type the following command exactly, respecting spaces and capital letters where appropriate: taskkill /F /IM oobenetworkconnectionflow.exe and press Enter. The /F modifier forces the program to close, and /IM indicates that you are going to specify the name of the image (the executable).

When the command is executed successfully, The “Network Connection Flow” window disappears from the wizard Instead, the installer moves on to the next screen, which is usually the local account setup.

If you wish, you can end the command session by typing exit and pressing Enter, although it's not strictly necessary for the bypass to work. The important thing is that The process that was blocking the offline installation is no longer running..

This same process finish has been documented on several technical websites and forums, noting that network discovery in Windows can influence how and when it is appropriate to apply these shortcuts (for example, in isolated or controlled networks).

Method using Alt + F4 in older versions of Windows 11

In some early versions of Windows 11, there was an even simpler way to skip the network connection screen without touching processes or using commandsThis trick, however, tends to disappear in newer builds, but it's still interesting to know about it.

During the wizard, upon reaching the "Let's connect you to a network" screen, it was enough to Hold down the Alt key and simultaneously press F4This closed the current OOBE window in a similar way to how other applications are closed in Windows.

In many cases, when that screen closed, the wizard itself directly displayed the next step of the installation. without further insistence on the network connection and allowing to continue with the account creationIt was, in essence, a "polite" closure of the connection flow.

With the changes that Microsoft has been introducing, This trick may not work in newer versions. of Windows 11, especially in builds released from certain years and in editions where the Microsoft account requirement is mandatory according to the company's notes.

Even so, if you are reinstalling or deploying An older Windows 11 ISO might be worth trying. Alt + F4 before resorting to more advanced commands, as it sometimes solves the problem in a couple of seconds.

Bypass with the oobe\bypassnro command and variants

In later builds of Windows 11, Microsoft introduced, and at the same time attempted to "hide," an internal mechanism that allows enable the "I have no internet connection" option within the assistant itselfThis method is somewhat more elegant than simply killing processes.

The trick is to use a specific command from the OOBE console. Again, when you're on the "Let's connect you to a network" screen, Press Shift + F10 to open the CMD window with elevated privileges about the installation environment.

In that console, enter the following command and press Enter: oobe\bypassnroThe term “bypassnro” refers to disabling mandatory network restrictions that block the offline installation option.

When running this command, The installer usually restarts the computer automatically Or at least restart the OOBE environment. When the assistant reloads, you'll notice a significant change on the connection screen.

Now a new button or option should appear that says something like “I don’t have internet” or “I don’t have an internet connection”Even if Wi-Fi networks are detected or a cable is connected. By selecting this option, the assistant allows you to continue without needing to register with a Microsoft account online.

In some more modern compilations (up to relatively recent dates), it has been observed that oobe\bypassnro may stop working or fail to produce the expected behavior. This often coincides with changes introduced by the automatic updates in Windows 11 that modify the OOBE.

Modern alternative: start command ms-cxh:localonly

In even more recent versions of Windows 11, especially in builds from 2025 and later, cases have been documented where the command oobe\bypassnro stops working or doesn't add the "I don't have internet" button in the network assistant.

In response, one alternative discovered by the community involves using a command based on a special Windows protocol: start ms-cxh:localonlyThe goal is to force the assistant to focus on creating a local account without needing a connection.

The procedure is similar to the previous ones. On the network connection screen, Open the console with Shift + F10 And in the CMD window, type exactly: start ms-cxh:localonly and press Enter to run it.

This command launches a kind of internal “deep link” that tells the OOBE environment to offer the option to work only with a local accountIn some builds, this triggers a new interface or enables routes that were hidden behind the connection requirement.

After executing the command, the system can restart the assistant or redirect you to a different screen where a network connection is no longer required as an essential step. From there, you should be able to complete the installation by creating a traditional local user account.

It is worth noting that, since it is a matter of behaviors observed in development builds and Insider versionsMicrosoft may modify or remove these alternative paths in the future. Therefore, it's also useful to be aware of methods based on terminating processes, which are more "universal."

Internal scripts: BypassNRO.cmd and system path

In some technical environments and conversations, the direct use of a script included in the system itself, called BypassNRO.cmd, which is located in the Windows OOBE folder.

This file is usually located in the system path corresponding to the installation, specifically in %systemroot%\System32\oobe\BypassNRO.cmdFrom the installation environment, it can be invoked to cause changes similar to the oobe\bypassnro command.

To use it, the typical procedure consists of, once again, Open the advanced command window with Shift + F10 from the "Let's connect you to a network" screenIn the console, simply run:

%systemroot%\System32\oobe\BypassNRO.cmd and press Enter. If the path is correct and the script is present, it will adjust the installation policy to allow offline continuation.

After execution, the system normally Restart the installation environment and, upon returning to the OOBE, the "I have no internet" button is enabled. which wasn't showing up before. This lets you continue with the local account setup.

This method can be especially useful when The oobe\bypassnro command does not respond as expected, but the script is provisioned in the Windows image. that you're using. It also suggests that, internally, Microsoft maintains its own mechanisms to disable the network requirement in certain scenarios (likely corporate or support).

Home and Pro Editions: Differences and Recent Changes

For a time, it was thought that this internet connection and Microsoft account requirement was basically limited to the Home edition of Windows 11. However, Microsoft announced in a preview build (like 22557) that the Pro editions would also start requiring an online connection and account. during the initial installation.

Until that time, many system administrators and advanced users resorted to Windows 11 Pro to avoid the requirement to use a Microsoft account during the initial setup. With that change, the boundary between Home and Pro becomes blurred in this respect.

According to feedback from users who have tested these test builds, Some of the bypass techniques that worked in Windows 11 Home are no longer effective in Pro either.This includes, in certain cases, the closure of the Network Connection Flow process, which may behave differently.

However, as long as the stable build you have installed or in your ISO has not yet incorporated these restrictions, The tricks using Task Manager, taskkill, oobe\bypassnro or BypassNRO.cmd are still validIt's important to check the version and build to know what to expect.

The general trend suggests that Microsoft wants the use of a local account without internet to be the exception, not the rule.That's why many users rely on these methods as a temporary solution, but it's wise to be prepared in case they become unavailable in future versions.

Privacy, local accounts, and reasons to avoid connecting

Beyond the technical aspects, this whole issue of "network connection flow" is closely linked to privacy and the control you want to have over your deviceNot everyone is comfortable linking their Windows installation to an online account from the very beginning.

By forcing you to connect to the internet during installation, Windows 11 links your computer to Microsoft cloud services, synchronization, OneDrive, activity history, and also records data such as IP, approximate geographic area and other telemetry parameters.

For home users with a single machine, this might even be useful, but in corporate environments, isolated networks, laboratories, or scenarios where stricter control is desiredIt is common to prefer local accounts that will later be integrated into domains, directories, or other solutions.

Furthermore, there are very simple situations: devices without real internet access at the time of installation, slow or unstable connections, or people who simply want to get to the desktop as soon as possible without going through updates or forced downloads.

Knowing these methods to bypass the network connection flow is not so much "cheating" as to regain some flexibility when deciding how and when the system is connectedespecially during the initial start.

The concept of "flow" in networks beyond Windows

The term “network flow” or “flow” is not limited to what we see in the Windows 11 wizard. In the field of networking, A flow is a sequence of packets that share common characteristics and that network devices treat as a logical unit..

For example, in Internet routers, a flow can be defined by the combination of source IP address, destination IP address, source and destination ports, and the transport protocol (such as TCP or UDP). With these fields, the device identifies a specific communication between two points.

In the case of TCP connections, that flow can be seen practically as a virtual circuit or a continuous byte streamwhere the data travels in an ordered manner and the protocol is responsible for ensuring reliable delivery, sequencing, and congestion control.

In Layer 2 switched networks, such as Ethernet with tagged VLANs (IEEE 802.1Q), A flow can also be defined at the VLAN tag level or through label-switching paths in technologies such as MPLS (Multiprotocol Label Switching).

The concept of flow is also fundamental in tools such as queuing network analyzers, packet tracing systems and advanced monitoring solutions that need to distinguish between different types of traffic.

For example, in scenarios where delays or packet loss occur, diagnostic and analysis tools such as Windows Performance Recorder They help identify bottlenecks and anomalous behavior in the flows.

The idea of ​​representing network traffic as a water flow through pipes —the pipes would be the links, the capacity would be equivalent to the bandwidth and the flows the data rate— helps to understand phenomena such as queues, delays or the need to reserve resources for critical services.

Flow-based traffic control and quality of service

When network devices are able to identify and separate flows, they can apply differentiated treatments for each: queues, priorities, shaping, policing or quality of service (QoS) policies.

For example, on an enterprise router, you can configure that Voice traffic (VoIP) should take priority over bulk downloads, assigning that flow queues with less latency and a lower probability of being discarded.

Similarly, in advanced network cards, managed switches, and carrier equipment, Separate queues are used for different flows in order to guarantee a certain fairness (fair queuing)preventing a single user or application from monopolizing all the bandwidth.

This approach is also essential in technologies and formats such as Cisco NetFlow, IP Flow Information Export (IPFIX), or auditing solutions such as Argus, which collect flow information to analyze network performance, security, and utilization.

Even at a conceptual level, network traffic is often represented as a water flow through pipesThe pipes would be the communication links, their capacity would be equivalent to the bandwidth, and the flows would be the data flow that circulates, with possible bottlenecks, queues, and overloads.

This mental model helps to better understand phenomena such as queues in routers, packet delays, or the need to reserve resources for certain critical services, much like how pipe networks are sized in civil engineering.

When is it better to restore the network instead of skipping the connection?

Sometimes the problem isn't that Windows 11 forces you to connect, but that You really can't connect to the network due to some configuration or adapter failure.In these cases, rather than looking for a bypass, you might be interested in repairing the network.

If, for example, you can't connect via Ethernet to an already installed computer, a typical option is Check other devices on the same network: connect the cable to another PC, check if there is working Wi-Fi, etc., to rule out that the fault is in the router or in the cable itself.

If other devices do work, they might help. Reset the Windows network stack using the command prompt with administrator privilegesOn a system that has already started, you can open the command prompt as administrator and run a series of commands.

First, they are usually used ipconfig /release and ipconfig /renew to release and renew the device's IP address, followed by ipconfig / flushdns to clear the local DNS cache, which helps resolve name resolution problems.

Then, commands such as netsh int ip reset and netsh winsock reset to reset the IP configuration and the Winsock layer, which can resolve conflicts and corruptions in the system's network configuration.

After restarting the computer, it's a good idea to check again if The Ethernet or Wi-Fi connection is now established normallyThis approach is different from bypassing the "network connection flow" and is more suitable for cases where you do want to connect but Windows cannot do so correctly.

Ultimately, There is a clear difference between intentionally avoiding the connection during installation and fixing connectivity problems. in an already installed system. Depending on your situation, one type of solution or another will be more suitable.

With all of the above, it is quite clear that the term “network connection flow” encompasses from The annoying Windows 11 assistant that forces an internet connection even the most technical notion of traffic flows in advanced networks, and knowing both the tricks to avoid mandatory connection as well as the concepts of flow in routers, queues and QoS gives you a more complete view of how communication is really managed in your equipment and in the network that surrounds it.