New
#11
Those are high-level errors that cannot be troubleshot easily - run LicensingDiag.ps1 from Activation troubleshooting
We need to see the full Event log errors.
Have you tried re-entering the COA sticker key in Settings -> Activation -> Change Product Key? If so what error code does it spit out?
PS If you are not comfortable with Powershell run the exe from there - it won't give as much info but more than we have now.
I tried entering the original COA sticker key, but remained not activated.....decided to do a fresh install of windows 10 pro and see if it activates.....I couldn’t get the install to proceed as it said it needed to be GPT, So converted to GPT using mini tools partition wizard FREE.....then rebooted and all I got was a flashing cursor top left of a black screen......so decided to reboot and try installing W10, low and behold, it installed completely, seems to be a lot more things to decide on during the install process, but all went ok and activated immediately on its own......so I assume that’s good news.....now going to restore a Macrium reflect image and if not activated, may well have to start again......with a list of installed programs from Revo uninstaller ( be good if three was an option to export a program list to a text file.....but a screenshot and print out will suffice, will reinstall programs as needed, with a MR image back up before each install.......will update when MR image restored...
- - - Updated - - -
the Key from the sticker on my PC came with an installation W7 disk unfortuantely after the image restore I have an unactivated PC again.....would prefer to fix it, if not will start over...
The PC accepted my W7 Key but got this after it whirred for a while
AS REQUESTED i HOPE !!!
I put some XXXs where key info was, hope that was ok....
- - - Updated - - -
------------------ Licensing Data ----------------
ToolVersion : 10.0.18362.1
LicensingStatus : SL_LICENSING_STATUS_NOTIFICATION
LicensingStatusReason : 0xC004F034
LocalGenuineState : SL_GEN_STATE_INVALID_LICENSE
LocalGenuineResultP : 0
LastOnlineGenuineResult :
GraceTimeMinutes : 0
TotalGraceDays : 0
ValidityExpiration :
ActivePartialProductKey : 3V66T
ActiveProductKeyPid2 : XXX
OSVersion : 10.0.18363.2.00010100.0.0.048
ProductName : Windows 10 Pro
ProcessorArchitecture : x64
EditionId : Professional
BuildLab : 18362.19h1_release.190318-1202
TimeZone : GMT Standard Time(GMT)
ActiveSkuId : 4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c
ActiveSkuDescription : Windows(R) Operating System, RETAIL channel
ProductUniquenessGroups : 55c92734-d682-4d71-983e-d6ec3f16059f
ActiveProductKeyPKeyId : XXX
ActiveProductKeyPidEx : XXX
ActiveProductKeyChannel : Retail
ActiveVolumeCustomerPid :
OfflineInstallationId : XXX
DomainJoined : false
ComputerSid : XXX
ProductLCID : 2057
UserLCID : 2057
SystemLCID : 2057
CodeSigning : SIGNED_INFO_PRS_SIGNED
ServiceAvailable : true
OemMarkerVersion :
OemId :
OemTableId :
OA3ProductKey : OEM key not present in firmware
ActivationScenarioCode :
ProductKeyCode :
Manufacturer : Gigabyte Technology Co., Ltd.
Model : To be filled by O.E.M.
InstallDate : 20200301205217.000000+000
Result : PASS
TamperedItems :
ServerProps : 0xc004f200
--------- SPP Event log data ---------
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 16 March 2020 22:38:220
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=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 16 March 2020 21:48:470
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=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=TimerEvent
Time Created: 16 March 2020 21:48:470
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=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=UserLogon;SessionId=1
Time Created: 16 March 2020 21:47:450
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 19:41:030
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 19:40:010
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 19:07:490
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 19:07:270
License Activation (slui.exe) failed with the following error code:
hr=0x80072EFD
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 18:59:140
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 10:56:180
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 10:56:180
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 10:23:140
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 10:23:140
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 10:22:310
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 10:21:280
License Activation (slui.exe) failed with the following error code:
hr=0x80072EFD
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 10:07:050
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=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 01:03:360
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=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 12 March 2020 01:03:360
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 11 March 2020 20:32:270
License Activation (slui.exe) failed with the following error code:
hr=0x80072EE2
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=NetworkAvailable
Time Created: 11 March 2020 20:14:120
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=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=TimerEvent
Time Created: 11 March 2020 19:48:020
--------- Hardware Data ---------
+Registry: SOFTWARE\Microsoft\Windows NT\CurrentVersion
BuildLabEx: 18362.1.amd64fre.19h1_release.190318-1202
DigitalProductId: Encoded info redacted
DigitalProductId4: Encoded info redacted
+Registry: SOFTWARE\Microsoft\Windows NT\CurrentVersion\DefaultProductKey
DigitalProductId: Encoded info redacted
+Registry: SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform
BackupProductKeyDefault: *****-*****-*****-*****-3V66T
+Registry: SOFTWARE\Microsoft\SQMClient
MachineId: {F900A8E5-74A1-4CA3-9DB1-C1A6352A57C2}
+Registry: SYSTEM\CurrentControlSet\Control\ProductOptions
OSProductContentId: 2907b935-0ea5-dca1-85a7-75597491a18b
OSProductPfn: Microsoft.Windows.48.X19-98841_8wekyb3d8bbwe
SubscriptionPfnList: "Microsoft.Windows.Pro.Addon_8wekyb3d8bbwe"
+Registry: HARDWARE\DESCRIPTION\System\BIOS
BiosMajorRelease: 4
BiosMinorRelease: 6
ECFirmwareMajorRelease: 255
ECFirmwareMinorRelease: 255
BaseBoardManufacturer: Gigabyte Technology Co., Ltd.
BaseBoardProduct: F2A88XM-D3H
BaseBoardVersion: x.x
BIOSReleaseDate: 02/23/2016
BIOSVendor: American Megatrends Inc.
BIOSVersion: F10a
SystemFamily: To be filled by O.E.M.
SystemManufacturer: Gigabyte Technology Co., Ltd.
SystemProductName: To be filled by O.E.M.
SystemSKU: To be filled by O.E.M.
SystemVersion: To be filled by O.E.M.
+Registry: SYSTEM\CurrentControlSet\Services\ClipSVC\Parameters
LastBiosKey:
ProcessBiosKey: 1
+ClipHWID:
+SMBIOS:
#text: Encoded info redacted
+LegacyHWID:
#text: Encoded info redacted
--------- Clip Event log data ---------
Application license successfully installed.
Package: Microsoft.Windows.48.X19-98841_8wekyb3d8bbwe
User Id (if available): NULL
License Id: 4aa32f44-c081-5dca-9193-00c16a89ff2b
Associate Id: 4aa32f44-c081-5dca-9193-00c16a89ff2b
Time Created: 01 March 2020 20:50:22
The license with Id 4aa32f44-c081-5dca-9193-00c16a89ff2b has been archived successfully. PFM if available: Microsoft.Windows.48.X19-98841_8wekyb3d8bbwe
Time Created: 01 March 2020 20:50:22
------------ Clip Event log errors ------------
No Digital License errors found!
- - - Updated - - -
Last edited by reddwarf4ever; 16 Mar 2020 at 18:03.
If you installed W10 Pro and skipped entering a key when asked, then it activated from a digital licence stored on the activation servers and linked to the hardware ID of the PC.
... unfortuantely after the image restore I have an unactivated PC again.....would prefer to fix it, if not will start over...
You have shown above that the PC has a digital licence for W10 Pro. What happens if you change the installed key to the generic W10 Pro key?
VK7JG-NPHTM-C97JM-9MPGT-3V66T
Generic Product Keys to Install Windows 10 Editions
Instructions are in the post...cant work out how to run LicensingDiag.ps1
Activation troubleshootingSave the .ps1 file to any folder - right-click and select "Run with Powershell"
I worked out how to create and run LicensingDiag.ps1, which is seen in the log in my previous post,
will try the generic key, but I thought the generic key allowed an install but NOT activation, unless I a, wrong
Did you enter a key when you clean installed Pro? If not, it would have installed using the generic key. That can only activate if there's an existing digital licence for the PC.
What is the current installed key? If it's not the generic key, then installing the generic key should activate from the digital licence just as your clean install did. That the theory, anyway. If it doesn't work you still have your image to restore, so it's worth a try.
Any hardware changes (OEM license)?
Key for key - version for version : Was the Win 10 upgrade the same version as the Win 7 license (Home > Home, Pro > Pro)?
His errors indicate that the files containing the license information are corrupted. Messing with product keys is not going to help.
Yes both PRO . . .
- - - Updated - - -
When I did the clean install, I ticked “don’t have a key” so the digital license on MS servers is valid for my machine.....is there anyone on this forum that knows how I can reset / repair / clean the corrupt activation files.....can’t be impossible, for someone who knows how......will save me so much time, which I do t have being a 24/7 carer.....fingers crossed help is out there