← Windows & Intune
🟦 Windows

Common Windows Administration Issues & Fixes

Comprehensive troubleshooting for Windows environments — BSOD analysis, driver issues, RAM diagnostics, Group Policy failures, and network connectivity problems.

📅 May 15, 2025
⏱ 10 min read
✍️ TheiTnotesguy
💬
Enterprise IT use case. Windows 11 requires a Microsoft account during OOBE by default. In corporate environments, IT teams need a local admin account first — to prepare the device before domain join, Azure AD join, or MDM enrolment via Intune or Jamf.
01
Disable Internet Connection

At the Windows 11 setup screen (before you reach the Microsoft account sign-in page), open a Command Prompt using the keyboard shortcut:

SHIFT + F10

This opens an elevated Command Prompt directly within OOBE. From here, open the Network Connections panel:

ncpa.cpl

In the Network Connections window, right-click your Ethernet or Wi-Fi adapter and select Disable. This removes the internet requirement, which is what forces the Microsoft account prompt.

Why this works → Windows 11 Home and Pro require internet during OOBE if a connection is detected → Disabling the adapter at this stage removes that requirement → The adapter can be re-enabled after setup is complete
02
Run the OOBE Bypass Command

With the Command Prompt still open (SHIFT + F10), run the following command:

OOBE\BYPASSNRO

Press Enter. The system will restart automatically — this is expected. After the restart, Windows will return to the setup screen.

After restart, you will see a new option: → On the network screen, click "I don't have internet" → Then click "Continue with limited setup" → This bypasses the Microsoft account requirement entirely
⚠️
If you don't see the "I don't have internet" option after restart, make sure the network adapter is still disabled. Go back to Step 1 and disable it again before proceeding.
03
Create Local Administrator Account

After choosing "Continue with limited setup", Windows will take you through the standard local account creation flow. Set up the account as your local administrator:

→ Enter a username (e.g. LocalAdmin or your company's naming convention) → Set a strong password → Complete the remaining setup steps (privacy settings, etc.) → Windows will boot to the desktop with your local admin account
04
Re-enable Network & Complete Deployment

Once at the desktop, re-enable the network adapter and proceed with your standard IT deployment workflow:

✔ Re-enable network adapter → Settings → Network & Internet, or ncpa.cpl → right-click adapter → Enable ✔ Run Windows Update → Get all latest patches before domain join ✔ Join to Domain / Azure AD / MDM → Domain Join: Settings → Accounts → Access work or school → Connect → Join domain → Azure AD Join: Settings → Accounts → Access work or school → Connect → Sign in with org account → Intune MDM: Enrol via Company Portal or via Azure AD join (auto-enrolment) → Jamf: Enrol via Jamf enrolment URL or pre-stage enrolment ✔ Apply Security Policies → Group Policy (GPO) applies automatically on domain join → Intune/Jamf Configuration Profiles push on MDM enrolment → Run: gpupdate /force to apply Group Policy immediately
gpupdate /force
✅
Summary. This three-step method (disable network → OOBE\BYPASSNRO → create local admin) is the standard IT deployment approach for setting up Windows 11 devices without a Microsoft account — especially useful before domain join, Azure AD join, or Intune/Jamf MDM enrolment.