Query Tool v92.0 has been uploaded, 2nd post download link, password and hashes updated. Spoiler: QT92.0 Summary + If the Windows Script Host, (WSH), is not enabled, for whatever reason, you will see a note that it is disabled and that some data will show errors. The QT will NOT re-enable the WSH that is for you to decide. Without the new error checking the QT will either crash (rare) or just put lots of lines about the WSH is not enabled etc. This check was done this to keep the display tidy. The QT will attempt to show the majority of the information, as other methods are used to obtain the data. Mainly it is the calculation routines are reliant on WSH for CPU L2/3 Cache, system RAM also MS Office detection but that part will use another checking routine if needed which is not as reliable. + Fixed a bug if the CPUID was not defined, usually with Virtual Box (VBox) VM's. Thanks @Carlos Detweiller for letting me know. + Other code tidying done. A bit later than expected to upload but had a call out this morning which the job took a bit longer than i had anticipated. Hopefully this will be the current release for a week or so , barring any bugs.
Can these settings through the MRP on Win 10 affect the speed of raising windows after installation? I do not speak English, I'm sorry.
The tweaks/options used in the MRP should not cause any slowdowns, most may even help speed up certain aspects of the OS. Only three that i know of 'may' slow down the OS over time are: 1. If the 'SSD Tweak' is used on a normal spinner HDD - that can be reverted, if required via the 'Revert_SSDTweaks.cmd' script. 2. Using the 'Search Indexing' option on a normal HDD, however that can be reverted via settings in the OS and turning on the relative Services again. 3. Turning off 'Fast Boot' on a normal HDD, but that only affects boot/shutting down, sometimes enabling 'Fast Boot' can cause other problems with the Sleep function on Laptops. The OS will slowdown anyway even without the MRP's tweaks/options due to the nature of how 'bloated' it gets with programs installed and many startup items. Plus now with the Meltdown/Spectre patches on older CPU's being within the OS via updates etc that will affect performance more than any tweaks used in the project. As all the options/tweaks are selectable, it is up to the user to decide which to use, nothing is used unless selected. If the .ini file is not used then no options are set, only branding, (if the OEM's.7z file is present), and SLIC activation is performed as it always was.
odd that ECC detection isn't showing It may be because something is causing the routine to return a invalid result and in doing so the QT has null'ed the value hence not showing. On Win7 and Vista OS's some data is not read due to certain queries not present in WMIC, or if the results are invalid then they are also null'ed, this may of happened with the memory ECC detection for some unknown reason. Invalid characters in the SMBIOS/DMI area is outside the scope of the project/QT as that is hardware/BIOS related and nothing I can do to rectify that. I could filter any character above chr$(128) ASCII out, but then results would not be a accurate representation of the data. As for the Other/Reserved result, that is a fall back result if the routines used cannot determine the actual HDD/SSD mode, i was going to have the QT not show that line but then if the real reason was because it is actually a OS 'Reserved' result the representation would not be correct. You have to remember the QT is not competing with such tools as BelArc, HWinfo, AiDA etc and i am not able to write any special tools in C# or .Net to do the fancy stuff to interrogate the OS at kernel level.
The Autounattend.xml is the same one that was there when i took over the project in Oct 2016 ! I think it was just an example of how one is designed/created. As Windows 10 has changed some elements may need to be researched before its use. Not used unattended mode since the XP days so i can't really help with the xml layout.
I may be wrong but i think they used the xml file 'as-is' and not put a valid key in, so the key part was just XXX's so that would cause the OS to abort with invalid key etc. If i need to set a specific edition i mainly use the PID.txt way, but the odd time i may use the ei.cfg set to the edition.
I believe the two key sections are required in this case, as one is for x86 and the other for x64, if the XML was just for one single architecture then only one key section will be needed. In my previous experience sometimes having the two architecture structures within the one XML caused a few errors. I therefore had one XML file for x86 only and another for x64 only, plus it made it easier to edit later if anything needed to be done.