Playing about with some VC++ detection script... Results so far: (only VC++ 2015 installed on my laptop... Code: VS 2010 not installed VS 2012 not installed [VC++ 2015 x86 v14.0.23026] [VC++ 2015 x64 v14.23.27820] Will test other VC installs but im not sure on those below 2010 so may just detect 2010 and above....
Installed the VC++ AIO results gave this: Code: VS 2010 not installed VS 2012 not installed [VC++ 2012 x86 v11.0.61135] [VC++ 2012 x64 v11.0.61135] [VC++ 2013 x86 v12.0.40664] [VC++ 2013 x64 v12.0.40664] [VC++ 2015 x86 v14.32.31332] [VC++ 2015 x64 v14.32.31332]
Maybe rebrand it to VC++ 2015-2022 or 2015+ below 2010 detection is indeed not easy VC++ 2008 got this Version registry, VC++ 2005 don't Code: ; x64 or x86 on x86 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VC\Servicing\9.0\RED\1033] "Version"="30729.7523" : x86 on x64 [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\DevDiv\VC\Servicing\9.0\RED\1033] "Version"="30729.7523" other nonpractical check Code: dir /b %SystemRoot%\WinSxS\amd64_microsoft.vc80.mfc_* dir /b %SystemRoot%\WinSxS\x86_microsoft.vc80.mfc_* dir /b %SystemRoot%\WinSxS\amd64_microsoft.vc90.mfc_* dir /b %SystemRoot%\WinSxS\x86_microsoft.vc90.mfc_*
Agree about that! I am struggling with below 2010 V++ , at moment just working out how to get the variables onto one line to look neater than separate lines.... to look like: VC++ 2010+ : 2012 x86 v11.0.61135, 2012 x64 v11.0.61135, 2013 x86 v12.0.40664, 2013 x64 v12.0.40664, 2015 x86 v14.32.31332, 2015 x64 v14.32.31332 almost got it to look like above... once i perfect it i will add it into the QT But might just leave them on separate lines saves loosing more hair over it
Snippet from QT 123-RC4 showing the VC++ 2010->2015 Code: Current .Theme Detected : Custom.theme Current Wallpaper Style : Stretch image to display resolution. MRP DMI Internal Reference : 1/4 Detected .Net Version{s} : v1.1.4322, v2.0.50727, v3.0.30729.4926, v3.5.30729.4926, v4.0.30319, v4.8+ Powershell Version{s} : 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 PS Execution Policy : Unrestricted PS Scripted Diagnostics : Unrestricted VC++ 2010-2015 Information : {2012 x86 v11.0.61135} {2012 x64 v11.0.61135} {2013 x86 v12.0.40664} {2013 x64 v12.0.40664} {2015 x86 v14.32.31332} {2015 x64 v14.32.31332} Due to the hassle to get the info for below 2010 VC++ runtimes i have decided to only check for 2010 and above. I have shown the x86 and x64 VC++ versions because sometimes there can be a difference and that may be a reason for a application to give errors..
Only just been over 40c at times outside and in my home been 85c or bloody hot for England. Updated QT 123 to RC6 added a bit more checks for 22h2 (w11) update target section , shows a few more bits - not sure what it means but they can be detected so i shown the results.
Had to take a few days off as the heat made me feel ill, plus with these coils stuck in my head they heat up and cause headaches, but as it cooled a bit this morning i done a bit more coding. MRP will be next to get a bit more done as it about finished code wise.
Do you think that it is possible to include the TPM Bypass check in MRP? I know that it is possible to add registry lines in autounattend.xml, but MRP with this included would be nice. [OSINF] TPM 2.x Bypass Check : No [OSINF] SecureBoot Bypass : No [OSINF] Low RAM Bypass Check : No
It has TPMBypass for upgrades already included. You can set it with the MRPConfig Creator. For clean install from boot, Windows Setup must be patched. Nothing MRP could do, it only starts later.
To set the registry flags for the TPM etc bypass needs to be done pre-oobe either by a unattend.xml which is run/called by setup.exe before oobe stage starts or via other methods which can be found here on MDL. As MRP is run at normal oobe stage sadly that cannot be done, the settings in MRP's config, as mentioned above, to bypass those type of checks are only for when upgrading to w11 from within a running OS such as w10.
Will resume work on the projects in next day or two, took some time out. There could be another w11 option added but it still in research and development stage. Working on a Exam now so all my time taken today.