QT 81.0 has been completed - soon be ready for upload. MRP 105.0 is at BC1 (baseline candidate) stage - final touches being made.
Bumper Bundle Time Again! MRP 105.0 Baseline, Query Tool v81.0 have been uploaded, 2nd Post download links, passwords and hashes updated. Spoiler: MRP 105 Summary + Added new Locale information from Microsoft's Locale database. Any that is missing then the standard data will appear. + Added extended KMS/MAK data such as renewal times etc. Note it does not detect MS Office if you have pre-installed that. Maybe another time it is not a requirement as MRP is designed for OS management. + Fixed a glitch in which on Windows 7 Czech language (maybe others too) the project would abort due to some strange reason. Have hopefully cured it with a bit of tweaking. Thanks to JanCerny and Dubioza Kolektiv for letting me know. Also a big thanks to Enthousiast for testing my edits/fixes with CS-CZ Windows 7. + Added a new option for Windows 10 Only, remove tiles from the Start Menu, this does NOT uninstall any apps/programs you will have to do that manually after setup has completed. But it does leave you with a 'slim' menu and not the large sided one. Note this also transfers to any new user created by OS design. + In addition to the above option, if you have your own LayoutModification.XML file with tiles set up how you like you can use that with MRP too! Just copy your XML file to the Scripts folder where decompile.exe is located and MRP will detect this file and use it instead of the preset MRP 'blank' one. You will see a note in the project.log that the file is beyond MRP's control and that YOU are responsible for its contents and that it is set out correctly. + Slight re-design of the project.log output, this is a phased operation and is the start of the transformation. + MRPConfigCreator has been updated to v9.0 to include the new option. ++ Note for Insider Core/Home Editions the Windows Mode Dark theme does not always work not sure why as the registry entries are correct. This may be a glitch with M$ OS code and nothing can be done about it at present. For Pro and higher Editions a logout/login or reboot cycle should set the mode(s) correctly. It seems like M$ are forcing the 'Light Theme' regardless of the users wishes, (nothing unusual there!), I will find a work-around for it at some point. ++ Note2: It is wise to do a reboot/logout cycle after setup has completed anyway to make sure all options/theme elements have been set correctly. Spoiler: Query Tool v81.0 Summary + Updated header lines to be more clearer on what each section it is for. + Updated the routine for activation and License channel detection it can take a few seconds so please wait while when it obtains the data. + Added current .theme in use it is experimental and may not always show depending circumstances as the information is stored in various locations within the registry. + Hopefully fixed a small glitch with Language detection. + Separated the Meltdown/Spectre results into their own section. + Few other things but can't remember as was distracted with an abort glitch on the MRP code which had to be sorted asap.
Upgrade Method/Socket - [Socket 478 {15}] i thought i had removed that line, I rechecked the QT code and realized when i had reverted back a couple of internal test versions to fix another problem and forgot to remove it again Fixed for next version.
looks like the setupcomplete.cmd has a RD scripts and/or delete of the scripts folder hence why the project was aborted. [SCDET] Note: SetupComplete was detected. [NOTES] This file is 'SYSTEM' ran beyond MRP's control and may cause malfunction of the project. is the clue as the project stopped exactly after this file was ran.
I get an error with Query Tool v81.0 and stops working "4 was not expected in this moment" no report. Tried in other PC and Works perfect.
Because it is not a PowerShell script! The QT is designed to be ran by double clicking the file as it is a self-contained EXE. PowerShell can struggle with the QT because it contains a mixture of CMD scripts, VBS and EXE files which obviously can confuse it. I could add code to detect if the QT is being ran from a PS shell and exit.
You could also spawn a new process for QT and run from that (e. g. break out from whatever parent it has been started from). Together with a new window, it would solve my resizing issue, too. Skip that method if you detect running from Explorer.
Well, I did run it as it was designed, as a self-contained EXE. It started and stopped in the window, that I just have sent, but I was unable to read the last messagge because the window closed very fast, that is why I used the PowerShell script!. I did the same in a DELL DIMENSION 9200 and worked perfectly in PowerShell script! and as a self-contained EXE The laptop in which this utillity fails is HP ELITEBOOK FOLIO 1040 GE Thank you for your fast answer Regards
HP/Compaq has always been a fussy make with the project, Lenovo and Sony was others but have managed to sort those, but HP is still one that can be problematic still. I am looking into ways to detect the parent and child processes and this is giving me a bit of grief, nothing is ever simple grr.
Carlos thank you for your answer, but I don't understand what I should do. Could you elaborate?(Lo siento no entiendo)
Thank you and sorry. I hope you can solve it. Any info from my side that could help you, let me know. Let me add that your project is impressive, congratulations!!!!! Regards