Windows thinks my hardware has changed and is no longer activated

I have a Lenovo Workstation that came pre-installed with Windows 10 Pro for Workstations. I purchased this about 3 months ago, and the first thing I did was install a new SSD and a clean copy of Windows 10 downloaded directly from Microsoft. I was able to get it up and running and successfully activated as Windows 10 Pro for Workstations. (I don't remember if I did this using my embedded UEFI key, or if I used the generic key, but either way, the activation process evidently successfully recognized the embedded entitlement and activated.)

I experienced a system crash last night, and when I rebooted this morning, Windows is suddenly no longer activated. The Activation page in Settings says, It looks like the hardware on this device has changed. … Error code: 0xC0EA000A. Note that the hardware has NOT changed since the initial setup 3 months ago.

Further details:

• (Get-WmiObject -Class SoftwareLicensingService).OA3xOriginalProductkey successfully reports the UEFI embedded product key.
• wmic bios get serialnumber successfully reports the motherboard serial number.
• slmgr.vbs /ipk with the product key reported by OA3xOriginalProductkey results in Error: 0xC004F060 The Software Licensing Service reported that the product key is invalid.
• slmgr.vbs /ipk with the generic product key (DXG7C-N36C4-C4HTG-X4T3X-2YV77) succeeds, but activation is still unsuccessful.
• slmgr.vbs /dlv reports that my Prouduct Key Channel is Retail, regardless of which key I use. This seems wrong. I should be on the OEM channel. Furthermore, it reports my Partial Product Key as 2YV77 (the generic key), also regardless of which key I use.
• slmgr.vbs /ato results in Error: 0xC0EA000A CLiP license device ID does not match the device ID in the bound device license. (SWbemObjectEx) (again, regardless of which key I use)

Does anyone have any ideas of how to fix this – preferably without a full reinstall?

UPDATE: The problem has fixed itself. Roughly 24 hours after the activation problem appeared, the system now activates without a problem. I assume this means there was some problem with Microsoft's activation servers yesterday, which is now fixed.

Paste the following script in an administrative PowerShell:

$key = (Get-WmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey
$instance = (Get-WmiObject -query 'select * from SoftwareLicensingService')
$instance.ClearProductKeyFromRegistry()
$instance.InstallProductKey($key)
$instance.RefreshLicenseStatus()

This is an excerpt from a script I use to automatically activate Windows during deployment.

You said you installed Windows 10 Pro for Workstations. You'll need to make sure your system came with Windows 10 Pro for Workstations. If it didn't you will need to reinstall Windows with the proper version using the generic product key for that version. For instance, Windows 10 Pro is VK7JG-NPHTM-C97JM-9MPGT-3V66T. Typically, if you have the proper installation media, Windows 10 will not ask for a product key during setup. It will pick it up from the UEFI firmware and automatically install and activate the proper version of Windows 10.

There is no downgrade path from Windows 10 Pro for Workstations to Windows 10 Pro according to this article: https://docs.microsoft.com/en-us/windows/deployment/upgrade/windows-10-edition-upgrades.