I'm not sure what else is relevant for trouble shooting but let me know and I will get it. I am banging my head against the wall on this one so if anyone has an ideas let me know and you might just save me from a headache. I have no dependencies or supersedence on this application. My detection method is a line in the registry HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office14.VISIO\DisplayName and this does not have the "This registry key is associated with 32-bit application on 64-bit system".
I don't have "Run installation and un-installation programs 32-bit process on 64-bit clients checked. The content location is two separate folders 32/64 not inside of themselves. Operator = "One of" and the appropriate selections are checked "All Windows 7 (32bit)", etc.
How to download Microsoft Office Visio 2010 Full Activated - Standard - Premium - Professional Incl. Microsoft Visio Premium 2010 (64-bit) Key Gen - Legit Download 2015. I use with 10-15 other applications and it works), basically a global condition that Microsoft Visio Premium 2010 Serial (microsoft visio premium 2010 key) Dana Butler. Each deployment type uses a custom requirement to determine the OS architecture (same one I have the 64bit deployment type as primary and 32bit as #2 (I have switched these in testing and nothing changes). All three of these applications behave the same way and download the I do have three different Application Packages "variations" of MS Visio 2010 (standard, pro, premium), but each of these have there own operate content folder. Version on 32bit OS and 32bit version on 64bit OS). It will download the installation to "C:\Windows\ccmcache\1" (32bit version on 32bit OS and 64bit version on 64bit OS) however upon testing the un-installation it re-downloads, the wrong architecture, to "C:\Windows\ccmcache\2" (64bit when checking the "C:\Windows\ccmcache" folder
I have several applications that are similarly designed to this one and all work as intended, I have also rewritten this particular one three times with the same results. I'm on Config Manager 2012 (non-SP1), not sure what other information is relevant.