[TOOL] EzWindSLIC: Easily activate Windows 7/Vista/Server 2008-2022 on UEFI-GPT

Yep, that's not good.

You can try (F) > On



Then (I) Install.
This will install WindSLIC even if a SLIC/partial SLIC is reported.
I suspect that your invalid SLIC will be read first but that remains to verify after you installed WindSLIC, rebooted and check which SLIC is reported back.
If it doesn't work then (U) Uninstall and you are back to where you started.

Then you could ask @Serg008 for a possible BIOS mod.

 

Forceful mode can successfully install the certificate, but activation still failed. Actually it's only a simple report，because that old Lenovo IdeaPad can be activated (UEFI) via other methods.

 

It is possible to test (and use) individual SLIC's cutting out custom ROM in VMware.
(i tried with VirtualBOX as well but EFI support isn't on level with what VMware can offer)



Open *.vmx with a txt editor:

Code:

firmware = "efi"
#efi64.filename = "EFI64.ROM.mod2.rom"
acpi.addtable.filename = "LENOVOCB-01-nonvalid_slic.bin"

1. sets firmware to EFI (before installing OS)
2. with (#) in front - deactivate parameter (saving time adding parameters in test environment)
3. SLIC added to BIOS

Practical use:
A valid SLIC in Bios can be used to test further how a secondary SLIC added by a bootloader acts.
As it is atm, SLIC read from BIOS takes precedence if WindSLIC is installed.
Adding (#) (or delete) line 3. SLIC and WindSLIC will take over, activating if OS is on lewel or lower than SLIC presented.

Added the non valid SLIC from @asasadad_1 for further testing, next is of course to see if we can change order when 2 SLIC's are present.

 

You need to login to view this posts content.

 

@Exe Csrss
Filling SLIC with FF - absolute minimum string to make it a readable but non valid SLIC, starting from offset 0x00 > 0x07 (8 byte):

Code:

53 4C 49 43 76 01 00 00

Change first byte and WindSLIC's emulated SLIC is read and i'm activated:

Code:

00 4C 49 43 76 01 00 00

And seems to be absolute minimum to be allowed to boot with this SLIC in Bios:

Code:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00000000   FF FF FF FF 76 01 00 00  FF FF FF FF FF FF FF FF 

And SLIC must be exact 374 bytes in lenght (0x176) to be "bootable".

 

1. @Exe Csrss Is it possible to change colour to white on Windows 7 (Ultimate x64) ?

Purple colour doesn't look good.

 

Yes On windows 10 colour is white. But not sure why on my Windows 7 Ultimate x64 its Purple.

When I run KMS_VL_All or MAS the colour is proper (White) but with EzWindSLIC I'm not sure what's wrong.

 

fwiw: it's white when I run it on 7 Enterprise. (although I'm not sure why it should ever be used on Enterprise )

 

@Exe Csrss I have compared value of color with KMS_VL_ALL and changed it from 0f - > 07

Now with value 07 it is showing proper white color text.

With value 0f the color is purple.

 

You were right. There were some issues with colour settings. I set them all to 238 value and it's fixed now.

Usually I don't play with cmd colours. Not sure how it were changed.Thanks.

 

@Krinal - It is weird. I just did a fresh install of 7 Ultimate in VMware (UEFI mode). It's white there also.

 

I just edited my previous reply.
Thanks for testing.
Somehow my cmd colour settings were changed. Now it's fixed thanks to @Exe Csrss .

By the way, I just learned today that cmd has Properties option too.

 

Hello, i am trying to activate windows 7 ultimate on dell optiplex 7010 running latest bios. I am also using windows 7 ultimate iso updated by latest simplix update pack. My system is UEFI with CSM, when I use the tool to activate, it works as intended with any profile whatsoever, except, when I reboot, the activation does not hold and it gives me activate windows within 30 days. What am I doing wrong? Previously I was using windows 10 Pro activated by HWID on the same machine and it was activated successfully.
Am I doing something wrong? Does the system needs to be pure efi for this to work? Please Help

 

You need to login to view this posts content.