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

i think i’ve had this happen on vmware 15 before with the aio script (windows 7 is my main os/daily driver for now)
have you tried the normal traditional script?
i only have mbr disk running windows 7 with daz loader installed so i can’t test it on real hw to see if there’s issue.
if there’s another report of certificate installation failure, there’s a serious problem in the aio script somewhere @Dir3ctr1x

 

You need to login to view this posts content.

 

first,
i doubt 15 and 16 make a difference for 7, only difference is 15 is the last vmware pro for 7 host. (i could upgrade OS but i’m sticking with 7 for a while) this is probably why i gave detail on version

anyways, glad traditional script is working for you (and probably for everyone else too)
@Dir3ctr1x fix your aio script pls asap; ur certificate extraction method is broken

 

You need to login to view this posts content.

 

Can't get it to work on Server 2022. Installs just fine, but Windows still says it's not activated.

 

@Pieter de Zwart

Post some screenshot's/log's so we can have a closer look.

 

This might be a case of RSDP not being in ROM. Here is the passage from the Windows Loader Read me.txt (generally also applies to other SLIC solutions):

 

Hello! I have the same problem as Pieter. When I run EZWindSLIC 3.62f, no matter if classic or AIO, all installs fine but no activation.When I use the script to view SLIC table it says "no SLIC found". I tried with ASUS, Dell, HP but no good.Forceful mode ON changed nothing. My system is Asus X552CL notebook with Windows 7 Ultimate x64, EFI. Please help.Where can I find the log file?

 

You need to login to view this posts content.

 

looks like your system is still booting from the original bootmgfw.efi efi entry, try going jnto the uefi bios and changing the boot order to boot from windslic.efi or another “windows boot manager” instance
try different ones until you’re activated
not sure if what i highlighted was important or it’s just where boot manager resides and nothing else

 

Unfortunately in BIOS is a really strange situation. I have a SSD with Win 10 in HDD bay (that at the moment is removed) and a HDD with Win 7 x64 in DVD bay with adapter.If the SSD with Win 10 is removed, the BIOS shows nothing at "Boot option priorities", when I start the system it goes straight to BIOS, and I have to check every time "Save settings and exit" to be able to start Win 7. The log I got is with only the HDD in the DVD bay.
If I put both the HDDs, in BIOS I have only 2 options, 1 boot manager from the SSD and one boot manager from the HDD.No other options.
Can't I just overwrite the original bootmgfw.efi with your patched version? I can fix the boot if necessary by restoring the UEFI partition from a backup image.
LE: At Boot Override there is no entry. When choosing "Launch EFI Shell from filesystem device" it says "not found". With both the HDDs in place I also have to 2 entries at Boot override, one for each HDD.
About a year ago I had only 1 HDD in its slot, with Win 7 x64 MBR, working perfectly. For work I had to move to Win 10 x64, turn the HDD to GPT, and messed up my notebook, it was very slow on 4500 rpm HDD.Now I got the SSD for Win 10 and tried to return to Win 7 for home tasks and gaming (slow HDD in DVD bay, but fast enough for Win 7). Not an option to convert the HDD to MBR, I have a 450GB partition full of data that I don't want to move elsewhere, and I want to keep the HDD as GPT for Win 10 fallback if the SSD malfunctions.

 

No, WindSLIC.efi loads bootmgfw.efi so overwriting it would be useless.

 

I found this https://forums.mydigitallife.net/threads/windslic-uefi-slic-injector.29740/ and it says

Just renamed WindSLIC.efi to bootmgfw.efi and copied everything from WindSLIC folder to "EFI\Microsoft\Boot" overwriting the original "bootmgfw.efi. Now I have an activated copy. Might have worked also with

but I didn't try. I still like the old ways.

 

need advice,

I have an old ECS motherboard GF7100PVT-M3. No SLIC table. hence my trial of Windows 7 Pro activation failed.
It was running XP. Any chance I can try next? I prefer Win7 if possible.

Thanks,

Serg008 is NOT here. BIOS mod would be last I can ask

 

if you're using mbr partition table, then have you used daz loader?
if that fails have you tried kms_vl_all? if that fails then you've got bad slic, and bios mod would be only option

 

I am unlucky.
I have tried that one. Win7Loader by daz also not working. according to Tito both exactly act same
[GUIDE] Activate Windows 7 on PCs with UEFI | My Digital Life Forums

I will try the 3rd one you mentioned. kms_vl_all

Thank you very much,