Windows 10: Windows 10 Enterprise build 10240 activation

Hi all! I have been reading through the forums for the past couple days after installing the Windows 10 Enterprise TP 10074 on a laptop here at work. I ran through the activation and setup of a MS account on that build and then ran Windows updates. This updated the build from 10074 to 10166, which at the time did not transfer the activation. I was able to get 10166 to activate, thanks to the forums. 10166 was activated and was functioning perfectly, checked the registry for TH1- it was there, got the 10240 update from Windows update, had no problems with the update process it went great. My problem now is that 10240 build of Windows 10 Enterprise wont activate. 10166 was activated when I did the update. So by all means 10240 should have been activated upon first boot. It was not. And I have not been able to get it to activate. Any thoughts suggestions?

:)

 

Windows 10 Home build 10240 cannot activate error code "0x8007232B" DNS name does not exist?

My machine originally had enterprise on it and the upgrade to build 10240 appeared to be successful, but for the first time it is not activated, shows the last digits for the enterprise key with the XXXs in front; but it will not activate for days now telling
me to try later.

Will this build upgrade to the next build even if it is not activated?

 

Windows 10 Pro or Windows 10 Enterprise?

I have Windows 10 Pro Build 10240 now. I am debating whether I should upgrade this to Windows 10 Enterprise Build 10240. What do you think?

 

The first thing is that you are running Enterprise. Enterprise is meant for businesses and will generally be activated via a business volume licensing system. Do you have this system in place? If not, that is why it will not activate.

I think you should be running either Professional or Home version of Windows 10 meant for personal use. Enterprise and Professional are nearly identical in everyday use.

If you had been on the professional route, it would have activated automatically when the update to 10240 had installed.

 

I am running Enterprise because that is what I am testing for the company I work for. As far as I know we do not have a KMS setup for Windows 10, since we are just testing Windows 10 for a future roll out. What strikes me as strange, was that 10166 did activate and was activated for 24ish hours before 10240 was released. I was hoping that 10240, since it is still not a final build, would be activated because 10166 was.

 

10166 was a preview - a trial version, 10240 is to all intents a release version and will possibly need a KMS server to activate it. There are several (non-kosher!) KMS options available, but this site is not the place to discuss it.