Yesterday I got interesting problem: 1. Install fresh Fedora 25 2. patch SeaBIOS 1.9.3 with Dell SLIC 2.4 3. Install Win2016 Srv Std in VM 4. run SLIC_ToolKit_v3.2 on Win2016 WTF?! "Sorry, your BIOS has no SLIC at all" I checked patches, then recompile seabios from scratch - no success. Ok... 1. Start my old VM (Win2012R2 Std) on same machine with same patched SeaBIOS 2. run SLIC_ToolKit_v3.2 on Win2012r2 3. Got "You BIOS has correct Dell SLIC 2.4" I hope, that problem with incorrect BIOS dumping in SLIC_ToolKit under Win2016. Or not? P.S. Can somebody test SLIC_ToolKit with Win2016 on real hardware with patched BIOS?
Yes. Latest collection of SLICs are there ("h_t_t_p_s://forums.mydigitallife.net/threads/5952-Win-7-amp-Server-08-R2-SLIC-2-1-Bin-Collection?p=514521&viewfull=1#post514521"). HP, Dell and somebody else has SLIC 2.4 + certificates.
Sorry for disinformation. HP and other possible 2.4 SLIC vendors really has only 2.3 SLICs. I definitely need more sleep.
Please, try to test SLIC_ToolKit_V3.2 on your system. Will toolkit properly detect SLIC in your BIOS or not?
Same problem KCB can detect Dell SLIC 2.4 on Win2012 R2 Std and can`t on Win2016Std. If Win 2016 read SLIC tables and then block access to SLIC for other software - it is no real problem for me. If SLIC_ToolKit and KCB can read SLIC tables on real hardware with Win2016 then something wrong with my patched BIOS/virtual machine.
Something has to be wrong with your patched BIOS/virtual machine...in my test on HYPER-V SLIC_ToolKit shows SLIC 2.4 just fine
Not something I've tried, but are SLIC versions backwards-compatible? My Dell 2950's are SLIC2.3 modded for 2012 R2, if I update to SLIC2.4 .... do the SLIC2.3 certs/keys still make it activated? EDIT: Updated my 2950 from SLIC 2.3 to SLIC 2.4 Windows Server 2012 R2 with Dell key remained activated.
I've removed the fake key. It might appear to work, but these fake keys are easily blocked since they don't contain valid data. If other fake keys are posted here then the thread will be closed.