I seen your edited post on other page and I have an idea....I ran on my machine and it shows key where you showed the slic which doesn't show key...you need to show msdm....run this cmd for rw everything and let me know if it works in win pe...I really want to know this. lol I would show you a pic but my key info is in there and I am too lazy to edit it out. lol It did create file on c:\ with key data which can now be easily used with findstr in cmd script. I am going to add this to my own modded searchengines oem project so I can get rid of the oem-sync and make the script do it with the help of rw everything. This way I can update when new OS's come out. lol I am a happy camper about this (thanks for the useful info) but I am curious about the win pe issue...not everything works in that environment. Searchengine isn't here anymore and he didn't share source of oem-sync so looking into alternatives.
No real need for I am going to get rid of the oem-sync in time. This is off subject for this thread. Please post any info regarding the oem project by searchengine on that thread, thank you.
I got what I need for the modded oem project from searchengine. Now I don't need the oem-sync anymore. Will give credits to you when I am done with compiling it. Thanks again for your help. Two brains are better then one. That really made it easy as far as scripting. getwin8key virus results: Virus total results are 0/54 for the exe Virus total results are 0/52 for the dll Great news!
Re: Win 8.x • Win 7 • Vista - 'Multi-OEM' ISO Project OEM-Query.exe runs in Win8SE, and displays full summary, including OEM-DM key and SLIC info etc.
Off subject of this thread but... Some of WMIC is disabled during oobe part of install. That's why I needed to use another method to extract key which we already solved. skolar is picking apart at the oem-sync for no reason for it will not be used anymore (no source code to update that exe). Also the tool that searchengine created will be updated by myself as well so I can update when needed. It will all be open source so if I am busy or bored with it someone else can edit to update it. This just make more since because its all about sharing. Lets keep the oem project in its own thread. The only reason I brought it up was because we were both looking for solution to key extraction from bios but for different uses. Back on to the kms topic.
To me, no off topic. Because I am thinking of WinPE AIO (BIOS/UEFI/x86/AMD64 and WIM Nin1) for my own KMS solution plus OEM isolation. Everybody knows OA3 key in MSDM table. And, of course, Windows knows it too. Why bother? I intend to detect the oem key before applying the image and ask the user what he's gonna do about it. To be frank, I have manual mode in place. But I won't post it, for I am not satisfied with it.
True on all accounts. I just don't want no mod or admin to get mad over it, that's all. It will be about three weeks before I compile the new oem project for I am waiting to see if anyone posts any new oem images plus I still need to update keys, plus real life so it will take me a bit to do all that and test as well. I'm in no hurry nor do I wish to be for that is when mistakes happen. lol