I noticed that not all my machines are picking up the Visual C++ 2015-2019 redistributable updates. attached is a client (server 2016) that does not get the x64 update, but I think I have situations where x86 is not picked up.
The update of last week is not yet approved for deployment, but detection is the same.
If you can tell me the detection method (or where I can find myself) I can check the machine why it is missing this 1 update.
Microsoft Visual C++ 2015-2019 Redistributable 14.24.28127.4 (x64)
<lar:And>
<bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X64" Value="Bld" Type="REG_DWORD" />
<bar:RegDword Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X64" Comparison="LessThan" Value="Bld" Data="28127" />
</lar:And>
On my machine the key does not exist, but it is in WOW6432Node. Tomorrow I will search if I have also machines the other way around.
Below the export of the same machine in the screenshots.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x64]
"Version"="v14.0.23026.00"
"Installed"=dword:00000001
"Major"=dword:0000000e
"Minor"=dword:00000000
"Bld"=dword:000059f2
"Rbld"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x86]
"Version"="v14.0.23026.00"
"Installed"=dword:00000001
"Major"=dword:0000000e
"Minor"=dword:00000000
"Bld"=dword:000059f2
"Rbld"=dword:00000000
I have a machine where x86 version is not detected, but I can't find a reg key containing any of the info, even if "Microsoft Visual C++ 2017 Redistributable (x86) - 14.16.27012" is in add and remove programs.
So this is a VC++ install issue and not a detection issue.
A manual update did remove the 2017 x86 version and created correct reg keys so SCCM detects the product correctly.
The entries for the x64 bit are located in de location you provided, but also in WOW6432Node and are perfectly detected and updated.
Did you see the detection method from the Publishing service: <lar:And>
<bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X86" RegType32="true" Value="Bld" Type="REG_DWORD" />
<bar:RegDword Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X86" Comparison="LessThan" Value="Bld" Data="28127" RegType32="true" />
</lar:And>
can the x64 detection method be extended to also search in WOW6432Node?
In our test, the x64 is in the native key as well
(https://i.imgur.com/FNIi52f.png)
mine is an older version, VS 2015 x64 redist
I have the idea that MS is making the latest versions better than the previous ones. see the issue I discovered with the x86 version that not even has the reg key in 1 of both locations.
you can download the version here
http://download.microsoft.com/download/9/3/F/93FCF1E7-E6A4-478B-96E7-D4B285925B00/vc_redist.x64.exe
not a single trace of this and previous VC++ versions (both x86 en x64) in the normal x64 reg location but all in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\
We can probably add that into the next update for Visual C++
tnx, would be great to be able to update also the older leftovers.