Windows Insider stuck on build 9841 - "No new preview build was found"

Question

I am in the insider program and on build 9841. I did this same process on 2 other machines, starting at 9841, running through windows updates, and then upgrading to build 9860. However, on this one particular desktop machine, I have all other windows updates
applied, but every time I check for a new preview build I simply see the following message:
"No new preview build was found, please try again later."
Any idea how to force this thing to detect the newer build which I know is available?
Patrick

Answer 1

I changed my registry to what you said, but I still can't get any update. Do you have any ideas for me? Only have 10 more days :\
thanks
For anything newer than 9926 registry settings must be as follows:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability]
"BranchName"="fbl_impressive"
"ThresholdRiskLevel"="low"
"Ring"="WIF"
"ThresholdOptedin"=dword:00000001
Copy this into the registry file and double-click it to import settings into your registry.
Then restart Windows Update and BITS services for the settings to apply on the running instance of Windows. You may use the following script:
net stop wuauserv
pause
net stop bits
pause
net start bits
pause
net stop wuauserv
Copy the text above into a text file, rename its extension to CMD, and run the command file with elevated privileges (right-click the CMD file and select Run as administrator from the shortcut menu).
Note: the branch name changed since 9926 days. Previously you could have the following settings:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability]
"BranchName"="fbl_awesome1501"
"ThresholdRiskLevel"="low"
"ThresholdOptedin"=dword:00000001
or even
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability]
"BranchName"="fbl_release"
"ThresholdRiskLevel"="low"
"ThresholdOptedin"=dword:00000001
Both did NOT work for me. The fbl_impressive value worked flawless.
Remember the value of BranchName MUST be the same as the keyword found in the name of the ESD file you download from Microsoft when you click
Download now in Update & recovery . The ESD could be found in %systemroot%\SoftwareDistribution\Download or in %systemdrive%\$Windows.~BT\Sources.
You can check to see what is the
valid branch name for a particular build on Windows here.
To cut the long story short:
The official Technical Preview releases of Windows 10 are known as:6.4.9879.0.fbl_release.141103-172210.0.9926.0.fbl_awesome1501.150119-1648
10.0.10041.0.fbl_impressive.150313-1821
10.0.10049.0.fbl_impressive.150325-1700
Set BranchName REG_SZ value in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] to:
fbl_release -- to upgrade to 9879
fbl_awesome1501 -- to upgrade to 9926
fbl_impressive -- to upgrade to 10041
fbl_impressive -- to upgrade to 10049
Well this is the world we live in And these are the hands we're given...