System Locked Pre-installation
System Locked Pre-installation, often abbreviated as SLP, also referred to as OEM Activation, is a procedure used by major OEM computer-manufacturers in order to pre-activate Microsoft Windows before mass distribution.
Details
SLP comes in eight different versions:- SLP
- SLP 2.0
- SLP 2.1
- SLP 2.2
- SLP 2.3
- SLP 2.4
- SLP 2.5
- SLP 3.0
The product key sticker attached to OEM computers, prior to Windows 8, will not activate the copy of windows supplied with the machine. Only the SLP key can do that and the product key is never requested during activation. The purpose of the external sticker with a key is not known with certainty, but it is most likely a way for Microsoft to check that items for retail sale have had a full royalty paid by the OEM.
Version | Windows |
SLP | Windows XP, Windows Server 2003 |
SLP 2.0 | Windows Vista, Windows Server 2008 |
SLP 2.1 | Windows 7, Windows Server 2008 R2 |
SLP 2.2 | Windows Server 2012 |
SLP 2.3 | Windows Server 2012 R2 |
SLP 2.4 | Windows Server 2016 |
SLP 2.5 | Windows Server 2019 |
SLP 3.0 | Windows 8, Windows 8.1, Windows 10 |
SLP installations require a master product key issued by each OEM maker, which is unique to the specific edition of Windows, such as Home, Starter, Home Basic, Home Premium, Professional, Ultimate, Server, etc. This SLP key is different from the product key printed on the Certificate of Authenticity affixed to an OEM assembled PC; COA product key is used in cases when Windows license stored is invalidated for some reason and re-activation is required. On February 28, 2005, Microsoft attempted to reduce software piracy by invalidating COA keys for normal online activation and requiring phone activation, but this does not apply to SLP keys which can still be used for offline activation. If the product key used for activation is lost, then product key finders, readily available on the Internet, can decrypt the key from a local installation, however only SLP keys allow the user to avoid activation upon re-installation.
However, since SLP 2.0 was introduced, hackers have been able to create modified bootloaders based on the bootloader GRUB4DOS; these are capable of emulating a SLP text string, so it appears to be present in the BIOS. This combined with an OEM certificate and OEM product key can instantly activate a Windows Vista/7 installation illegally but also be very hard to notice. This method can also be integrated into a Windows installation disk to activate on initial boot.
Another method consists of modding the BIOS to insert the SLP 2.1-2.5 table, which can be used to replace blacklisted keys, or to add the SLP table to motherboards that do not have it. Some brand-name computers such as Dell, already have the SLP table in their BIOS, which means that using software readily available on the Internet, a pirated retail installation can be converted to OEM, and the appropriate certificate installed into the OS, which results in Windows becoming genuine. Pirates refer to copies of Windows activated in this way as Pirated Genuine Microsoft Software.
With SLP 3.0, OEM SLP keys are no longer used at all. Instead, a tool is used by the OEM to embed a unique key in each computer's BIOS, making consumer versions of Windows 8 and later very difficult to pirate using the SLP insertion technique.
Microsoft released the following generic product keys that users can enter to avoid product activation on any SLP-enabled computer using the corresponding version of Windows XP:
Product Name | Product Key |
Windows XP Professional | MVF4D-W774K-MC4VM-QY6XY-R38TB |
Windows XP Professional | FM634-HJ3QK-6QVTY-RJY4R-XCR9J |
Windows XP Tablet PC Edition | XT67V-GY7FW-GR6FR-WDK2C-8T97J |
Windows Server 2003 R2 Standard Edition x86 | PWBJC-22697-D4CVH-FCJWW-DTF9J |
Windows Server 2003 R2 Standard Edition x64 | XCP6P-7WVXP-F8FQ4-JV6CD-6XV28 |
Windows Server 2003 R2 Enterprise Edition x86 | XHPV3-PTCWJ-7Y94F-Q6BVH-J849J |
Windows Server 2003 R2 Enterprise Edition x64 | WQ3GW-Y8GQW-8VJYB-JYM43-D24C8 |
Windows Server 2003 R2 Datacenter Edition x86 | FXYF6-VTXGX-3JPX9-HJ9K4-6TKTW |
Windows Server 2003 R2 Datacenter Edition x64 | KDX8X-FYW4T-C6D9J-BKM6M-M89TW |
Windows Server 2003 R2 Web Edition x86 | GM8KD-GB7JY-QGQYP-XRV74-RT728 |
Windows 8 | 46V6N-VCBYR-KT9KT-6Y4YF-QGJYH |
Windows 8 Professional | V7C3N-3W6CM-PDKR2-KW8DQ-RJMRD |
Windows 8 N | 7QNT4-HJDDR-T672J-FBFP4-2J8X9 |
Windows 8 Professional N | 4NX4X-C98R3-KBR22-MGBWC-D667X |
Windows 8 Single Language | NH7GX-2BPDT-FDPBD-WD893-RJMQ4 |
Windows 10 Home | 46J3N-RY6B3-BJFDY-VBFT9-V22HG |
Windows 10 Home N | PGGM7-N77TC-KVR98-D82KJ-DGPHV |
Windows 10 Pro | RHGJR-N7FVY-Q3B8F-KBQ6V-46YP4 |
Windows 10 Pro N | RHGJR-N7FVY-Q3B8F-KBQ6V-46YP4 |
Windows 10 SL | GH37Y-TNG7X-PP2TK-CMRMT-D3WV4 |
Windows 10 CHN SL | 68WP7-N2JMW-B676K-WR24Q-9D7YC |
Note that generic keys for versions of Windows later than XP will install the operating system in trial mode, and will request a new key after the trial period is up.