# Bypassing TPM, Secure Boot, and Microsoft Account During Windows 11 VM Setup

#### **Date:** June 7, 2025  
**Category:** Windows / Virtualization / Lab Setup  
**Purpose:** Create Windows 11 VMs for a domain lab without being blocked by hardware checks or Microsoft Account requirements.

---

### Background

When installing Windows 11 on VirtualBox or similar platforms, you may encounter the following issues:

- TPM 2.0 or Secure Boot not detected
- Forced sign-in with a Microsoft account

This guide walks through bypassing both roadblocks for lab environments.

---

### Requirements

- Windows 11 ISO
- VirtualBox or other VM platform
- No TPM or Secure Boot hardware needed

---

### Step 1: Bypass TPM, Secure Boot, and RAM Checks

1. When you see a message like “This PC can’t run Windows 11,” press:
    
    ```powershell
    Shift + F10
    ```
    
    to open Command Prompt.
2. Type:
    
    ```powershell
    regedit
    ```
3. In Registry Editor, navigate to:
    
    ```powershell
    HKEY_LOCAL_MACHINE\SYSTEM\Setup
    ```
4. Right-click `Setup` → **New > Key** → name it:
    
    ```powershell
    LabConfig
    ```
5. Inside `LabConfig`, create the following **DWORD (32-bit) Values**:
    
    
    - `BypassTPMCheck` → 1 (Decimal)
    - `BypassSecureBootCheck` → 1 (Decimal)
    - `BypassRAMCheck` → 1 (Decimal)
6. Close Regedit and the Command Prompt.
7. Click **Back** then **Next** to retry setup.

---

### Step 2: Bypass Microsoft Account Requirement

Once Windows setup asks you to connect to a network or sign in:

#### Option A: Use Bypass Command

1. Press:
    
    ```powershell
    Shift + F10
    ```
2. Type:
    
    ```powershell
    oobe\bypassnro
    ```
3. The VM will reboot automatically.
4. On reboot, choose:
    
    
    - **“I don’t have internet”** or
    - **“Continue with limited setup”**
5. Create a **local user account** to complete setup.

#### Option B: Temporarily Disable Networking (Optional)

If `oobe\bypassnro` doesn’t show the offline setup:

- Shut down the VM
- In **VirtualBox Settings > Network**, uncheck:
    
    ```powershell
    Enable Network Adapter
    ```
- Boot the VM and try setup again — no internet = local account path
- Re-enable networking once setup is complete

---

### Result

You now have a clean Windows 11 VM with:

- Local admin account
- No TPM, Secure Boot, or Microsoft Account enforced