why would anyone install this? everyone says it's buggy as hell. you gain nothing from installing it and sooner or later you will get is as a stable release anyway.
I followed your instruction and clean installed 10130 today. The Applicability/BranchName and UserPreferredBranchName showed as th2_release. And I could not get 10525. Any help would be greatly appreciated. [Note] Last week, I changed the Applicability/BranchName and UserPreferredBranchName of 9926 from fbl_impressive to th1, and I could receive 10240.
Im kinda surprised how more memory efficient is chrome 32bit vs 64bit i guess im sticking with 32bit version after all cuz i didnt notice any speed difference the 64bit version just hog more resource edit : i tested it with 4 tabs Google plus , youtube home page , youtube subscription page , and 720p video playing the 32bit dev version used around 600MB while the canary 64 build used +900Mb with same profile..extensions..etc
I've not had any lasting success with this method either. Tried on two devices now, one came with W8.0 Core the other W8.1 /w Bing. Both activate fine with 10130 Pro Insider build and upgrade and stay activated on 10240 or 10525. But, if I format and do a clean install or do a PC Reset, they both lose activation. I'm guessing its got something to do with the Core and /w Bing keys in the BIOS.
I had similar experience i did however managed to get it after clean install of 10240 (activated), without any sort of modifications/tweaks (only disabled nasty Defender) and after couple of reboots.. idle system for a while i tried the reg setting trick to get other languages, but after reboot the build is gone until i returned the current UI kanguage settings (en-us)
Gone? Abbodi, after reboot, the Windows Updates will find that your new UI setting is being different from that of the old ESD, and hence deleting the old ESD and prompting an error. This is normal. Give it a second or third attempt, and there you should go. If NOT, there must be something wrong with your new UI setting trick.
Yeah the activation is entirely tied to the activation status of the previous build, not to the Microsoft account. I understand this about the RTM but for an Insider build is just plain stupid.