windows no longer activated after 1809 update

I have removed the VM and in the process of restoring from backup prior to the update

Did the Host environment change or main drivers change enough to make the Windows 10 machine think it was in a new place? That is the only reason I have come across for Windows to become deactivated.  I do not know of any other reason (assuming I am very sure that the Keys are good) .

nothing else changed
finished restoring and is working fine again on 1803
very strange

I am running V1809 on the my consulting Laptop, Home Desktop, and two Client Desktop machines with no issues.

There have been a half dozen cumulative updates since the October 1 introduction and I have done all of these.

very strange    <-- I agree. I will keep looking. I do not see anything in V1809 that should cause this.

https://answers.microsoft.com/en-us/windows/forum/all/windows-suddenly-deactivated/fe9a4ecf-2e2a-491d-a43e-b010c316d1c4

When you upgraded this machine to V1809, did you run all the cumulative updates?  Can you do this if not activated?

Shot in the dark:   Windows 10 Store requires UAC to be ON Second from the Top (Most Secure). Store will not work properly with low UAC Security. But I have not heard of Store issues deactivating Windows.  Worth considering perhaps.

When you upgraded this machine to V1809, did you run all the cumulative updates?

didn't do any updates.  blew away the vm since it was causing issues with my vdi environment not being able to activate
thread doesn't apply anyway since it refers to a digital license which doesn't apply here

Windows 10 Store requires UAC to be ON Second from the Top (Most Secure).

it is already set there

Hmmm.  Try again if you will and do all the cumulative updates and test.  Thanks

from an administrative cmd prompt.
slmgr -ipk <see chart below>
slmgr -ato
Semi-Annual Windows 10 KMS keys

Windows 10 Pro	W269N-WFGWX-YVC9B-4J6C9-T83GX
Windows 10 Pro N	MH37W-N47XK-V7XM9-C7227-GCQG9
Windows 10 Pro Workstations	NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J
Windows 10 Pro Workstations N	9FNHH-K3HBT-3W4TD-6383H-6XYWF
Windows 10 Pro Education	6TP4R-GNPTD-KYYHQ-7B7DP-J447Y
Windows 10 Pro Education N	YVWGF-BXNMC-HTQYQ-CPQ99-66QFC
Windows 10 Education	NW6C2-QMPVW-D7KKK-3GKT6-VCFB2
Windows 10 Education N	2WH4N-8QGBV-H22JP-CT43Q-MDWWJ
Windows 10 Enterprise	NPPR9-FWDCX-D2C8J-H872K-2YT43
Windows 10 Enterprise N	DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4
Windows 10 Enterprise G	YYVX9-NTFWV-6MDM3-9PT4T-4M68B
Windows 10 Enterprise G N	44RPN-FTY23-9VTTB-MP9BX-T84FV

Select allOpen in new window

So, in effect this issue can be understood as : upgrading a Win10 KMS Host (configured with a KMS Host Key) to v 1809, that is Activating client machines on the network causes the KMS Host key to be replaced, thereby deactivating the Host and potentially hundreds of other client machines on the network (if they were being activated by it) .... is that correct ??

not if you used the image from vlsc.. By the way all KMS clients have to renew their activation every 6 months i.e. os and office

peeterb....yes, the vdi clients (very small horizon install) failed during the customization process because composer said it couldn't get a license.  this was after reverting back to 1803 (kms host did retain the product key though and shows activated).  manual activation of the vdi guest said it failed because the required client amount (25) hadn't been reached.  strange because it was working before the update though restoring from a good backup caused it to lose that part.  i can fix that piece easily enough to get the 25 minimum again to get vdi working.

david...yes every 6 months though i just built this machine in early november and got kms working shortly after so it hasn't been 2 months since i started testing windows 10 vdi pool.  from your table above, that was the default kms key it reverted to after the 1809 update (recognize the last part of the key it showed for pro workstation)

did the update again.  this time using 1809 volume media instead of windows update - same thing; no longer activated and lost product key.
reverted the snapshot and is ok.  no idea why it is doing this

That certainly is strange.  I have done a couple of 1803 -> 1809 updates since this thread began (and some before as I noted) and no loss of activation. I can only say that I will keep looking.