Skip to content
How to Fix Apple Error -2100F: Internet Recovery Wi-Fi network requires captive portal authMappleCare Community ↗
Error -2100F macOS / Internet Recovery Captive Portal Unsupported

How to Fix Apple Error -2100F: Internet Recovery Wi-Fi network requires captive portal auth

Reference ID: Error -2100F •

1. Overview & Failure Manifestation

Error -2100F manifests exclusively during macOS Internet Recovery (invoked via ⌘+⌥+R or ⌘+⌥+Shift+R) when the EFI firmware’s Wi-Fi connection manager (AppleWiFiManager.efi) attempts to associate with an 802.11 network that enforces captive portal authentication. The recovery environment presents a modal dialog titled “Wi-Fi Network Requires Authentication” with the body text: “The network “SSID” requires you to log in via a web page. This network is not supported for Internet Recovery.” The dialog offers only a “Try Another Network” button; no browser shim or captive portal assistant is loaded in the pre-boot EFI context. Immediately after dismissal, the wireless interface (en0 on Apple Silicon, en1 on Intel T2) disassociates, the EFI network stack (AppleNetBoot.efi) aborts the DHCPv4/DHCPv6 transaction (state DHCP_STATE_SELECTING → DHCP_STATE_ABORTED), and the recovery UI falls back to the network selection screen. In the unified log (accessible post-boot via log show --predicate 'subsystem == "com.apple.internet-recovery"'), the following entries are recorded:

2024-06-15 14:32:11.123456-0700 0x1a3b   Default     0x0                  0      kernel: (AppleBCMWLANCore) wl0: captive portal detected, redirect URL: http://captive.apple.com/hotspot-detect.html
2024-06-15 14:32:11.124001-0700 0x1a3b   Error       0x0                  0      kernel: (AppleWiFiManager) EFI_WIFI_ERROR_CAPTIVE_PORTAL_UNSUPPORTED (-2100F)
2024-06-15 14:32:11.124512-0700 0x1a3b   Default     0x0                  0      kernel: (AppleNetBoot) NetBoot abort: error -2100F, reason: captive portal auth required

The device remains in the Internet Recovery UI; no NVRAM variables are modified, and the boot picker (boot.efi) does not advance to the macOS installer download phase. This error is deterministic: any SSID that returns HTTP 302/307 to a captive portal landing page before full IP connectivity is established will trigger -2100F.

2. Silicon & Firmware Architecture Root Cause

The root cause resides in the EFI Wi-Fi connection manager (AppleWiFiManager.efi) which executes in the DXE phase of the UEFI firmware on both Apple Silicon (M1/M2/M3) and Intel T2/T2e platforms. On Apple Silicon, the Wi-Fi controller is the Broadcom BCM4377/4378/4389 (PCIe 3.0 x1, MSIX interrupts) attached to the IOMMU via the AppleS8000 SoC’s PCIe Root Complex. The firmware driver (AppleBCMWLANCore.efi) initializes the controller through the PCIE_RC_EP handshake, configures the PMU power rails (VDDIO_1V8, VDD_1V2, VDD_0V9) via the PMGR (Power Manager) over the APM (Apple Power Management) I2C bus (address 0x68), and loads the RAM firmware (brcmfmac4389-sdio.bin) into the controller’s TCM (Tightly Coupled Memory).

During Internet Recovery, the EFI network stack (AppleNetBoot.efi) invokes AppleWiFiManager.efi’s Connect() interface. The manager performs an 802.11 open-system authentication and association, then triggers a DHCPv4 discover (RFC 2131) on the EFI_SIMPLE_NETWORK_PROTOCOL. If the AP responds with a DHCP offer but the subsequent HTTP GET to http://captive.apple.com/hotspot-detect.html (hardcoded in AppleCaptivePortalDetect.efi) returns a 302 redirect to a non-Apple domain, the captive portal detection logic sets the EFI_WIFI_STATUS_CAPTIVE_PORTAL bit in the WIFI_CONTEXT structure. However, the EFI environment lacks a WebKit instance, NetworkExtension entitlements, or a CaptiveNetworkSupport daemon. The Secure Enclave (SEP) is not yet unlocked (SEPOS bootstage SEP_OS_BOOT_STAGE_EARLY), so no user credential vault is accessible. Consequently, the AppleWiFiManager.efi returns EFI_UNSUPPORTED mapped to error -2100F (defined in AppleWiFiError.h as kAppleWiFiErrorCaptivePortalUnsupported). The I2C/SPI buses to the Wi-Fi controller remain active, but the TX/RX DMA rings are torn down, and the controller is placed into D3cold via PMGR command PMGR_CMD_SET_STATE(DEVICE_WIFI, STATE_OFF).

3. Diagnostic Verification & Terminal Commands

Execute the following commands in a macOS Terminal (post-boot) or in the Recovery Terminal (⌘+⌥+T) to confirm the captive portal condition and error code.

3.1 Unified Log Stream Filter (Real-time)

log stream --predicate '(subsystem == "com.apple.internet-recovery" OR subsystem == "com.apple.wifi.manager") AND (eventMessage CONTAINS "captive" OR eventMessage CONTAINS "-2100F")' --info --style syslog

Output fields: timestamp (mach absolute time), process (kernel/efi), subsystem, category, eventMessage containing EFI_WIFI_ERROR_CAPTIVE_PORTAL_UNSUPPORTED and the redirect URL.

3.2 Historical Log Extraction (Last 4 hours)

