Announcing Windows 10 Insider Preview Build 10565 Insider

That new activation will probably be available for new installations at Windows Retail edition after 10240 and of course will be unusable after free upgrade time expires next year.

BunnyJ said:

From what I think I understand you can now get the ISO via the media creation tool and perform a clean instillation by just entering the 7/8.1 key, no previous activation required. If you have 10 activated on the PC it would be pointless to use the key.

No, Jeff, Kari said it won't work with RTM Build 10240. Which, if I understand correctly, is what you get with the media creation tool. :)

BunnyJ said:

I was thinking that when 10565 becomes publicly available then wouldn't that build be available via that media creation tool as well?? Or would it replaced 10240??

And now I will say that my understanding is that what we're previewing as Insiders is what will be "service releases" to RTM Build 10240. Even if Build 10565 were to be pronounced stable with no bugs, it won't be released to the public. Too many things could/would go wrong.

Wynona said:

Whoop! Whoop! Whoop!

You do have a way with words! 565 Is running great!

Rocky said:

I have been trying to keep up with this thread, especially regarding the new activation procedure, but I still have one question; Does Kari ever sleep?

Short answer: Yes, but not very much. :)

Kari said:

OK, this is how and what I tested now:

1. Clean install Windows 10 Pro Build 10565 on a machine which had never before had any version of Windows. When setup asked for a product key, I gave a never before used Windows 8.1 Pro retail product key. Key was accepted and activation successful.
2. As I had no more "virgin" hardware, I created a new Hyper-V virtual machine, clean installed Windows 10 Pro Build 10565, entered the same Windows 8.1 Pro retail product key as above in #1. Key was again accepted and activation successful.
3. One more new vm, clean installed Windows 10 Pro Build 10565, entered a Windows 8.1 Pro retail product key which has been used multiple times, last time on this very PC I am using at the moment for a clean install which was then immediately upgraded to Windows 10 Pro. This key was now accepted on the new vm for a clean install of Windows 10 Pro and activation was successful.
4. Third new vm, this time clean installing Windows 10 Pro RTM Build 10240, trying to use any Windows 7 or 8.1 retail keys I have, used or unused, the key was not accepted and Windows could not be activated.

Conclusion, only based on this very simple set of test installs:

• Build 10565 can be activated with a valid Windows 8.1 (and most probably 7 & 8) product key, also when clean installing on a new machine.
• The RTM build, and most probably all builds prior to build 10565 need to be activated with a valid Windows 10 key, product keys from qualifying old operating systems will not work.

Kari

Great work Kari! You're my hero!

Edwin said:

Be nice if all menus were consistent.

Attachment 42683

Edwin, Edwin, Edwin.....are you never satisfied?

Rocky said:

I have been trying to keep up with this thread, especially regarding the new activation procedure, but I still have one question; Does Kari ever sleep?

Was just thinking the very same thing!


Maybe I should switch to the fast ring and grab this esd....

doorules said:

While waiting at airport gave the language pack a try, no difference. Does not see any new builds.

Installing a language pack is only a workaround to get Search working in 10565 if it after the upgrade does not work. As far as I know it has nothing to do with getting builds faster or anything else.

Tweet

— Twitter API (@user) View on Twitter