@sebastian-roth yes, the command only calls the product key. I activate it via the “change key” option in the settings. Enters the called key.
as i wrote “After preparing the image from devices (Lenovo E15 Gen 2, Vostro 3681, Optiplex 3080) and uploading the images to other devices, the license key is copied from the first device from which I recorded the image”.
@sebastian-roth wmic path softwarelicensingservice get OA3xOriginalProductKey
@sebastian-roth
If FOG calls the commands from slmgr.vbs, maybe the latest build changes something in the way of activating the keys? Can you verify it somehow?
I can activate a key using a command to call the key and enter it. The point is that windows “stopped doing it by itself” after uploading the image.
December build works fine.
I could enter manually the keys assigned to the device, but there are many of them so it is very difficult.
The question is: on what level is the problem? fog or windows? 
Regards.
Hello,
I have fog version 1.5.9, updated kernel to the latest available version, centOS.
I noticed a problem with the Windows 10 license key. After preparing the image from devices (Lenovo E15 Gen 2, Vostro 3681, Optiplex 3080) and uploading the images to other devices, the license key is copied from the first device from which I recorded the image. Until now, Windows activated with the key assigned to a given device, automatically detecting the key in the BIOS.
I don’t know if it’s the fault of the FOG itself or the Windows update. Has anyone reported any problems with the latest build of Windows and uploading images from FOG?
I will add that computers / laptops are brand new. They have a pre-installed system and new license keys provided by laptop / computer manufacturers.
I have tried various combinations with Slmgr but to no avail. Sysprep does not solve the problem either.
Image: Windows 10 Pro, x64, 20H2 latest build.