Windows Activation of Re-Deployed Images – OEM_SLP keys – System Builder Stuff

So you want to

  1. install Windows
  2. configure it how you want, including adding users, installing and configuring software
  3. image that system C:\ drive
  4. then restore or redeploy that image on another PC.

Definition Helps:

OEM_SLP keys

OEM = Original Equipment Manufacturer, eg Dell, HP

SLP = System Locked Pre-installation


user=Darin Smith MS

Hi dgranata,

Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

A) OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer’s computer hardware. So when Windows was installed using the OEM SLP key (at the factory) windows looks at the motherboard and sees the special instructions and Self-Activates. (that’s why you did not need to Activate your computer after you brought it home)

B) COA SLP: This is the Product key that you see on the sticker on the side (or bottom) of your computer. It is a valid product key, but should only be used in limited situations (sush as if the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone. (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer)

The COA SLP key is a backup to the OEM SLP key. The only difference if you change to the COA SLP key is that you would be required to Activate by Phone.

Thank you,
Darin MS

Quick answers:


use generalize

that puts the image in “OOBE” (Out Of Box Experience) mode.

So it loads drivers at start. And maybe otherwise diassociates from particular hardware.

But did not for me fix the OEM_SLP


user: Cursed Lemon

What you can do is a little trick I learned.

If you didn’t know, Windows has a tool called “SysPrep” which dissociates the Windows installation with the hardware it was installed on. You can then transfer this hard drive to a brand new machine, and Windows boots up as if it’s being used for the first time. It will prompt you to create a new user account, but you can log into the original/old user account you already have and delete it later.

What I’ve done is do a brand new, fresh Windows installation and installed all of the programs I like to use on it, getting everything configured the way I like. Then I use SysPrep to put the computer into “OOBE” (Out Of Box Experience) mode, which performs the aforementioned driver stripping.

After that, I pull that hard drive out of the computer and put it in an external HDD enclosure or carriage hooked up to another computer. On that computer, I use Macrium Reflect to create an image file of that SysPrep’d drive, and store that image file somewhere safe.

So now, whenever I need to install a fully-configured Windows 7 to another computer entirely, I just take the hard drive that’s going to be in that computer and use Macrium to restore that image to the hard drive, at which point I will use totally-not-unscrupulous-and-illegal methods (coughRemovecoughWATcough) to bypass the authentication software.

remove *cough* wat *cough* (did not try; did not need; certificats below worked)

System Preparation Tool (Sysprep) in Microsoft Windows 10/8/7

url =

The big one:

talks about loading new certificates for the manufacturer using slimgr

Windows 7 OEM – Applying OEM System Locked Preinstallation Activation
url =

see below

This one talks about windows 8 BIOS keys :

recreate the licensing store

There’s still a problem somewhere – you have an error I’ve only ever seen once before.

Script execution time was exceeded on script “C:\Windows\system32\slmgr.vbs”.

I suspect that there’s some minor corruption preventing proper function….

Please first try recreating the Licensing Store.
Recreate the Licensing Store
1) Click Start button.
2) Type: CMD.exe into the ‘Search programs and files’ field
3) Right-Click on CMD.exe and select Run as Administrator
4a) Type: sc query sppsvc to see if it’s on (it probably is)
4) Type: net stop sppsvc (It may ask you if you are sure, select yes)
Note: the Software Protection service may not be running, this is ok.
5) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
6) Type: rename tokens.dat tokens.bak
7) Type: cd %windir%\system32 (no need, really)
8) Type: net start sppsvc
9) Type: slui.exe software licensing UI
10) After a couple of seconds Windows Activation dialog will appear. You may be asked to re-activate and/or re-enter your product key or Activation may occur automatically.

If you are asked for your Key, use the one on the COA sticker on the machine’s case

Reboot and Post back with a new MGADiag report

The big one (quotd):

talks about loading new certificates for the manufacturer using slimgr

Windows 7 OEM – Applying OEM System Locked Preinstallation Activation
url =


Windows 7 OEM – Applying OEM System Locked Preinstallation Activation

10 Votes

Make a Donation Button

Microsoft Code of Authencity – Windows XP OEM, Windows Vista OEM and Windows 7 OEM

For systems shipped with Windows XP, Windows Vista and Windows 7 a Code of Authenticity (COA) with a 25 digit product key was shipped affixed to the system.

Windows 7 COA

There was a change in print quality of the COA when Windows Vista was released which made the COA prone to fading. As a consequence for most Windows 7 systems the COA was Placed in the Battery Compartments of Laptops to Reduce the Problem of Fading.

Laptop COA
What is Original Equipment Manufacturer System Locked Preinstallation Activation?

Examples of Microsoft’s Major Partner Original Equipment Manufacturer (OEMs) are:


Microsoft Major Partner OEMs preinstalled Windows 7 on millions of machines. In order to save production time these Major OEM licenses utilised a BIOS based activation mechanism and as a consequence the key on the COA is typically not used for Windows Installation. The system BIOS of Windows 7 OEM will contain a SLIC of version 2.1.

Microsoft’s Minor OEMs are small scale OEMs that sell a low volume of machines. These licenses known as Commercial OEMs do not apply OEM System Locked Preinstallation. Motherboards with Commercial OEM Licenses will not contain a SLIC.

The conventional activation mechanism (using the key on the COA) would have required the OEM to input a unique 25 digit product key and call Microsoft for every single machine they made… For Windows 7 OEM installation the 25 Digit Product Key on the COA is hence typically unused. Instead OEM System Locked Preinstallation is applied:

