Yeah found the little gremlin! When i edited the script it altered the echo to a exho lol so it ignored the output! It should now show the SKU. Code: OEM Query Tool v14 Build 4 Advanced 05:49 PM 26/12/2016 OEM INFORMATION FOR THIS MACHINE -------------------------------- OS Name: Windows 10 Pro [x64] SKU: Professional Processor: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz <snip> Will reupload corrected version, thanks for pointing it out
The chance I pointed out was mere coincidence lol It just crossed my mind the idea to have a sku line
ok bro, have uploaded corrected version it should be there to download and named correctly too. It no longer outputs the long 10.0.xxxx-frex-xxxxxxxxxxx type name, as when compiled it somehow screws that up no idea why, but I did add the SKU name but exho is not a command lol.
Looks ok The only important bits for MRP are the Scanned #1 to #14 and summary theme/activation, as those are what are also used within the main project. If anything needs to be edited DMI scan wise this is the areas i need to edit/check. The rest is just general info about the PC the QT run on.
As i was not sure what you wished to rename, I shown all the parts that are safe to edit text wise that will not break the branding system. I had an idea it might be the name of the theme display name that is shown within the Personalize window. Hence why i put little notes next to the text areas and what/where they, would be shown.
@TheWraith, Looks like you be good to go if you needed to reformat a Windows 8.1 fresh and use MRP. If you reinstalling the W8.1/Bing(CoreConnected) it would brand with Medion [id #4], and pull the MSDM key from the bios and insert the key, then once you connected to the 'net be all nice and activated.
The checksums you posted doesnt match the downloaded ones (QueryTool) And in the link it says MRP 23rd dec, your changelog says 26 dec
I'll check , its possible i have put checksum on the wrong file... The 26th entry was for the Query Tool change/upload. MRP is correct 23rd Dec release date. Checksum Correct. Query Tool Checksum is incorrect - There is a new update to build 5 I have done, so will update that with new one, covers SLIC v2.4, as before it said un-listed.
Updated: Query Tool V14.b5 Query Tool v14-build 5, updated and uploaded. Should now cover slic v2.4 detection.
Hmm odd, usually it will say Possible Emulation if a loader was present. If there is an MSDM key in bios it should display it on the screen, but when saving the report it will not show it, was done like that so it safe to post the report in the thread.
It looks like a newer Skylake cpu laptop. Also the slic bit may be getting confused because the GPT and secure boot on. As it in Win 10 'mode' it may not display the slic part correctly. I know the Slic Tool kit v3.x has a similar issue with reading SLIC if GPT/SecBoot on.