I've been scratching my head about this one, and have googled around for answers, but didn't find anything interesting - I am sure it's probably a matter of my search terms at this point, but I hope someone out there knows why I am seeing this behavior.
I am looking to link an msi install to it's corresponding \Windows\Installer\msi_munged_file_name.msi. I use /l*vx logging to get the MSI install log, and I see an entry like this:
PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\1f219540.msi'.
And I watch as the file system does indeed get that file created. But, after MSI finishes, the file gets renamed. o_O
I've gone through 2 iterations of this, and both times the file has been renamed to what it was before +3 hex, I think. So, in this case I wind up with a file named:
I am curious as to why the rename happens, and if the algorithm is to indeed +0x3 the last character in the file name, or if this is just coincidence on my 2 runs so far.
I've used Orca.exe to verify that the file that results in C:\Windows\Installer is indeed my msi.
This is for research I am doing on Windows Installer, and I am trying to better understand the MSI/Windows Installer platform.
Thanks in advance!