Reinstalling MSI applications using MDM and EnterpriseDesktopAppManagement CSP impossible

I am currently experimenting with Microsoft Windows OMA-DM API and implementing endpoints for the EnterpriseDesktopAppManagement CSP to deploy MSI app installation packages.

For now, the first installation of the applications runs fine. However, reassigning the same MSI for installation runs into an error.

Relevant lines from the MSI logs:

MSI (s) (B4:2C) [22:00:12:926]: Determining source type
MSI (s) (B4:2C) [22:00:12:926]: Note: 1: 2203 2: C:\WINDOWS\system32\config\systemprofile\AppData\Local\mdm\{CA282C65-FBCD-47F3-B929-0DEAE074AAC8}.msi 3: -2147287038
MSI (s) (B4:2C) [22:00:12:926]: Note: 1: 1316 2: C:\WINDOWS\system32\config\systemprofile\AppData\Local\mdm\{CA282C65-FBCD-47F3-B929-0DEAE074AAC8}.msi
MSI (s) (B4:2C) [22:00:12:926]: SECREPAIR: Error determining package source type
MSI (s) (B4:2C) [22:00:12:926]: SECREPAIR: Cleanup the Hash Value
MSI (s) (B4:2C) [22:00:12:926]: SECUREREPAIR: SecureRepair Failed. Error code: 524175C5FC8
Aktion gestartet um 22:00:12: RegisterProduct.
MSI (s) (B4:2C) [22:00:12:926]: Note: 1: 2265 2: 3: -2147287035

The file C:\WINDOWS\system32\config\systemprofile\AppData\Local\mdm\{CA282C65-FBCD-47F3-B929-0DEAE074AAC8}.msi is not found and does not exist.

Investigations showed that the file was created as download target during the first installation and deleted after successful installation. During the second attempt the MSI file gets downloaded to another GUID filename.

Research showed that Windows Installer relies on the filename from initial installation.

However using MSI deployment capabilities of MDM and EnterpriseDesktopAppManagement CSP it seems implossible to successfully install an MSI application again.

Only workaround seems to remove the application an then install again.

The observed EnterpriseDesktopAppManagement CSP looks erroneous to me.

Regards,

Mario