by admin
Slic Toolkit Windows 10
In general, activating Windows 10 with Microsoft Toolkit is an easier, smoother process. The process is mentioned below for your reference. First, you should run Microsoft Toolkit.exe with administrator privileges. From the bottom-right corner of the window, you should select the option that appears with the “ Windows ” icon. Various SLIC 2.1 BIN has been retrieved from various notebook computer that shipped with new SLIC 2.1 in BIOS to support the free Windows 7 Upgrade Option from Windows Vista. Samsung usb driver for mac. Download the same or newer BIOS file: Go to HP Desktop PCs Recovering the BIOS, and then follow the steps to create a BIOS recovery USB key on another computer.Insert the.
SLIC table in VirtualBox
Having the need to run a few Windows applications in my Lenovo Carbon X1 - but unwillingly to dual-boot or in other ways run Windows natively, I decided to give VirtualBox a go.Slic Toolkit Windows 10 Iso
My laptop came with Windows pre-installed, and is using the SLIC table as identification for activation of Windows.
- Host OS: Ubuntu (Usually following the LTS releases)
- Guest OS: Windows 10.
Slic 2.5
Getting SLIC information
In any recent Linux distribution, it is fairly easy to retrieve such information from the DMI tables.
Getting product key from MSDM ACPI table
The SLIC table is used for identification when activation Windows in combination with a a product-key and a SLIC certificate. As with my Lenovo laptop, this product-key was embedded in the MSDM table - and can easily be extracted under Linux.
# Get product key from MSDM table ###########################
productKey=$(sudo hexdump -s 56 -e '/29 '%sn' /sys/firmware/acpi/tables/MSDM)
[ -z '$productKey' ] && errorHandle 'Error fetching product key from acpi table MSDM'
$zenity --info --height=70 --width=400 --text 'Your product key is: $productKey'
############################################################
Setting SLIC information
In VirtualBox, this can be done using 'vboxmanage setextradata' to configure 'VBoxInternal/Devices/pcbios/0/Config'
Activating Windows
To use the SLIC and productkey table for activation, we need a SLIC certificate. If you already have Windows installed, there is ways to retrieve the same information - including the certificate using a SLIC_ToolKit.
As alternative, dumps of the certificates can be found for most hardware manufactures.
Start cmd.exe as administrator, and issue
- slmgr -ilc <path xrn.ms file>
- slmgr -ipk <your product key>
Putting it all together
A simple bash script should do the trick - and can easily be shared with people in the same situation as me.
The script setslic.sh can be downloaded from my github repository.
The basic idea of the script is modify the required 'pcibios' for a selected VM, with the acquired information from dmidecode.
The steps are:
- Configure a VM in VirtualBox, and attach your Windows ISO
- Run this script to modify pcibios on the VM (The script will print your productkey - write it down)
- Start the VM, and install Windows (Choose 'I do not have product key' when installing)
- When Windows is loaded, install the certificate and activate using the productkey
SLIC table in VirtualBox
Having the need to run a few Windows applications in my Lenovo Carbon X1 - but unwillingly to dual-boot or in other ways run Windows natively, I decided to give VirtualBox a go.My laptop came with Windows pre-installed, and is using the SLIC table as identification for activation of Windows.
- Host OS: Ubuntu (Usually following the LTS releases)
- Guest OS: Windows 10.
Getting SLIC information
In any recent Linux distribution, it is fairly easy to retrieve such information from the DMI tables.
Getting product key from MSDM ACPI table
The SLIC table is used for identification when activation Windows in combination with a a product-key and a SLIC certificate. As with my Lenovo laptop, this product-key was embedded in the MSDM table - and can easily be extracted under Linux.
# Get product key from MSDM table ###########################
productKey=$(sudo hexdump -s 56 -e '/29 '%sn' /sys/firmware/acpi/tables/MSDM)
[ -z '$productKey' ] && errorHandle 'Error fetching product key from acpi table MSDM'
$zenity --info --height=70 --width=400 --text 'Your product key is: $productKey'
############################################################
Setting SLIC information
In VirtualBox, this can be done using 'vboxmanage setextradata' to configure 'VBoxInternal/Devices/pcbios/0/Config'
Activating Windows
To use the SLIC and productkey table for activation, we need a SLIC certificate. If you already have Windows installed, there is ways to retrieve the same information - including the certificate using a SLIC_ToolKit.
As alternative, dumps of the certificates can be found for most hardware manufactures.
Start cmd.exe as administrator, and issue
- slmgr -ilc <path xrn.ms file>
- slmgr -ipk <your product key>
Putting it all together
A simple bash script should do the trick - and can easily be shared with people in the same situation as me.
The script setslic.sh can be downloaded from my github repository.
The basic idea of the script is modify the required 'pcibios' for a selected VM, with the acquired information from dmidecode.
The steps are:
- Configure a VM in VirtualBox, and attach your Windows ISO
- Run this script to modify pcibios on the VM (The script will print your productkey - write it down)
- Start the VM, and install Windows (Choose 'I do not have product key' when installing)
- When Windows is loaded, install the certificate and activate using the productkey