Query Tool v70.0 has been uploaded, 2nd post updated with download link, password and hashes. Summary of changes: + Advanced SLIC checking, (if needed) - which should eliminate odd errors if the SLIC table is dummy/invalid. + Some slight cosmetic changes in certain lines/text data.
seems like Kaspersky not like the QT at all. At that stage of the QT Alphawave's Generic.exe is ran to obtain the SLIC/MSDM information stuff, which can trigger AV's even in 'paused' mode. Sadly nothing i can so about that. The QT has been fully tested on many computers, albeit none had a AV installed. Only one did Total Security (360Safe), which is very sensitive and grabs even some Windows updates lol. ESET NOD32 - all clear (which i use).
Don't the AV's have a learning mode anymore? In the old days, when i still used one, it was set to ask what to do, when it got triggered, with an option to save the selection for future use.
If you use spaces in the COMPUTER/Device name then use of Networking can be problematic too. Networking protocols not like spaces or most non standard characters either in any device name.
Not all AV's have that 'learning mode' they either allow or just block/quarantine these days. But in this case it was the use of spaces within the Computer Name (used on Networking too). Using _ instead of a space gets around that problem.
I have edited the ComputerRename script to change any spaces to a - (minus) character automatically this will be in the next MRP release's Optional\MiscScripts folder. So a name of: My Beast Of A Machine Would become: My-Beast-Of-A-Machine **EDIT** Have further updated the script which attempts to filter the non allowed characters, but due to limitations of batch scripting and certain special characters such as * < > etc they cannot be filtered and will cause the script to fail. Also added a ReadMe which explains the scripts use and other notes. Have altered to use the - character instead of a space as the _ character has a special meaning too!
Its a hit and miss with AV's the compilation method/program is the same, no use of UPX which always triggers warnings. All being well when the next update of Kaspersky database is due they will have cleared that flag. Always the same for each release. *sigh*
But, already 1-2 years ago. Yoga/Idea-Series has Orange Lenovo-Logo now. Premium T-Series and all other, has Red-Logo. Also the Wallpapers and Themes where discreted and changed by Series. Do you have possibility to provide them?
Not at moment no, plus the oem theme's within the OEM's.7z are just generic, the end user can alter the theme elements, logo's etc if they require. I read they changed the main logo (think 2015?) to have a slightly different blue and the letter e was changed. To have specialized theme's for the different series's on a certain brand would not be an easy task, so as mentioned above they are generic in nature and the end user can alter the theme to their liking, all info about the sizes, (pixel and file size), are mentioned in the 'Optional\! Info About Images.txt' readme file.
Query Tool problem: Tried to run it on the latest RS5 17751.1 (VirtualBox). Windows Defender killed by Group Policy (No other AV). Exploit Settings (EMET) deactivated for the .exe. Still, it runs only to 50% and then simply disappears. No result file at all. Tried 69 and 70, outcome is the same.
Hmm strange, in all the tests we did it never failed Not used VirtualBox for a couple of years as it was buggy on certain aspects, (think most have been fixed now), so went to VMWare instead. If you open a Admin Command prompt at the location of the QT and then type the filename and press enter to run, it should hopefully, when it fails, show any errors in the window as running the QT this way will not close the window it's called from. Also if you open your temp folder %TEMP% you should see a QTLog.log text file, this should show where the QT failed at. That log is auto deleted when the QT has fully completed or on the next run if it is present and recreated during running.
Has the Computer Name been changed? As noted before any spaces within it can cause the QT to fail. At 40% SLIC checks are done, 50% is Memory checks. Have added error checking which should allow the QT to continue.. I extensively tested the routines with different test values and it didn't cause any problems, it either used the given values or null'd them respectively.