Windows 10 registry tweak to see new preview builds will block future updates

About two weeks ago, we posted up a tweak that would allow you to see unreleased Windows 10 builds that were ready for download. While we said that this was not for the novice users and there were no benefits at the time, it looks like this may do more harm than good.

Microsoft's newly appointed Windows Preview lead for the Insider program, Gabriel Aul, has stated on Twitter that if you made this tweak, your machine will not receive future builds. As we speculated when we wrote the post, this is trick is for internal use only, and by applying it to your machine, it takes you out of the public release cycle.

Note, if anyone has done this for #Windows10 it will actually turn off your ability to get updates. https://t.co/MvbdySJ9aL via @NeowinFeed
— Gabriel Aul (@GabeAul) October 15, 2014

If you need to fix your registry, the following information was posted on the Microsoft Answer forums.

If you did change the registry keys a refresher on what they should be is as follows:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability
    BranchName = fbl_release
    ThresholdRiskLevel = low
    ThresholdInternal = <should not exist>
    ThresholdOptedIn = <should not exist>

You can use these commands from and Admin Command prompt (Windows Key + X, select Command Prompt (Admin))

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability" /v "BranchName" /d "fbl_release" /t REG_SZ /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability" /v "ThresholdRiskLevel" /d "low" /t REG_SZ /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability" /v "ThresholdInternal" /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability" /v "ThresholdOptedIn" /f

After performing that fix, you should be back into the release channel that will allow your machine to receive the new updates. As always, tweaking your registry is not for the novice user and we are betting that if you made the change in the first place, you should know how to perform the action described above.

While we do not have a date for the release of a new build for public consumption, we do know that it is coming soon. Until Microsoft gives us a new build to play with, keep digging around in the current release as there are many less popular features still being uncovered.

Source: Gabriel Aul