Newsletter Archives

  • Removing bypassnro

    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.

    Today, Microsoft announced that the Windows 11 Insider Build (26200.5516) had been released to the Dev channel. The nugget quoted above is mentioned in that Windows Blog post.

    What’s it about? “Bypass” refers to the methods we’ve used in the past to avoid using a Microsoft account when installing Windows Home edition. It’s being removed.

    Does this bother you? If so, it’s time to get into that feedback hub and make your voice heard. Unfortunately, you may not be able to do so, at least for the moment. Use this link, which will prompt you to open the Feedback Hub app on your PC and sign in. Microsoft may tell you that “Your account doesn’t have access to this feedback.” That happened to me on a 23H2 PC, but I was able to get there on a PC running 24H2.

    Update: Click on the social media post by Will Dormann and the resulting responses. They removed the built in command file, they did not remove the ability to bypass it. You can just type in the commands by hand and still get around the mandate for a Microsoft account.

  • Parallels removes functionality to run Insider Dev Channel Previews unannounced

    I have been in the Insider Program since October 2014, running the Insider Fast Ring/Dev Channel Previews in Parallels Standard Edition VMs on Macs with no problems during that time. Parallels v15 has been hosting the VMs since the end of 2019 flawlessly – until Win10 Pro Insider Build 20175.1000 when the Builds suddenly started failing to install.
    Parallels recently issued version 16, and thinking that would solve the problem, I upgraded on August 14th. Still the Insider Previews failed to install, so I opened a support ticket. After a remote session with a Parallels Engineer, who said to contact Microsoft because it was an MS problem, the followup email response from Parallels:

    We have escalated the issue you reported to the Development Team and they are working to address it in one of the future builds of Parallels Desktop for Mac.

    While we do not have ETA for the fix, it has been prioritized appropriately and you can track the changes in the product at the corresponding knowledge base article page

    Reading through the Parallels Forums, sheds light on the problem. Parallels removed functionality from version 15 between updates without notice.
    Parallels Support agent Ajith says:

    Enabling nested virtualization helps in updating to latest Windows Insider build which is only available with Pro and Business subscription. As you are testing Windows beta versions as a professional using Pro is the right choice and will have more features compared to the standard edition.

    And I have to agree with Parallels Forum poster “SoonToBeFormerParallelsUser” who responds

    It is DISHONEST to not publicly announce you are no longer supporting Previews and then turn around and demand upgrade to Pro to re-enable that functionality.

    And follows with

    You misstated that Parallels has removed the feature & ability to boot recent Windows Insider Preview builds. Preview builds WORKED FINE until build 20175 through NO FAULT of Microsoft. It is Parallels’s FAULT.

    You left out that within the same version (v15) Parallels has mysteriously not been able to install and boot these recent builds. It’s no accident.

    Why didn’t Parallels do the HONEST thing and announce that starting with v16, the new release, that Preview builds would not be supported and you would have to upgrade to Pro. Instead they broke the software ON PURPOSE with NO ANNOUNCEMENT.

    In the past, I have praised Parallels Desktop for functionality and Parallels Support for being among the best. What a shame they have fallen to this kind of deceptive practices.

  • Blocking Automatic Windows Updates – another reason (on Ghacks.net)

    Martin Brinkmann is reporting on ghacks.net of Win10 “stable update” machines being offered “preview builds” – Insider versions!

    Microsoft’s Brandon LeBlanc confirmed that activation of the “update” button would not install the new build on Stable versions of Microsoft’s Windows operating system, and that the issue affected only a small number of devices.
    Microsoft turned off the notifications as a consequence to investigate the issue. It is rather obvious that devices that don’t run Windows 10 Insider Build should not receive notifications about new Insider versions.

    Martin goes on to say:

    The main takeaway from the incident is that mistakes happen and that Microsoft is not exempt from making them.

    I’d call that an understatement!

    You can read @martinbrinkmann‘s article here

  • Win10 admins and developers: Get Win10 10586.456 for testing

    It’s the latest Insider Release Preview build for the current version of Windows 10.

    InfoWorld Woody on Windows.