Activation troubleshooting

Page 3 of 30 FirstFirst 1234513 ... LastLast

  1. Posts : 56
    Win 10 Home
       #21

    I just ran a reactivation using my original product key, clicked on CHANGE PRODUCT KEY and re-entered it the result was "Genuine". That doesn't mean I'm home free.
      My Computer


  2. Posts : 18,424
    Windows 11 Pro
       #22

    @DAVEY JONES,

    Blank out the product key in your previous post! Come on now...you have to use some common sense too, respectfully. Nobody can be responsible for your product key being abused but you when you give it to people on the phone and post it publicly on the internet.
      My Computer


  3. Posts : 18,424
    Windows 11 Pro
       #23

    This is my take on it, and my experience. I've been working with PCs since the mid 1980's when I had a Radio Shack TRS-80 Model I. I was my ship's IT administrator in the 90's when we were upgrading from 286's and 386's to 486's and upgrading from Windows 3.1 to 3.1.1 and then to NT 4.0. I was an official Microsoft beta tester for Windows 95, 98, ME, and Vista. I've built multiple desktops, upgraded and repaired multiple laptops and my current household has a dozen networked computers of all types and 4 users (5th user passed away 3 months ago).

    The first goal, IMHO, should be to ensure that you have a clean Windows system to start from. You stated in your other thread that you allowed the scammers you were dealing with to install TeamViewer on your computer. It is more likely than not that they can now access your computer remotely, over the internet, any time they want to as long as it is connected to the internet. Your computer was infected with malware (virus, ransomware, whatever you want to call it.) I'll talk about the product key in a minute. The safest thing to do now is to wipe the hard drive and start over from a reliable source to install Windows 10 and you just happen to have a reliable source because the Windows 10 USB flash drive you purchased is read-only and would be next to impossible to infect with a virus - unless Microsoft themselves were infected and we have no indication of that.

    Like I posted earlier, the way to wipe the HDD and start over from ground zero is to delete every partition on it (at this point, even any data only partitions you might have) and clean install Windows 10 to the big, blank, unallocated space. It is very unlikely that the infection is in the UEFI firmware (BIOS) because not only is each model of computer firmware different, but even the same model computer may have several different builds of firmware and the infection would have to be specifically made for that specific build of firmware in order for the computer to still boot. So the clean install after wiping the hard drive is 99.9+% likely to remove any and all viruses until you do something to re-introduce it like open a previously infected file saved from the old infected installation.
      My Computer


  4. Posts : 18,424
    Windows 11 Pro
       #24

    Now, regarding your product key. First, Microsoft will never ask you for your product key over the phone or chat. They might ask you to enter your product into a Windows activation screen, but they will never ask you directly for it. That is one way to know if you are dealing with Microsoft or not. Microsoft will ask you for your Installation ID. The Installation ID is entirely different than your product key. The Installation ID is calculated by Windows using a bunch of different parameters and the Installation ID will be 99.9+% guaranteed to be unique to the combination of the motherboard, the version of Windows installed, and the product key. Change any one of those three factors and the Installation ID changes. Microsoft actually activates Windows against the Installation ID - not against the product key alone. The product key only designates which type of license the user has but Microsoft tracks the installation IDs to determine how many times on different computers that product key has been used because they can extract the product key from it. As of yet, I have not seen any information to suggest that installation IDs are being hacked.

    Each time you install the same version of Windows on the same computer with the same product key the Installation ID will be the same and Microsoft should not have any issue reactivating it over and over. Until a very high threshold of using the same retail product key on different computers is reached, Microsoft doesn't have much issue with activating the same product key on a different motherboard which will change the Installation ID. There is a low threshold of the number of times a product key can be used on different motherboards and once you get to that threshold then the product key will no longer activate automatically on the internet, you have to call the real Microsoft activation number and a voice recording will ask you to enter the Installation ID - not the product key - and then it will ask you how many computers you have it installed on. You answer ONE and you get the activation in return - which will only work with that corresponding Installation ID. I have Microsoft retail product keys that have been blocked from internet activation, but I've activated on at least a dozen different computers and they still activate just fine over the phone.

    I suggest installing your Windows 10 clean without entering a product at first because in some situations a digital license for that computer and that version of Windows gets saved to Microsoft activation servers based on the Installation ID and a generic product key. I doubt that happened with your computer in these circumstances, but it is a small possibility. If that did happen, then your Windows 10 will activate automatically when connected to the internet and you are good to go - no worries.

    If Windows is not activated, it will continue to function. You just will get nag screens telling you Windows 10 is not activated and some personalization functions will be disabled. You can always then go the activation screen under settings, updates & security, and change product key and enter a different product key and if it is valid it will either activate online or tell you to call Microsoft. Microsoft will allow the product key to be used on different computers. They just make you call them and tell them it is installed on only one computer - up until a very high threshold is reached where it becomes obvious the product key has been compromised and it is no longer a single user that is attempting to use it. And again - Microsoft will not ask you for a product key over the phone or on chat - they will ask you for the Installation ID and tell you how to display the Installation ID to give to them.
      My Computer


  5. Posts : 62
    10
       #25

    so i purchased windows 8.1 home from amazon, but only used the key to successfully activate windows 10home , the gigabyte motherboard went faulty which i replaced with a asus, i was expecting an issue to reactivate went through the microsoft troubleshooter and it still is unable to activate.

    spoke with microsoft and they said purchase a new copy, despite there been loads ofs of references from Gabriel Aul saying change of motherboard is possible .

    any ideas from the activation tool report

    Windows Diagnostic Information------------------------------Tool Version: 10.0.14393.0Licensing Status: In NotificationLicensing Status Reason: 0xC004F034Local Genuine State: Invalid LicenceLocal Genuine Result P: 0Last Online Genuine Result: Grace Time Minutes: 0Total Grace Days: 0Validity Expiration: Active Partial Product Key: 8xxxxActive Product Key Pid2: 00326-xxxxxxxxxxxxxxxxxxxxxxO S Version: 10.0.14393.2.00010300.0.0.101Product Name: Windows 10 HomeProcessor Architecture: x64Edition Id: CoreBuild Lab: 14393.rs1_release.161220-1747Time Zone: GMT Standard Time(GMT)Active Sku Id: 2b1f36bb-c1cd-4306-bf5c-a0367c2d97d8Active Sku Description: Windows(R) Operating System, RETAIL channelProduct Uniqueness Groups: 55c92734-d682-4d71-983e-d6ec3f16059fActive Product Key P Key Id: aaexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxActive Product Key Pid Ex: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxActive Product Key Channel: RetailActive Volume Customer Pid: Offline Installation Id: 721149187668524710135839585204391146774712373566676204160762566Domain Joined: falseComputer Sid: S-1-5-21-3276720573-1360324439-850152558Product L C I D: 1033User L C I D: 2057System L C I D: 1033Code Signing: SIGNED_INFO_PRS_SIGNEDService Available: trueOem Marker Version: Oem Id: Oem Table Id: O A3 Product Key: 0xC004F059Manufacturer: System manufacturerModel: System Product NameInstall Date: 20160804154324.000000+060Result: PASSTampered Items: Server Props: 0xc004f200****** Errors from Event Log *****Message: 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=5Time Written: : 20170207125200.088756-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: : 20170207125138.273978-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: : 20170207125138.242757-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: : 20170119213412.783499-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: : 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=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: : 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=NetworkAvailableTime Written: : 20170117182319.995406-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: : 20170117054741.191956-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: : 20170117054720.542429-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: : 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=0x800705B4Command-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=TimerEventTime Written: : 20170116174730.919764-000Message: License Activation (slui.exe) failed with the following error code:hr=0x800705B4Command-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: : 20170116174630.865797-000------------------------------------------------Created by Superfly for EightForums & TenForums
      My Computer


  6. Posts : 18,424
    Windows 11 Pro
       #26

    Have you tried changing the product key on the activation window and manually entering the Windows 8 product key?
      My Computer


  7. Posts : 62
    10
       #27

    I read on a microsoft forum that once a windows 8 key was used , it became redundant and a new windows 10 key was generated. I extracted the windoows 10 product key but i can no longer find the windows 8 key only the cd's

    windows............................... pfff
      My Computer


  8. Posts : 18,424
    Windows 11 Pro
       #28

    SchrodingersCat said:
    I read on a microsoft forum that once a windows 8 key was used , it became redundant and a new windows 10 key was generated. I extracted the windoows 10 product key but i can no longer find the windows 8 key only the cd's

    windows............................... pfff
    Unfortunately, you were misinformed. Nothing happens to the Windows 8 product key when it is used to upgrade to Windows 10. The old product key will continue to function under the same conditions that it did before it was used to upgrade. When you log into your Microsoft account, which devices are shown listed on it?

    Activation troubleshooting-capture.jpg
      My Computer


  9. Posts : 3,453
    Thread Starter
       #29

    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 Superfly for EightForums & TenForums
    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.
      My Computer


  10. Posts : 3,453
    Thread Starter
       #30

    mikiep said:
    fwiw,
    Bought a used laptop off ebay with near matching chipset as my existing Sandy Bridge chipset so I could move my cpu, ram, ssd's into it when mine gives up the ghost. Guy had 50 listed for sale $50 area so I bought 2. They arrived... you'd swear they looked brand new. Fans had minimal dust, no signs of wear on anything.

    Anyhow, no hdd, no ram, no ac adapter T520 ThinkPads... no coa stickers .. I loaded enterprise eval as a local Mike account which was 90 days x 3 resets,, 270 days total . Think I had 45 days remaining of last slmgr /rearm.
    Then win10 creators insider iso became available, so I installed it with a double click of the iso keeping nothing and got the not activated message until I did my first Microsoft login to my email probably, magically it instantly at next restart required Mike local login to change the PIN to 6 digit for proper encryption and windows activated. Slmgr shows its lifetime activated... I cant discover a key with the ShowKeyPlus.. key shows as just a bunch of b's.

    I'm guessing here, but looks like the win10 enterprise eval version gave the ebay T520 laptop the win10 activation to my Microsoft account.
    alphanumeric said:
    Enterprise won't ever get a Digital License, local or Microsoft Account. Enterprise is VL only and only activates with MAK or KMS keys. Also, you don't have to log in with, or even have a Microsoft Account to activate Windows 10. It can be installed and activated with a local account. I have no idea what happened in your case but its not a normal occurrence.
    *** @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 :

    Activation troubleshooting-capture.png

    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....
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 13:18.
Find Us




Windows 10 Forums