Problems activating Windows 10 after update to 1607

Commissario
Joined
16 Oct 2002
Posts
343,964
Location
In the radio shack
I have a virtual machine which I built using Windows 8.1 prior to the free upgrade specifically to be able to get Windows 10.

It worked perfectly with 8.1, all activated and fine and I got the upgrade. All good, no problems. I've barely used it but I know it was activated because I checked and made sure.

A couple of days ago I did the 1607 update, whatever that is. It took ages!

Today I noticed a message telling me Windows needs activating so I tried to activate it.

First it failed like this.

activation-20170214-211219.png


I tried to troubleshoot it

trouble-20170214-211342.png


That doesn't make sense. It's telling me it found a Windows 10 Pro licence, I'm using Windows 10 Pro but I need to install Windows 10 Pro. Huh?

I also get this.

troubleshoot-20170214-211307.png


I've tried activating over and over again but I don't have any firewall, I've turned off Pi-hole in case that was blocking something (but I've set this PC to bypass and use Google DNS anyway) and as far as I'm aware, nothing is limiting my connection to the outside world.

I've also tried changing the licence key to a brand new unused one.. Same thing.

There's an option for having changed hardware. I haven't changed any hardware but I clicked that anyway. It makes me log into my Microsoft account (which I never, ever use) and then it tells me I don't have any licences registered!

Any suggestions please?
 
No, it found a Windows 10 Pro Digital license. They are different, although I don't think that is the issue. Are you sure it's able to see the Windows licensing servers? Anything more detailed in event viewer?

1607 is the anniversary update. It was well known to break a lot of things, including the networking stack and netnat. I assume you can browse normally from it?
 
I've reset the network stack - No difference.

Yes, I can access the internet perfectly. What's frustrating is that it worked prior to this stupid update!

Nothing fancy in the log really.

Code:
Log Name:      Application
Source:        Microsoft-Windows-Security-SPP
Date:          14/02/2017 21:57:55
Event ID:      8198
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
License Activation (slui.exe) failed with the following error code:
hr=0xC004F034
Command-line arguments:
 
Since the upgrade, is the user you are running as, still a Local Admin? If you elevate a command prompt (run as admin) with slmgr /ato what happens?
 
Yup, that account is still local admin.

Have tried that, just tried again after resetting the networking stack and get the same. Not sure if the code is anything linked to my activation key so I've blanked part of it.

this-20170214-224303.png
 
Hmm, this is interesting. I assume no changes to the VM (memory, CPUs, extra disks?). I would consider using the automated phone service and let it activate that way.
 
Hmm, this is interesting. I assume no changes to the VM (memory, CPUs, extra disks?). I would consider using the automated phone service and let it activate that way.
Not as far as I can remember. It was OK up until the update.
I have no problem using the telephone service to activate but it's been a while and I can't remember how to persuade it to let me - I've never used it in Windows 10. Can you remind me where it is please and I'll do it in the morning (I'm in bed now).
Ta.
 
Just wait for 24 hrs as it can be problems on Microsoft's end. I panicked when i reinstalled but it sorted itself the next day.
 
Still no joy this morning so I called the activation line to use the automated system. It failed. I spoke to them and they gave me one of their generic keys which worked.

Seems odd, that key is all over the internet and I guess anyone can use it.
 
Yeah, looks like it's a generic key they give out freely to anyone trying to update Windows 8 to Windows 10.

/edit - Which although it works and I'm now activated, doesn't explain why the key I was using and had activated successfully before suddenly stopped working and wouldn't activate.
 
Back
Top Bottom