I am running win 10 TP enterprise:build 9926:now when I go into settings to check for updates and new builds, In advanced options, In the box "choose what branch etc... the only option is:fbl_awesome1501: is this correct?.There are no options to serch for a new build.
am i worrying about nothing?.
regards Topper.
I went into the registry and made the change from FBL_AWSOME1501 to fbl_release.
You should be ok.
From Gabriel Auls' blog... However, it’s now clear that this trick was for internal use only, and might do more harm than good for users. According to this tweet from Gabriel, computers that have applied this registry hack will not be receiving future builds of Windows 10.
So essentially, it takes users out of the public release cycle.
Understood. I think it's great that Jeff found a way to stop the 993x build offers. The problem is that Jeff found a way to STOP build offers.
What worries you Topper?
If you did not change the registry key, no worries.
If you did change the Registry key, change it back to FBL_AWSOME1501, and no worries.
Win10 is a playground for techies - lots of fun, no worries. A lot like opening presents - "Oh look at that, I wonder what could be inside? It's very nice and very red, but my favorite color is blue. Oh, it broke alrea
I suspect that MS will remove the branch option from public use in the near future.
As dmolt57 indicated, the hack was more for internal use, I see the option itself as more of an internal development use.
Sorry to butt in,Understood. I think it's great that Jeff found a way to stop the 993x build offers. The problem is that Jeff found a way to STOP build offers.
What worries you Topper?
If you did not change the registry key, no worries.
If you did change the Registry key, change it back to FBL_AWSOME1501, and no worries.
Win10 is a playground for techies - lots of fun, no worries. A lot like opening presents - "Oh look at that, I wonder what could be inside? It's very nice and very red, but my favorite color is blue. Oh, it broke alrea
I suspect that MS will remove the branch option from public use in the near future.
As dmolt57 indicated, the hack was more for internal use, I see the option itself as more of an internal development use.
Thank you Bill for clearing that up. Seeing that we were not supposed to get that, I uninstalled update ( kb3035129 ) from
installed updates, and 3 hours later its installed again. So I'm going to leave it alone for now.
Jim
Last edited by jlr888; 30 Jan 2015 at 01:10. Reason: typo
No I left it alone and asked the questions first: All is good.Sorry to butt in,Understood. I think it's great that Jeff found a way to stop the 993x build offers. The problem is that Jeff found a way to STOP build offers.
What worries you Topper?
If you did not change the registry key, no worries.
If you did change the Registry key, change it back to FBL_AWSOME1501, and no worries.
Win10 is a playground for techies - lots of fun, no worries. A lot like opening presents - "Oh look at that, I wonder what could be inside? It's very nice and very red, but my favorite color is blue. Oh, it broke alrea
I suspect that MS will remove the branch option from public use in the near future.
As dmolt57 indicated, the hack was more for internal use, I see the option itself as more of an internal development use.
Thank you Bill for clearing that up. Seeing that we were not supposed to get that, I uninstalled update ( kb3035129 ) from
installed updates, and 3 hours later its installed again. So I'm going to leave it alone for now.
Jim
Thanks again all. Topper.
Glad to hear that Topper,
Here's an interesting twist. If you ever have WU issues, a post on insider.windows.com forum recommended going to update.Microsoft.com - you get prompted to load a control, and then the Settings - > Windows Update 'window' opens on your machine.
I had a failing Realtec driver - repeating fails - but after visiting the web WU, the offers and failures stopped.
After that, I decided to look at the registry re: the branch setting - it was not on my system!
Either my visit to the web WU or some other update removed the entry, .
If you want to easily check yours, open an elevated command prompt and enter the following command:
reg query HKLM\SOFTWARE\Microsoft\WindowsSelfHost\Applicability /s
Well.....here we go again. Seems like every time I install a update; like i installed a driver that was just pushed through for my graphics card; Well once that installed.....once again my sound got disabled; and once again I had to uninstall it from device manager and now gotta reboot to let it reinstall my sound card again......I know this is only a tech preview.....but still......this constant having to reinstall the sound card and having to reboot is gonna make me start drinking here in a moment........
Quote
