How should it be translated ... ? It reads '1' from WMIC then sets the values i want . Win 8/8.1 is either '5' = Notification or '1' = Licensed, nothing else, unless you /upk and get '0'. Else several tools here wouldn't support most languages ....!
For instance my JATD is tested working with Vista,7/8/8.1/10, so where should there be any limitations in WMIC, i would have heard of.
I am not here to argue but will address this later. For now I cant even get logging to write to file in win 8.x and win 10. grrrr It only writes on a few items and that is it. It is really hard to make a script that works on all OS's. Ppl have no idea. lol I got logging working perfect for vista/win7 but newer OS's is giving me a headache. lol Its hit and miss for some odd reason. Actually slave I have read about here on this site about wmic not working with some commands in win 8.0. This is where I got the info from and have experienced this myself. Now there might be updated iso's that now allow it but I am working on the logging for now. I will get back to this later. I am getting sidetracked. lol
Ok found the problem after bitznpcz posted key .bin and certificate Code: ================================================== Filename : TOSCPLTOSCPL00_V2.1.bin MD5 : fc5976858269776aaa2f89d111aa9fe9 SHA1 : fd270f866a415cf58591a6d7ba30b3edb569e400 Modified Time : 19/07/2015 12:59:22 Created Time : 19/07/2015 18:15:10 File Size : 374 File Version : Product Version : Identical : Extension : bin File Attributes : A ================================================== ================================================== Filename : TOSCPL_V2.1_Cert.xrm-ms MD5 : 74f8df43f4d197778bad6f685fed37d1 SHA1 : 3e252a65627edb4c68e3bb4e48ad5b54d8fe9853 Modified Time : 19/07/2015 13:00:12 Created Time : 19/07/2015 18:15:10 File Size : 2,731 File Version : Product Version : Identical : 1 Extension : xrm-ms File Attributes : A ================================================== ================================================== Filename : TOSCPL[TOSCPL00]2.1-39C53B76.BIN MD5 : 3d766dfd02f40ab1004f2bce552b44af SHA1 : ed7be04a7e9e52a1059bdcac983405ef904998c7 Modified Time : 14/05/2015 11:46:20 Created Time : 14/05/2015 15:25:07 File Size : 374 File Version : Product Version : Identical : Extension : BIN File Attributes : A ================================================== ================================================== Filename : TOSCPL-8538815E.XRM-MS MD5 : 74f8df43f4d197778bad6f685fed37d1 SHA1 : 3e252a65627edb4c68e3bb4e48ad5b54d8fe9853 Modified Time : 14/05/2015 11:46:20 Created Time : 14/05/2015 15:25:07 File Size : 2,731 File Version : Product Version : Identical : 1 Extension : XRM-MS File Attributes : A ================================================== ================================================== Filename : TOSCPL-714A1F77.XRM-MS MD5 : daee3f455591f9a5196362874d3fbd4b SHA1 : 547f0bc67b5005fefc4bea09e47404490e355265 Modified Time : 14/05/2015 11:46:20 Created Time : 14/05/2015 15:25:07 File Size : 2,731 File Version : Product Version : Identical : Extension : XRM-MS File Attributes : A ================================================== member bitznpcz TOSCPL_V2.1_Cert.xrm-ms is the same as TOSCPL-8538815E.XRM-MS we have that certificate and TOSCPL-714A1F77.XRM-MS but his TOSCPLTOSCPL00_V2.1.bin is different from the TOSCPL[TOSCPL00]2.1-39C53B76.BIN we have so activation was not possible.
May I ask are those your your original files or did Daz loader install them ? I have certificate and OEM:SLP key but did not have the .bin file different from version I have.
If loader would be using a bin to activate then it is using emulator in order to activate thus really isn't oem activated but instead would be simulated oem activation. We really need the original info, if not then we are beating our heads against a wall. lol
Not sure whether it helps, hinders or is irrelevant, but the key and cert in Daz Loader works on this model even though the key and cert on the original is different. Passes genuine advantage and Windows Update works OK...
Run the query tool to find out if loader is being used or if it is really oem activated. The tool will tell you.
Yes, the COA key works, but I prefer using this OEM project as it speeds things up and keeps the COA key free if required.
Without you doing factory restore (not system restore) with original info gathered from query tool, we are shooting in the dark because I don't know what needs to be added. Really complicates the issue. I wish you would have shared the query tool info before doing an install but oh well.
grrr this is all I get for logging on win 8.x and win 10: Start time and files extracted successfully. Nothing else will write to the file. I will work on this over the next few weeks. I got to finish my school work for this week so this must wait.
I am really confused on this matter. lol At least I am honest. This project doesn't use .bin files unlike windows loader does. You can add it in a folder and the loader will see it and use it but this project does not.
I shared the results in a later post from another laptop that is the same make and model... see post #1266 for files.