For those who don't know, Microsoft has been distributing a number of their Windows 10 builds via the "fbl_impressive" development branch, a branch created solely for Insiders and allows Microsoft to control what features are sent to the public for testing. There are many development branches which all focus on different things, however none of them are accessible by Windows Insiders. Microsoft announced yesterday that they were suspending Windows Update and Windows 10 Insider builds as they prepare for the Windows 10 RTM. The next build offered to Windows Insiders will be using production servers, which means the next build we receive could very well be the Windows 10 RTM, or at the very least an RTM candidate, depending on when Microsoft plans to push another build out. Microsoft has silently switched all Windows Insiders away from the fbl_impressive branch, and moved them over to the TH1 branch. The TH1 branch is where Microsoft is compiling RTM candidates, which means the next build delivered to Insiders can be nothing but an RTM candidate or the RTM itself. You can check to see if Microsoft has moved you over to TH1 by opening Regedit and navigating to HKLM>SOFTWARE>Microsoft>WindowsSelfHost>Applicability and double clicking "BranchName". If you see "TH1" you are ready for the next build. If you're not showing up as on TH1, just check for updates via Windows Update and the registry strings should update automatically. The Redmond giant announced recently that Windows Insiders will receive the Windows 10 RTM on July 29th. So Microsoft silently moving everyone over to TH1 could be in preparation for that. Regardless, the next build Insiders will receive will be from the TH1 branch, which is very exciting indeed. Source:WinBeta
Doubt it, since 10241 is just getting out, and there's no TH1 lab build yet... If we get a new build we usually get a build that's been through Canary and OSG ring some days and not completly crisp baked build... 10241 could be a test of some zeroday patches for the lab builds that's been pushed(fbl_marketplace and fbl_esc). I still think we'll get a 16384 th1 branch build between 10176 or 10240 (10176,10192,10208,10224 or 10240) Time will tell
Well, they have only uploaded 3 of the 12 billion builds so far so it's hard to tell but both 176 and 240 have no timebombs as they are RTM candidates so I doubt it will be either of those. The first entry into TH1 was 163.0 so it's quite possible when it's all done 241.0 may also be there.
I'm on the Insider Program with many desktops and laptops already sitting at 10162 Build with all of the updates from the insider program still updating my hardware daily, and after checking the HKLM-Software_Microsoft-WindowsSelfHost-Applicability, there is no Branch Name on any of my hardware devices, yet I just got my updates today as of 11"15AM
Sounds like you're on the slow ring, if you're only at 10162. Fast ring is 10166, and you're sh#t out of luck, since updates should be unavailable/suspended right now...?
seems you haven't got the 10166 during its deployment over fast ring. Perhaps this is the reason why you don't see something new in your registry
Doesn't matter if your at 10162 or 10166, the updates are still available to both builds, and as I said before all my 10162 updates are current, and we are just waiting for the RTM to happen. By the way, as insiders we will be able to have the best of both worlds when the RTM happens. We get the normal RTM updates to our 10162 0r 10166 builds, plus we get a link for the RTM ISO Download if we want to build new install hardware.
I highly doubt that there will be an ISO of RTM before GA. They are probably also going to change to encryption key in an attempt to prevent ESD decryption. I'd expect a pre-RTM build for MS to test how secure their delivery platform is.
No i think Microsoft give iso at OEM, because Microsoft give Windows 10 RTM Iso's for OEM. The reason is sample, OEM (Dell, Acer...) configured a personalized image of the iso and OEMs have a lot of pc configuring. And even if the file was esd I doubt he resists to wzór.
Since the encryption key is sent with the ESD ... no problem. Would be afaik the 4th time they change it.
We've been seeing it in an xml file in the BT Windows directory (whatever it's called) right? I've never actually tried to find it myself.
instructions from our friend XINSO: Code: To get decryption Cryptokey, let installation start few seconds and then 1. copy C:\$Windows.~bt\sources\Panther\windlp.state.xml to desktop 2. Open it with notepad and find "CryptoKey" such as example esd decryption key: BwIAAACkAABSU0EyAAgAAAEAAQCb7Jceg+YeJXNdb7HHJ0irxNsGSWu7itcuEQkfS+znxm6XwxmfINt8SGzbIIka2eOB2t9L0lGwSM0uP3UPyhBzzc8FL735OL+RnimL4SVKDb5AsYpREOcNQgKsk6OOeo8q8+4+swvwfe6+VloNqCrjiE6bCS7TrC+haV+eabj1QaT+aSXNWrukmrvi1VFoQIVeet5BqHzciVV+bv3/iSG/EEkxV6Yqq4Y2o9bvSDIbE+lGc1bKPlT9zy+lYx+WMB0Nfzo7nIrKs7qCw8GbeRTsHo5GMWxrLNltFsDpoO0C62pSvxEGB/id2TwESrd7brudppjjJ+LdbCBUNam6zx2lhZmjconDvvWLYC6KXVVgTh5WHjv8z0dxkD+Hc6o6OhdXuxAA5xtZYgIah8t2ZVK5V2PEFnusqZP7fqbSUJOp6sZe3AZWWVZz6dg6VqYpDMbKBz8rhHXXHjkaqIMrmxnSmHoB4fsxelWre9oxQoQJUkASAUhflDPKtFVe30oLsN6fNwBBNVKywJogPsClqIuNiQDpsXRFg8PYBgvqDQz8DRfDpu5WyhQjdD+eVQpeczWmTyPuwfGB0TscKDhzIhSwebKK0NwCn2LunmdJEOjJsnsYLrE63rsQdcXimzPifQ5XWlV9GUqo5ce+AlX0IMmw7DSZJBe9Sr1adBFuHQvRvQ1tGyQ5oD7WxKshS8WbvKT6cZb0XBE0Ru82gl9uSvJAgOJG9E8g7BApwCfaWAMEVj/Xd8DZSjZ0VWxRlsVkhjxWeiiQWg85J08JdjC2soG14IiXRTVAGogUTcUVlOPkovrWoRVqTMLAA+Vh0R6BpcAexwUv4YVmw2661iDUmnkYWyXMcSBQP43h5SjdLirO19b/1UD9lvaCaZpyokKMD6+GNJyCX9stVuS7c1ow/nsuVDgx3Rv7wE0as5h9WSheM5p6Lzf1UTHy1Mg2XpJAn37amw7rUnOkz4qqJ5ItRwAAhRn2Cn+PUtp5Ti1vfHmPd0PodAdTUo+5lYOGmXJxx0SHTh3dSCkSIJWjoAFYnrtEWMTszcenxYlZc2e6dWNZUPO4VyftrGkF4FpWxFC63Gd15uf3vUlStFXRArMh9KQ14sf4PGmpxmoXNZBWNsa7xizW83lkS3sbtnHtLEk6xyJ01sj+HWPoEuTzSbs6v3P8NstpN37xJui+hafIA5ILpB04qlxrxIRKEow31QzrMINyiwjCnxzIrXFuEQq9aY1930q5XgYfoV8OZirdIWKYtvPWzBgEkmi5w930kqjRyA81XwhH74guWww7A1lImbygBDl5wyE8GRVg2Emy7pU2sybyvtjMLSBgmTK8h6UqEXaupvuVCYjC8BzkUGWfTG9eh50TPpFZMO4vB2l2tbfwA2oTBwvjuwaDwdUIFXYjmdti3A+EGuhvDAeGzGxZhOmQir84CYXEKMj4yaqFvaKecMCtOOwWWpAEIzRWxXJIXN6EPqiZGEauZUAXjicVI/jpkKGhWUnaLZhNFTYD6Nl/eBMA2TPj6w4AiOnr21bDjgE=