Windows OEM activation

ch.b

New Member
I use NT Lite to customize the Windows image that I deploy in my company. The wim deployment is done with dism and then I push the drivers also with dism.
Until now on a new Dell machine that came with Windows 10 Pro OEM, I pushed the image and drivers from the first boot (without ever starting the Windows 10 pre-installed on the PC). Windows was automatically activated by reading the oem key in the bios I guess.
With the last image I made Windows does not read the OEM key anymore.
If I use the previous image Windows is activated (by reading the oem key in the bios). I can then deploy the last image and Windows is activated thanks to the hardware signature known by the Microsoft activation servers.
I specify that the parameters of the two images made with NT Lite (the one that works and the one that doesn't) are almost identical. For the second image I used a recent ISO and included the latest Windows update.
My post is about the inability of the new version of my image to be activated from the OEM key in the bios.
Does anyone have any idea what is causing this problem?
 
I ran into this problem. I removed all keys from the unattended.xml and that fixed it. Once the machine went online it would activate.
 
Until now on a new Dell machine that came with Windows 10 Pro OEM, I pushed the image and drivers from the first boot (without ever starting the Windows 10 pre-installed on the PC). Windows was automatically activated by reading the oem key in the bios I guess.
With the last image I made Windows does not read the OEM key anymore.

Does anyone have any idea what is causing this problem?
Upload the preset and will take a look.

Have you used the compatibility (toolbar button in Components page) option called Windows Activation (KMS)?
 
I confirm that the Windows Activation KMS compatibility is checked.
Here is the autounattended.xml
Thanks for your help
 

Attachments

  • autounattend.xml
    3.5 KB
Last edited:
Back
Top