Hello,
We're attempting to deploy the new Adobe Acrobat Pro application via Intune with our transforms file, but the installation files reporting "An error occurred while preparing the installation of the application: The system cannot find the file specified". The transform file, AcroPro.mst, was generated using Adobe's Acrobat Customization Wizard for Windows and uploaded to PMPC cloud portal as an extra file. My understanding of the documentation is that any mst files uploaded this way are automatically appended to the command arguments, so I didn't expect to need to do anything else. When invoked the installation fails and logs at C:\ProgramData\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log report the message above.
I next tried modifying the installation parameters to add "/msi TRANFORMS=AcroPro.mst". When configured this way the script runner gives the same error, except the exact file path of the .mst file is included - "C:\Windows\IMECache\9ce30df7-293a-4603-ac54-2d45c9581239_1\AcroPro.mst"
What am I doing wrong here?
The 2nd thing you tried should have worked. We'll do some testing on our end and let you know what we find.
It should work if you don't use the "/msi" switch. The following additional command-line should work.
TRANSFORMS=AcroPro.mst
Should be all that is needed to be added.
No luck. Here are the relevant log entries generated by an installation attempt removing the "/msi" switch:
<![LOG[No need to abort due to the running processes]LOG]!><time="14:03:44.191446" date="03-05-2025" component="ScriptRunner" context="" type="1" thread="1" file="">
<![LOG[Running application install: Adobe Acrobat\setup.exe with arguments: /sAll /rs TRANSFORMS="C:\Windows\IMECache\267ee1e1-d7fb-461f-80e4-c99e06b09e1e_1\AcroPro.mst"]LOG]!><time="14:03:44.195445" date="03-05-2025" component="PerfTimerLogger" context="" type="1" thread="1" file="">
<![LOG[Running application install: Adobe Acrobat\setup.exe with arguments: /sAll /rs TRANSFORMS="C:\Windows\IMECache\267ee1e1-d7fb-461f-80e4-c99e06b09e1e_1\AcroPro.mst" finished with Elapsed Time: 00 minutes 00 seconds 034 milliseconds]LOG]!><time="14:03:44.232504" date="03-05-2025" component="PerfTimerLogger" context="" type="1" thread="1" file="">
<![LOG[An error occurred while preparing the installation of the application: The system cannot find the file specified]LOG]!><time="14:03:44.234504" date="03-05-2025" component="ScriptRunner" context="" type="3" thread="1" file="">
<![LOG[End of installation. Exit code is: -2147467259]LOG]!><time="14:03:44.237504" date="03-05-2025" component="ScriptRunner" context="" type="1" thread="1" file="">
Thanks for letting us know! I think we've found a bug in cloud for this. We're working on reproducing the issue. I'll post when we've found a solution!
I happen to be going down this road myself and I'm interested in the outcome. Replying to follow.
We've confirmed this bug, I'm hoping we'll have a fix sometime next week. I'll update this post once I have more info!
Following. I just ran into this issue myself.
Ran into this too. I quickly copied the zip from te intune staging folder and notice setup.exe was missing. I extracted de setup form the zip and added as additional file in the deployment and also added te pre install script expand-archive (from the vscode KB artical custom apps). And it worked for me, installation succesfull.
We pushed a fix to PMPC Cloud for this issue this morning. The proper commandline looks to be: /msiTRANSFORMS=transformname.mst
Then upload the mst as an additional file.
Just a note, the fix does not work. I did a full redeploy, and it is the same error. The patch notes act like the mst was the missing file, but it looks more like it is the path to the setup.exe. If you open the IMECache before it is cleared, there is no path "Adobe Acrobat\setup.exe" as it is still in the archive.
To resolve the issue for now, you can expand the archive by adding this to a pre-installation script.
try { Get-ChildItem -Path $PSScriptRoot -Filter "*.zip" | ForEach-Object { Expand-Archive -Path $_.FullName -DestinationPath $PSScriptRoot -Force -ErrorAction Stop }; } catch { exit 1 }
Thanks for the feedback. I'll test again today, it seemed to work in my test environment.
I just tested this again in my production lab environment, and successfully installed the application via cloud.
Here are the steps I followed:
1. Generated an mst file (AcroPro.mst). To confirm my testing was successful, I had the MST add a brand new registry value under the Adobe Key.
CustWiz_LcGhdrEd7w.png
2. Created a new deployment of the Adobe Acrobat Pro application in PMPC Cloud
3. On the "Configurations" tab, set the "Additional Argument" to "/msiTRANSFORMS=AcroPro.mst"
RemoteDesktopManager_TlCytWHfr1.png
4. Upload the AcroPro.mst file as an additional file under "Extra Files"
RemoteDesktopManager_E4vklKHrHN.png
5. Assign the app to my device as available
6. Installed via Company Portal
RemoteDesktopManager_NRnM1uzkkK.png
7. Checked to see that the MST had applied by checking the custom registry value.
RemoteDesktopManager_G0IGvXH0kV.png
If you are still running into issues, please open a support case and we can gather more data and open a bug. Thanks!