PatchMyPC-ScriptRunner.exe clobbers installer verbose log files

Verbose installer log files produced by PatchMyPC-ScriptRunner.exe clobbers log files with every installation attempt in the PatchMyPCInstallLogs directory.

The file name of the verbose logs file in PatchMyPCInstallLogs are dictated by the file name of the .exe or .msi or .msp installer. The same log file is also used for install and uninstall.

This is very unhelpful for troubleshooting because it means if an installation failure occurs for one version but later succeeds for a later version, assuming the file name of the installer is the same (e.g. GoogleChromeStandaloneEnterprise64.msi), the contents of the logs from the failure is wiped/lost.

The same occurs if the customer manually remediates the device by manually uninstalling the software and and invokes a new install with the PMPC package - this is most common and very frustrating during troubleshooting for the customer and PMPC.

This request is to make a change in PatchMyPC-ScriptRunner.exe so:

• It formulates a unique file name of the verbose log file based on the software title and version.

• If there's a file which already exists with the same name, maybe append _01 _02 _03 etc at the end of the file name before the log extension.

This will preserve log retention and better aid customers, customer engineers, and the app cat team better troubleshoot installation failures.