New
#30
After days of not being able to activate 10162 with 0xC004F034 error code being displayed,
I was able to activate normally just now.
What ever was wrong with the servers apparently has been fixed.
After days of not being able to activate 10162 with 0xC004F034 error code being displayed,
I was able to activate normally just now.
What ever was wrong with the servers apparently has been fixed.
I tried the VM that I was having trouble with before, and it activated fine.
I'm hoping this means they fixed the servers now.
That's great. MS fixed their sever and my desktop wont boot. Lights say CPU problem. Time the get the meter out and check my PSU.
Good thing I have my laptop so I can still get my internet fix.
Jim
activated Windows 10 Enterprise Insider Preview build 10162
Shawn I am not sure what to do I think I installed the Pro version from an email I got and that email gave me the activation code for Pro ( 6P99N-YF42M-TPGBG-9VMJP-YKHCF) and a ISO download link but when I installed it I don't remember in fact I am sure I never was required to enter any activation code. However the install went ahead and I have been downloading updates and adjusting the look when I had the chance to.
Now I have scrubbed the activation code from my phone memo as I have just seen there is a new build and therefore a new activation code. I cannot find that email which gave me the code which according to the listings so I am not 100% sure that I was given the Pro version.
If I run the validation tool after updating the version will it let me know which version I have??
Sorry to be a bit thick and I should have hung onto that code I had I know.
Thanks Shawn - just one thing I should have asked if I make the new ISO will it override the old install or will I have to start from scratch
So, now apparently, with Enterprise, keys are no longer working, you need live VL keys for non MKS installs, and you need an updated KMS key with your KMS server patched in order to activate.
Is this correct, Brink?
A small argument has been brought up on the Microsoft TechNet Social forums about whether your info here is correct or not - and neither side wants to consider that Microsoft has changed things since your info was published :)