Windows 10: Activation troubleshooting

Firstly... the way to post the report is as such:

Code: Windows Diagnostic Information ------------------------------ Tool Version: 10.0.14393.0 Licensing Status: In Notification Licensing Status Reason: 0xC004F034 Local Genuine State: Invalid Licence Local Genuine Result P: 0 Last Online Genuine Result: Grace Time Minutes: 0 Total Grace Days: 0 Validity Expiration: Active Partial Product Key: 8xxxx Active Product Key Pid2: 00326-xxxxxxxxxxxxxxxxxxxxxx O S Version: 10.0.14393.2.00010300.0.0.101 Product Name: Windows 10 Home Processor Architecture: x64 Edition Id: CoreBuild Lab: 14393.rs1_release.161220-1747 Time Zone: GMT Standard Time(GMT) Active Sku Id: 2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8 Active Sku Description: Windows(R) Operating System, RETAIL channelProduct Uniqueness Groups: 55c92734-d682-4d71-983e-d6ec3f16059f Active Product Key P Key Id: aaexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Active Product Key Pid Ex: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Active Product Key Channel: Retail Active Volume Customer Pid: Offline Installation Id: 721149187668524710135839585204391146774712373566676204160762566 Domain Joined: false Computer Sid: S-1-5-21-3276720573-1360324439-850152558 Product L C I D: 1033 User L C I D: 2057 System L C I D: 1033 Code Signing: SIGNED_INFO_PRS_SIGNED Service Available: true Oem Marker Version: Oem Id: Oem Table Id: O A3 Product Key: 0xC004F059 Manufacturer: System manufacturer Model: System Product Name Install Date: 20160804154324.000000+060 Result: PASS Tampered Items: Server Props: 0xc004f200 ****** Errors from Event Log ***** Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=5 Time Written: : 20170207125200.088756-000 Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139F Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailable Time Written: : 20170207125138.273978-000 Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139F Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailable Time Written: : 20170207125138.242757-000 Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailable Time Written: : 20170119213412.783499-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170119213409.824605-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170119181022.936170-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170119181021.286439-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=4Time Written: : 20170119164752.076985-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170119164738.169285-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170119164732.137407-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170118220119.782867-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170118220119.751613-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=3Time Written: : 20170118150417.877961-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170118150322.444985-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170118150316.012438-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170117214155.318121-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=2Time Written: : 20170117200620.643060-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170117200559.604904-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=1Time Written: : 20170117192232.140782-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170117192216.279161-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170117192216.247876-000Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=1Time Written: : 20170117183124.519719-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailable Time Written: : 20170117182319.995406-000 Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=1 Time Written: : 20170117054741.191956-000 Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139F Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailable Time Written: : 20170117054720.542429-000 Message: License Activation (slui.exe) failed with the following error code:hr=0x803F7001 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=1 Time Written: : 20170116182319.339635-000Message: License Activation (slui.exe) failed with the following error code:hr=0x8007139FCommand-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=NetworkAvailableTime Written: : 20170116182151.754312-000Message: License Activation (slui.exe) failed with the following error code:hr=0x800705B4 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=TimerEvent Time Written: : 20170116174730.919764-000Message: License Activation (slui.exe) failed with the following error code:hr=0x800705B4 Command-line arguments:RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8;NotificationInterval=1440;Trigger=UserLogon;SessionId=1 Time Written: : 20170116174630.865797-000 ------------------------------------------------ Created by for EightForums & TenForums[/quote] Secondly... why mask stuff when asking for diagnostic help? My commenti n the OP relates to the FULL OEM key only..
partial keys and Pid's cannot compromise your licence - so leave them be - they help with the diagnosis.

Anyway ..from what we can gather you are using a Win 10 generic key (which cannot activate without digital entitlement)

As per these:
Active Partial Product Key: 8xxxx (assume -8HVX7)
Active Product Key Pid2: 00326-xxxxxxxxxxxxxxxxxxxxxx (00326 = Win 10 Retail)

So...yes, the Win 8 retail key is needed on a new mobo if the tranfer wizard does not work.

 

*** @mikiep, @alphanumeric - I brought these posts here as we were hijacking that thread.***

This is an interesting phenomenon. I have heard of KMS (Volume licence) installations being upgraded and resulting in digital licences with a MAK ( NB: The BBBB in ShowKeyPlus represents a masked MAK)

I had ungraded my work notebook from Win 10 Pro 10240 activated with a MAK to AU and got this :





That's the generic MAK I was alluding to - and it has digital licence.

Thus the official blurb regarding VL not qualifying seems odd.. why else have a generic MAK then...very strange....

 

There is a difference between the MAK licence and a VL which will need "phone Home" activation at regular intervals, (was every 90 days but may have changed), Not sure if this is a factor here. The Microsoft partner licences, (in House software Licence), were MAK key activated in the past and they will upgrade to a Digital licence (even one linked to a Microsoft account), without a problem, the same as any other Retail licence

 

Yip, correct ... MAK is a permanent VL, whereas GVLK is temporary and requires re-activation via KMS within each 180 day activation interval.

My concern, however, is that... be it MAK or GVLK, both are VL and should not be getting digital licences.

 

