or as the registry shows to obtain the 'Desktop's location via a check there. but the system drive may be the safest method, a bit of a pain but at least then the log would be found, one reason the MRP log(s) are always saved on the system drive's root. The use of the system drive would only be used if the 'Desktop' folder could not be found. Will adjust the QT code.
Have just altered the save location routine, it will check for the normal '%Userprofile%\Desktop' -- if that not found then it will query the registry and failing that location it will save to the SystemDrive (C: / D: etc) and if for some reason that fails too, the QT will just tidy up and exit. You will now see a line in the QT's window mentioning the save location, or if it happens a failure message, at the final stage. Just compiling a LT2 beta test.
Uploaded the Query Tool LT2 beta test with enhanced save location routine. Updated post #3 with download link, password and hashes. Many thanks for those that tested LT1 at least the /Locale WMIC parameter not cause any problems Thanks to @migascalp for informing me of the save glitch. Hopefully this update addresses that problem.
nice Another bug battered into the dust Many thanks for letting me know and the fix was fairly easy even if i went a bit over the top with the routine to make sure there was a location to save the report too.
Thanks again for letting me know about the strange save part, i guess it one of those things that can sneak in as Windows's internal code changes hopefully it has now sorted that gremlin out.
Been trying this for a few weeks now and i cant get it to work for me . I havent managed to activate my win 10 pro workstation . In the MRP_Debug log it says ---- > Checking for 'Retail.txt'. The 'Retail.txt' file was not detected within the 'Scripts' folder. Checking for 'ei.cfg'. The 'ei.cfg' file was not detected. Checking for 'Pid.txt'. The 'PID.txt' file was not detected. and ======================== ===[ License Status ]=== ======================== License Status : Notification Channel Status : Retail {PKC} VL/KMS Capable : Yes Reason Code : 0xC004F034 {Dec: 3221549108} Reason Text : License not found/invalid or could not connect to the Activation Server. Final Tidy Up : Started Final Tidy Up : Redundant Files Final Tidy Up : Redundant Environment Variables Final Tidy Up : Completed Unicode Mode : Deactivated Orig Codepage : 437 Anyone any ideas what i'm not getting right ? .......... and how to fix it please ?
Unless you have a HWID or genuine key you could use a KMS solution to obtain your activation. Remember MRP does NOT activate any OS unless it would be done via OEM/SLIC/Genuine Key - MSDM/HWID are handled by Microsoft activation servers when the device is connected to the internet the product channel's method will be checked via that and if meet criteria then activation takes place. Retail.txt is to inform MRP not to use any SLIC/MSDM checking so that the user can insert their genuine key within the 'Change Product Key' area within the OS later. Pid.txt is to inform MRP to bypass any activation method such as SLIC/MSDM/HWID etc the key MUST be genuine as the OS will check as does MRP to see if it is valid, if not then that key is ignored and will not be used for activation purposes. Ei.cfg is to tell the OS Setup to ignore any checks for an internal MSDM table/key - this allows the user to install say Pro on a MSDM device which has Home/Core, not using the ei.cfg file on a device with a MSDM the OS Setup would bypass MRP or any setupcomplete etc to get to the 'desktop' asap. More information about retail/pid and ei.cfg is in the readme files. As for your OS not activating , does your device have a HWID for WSPro? If not then unless a genuine key is used or 'other' methods to activate then i cannot help with that as it not a MRP issue. Reason Code : 0xC004F034 {Dec: 3221549108} Reason Text : License not found/invalid or could not connect to the Activation Server. Basically is saying the device is not connected to the internet OR there is no HWID detected for the device on the M$ activation server.
Thank you . I dont know ...... I have two files MRP_Debug1.log and MRP_Project.log but i dont know how to post them in a box or if / wich one/s i should post ? KMS_VL_ALL_AIO-37 does work .
As it not a MRP issue then the logs will not mean much only to confirm that no activation took place. I am guessing no HWID was done in which case only a genuine WS Pro key or KMS solution would be available to use, other methods cannot be discussed here. You would be better asking in the KMS_VL_ALL thread about the KMS side *if* that had failed to work. Other than that nothing i can personally help you with, sorry.
Thanks for your help . I understand that its not a problem with your tool but the logs are the only info i have to help me understand whats ( not ) going on so i posted here I'm confused now ...... from what i read it apears to me that it should have worked ...... but didnt because of three missing files ? ...... and also i read somewhere that maybe HP laptops can have problems ? ...... and it was a UUP .iso win 10 pro + workstation pro and i cut the pro out with NTLite so maybe i screwed it up doing that ?
Would it be possible to (optionally) save the screen log, to? Not for posting anywhere, but for own purposes. I know I can copy-paste, but I'm lazy.
HP/Compaq amongst a few brands can have a few problems with branding or in the case of the Query Tool some memory detection issues. Activation is usually straight forward if the device has a MSDM for 8.1/10 or SLIC for vista/7/Servers. As for 'chopping' a OS , if you not sure what is being done, the items removed and the consequences of those actions etc then that can lead to all sorts of problems later. But that process is up to the user and not part of this Tool set.
If you didn't previously establish an HwID for Pro Workstation, or have an otherwise valid license for ProWS (MSDM, Retail), then there will be no activation. MRP will not do anything about KMS.
I will need to re-write the GUI exe but i gather that should not be too much of a problem -- once i work out the context menu bit within that GUI
The text in the GUI display can be copied/pasted, such as CTRL-A to select all the text and then CTRL-V into say notepad to paste it. But i will work on the GUI for a right click save requester thing.
Thank you Carlos . What do you mean by ' establish an HWID ? With win 7 i just put the $$ folder in the sources folder of the .iso and it activated it . Please can someone tell me if it should have worked with this .iso ---- > 18363.753.200326-0714.19H2_RELEASE_SVC_PROD3_CLIENTMULTI_X64FRE_EN-US.ISO and the laptop is CSNAME : [HP EliteBook 8540p] SYSMODEL : [HP EliteBook 8540p] CSVENDOR : [Hewlett-Packard] SYSMNF : [Hewlett-Packard] BASEMNF : [Hewlett-Packard] BASEPRO : [1521] BIOS or SLIC ID 1 : HPQOEM - f SLIC Information : v2.1 - SLIC table with marker present MSDM Information : No MSDM Table Present
Well as no MSDM then w8.x/10 will not activate as no acpi table with any internal key present. SLIC is no use for W8.x/10 only for Vista/7/Servers. So unless a HWID was done such as upgrading from win 7 in your case to w10 of same edition then only KMS/Genuine key or 'other' methods will work.