Instead of using this unique 25 digit product key on the COA for installation an OEM System Locked Preinstallation (SLP) Key is input by Dell Branded Reinstallation Media.
In essence the System Locked Preinstallation (SLP) Key must match up to the System License Internal Code (SLIC) incorporated in the systems BIOS for System Locked Preinstallation (which is automatic offline Product Activation) to be applied.
This means you can still use OEM SLP to activate Windows 7 OEM even if your COA has Faded.
Windows 7 Pro OEM SLP can also be used for Downgrade Rights from Windows 10 Pro or Windows 8.1 Pro.

SLIC Version:

Version 2.1 – Eligible for Windows 7 OEM System Locked Preinstallation
Version 2.0 – Eligible for Windows Vista OEM System Locked Preinstallation
Version 1.0 – Eligible for Windows XP OEM System Locked Preinstallation

This means that one may Clean Install Windows 7 OEM on systems that have faded COAs:

It also means one may exhibit Downgrade Rights to Windows 7 Pro without a Windows 7 Pro Product Key:

win10Pro Win8Pro

A SLIC version of 2.1 is required for Windows 7 OEM SLP. To determine your SLIC launch RW-Everything and select Access → ACPI Tables:


Select the SLIC Tab:


Scroll down until you get the SLIC Marker Structure. You are interested in 2 fields:

SLIC Version

In this case the OEM is Dell and the SLIC Version is 2.1.

The example I used was from a Dell Latitude 7350 shipped with Windows 8.1 Pro. It doesn’t have a Windows 7 Pro COA but is eligible to run Windows 7 Pro using OEM Downgrade Rights.
An Inspiron 7347 shipped with Windows 8.1 (Home) and hence doesn’t have any OEM downgrade rights. It has no SLIC tab and hence Windows 7 cannot be activated by use of OEM SLP.

Systems sold with Windows Vista OEM in the period of 6 months before the release of Windows 7 may have an SMBIOS of 2.5 with an original SLIC version of 2.0. The latest BIOS update won’t change the SMBIOS which will remain at 2.5 however it may update the SLIC version to 2.1.

The OptiPlex 760 for example has a SLIC version of 2.1 with its latest BIOS Update so the Free Upgrade to Windows 7 may be taken (documented in detail here) but the OptiPlex 755 was sold just a wee bit earlier and retains a SLIC version of 2.0 even with its latest BIOS Update.
I have listed the latest BIOS Update for systems with an SMBIOS of 2.5 here (please comment to let me know what SLIC version your system has with its latest BIOS update as it may help others).

Note RWEverything doesn’t state the Edition of Windows 7 to be installed. In testing the SLIC seems not to be Edition specific. To be licensed correctly you should match the Edition on the Windows Vista/Windows 7 COA.
System Locked Preinstallation Key and Product ID List

One can check the Product ID and Activation status in system (go to Start, Right Click Computer and Select Properties). If it contains OEM-899 (Windows 7) or OEM-733 (Windows Vista) then it is activated using OEM-SLP:


The SLP keys and Product IDs are generic every single Dell system shipped with Windows 7 Pro OEM will have the Product Key 00371-OEM-8992671-00524. The SLP key associated with this is 32KD2-K9CTF-M3DJT-4J3WC-733WD. This Product Key can only be used for OEM SLP and cannot be used for conventional activation.

If Windows 7 has been activated by the 25 Digit Product Key on the COA the Product ID will contain OEM but not 899. One should verify whether a SLIC exists in the system BIOS or not.
Installation Media

Major OEM Installation Media e.g. a Dell Windows 7 Reinstallation DVD will automatically Apply OEM SLP Activation without asking for a Product Key.

Windows 7 Retail Installation Media and Windows 7 Commercial (Minor) OEM Installation Media won’t automatically apply OEM SLP Activation and instead ask for a Product Key.

Unfortunately Major OEM Installation Media was not Downloadable while Windows 7 Retail Installation Media and Windows 7 Commercial OEM Installation is Made Readily Available to Download.

OEM customers are hence forced to Download the Retail Installation Media or Commercial OEM Installation Media, Install Windows 7 by Skipping Input of their Product Key and Manually Apply OEM SLP.

If the EI.cfg file is deleted from the sources folder of your Bootable USB you will get the option to install all the Editions of Windows 7 present on the .iso if not you will automatically install the Edition the EI.cfg file is locked to:


Accept the license agreement:


Uncheck “Automatically Activate when I’m online”. Select skip:


This will install Windows 7 without a Product Key allowing a 30 day trial.

One can check the Product ID and Activation status in system (go to Start, Right Click Computer and Select Properties). They should see that Windows 7 is not activated.

OEM Cert Collection

To activate using OEM SLP download the OEM cert collection:


Select save:


Right click to Extract the Folder:


Select Extract:


Open the extracted folder:


Select your OEM:


Select your Edition of Windows 7:


Copy the OEM folder:


Ensure the OEM folder is placed directly on your C:\ Drive:


Right click the slp.bat and select Run as Administrator: 13

Accept the UAC prompt:


Press OK:


Press Ok again:


Press any key to continue (this will close the command prompt):


One can check the Product ID and Activation status in system (go to Start, Right Click Computer and Select Properties). Windows 7 should be activated using OEM SLP:

WAT Windows Activation Techonology Checker Windows Update KB971033

research about how it works what it does. It searches for exploits:

how to manually uninstall: