Insider builds are just weird anyway so many subtle changes then on next build release they change things yet again Look at the Tabs/Sets 'feature' for file explorer , on then off so you have to mess about with vivetool to have them and yet it a constant battle to keep them on every update!
I think why it reverting to blue is because that is the 'default' color. If the OS is not activated (according to m$) then some theme elements are not set and are 'ignored'... Seems to be on recent w11 Insider builds mainly this happens, as on the normal general release OS's it is set properly. Not much i can do about it
Re: QT Added a new check for the 22H2 upgrade experience, silly name for what could be a simple yes or no result , or in this case Green or Red as m$ says... This simply checks a part in the registry that m$ will populate at some point (may be in later Insider builds) that will tell the OS installed that it can be target upgraded to 22H2 or not and give a 'RED' reason to say why, such as no TPM or Secure Boot etc.. Info is a bit sketchy at present and the code added into the QT is based on what i have found, not what i have 'experienced' in my tests, or on my main pc's i use, so it may need some tweaking as time progresses. The registry area i am looking at is: "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" --> "NI22H2" The registry results will look something like: (image off internet) On all my tests and PC's that area is not populated at all -- maybe because they was all clean installed and not in-place upgraded -- so will have to see if anyone has results when i release the next QT...
Thanks to @Enthousiast testing the QT for me on a laptop with the info available in the OS's registry so it shows: Code: Destination Build Number : 22621 22H2 UpgradeExperience {1} : Red {Green OK / Orange Blocked / Red Fail} 22H2 UpgradeExperience {2} : Red {Green OK / Orange Blocked / Red Fail} 22H2 UpgEx Red Reason Info : CpuFms\0SystemDriveSize\0Memory {If not 'None' then any listed are not compatible} The Red Reason 'CpuFms\0SystemDriveSize\0Memory' in this test means that the CPU , Memory and Drive Size (space) is not compatible , TPM could be listed if that not right and i think a few other ones, it all depends on if any flags are set by the OS check. The QT just reports back the data in the registry areas checked and could be in the OS's native language or default english. Not all OS installs will have this information due to various reasons such as Updates blocked by gpo etc or on a clean install, it may take a few CU updates to activate the registry settings. Will have to see how it progresses...
Asus TUF Gaming B660-Plus WiFi D4 Core i7-12700F MSI RTX 3080 GAMING Z TRIO 10G LHR 1 TB NVMe WD SN 850 Windows 11 Pro WS 22H2 22621.290 Installed from image version 22622.290, however Windows Update has downgraded the version to 22621.290. Code: Index : 9 Name : Windows 11 Pro for Workstations Description : Windows 11 Pro for Workstations Size : 19 028 855 526 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.22622 ServicePack Build : 290 ServicePack Level : 0 Edition : ProfessionalWorkstation Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 25312 Files : 112918 Created : 13.07.2022 - 2:00:32 Modified : 13.07.2022 - 2:07:42 Languages : cs-CZ (Default) Please check the DM, QTv123.0-T7 report is crippled.
Is this the line you mean: ? OS Process Information : 64 bit, but is running within a 32 bit process as the QT is compiled It is just informing that the QT is 'compiled' into a single exe file, if the QT was corrupted it probably would fail to run at all. Will adjust the line to avoid confusion and translation issues. I could not see any issues in your report that you posted in the DM. --------- I think that the downgrade to a lower 'build' number was because something triggered an issue with a 'new feature' so the OS reverted back. Only a guess as it seems a few people have had it happen.
Try latest RC3 uploaded Not changed the QT that much, mainly added new lines not removed any from the logs...
If anything gets messed up it usually due to a A/V grabbing some files used in the QT so certain parts get skipped in the code as something not available.
This W11 build seems stable however, it has many compatibility issues. Maybe it caused by Asus or Intel. For example: Intel AHCI VMD driver causes BSOD - I will try backup and test more versions, currently runs with yellow exclamation mark without a driver MSI Mystic Light Driver ene.sys flagged as a "Vulnerable Driver" (certificate is outdated), this package is required for disabling RGB backlight - waiting for a new MSI release some issues with Intel MEI driver and ME firmware can't be updated by Asus package - I will do custom firmware package and try it again I built this computer for my friend. I will try some fixes and do some tests a few weeks later.
Win 11 is still evolving and every update seems to cause more issues than fixing them , mainly in drivers and some software. Re missing lines, not sure why comparing two different reports show missing lines, i use KDiff and using your two reports you attached to your previous post , i too got missing lines - very weird!
W11 22000 to me isn't a properly finished product as most bits was missing, 2262x seems to fixed most of those issues but as it still in 'testing' stages that could change again