Vcredist 2012 11.0.61030 Registry Applicability check
I’ve read posts / watched all the videos linked on how to / talked to person on phone that said they couldn’t really help me with the specifics as it’s available but not supported! So I figure I’d come here to see if anyone got this working or can help.
None seemed to be specific on registry checks without file version check.
I’ve tried the following setups with “Not Rule” both checked and uncheck as the only rule in applicability rules.
In all cases it appears to ignore it and try to install on both the machine that does have the registry entry already and the one that does not.
I found this one specifically that broke down the troubleshooting to supposedly only need to use the Applicability Ruleset if I’m reading it right.
“FAILING TO REPORT AS NOT INSTALLED
This is an update that reports as Not Applicable when it should be detected as needed. The techniques for diagnosing the problem are identical to the techniques just described in the previous paragraphs, except now you have two rulesets to troubleshoot -- the Prerequisite Ruleset and the Applicability Ruleset. However, we can take advantage of the fact that the PreRequisite Ruleset is actually optional (the Applicability Ruleset is not). So after visually verifying each and every rule (and presuming you've not already identified the errant rule), create test packages as before, except populate each rule in to the Applicability Ruleset only. At least one package will detect as Not Applicable, and that will identify the errant rule. Fix the appropriate ruleset in the original package and republish the package.”
Registry Key in question that I want to check for, specifically that the version number matches.
Can anyone give me the proper Applicability Rule and Installed Rule to check if it's there to not install it and if it isn't to go ahead and install?
Thanks - Charles
EDIT: Even just tried a "Registry Key Exists" as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\VC\Runtimes\x64 in the "Applicability Rules" and it still updates on both as needing to install when one has it and the other does not.