MSIs are not able to repair when the MSI file(s) are located under the Files sub-folder when using ConfigMgr DP as alternate repair source. The reason is because the content source in ConfigMgr is set to the root folder of the PowerShell Application Deployment folder structure which has the MSI file under the Files.
When ConfigMgr is set to be a fallback source for MSI deployments, a URL path the DP content source is added to the source list for MSI resiliency. the repair does not happen because it cannot find the MSI since it’s in the nested Files sub-folder. Has anyone else experienced this behavior?