I actually see a MAK as a form of Retail Licence rather than a form of GVLK and It would appear that Microsoft, ( at least at present, but we all know how soon MS can change the rules), are treating the MAK as a Standard retail, possibly due to the fact that you cannot easily tell those MAK's issued to VL customers from those issued to other legitimate users. *Confused

 

Well just for fun I did a change key on my 10 Pro 1703 install and entered my MSDN 10 Enterprise MAK key. It upgraded and shows as activated with a Digital License linked to my Microsoft account.

Tried it on a second PC and it didn't work. It was 10 Home 1703. MAK key was rejected via change key. Entered the generic Pro key and it upgraded to pro though, and activated with a DL it already had. Then tried my MAK key again and it was accepted, upgraded but won't activate? That PC won't activate with my MAK key now? I get a "Windows can't activate with this product key, 0xc004b100. Was able to go back to 10 Pro by entering the Pro generic key though. Now shows activated with a digital license.

Worked once and failed once.

 

Going back to the early days of Windows 8 RTM, October/November 2012, you could upgrade trial Enterprise Windows 8 versions with genuine retail ESD Windows 8 Pro upgrade downloads (I had a £14.99 retail offer with my Windows 7 Laptop in August).

There were "Qualifying OSs" - in my case OEM Windows 7 Home Premium enabling ordering and payment, then download of the ESD package with the product key in the email, and then there were "upgradeable OSs" - Windows 7 (any), and some later Windows 8 Pro trials and Windows 8 Enterprise trials too. I don't remember which other OSs were upgradeable, or which were qualifying - it may have been that XP SP3 was qualifying, but not upgradeable etc.

The upgrades seemed to be able to gather the Product Key from somewhere (a PID.txt perhaps included when the ESD download took place?), it was a bit of a mystery at the time, as was the nature of the ESD file, since it could not be opened or mounted like a WIM file then. These were my notes at the time on Eightforums:

How did you setup your Win 8 install? - Page 16

I was not prepared to dump 7 yet 8 was too strange at the time.

 

Om my last PC running 10 Pro, the one that wouldn't activate with slmgr /ato, I mounted my Enterprise MSDN ISO and ran setup.exe, figured it may be easier than starting all over with a clean install. If it didn't work I'd just clean install. Booted up real slow and to a totally blank screen? Just a cursor. A couple of reboots latter it appears normal again? Entered my MAK and got a 0xc004b100 error. Running slmgr /ato changed it to a 0xC004F012 error. What finally fixed it was going to Setup >update & security >activation and running the trouble shooter. I clicked the "I have recently changed hardware" option and it activated with a DL. Confused, I am?

I now have 3 PC's that all have Home, Pro, Education and Enterprise Digital Licenses. *Biggrin

 

Just did up a Windows To Go drive via the official control panel utility. It prompted to activate, entered my MAK key and it instantly activated with a DL linked to my Microsoft Account. Booted it up on my spare desktop and it initially said it couldn't activate. That was just because I hadn't setup my WIFI though. *DohOnce I did that it activated with a DL.

 

Typical Microsoft Dirty Tricks - Expecting you to have an internet connection to activate over the net *Tongue

 

I did the OOBE on my main desktop which has a wired connection. It just prompted OK we're connected. If I had done it on the other PC it would have asked for the WIFI password etc during setup. Just a brain fart on my part. Plus the other activation problems I had with my other Enterprise installs had my second guessing why it wouldn't activate. They also said "we can't connect to the activation server" but had a working Internet connection. Once I looked at the Network taskbar Icon I realised I had no connection. *Redface

 

Well, I just don't get it... entering an edition specific (non-generic) Win 10 key gets DL?

That's just nuts...notwithstanding that MS have total control with online activation, there does not appear to be any logic

 

*Ditto to the no logic part. My Education installs that were all installed and activated with my MSDN keys, keys listed as Retail, all got a DL when I upgraded to the AU. Before that they showed as activated with a product code. I just assumed it was a glitch. Either way I wasn't going to ague, DL makes installs easier, no having to enter a key. Education is excluded from the free upgrade, there was no Education version for Windows 8 or 7 to upgrade from. Logic would dictate that they stay activated with a Product key, not a DL.

Now my Enterprise installs all have a DL too? IMHO that has to be a glitch, the MAK keys must be being treated as Retail keys? In a corporate setup they would all be KMS keys which I assume will never get a DL. One would hope anyway as they are subscription based. A DL is forever and would end the need for paying the subscription fee to Microsoft. I don't have a KMS key to test it though, I don't get KMS keys via MSDN. MAK keys would only ever be used by those with MSDN subscriptions for testing the Enterprise version.

 

Yup, Alpha... it's hard figuring out what MS does... :sigh:

I'm thnking DL takes precedence in the quest for the billion...anyway far be it for me to complain .. still got a bunch of Win7/8 keys for DL... so let sleeping dogs lie, that's what I say ... *Wink

 

I think the end is near though for activating with Windows 7 and 8 keys. One thing that has changed is reading Windows 8/8.1 OEM Embedded keys. The CU install media now ignores my laptops OEM 8.0 Core key. I get prompted to enter one.