Windows 10: Can't update to TH2 after upgrading from PRO to ENTERPRISE...

I run Enterprise because it has the official Windows To Go utility built in Control Panel. Pro doesn't have it. As a Microsoft MVP I get a free MSDN subscription with the legal keys to use it, so why not? There may be other reasons for other people depending on their situation.

 

I was asking the OP where he got his enterprise product keys from. In his instance it does matter because if he has illegitimate product keys that might explain why he can't update to build 1511. It would be similar if you were asking why your install of Enterprise was not activated - the answer to that would be because the product key you used is only valid for activating products that already have a digital entitlement stored on MS activation servers.

 

Changed 3 different product keys (Enterprise) and same problem; "...different edition...".
(Now my Windows 10 Enterprise is not activated.)

 

Hi,

Have you tried running setup.exe from within Windows yet ?

If I understand everything correctly, Windows Pro accepted an Enterprise key, activated with that and now TH2 sees it as a Pro version ?

What does running winver tell you ?

Cheers, *Wink

 

Pro will not accept an Enterprise key for installation or activation. Entering an Enterprise key via "change product key" in Home or Pro upgrades them to Enterprise. Activation happens after the upgrade. If you enter a blocked key it will still upgrade but then fail to activate.

 

Where are you getting all these keys? Are they legitimate keys? Enterprise keys are corporate keys? Other than MSDN etc.

 

Hi,

Precisely. I was just trying to phrase it errr....."diplomatically". LOL.

Still, quite odd all this.

Cheers, *Wink

 

I changed Pro to Enterprise with a Enterprise product key and then I activated via phone.
Now my system shows "Enterprise" but can't update to TH2 or reinstall the Enterprise ISO with TH2... because I have a "different" edition!

Today I tried 3 different keys. My Windows 10 Enterprise is not activated now. Same problem, my edition still being different.

 

Mount the ISO file. It should have a sources folder with an install.wim file or install.esd file?

From an elevated command prompt ("run as administrator" command prompt) run:
dism /get-wiminfo /wimfile:f:\sources\install.wim /index:1

The path in red needs to be the path to the install.wim file. If you have an install.esd file, then change install.wim to install.esd.

Post the results back and we can determine if there is something incorrect about the TH2 version you have downloaded.

 

Where are you getting all these keys? What ISO are you trying to upgrade the current Enterprise install with? The Media Creation Tool ISO cannot upgrade Enterprise. You need an Enterprise ISO to even attempt it.

 

Something just doesn't seem to be above board, does it?

 

Just wondering? I have MSDN and I still only get the one Enterprise key. If one was just pulling keys off of the internet it would explain why it won't activate.

 

Hi,

OP states that the current install (10240?) is activated though. See post #11.

Cheers, *Wink

 

1511 10586.14 is what he is trying to get
Which reading other posts he cannot do with what windows version he has.
I thought you could only have one product key am I wrong

 

Depends on where you work and how it's licensed. There are MAK keys and KMS keys. My MSDN key is a MAK key. I only get that one Enterprise key and its good for 10240 and 10586. I didn't get any new keys for build 10856 as it uses the same keys as the older build. But, yes normally you would just get the one key to use on all your enterprise PC's. Enterprise keys are good for multiple activations on multiple PC's. This is why I asked where he was getting all these keys?

I don't think the issue was a key issue though. I think the issue is you cannot upgrade Enterprise from 10240 to 10586 without doing a clean install. It just won't let you do it. When I was running Windows 8 Enterprise I am pretty sure I ran into the same issue. I remember having to clean install to go to a new build at least once. It was a while ago now so I can't remember the exact details.