log show --predicate '(subsystem == "com.apple.internet-recovery" OR subsystem == "com.apple.wifi.manager") AND (eventMessage CONTAINS "captive" OR eventMessage CONTAINS "-2100F")' --last 4h --style json | jq '.[] | select(.eventMessage | contains("-2100F"))'

Returns structured JSON entries; verify eventMessage includes captive portal detected and redirect URL.

3.3 Wi-Fi Controller Firmware Version & Capabilities

system_profiler SPAirPortDataType | awk '/Firmware Version|Supported PHY Modes|Country Code/'

Confirms the Broadcom firmware version (e.g., 17.10.355.100.10) and that the controller supports 802.11ax (HE) — required for captive portal detection offload.

3.4 Network Interface Capture (Recovery Terminal)

tcpdump -i en0 -n -s 0 -vvv 'port 67 or port 68 or (tcp port 80 and host captive.apple.com)'

Run immediately after selecting the suspect SSID in Internet Recovery. Capture will show DHCP OFFER/ACK followed by HTTP 302 to captive portal FQDN.

3.5 NVRAM Variable Inspection

nvram -p | grep -E 'prev-lang:kbd|boot-args|wifi-ap-list|wifi-ssid'

Ensures no stale Wi-Fi credentials persist that could auto-join a captive network.

4. Step-by-Step Resolution Protocols

Phase 1: Rapid Software & Cache Reset (Zero Data Loss)

  1. In Internet Recovery UI, click “Try Another Network”.
  2. Select a known-open SSID (no captive portal) or a personal hotspot from an iOS/iPadOS device (Settings → Personal Hotspot → Allow Others to Join).
  3. If no alternative Wi-Fi is available, connect a USB-C to Ethernet adapter (Apple part MJ1M2AM/A or Thunderbolt 3/4 dock with integrated MAC). The EFI Ethernet driver (AppleUSBEth.efi) bypasses Wi-Fi entirely.
  4. Restart Internet Recovery (⌘+⌥+R) after changing physical connectivity.

Phase 2: Terminal / Subsystem Pipeline Flush (Command-line Remediation)

Execute in macOS (post-boot) to purge cached captive portal profiles and reset Wi-Fi preferences:

# 1. Remove captive portal cache
sudo rm -rf /Library/Preferences/SystemConfiguration/com.apple.captive.portal.plist
sudo rm -rf /var/db/captiveportal/

# 2. Reset Wi-Fi preferences (requires admin)
sudo defaults delete /Library/Preferences/SystemConfiguration/com.apple.airport.preferences
sudo defaults delete /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist

# 3. Flush DNS & DHCP leases
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
sudo ipconfig set en0 DHCP  # or en1 on Intel T2

# 4. Rebuild network stack
sudo networksetup -setnetworkserviceenabled Wi-Fi off
sleep 2
sudo networksetup -setnetworkserviceenabled Wi-Fi on

# 5. Verify no captive portal auto-join
defaults read /Library/Preferences/SystemConfiguration/com.apple.airport.preferences RememberRecentNetworks
# Should return 0 (false) for managed environments; if 1, set to 0:
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.airport.preferences RememberRecentNetworks -bool false

Reboot and re-enter Internet Recovery.

Phase 3: Hardware / DFU Deep Restoration (Complete Firmware Reflashing)

Only required if the Wi-Fi controller firmware is corrupted or the EFI Wi-Fi manager binary is mismatched (rare, typically after failed bridgeOS update on T2 or failed macOS update on Apple Silicon).

  1. Place Mac into DFU Mode:
    • Apple Silicon: Power off → Hold Power 10s → Release, then hold Power + Right Shift + Left Option + Left Control for 7s → Release all but Power for 7s.
    • Intel T2: Power off → Hold Power 3s → Hold Power + Left Control + Left Option + Right Shift 10s → Release Power, hold others 5s.
  2. Connect to a host Mac running Apple Configurator 2 (v2.15+) via USB-C (DFU endpoint 0x1286:0x2048).
  3. In Configurator, select the DFU device → Actions → Advanced → Revive Device (preserves user volume) or Restore (erases all volumes). This rewrites the iBoot, bridgeOS (T2), SEPOS, and Wi-Fi controller RAM firmware from the signed .ipsw payload.
  4. After revive/restore, boot to Internet Recovery and verify Wi-Fi association on open network.

5. Technical Specifications & Parameter Matrix

Parameter Nominal Value Failure Threshold Remediation Target
EFI Wi-Fi Manager Handshake Timeout (DHCP Discover → Offer) 5,000 ms > 8,000 ms (triggers retry) < 3,000 ms on open AP
Captive Portal Detection HTTP GET Timeout 3,000 ms > 5,000 ms (treated as no portal) < 1,500 ms to captive.apple.com
Wi-Fi Controller PMU Rail VDD_1V2 (Active) 1.20 V ± 30 mV < 1.15 V or > 1.25 V 1.20 V ± 10 mV
PCIe Link Width / Speed (BCM4389) x1 Gen 3 (8 GT/s) Fallback to Gen 1 (2.5 GT/s) Stable Gen 3, LTSSM L0
EFI Network Stack MTU 1,500 bytes Fragmentation if > 1,472 (IPv4) 1,500 bytes, no fragmentation
SEP Unlock Latency (post-DFU) < 2,000 ms > 5,000 ms (SEPOS watchdog reset) < 1

Still stuck on Error -2100F?

Share your exact OS build and Finder/Console snippet in the OS Updates & Error Codes forum room.

Get Peer Triage →