I am trying to use the application model to install a Windows Installer patch (MSP) for some software. Understanding that each vendor is different in how they handle patching, what are some ways I can construct the detection method? I've tried checking the registry for the existence of a key that is created by the MSP, but it still fails the detection method.  My searches for examples have failed as well :)

Has anyone done this before?

Thanks,

Jeff

I would look at a specific file and version in the detection method.

When the product version is changed by the patch (e.g. Adobe Acrobat patches does) you can use the MSI product code AND the new version as DM

Stefan

• Edited by muecom (Stefan Mueller) 11 hours 38 minutes ago
• Proposed as answer by Jason SandysMVP 9 hours 58 minutes ago

You can also query the Windows Installer database by using the WindowsInstaller.Installer COM object and the PatchesEx property: https://msdn.microsoft.com/en-us/library/aa369442(v=vs.85).aspx .

When the product version is changed by the patch (e.g. Adobe Acrobat patches does) you can use the MSI product code AND the new version as DM

Stefan

• Edited by muecom (Stefan Mueller) Thursday, July 16, 2015 8:15 PM
• Proposed as answer by Jason SandysMVP Thursday, July 16, 2015 9:56 PM

When the product version is changed by the patch (e.g. Adobe Acrobat patches does) you can use the MSI product code AND the new version as DM

Stefan

• Edited by muecom (Stefan Mueller) Thursday, July 16, 2015 8:15 PM
• Proposed as answer by Jason SandysMVP Thursday, July 16, 2015 9:56 PM
• Marked as answer by Jeff Poling 17 hours 27 minutes ago

I ended up using the registry detection method but used the HKLM\Software\Microsoft\WIndows\CurrentVersion\Installer\UserData\S-1-5-18 and the key matching the product.

Jeff