Scripting

Off the top of my head...

- The WindowsInstaller writes a value in 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode]\InstallDate'
- You could resolve INSTALLDIR to its physical location and then get the file date/time stamp of the folder's creation.

You could use Ian's method for non-MSI installations (see vbscab post above) but for msi installations much better to use the win32_product collection using WMI. If you don't already have scriptomatic do a google search on it and download it.

ORIGINAL: aogilmor
You could use Ian's method for non-MSI installations Really? That's a neat trick, getting non-MSI installs to write their install data to the Windows Installer registry keys! And to use INSTALLDIR, too! :)

For non-MSI stuff, I'd go with the folder creation date but one would have to work out how to get the equivalent of INSTALLDIR for the application. of course.

ORIGINAL: VBScab

ORIGINAL: aogilmor
You could use Ian's method for non-MSI installations Really? That's a neat trick, getting non-MSI installs to write their install data to the Windows Installer registry keys! And to use INSTALLDIR, too! :)

For non-MSI stuff, I'd go with the folder creation date but one would have to work out how to get the equivalent of INSTALLDIR for the application. of course.


Non-MSI installations do write their uninstall strings and data to the control panel uninstall key, which is of course not limited to controlling MSI installations. If they're nice they might even write useful info like install date. However, there's no standard they must adhere to, so you're stuck with doing things like checking for folder modified dates. You're are correct, however, that non-MSI installations won't contain the Windows Installer property INSTALLDIR. [:D]

How about using RDT.EXE to read out the timestamp when the/a registry key was created and parse the info?

I suppose that would work indirectly, but if it's MSI no need to use indirect methods, just use InstallDate from the Win32_Product collection.

Sure, an MSI would be easier to catch.
I just though I throw it into the mix for mixed installations [;)]

Thankyou all you for your suggesstions.