Windows 8 OEM activation with Autounattend.xml

Discussion in 'Windows 8' started by Githlar, Aug 22, 2019.

  1. Githlar

    Githlar MDL Novice

    Jan 30, 2011
    1
    0
    0
    I'm probably a bit late to the party, but I recently set up a solution for the computer/phone repair shop I work for that does network installs of Windows so we can ditch our clunky multiple flash drive setup.

    I use a customized Windows PE with an OS selection script. Then, it mounts the appropriate network share for that installation and provides an Autounattend.xml so that we can skip all the questions with the exception of username and password.

    Usually, when somebody is using an Autounattend.xml, it's for automated deployments for an organization using KMS. In my scenario, since I work on mostly OEM computers for end users I had a major sticking point when attempting to deploy this solution using a Windows 8.1 ISO as provided by Microsoft.

    With Windows 10, I was able to use the generic install keys and get Windows to activate on OEM machines with no issues. This, however, doesn't seem to work with Windows 8.1. If a key is provided via the Autounattend.xml it simply won't attempt OEM activation. But, Setup.exe complains if no key is specified in the Autounattend.xml file and won't install.

    After banging my head against the wall repeatedly and trying the installation many times on a very slow Windows 8 OEM machine, I managed to both provide an Autounattend.xml and get Windows to do OEM activation: provide the <Key> section, but leave it blank. This way Setup.exe doesn't complain about not being able to find the key section and it leaves the automatic OEM activation process intact.

    Just in case this is helpful for anybody else that might find themselves in the same situation.
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    23,010
    32,083
    390
    Win 8/10 use the msdm key from the bios by default, using the multiple editions iso (8/8.1) or consumer iso (win 10).

    You probably can leave the key part out of the xml entirely.

    But when using an oem key, no setupcomplete.cmd can run, providing a generic ei.cfg should solve this.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...