tried running afuwinx64.exe /aOA3.bin again, but now it says Error: OA key is available, and OA Key is the same as BIN file in the system.
is it possible to use SLPbuilder without oa3 flashing? i don't want to use key for specific edition of windows server. flexible system will be better for me.
SLIC2.5 table from angelkyo is correct, i have check it. SLIC file from aaalekseyyy is corrupted and not to be used. checked on mobo asus prime h370m-plus.
sorry, unfortunately, it already work as remote server, so i can't make dump, but you can use most of bios tool to find it. this information is not undercover.
Why would you want the MSDM table anyway. You don't have a valid Windows 10 OA3 key to inject to it anyway. The only useful thing is the Slic for server/win7 activation...
Trying to add Fuji2.5 to an asus P8P67-m motherboard. Using updated/correct slp25.bin. Running cmd as admin, typing: SLPbuilderX64_3_6.exe /oa20:SLP25.bin /oemid:FUJ /oemtableid: PC /act:9C134SIMF51GYI8HEDJ2F47ZWOA3 The command creates a file, arbitrarily named string.sys 16kb large. In my case 690b33e1-0462-4e84-9bea-c7552b45432a.sys Then the prompt returns stating; Invalid activation - program abort! Retyping the command creates the create ASIO driver file error, I think this is due to the file just created, which is impossible to delete, the command fails. Since it is a headless server, I tried to save time by not reinstalling a graphics card & flash bios normally. As such, I did not clean the existing dell slic 2.4 prior using: SLPbuilderX64_3_6.exe /clearoa30 And due to heedlessness, I haven't enterd bios to check the security settings, I know I run UEFI. Any hints about the error? /ssabb3.