Page 2 of 2 FirstFirst 12
  1.    23 Aug 2015 #11
    Join Date : Aug 2015
    Posts : 1
    windows 10

    Quote Originally Posted by Fafhrd View Post
    (Insider since 6/6/2015)
    I installed Technical Preview 10074 yesterday, with a local account, then updated whatever was available through settings, and switched to my Microsoft Account, and switched to fast builds update (no explicit "Insider" option available at the time this TP 10074 version came out).

    It failed to activate, or use the key (-YKHCF), even when I entered that key for 10074 using settings, activation or Slmgr -ipk. It remained with the key -HQRJR.

    Today I used the registry hack in the post above to upgrade to 10240, and it auto-activated fine with -3V66T - I did not have to enter a key. No issues with sign-in with the MSA, and it had set to receive Insider builds automatically.
    That's great you were able to activate, but I'm a bit confused. Did you signup as an insider on 6/6/15 and did not run any insider build until last week on your computer? Since M$ is using hardware based activation, if you ran one of the preview builds on 6/6, your computer is activated for the insider builds, even if you did a fresh install last week.

    Your post in the Insider FAQ thread said that "I had been unsuccessfully been trying to activate 10240 since 19/07/2015". I'm in exactly that situation. Not excited about starting over from scratch, but would if your method works to be activated on insider builds.
      My System SpecsSystem Spec

  2.    24 Aug 2015 #12
    Join Date : Dec 2013
    Portsmouth Hampshire
    Posts : 1,130
    Windows 10 x86 14383 Insider Pro and Core 10240

    I first ran an insider build on that machine on I guess 6/6/2015 - it would have been 10130, and followed it up with upgrades 10158, 10159, 10166, and I did not bother to check if these were activated - they were of course previews, and activation hardly mattered.
    Then I received the 10240 build and upgraded on 15th -16th overnight. It was broken and did not do a lot of things properly (I can't remember exactly what, but the behaviour had carried over from an earlier upgrade. SFC etc., did not fix it, and I wasn't happy with having part of my email as username. A reset did not activate, so I was left with an unactivated 10240.

    I had kept the ESDs, and made ISOs of them and I tried 10166 upgraded to 10240 on 17th July - no activation. I then set about repeating the whole sequence of upgrades, different partition, (10130>>>10240) on the 18th to 19th, which left me activated, but unable to receive insider builds because of some error. I still have that. I reinstalled 10240 on the original partition and it remained unactivated. If my machine had been registered it should have been activated, but stubbornly remained not.

    I don't know why 10240 failed to activate is the simple answer. It was a very short window from 15th July (10204 made available to Insiders) until 17th or thereabouts when they apparently turned off the activation servers for Insider builds. Whatever happened, my 10240 installations went wrong, and either were fundamentally broken - no start menu for instance, or were active but remained unable to receive insider builds, or working but unactivated.

    Now maybe the insider builds activation servers are online again, but I discovered that the Technical Preview ESD for build 10074, not activated on install because it has a PID.txt* file containing the -HQRJR product key , would receive the download to upgrade to 10240 if the registry was modified to contain the TH1 preferred build references, and subsequently activate on upgrading.

    The latest build10525 failed to activate on upgrading an unactivated 10240 build set to receive insider builds, and on a clean install on a different partition. Microsoft defines different partitions as separate devices for the purpose of their EULA for Windows 10 - I wonder if this is reflected in the behaviour of different installs. However, my multiboot test machine now contains several activated build 10240 installations, done by the 10074>registry edit for TH1>10240, which seems to work infallibly. Some of these are purely on local accounts.
    I even have the 10074 backed up with Macrium for quick reinstalls.

    *I since discovered if the PID.txt file is edited to the -YKHCF key, 10074 activates on installation.
      My System SpecsSystem Spec

  3.    24 Aug 2015 #13
    Join Date : Apr 2015
    Posts : 8,812

    Good info to know. Thanks. If I run into this problem, I'm coming to you for the PID change instructions!
      My System SpecsSystem Spec

Page 2 of 2 FirstFirst 12

Similar Threads
Thread Forum
RTM/GA or Insider - What are you going to do?
As the Insider program will continue after Windows 10 is released I thought I'd see how many of you are going to stay an insider or jump over to RTM/GA version. How to Start or Stop Receiving Insider Builds in Windows 10
Windows Insider
Solved Insider after the 29th?
I have been an Insider member since last fall. I installed it on a fresh SSD in a separate (test) computer from my daily driver. The test computer has updated regularly to the latest Win10 build and is current. The daily driver computer is a...
Windows Insider
where is insider hub on 10240
cannot seem to find insider app for insider hub, any ideas guys
Software and Apps
Mobile Phone Insider app for Windows 10 Preview, renamed to Windows Insider
Windows 10 News
MS Insider Program
Hi, I've installed Win10 TP in VM player yesterday, received the security code from MS, 10 was activated. I'm not a PC expert or an IT pro, do I need to join the insider program to receive build updates? I have sent some feedback already when I was...
Windows Insider
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:27.
Find Us
Twitter Facebook Google+

Windows 10 Forums