Because of the options this happens. I'm gonna hang up or hook up This also happened on another computer I'm sorry about the English language. It's bad
The only option that can affect the start menu tiles would be the one for Block Adverts which also blocks certain tiles from updating. On testing it should only leave the standard Tiles such as Edge, Skype, My Office... and no 'extra' ones for games etc. If you used the 'Add Phone' option then as mentioned in the config creator etc adverts may appear - or try to. Also if the computer is connected to the internet during installation then some tiles may try to be put on - nothing i can do about that. The $1 zip on my other post will remove all tiles except one (Powershell) as you have to leave one tile present or it totally messes up the start menu. The tile can be removed after installation to leave just the program list on the side. Likewise with the Taskbar, it is wise to just have one icon there (in my new test $1 i have just done, there is just File Explorer), that too can be 'unpinned' after install. The XML system is buggy hence why one Tile and one pinned Taskbar icon is required to be present at setup/install. A lot of people butcher the OS and remove these tiles/pinned icons and then have problems with the Start Menu, Action Centre etc because of it. Attached is a screen pic of how my new test $1 start menu layout looks. I added a few extra 'useful' tiles to see how they can be integrated. Notice the Taskbar has just the 'file explorer' icon, no store, edge or mail icons. The layout was done purely by the 'LayoutModification.xml' file and no butchering required.
Query Tool v63.0 has been uploaded and 2nd post download link, password and hashes updated. Spoiler: QT 63.0 Summary GUI Version only this time as seemed to have cured various issues. + Fixed the strange '0 is unexpected at this time' error. + Fixed some text alignment issues in the display window. Saved report was ok. + Updated the Graphics Adaptor information section, sometimes it would give wrong information in the results due to confused results returned by the routines. Now if something isn't right it will not show that line or show N/A for some results. + Code tweaks to speed up some areas. Slight tidy up of code in some parts too. + Updated the GUI display to pick the right font for the OS installed, for Windows 10 kernels it will use Consolas, for other OS's it will use Lucina Console or if they are not present then it will try Courior font then if nothing can be used a message box will appear to say why. The desktop saved results will still be made regardless of if the GUI cannot be shown. Also if an antivirus removes the GUI reader program then the QT will attempt to use the old display method.
[SCKV7] HP [#08] SLIC Un-listed found for possible Windows 7 OEM activation. That's been fixed in a later MRP.
Hopefully the GUI QT will work for all languages etc. Saves having to update several sections and versions each time. The GUI allows a LOT more space for expansion, plus you can scroll and adjust the window to your display which was not easily possible with the old method as there was limitations for the dimensions which i had almost met.
MRP 96 code has been started, you can usually tell when one will be soon appearing when a new QT has been posted. At moment no new options added, it just a revamp of the log output's look for now. There 'may' be a new option or two added at some point but that not on the top of the to-do list for the time being. As for the false-positives, that will be reported to the AV's soon. ESET NOD AV does not show any false-positives (for the moment) as i use that AV myself. As mentioned before, if you set an exclusion in your AV to whitelist/ignore '%TEMP%\MRP_QT' that should prevent them from touching the files within that folder where the QT operates from.
The next MRP is progressing... Not reached Release Candidate status just yet as still in developing mode. All log changes are done. Testing new General all OS option: Disable restart after a system failure {BSOD}, a simple thing i know, but it can be something people forget to change. Normally the PC will just flash up the message and restart, you then have to go hunting through the Event log to find why. This option just changes the default 'Automatically restart on system failure' to don't, so you can see the message to note down and research what caused the OS to crash. It will still save the information in the Event log as normal. As always this will be set to No by default.
It is a very useful little tool It has expanded to cover majority of things, most is just eye candy really, but it can help pin point most problems with installs, such as showing the PC has a MSDM which was causing problems with say a Pro install but the MSDM was for Home for one example. The reason codes cover a lot of activation stuff which can help with a KMS failure too as it can indicate certain information. As you used a KMS method you can see the 0x4004F040 appear mentioning it is activated but the QT (and OS) knows it a 'activator' and says to verify the usage rights. Granted some areas may not be 100% accurate ie the HDD total/free because how things are limited with 32bit SET /A, it's close and almost reflects the pie chart for the properties of the HDD/SSD.
I think you're doing a wonderful job and keeping the HDD simplified was the right move as doing a full probe would have only impacted performance unnecessarily anyways. Keep up the good work.
Thanks It's a balancing act at times for new info vs time penalty, with a bit of tweaking i could get the QT to complete within 7 seconds, but because some of the results are quite important it is slowed down on purpose in some areas to give enough time for variables to be set correctly and rechecked. To get the HDD info right as you mentioned would cause a delay because of all the calculations, and to be honest as long as it close, i see no reason to make things more complicated. Plus as we know HDD makers use one calculation and m$ uses another, so as the QT runs on Windows i went for the latter to be as close to the numbers shown on the drive's properties (rounded up/down as required). ============MRP 95.1.3 Internal test will soon be 96.0 RC1 so won't be too long for release folks. The new option works, i used a trick to cause a BSOD on purpose and it didn't reboot like it would normally. Have reworked some of the main code base and this has taken longer than expected due to some 'fatal' errors, but at least those error checks i added worked! So 96 won't be anything special this time just one new option at the moment.