logoalt Hacker News

EvanAnderson • 04/01/2025 • 3 replies • view on HN

I just deployed three new Windows 11 Pro machines yesterday (two HP, one Dell) with local accounts. The HP OEM image was pre-24H2 so it doesn't count, but the Dell machine was 24H2.

I booted to the OOBE, hit <SHIFT>-<F10>, ran:

   REG ADD HKLM\Software\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1

   shutdown -r -t 1 -f
Waited for the machine to reboot and ran thru the OOBE w/o connecting to a network. Once I got logged-on w/ my local account connected to the Wi-Fi and joined the Active Directory domain.

Replies

easton • 04/01/2025

Does pro not have the “domain join instead” option in OOBE anymore? It definitely used to, and Enterprise does.

I don’t understand how you’d domain join otherwise.

➕ show 2 replies
preciousoo • 04/01/2025

you can also do ipconfig /release in some contexts (works in hyperv but never in the real world for some reason sigh)

bayindirh • 04/01/2025

Sorry to be blunt, but if this is not a workaround, then I don't know what is.

➕ show 1 reply