Shortly before the weekend, Microsoft made a notable adjustment to the preview versions of Windows 11 for Insiders on the Dev Channel by removing the BypassNRO.cmd script. This decision was articulated in a recent blog post from the tech giant:
“We’re removing the bypassnro.cmd script from the build to enhance security and user experience of Windows 11. This change ensures that all users exit setup with internet connectivity and a Microsoft Account.”
The BypassNRO.cmd script previously allowed users to circumvent the Microsoft Account requirement during the installation of Windows 11, enabling them to log in with a local account instead. While it is theoretically feasible to replicate the functionality of this script by manually creating the corresponding registry entry, the process is intricate and demands a solid understanding of the Windows registry. For those interested, the necessary registry entry can be found on BleepingComputer.
New Workaround Emerges
In a twist of innovation, resourceful Windows Insider testers have already discovered an alternative solution for both Windows 11 Home and Pro editions. A user known as Witherornot1337 has shared a straightforward method on X/Twitter. This approach involves accessing the command prompt via the Windows key + X menu and entering the following command:
start ms-cxh:localonly
Executing this command opens a window reminiscent of the classic Windows 10 interface, allowing users to create a local account complete with a username and password, thus facilitating the continuation of the Windows 11 installation process.
A video clip accompanying the tweet illustrates the entire procedure, highlighting its simplicity—far more user-friendly than the complexities of modifying the Windows registry. However, one lingering question remains: how long will Microsoft permit this workaround to exist?
At present, the removal of BypassNRO.cmd impacts only the preview version of Windows 11. The script remains available in the public versions of the operating system. Should this change be implemented across the board, it is anticipated that the script will be phased out from all Windows 11 PCs later this year.
This article was originally published in our sister publication PC-WELT and has been translated and localized from German.
