• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

using custom .mst while installing from winget

New Here ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard


My organization is looking into deploying Acrobat Reader via winget to Shared PCs. A normal, uncustomized install works great. Sadly, we have not been able to successfully apply our custom .mst to get the installation to work.


This is the command we're trying:



winget install Adobe.Acrobat.Reader.64-bit --override "/sAll /rs /l /msi /qn TRANSFORMS=C:\Custom.mst" --force --accept-package-agreements --accept-source-agreements


Sadly, the custom .mst settings are not being applied. If anyone can help point me in the right direction it would be appreciated.
Also, if there are any .admx files that can be imported into Intune, we could avoid the custom .mst altogether. These don't provide any of the options from Acrobat Workflows. 😞
Our environment includes:
  • Windows 10 Professional (22H2)
    • Shared PC mode for guest logins
  • Microsoft Intune (device management)
    • Win32 app deployment doesn't work unless a domain user signs in (despite the package being assigned to the device)
    • PowerShell script using winget is preferred
Download and install , Windows






Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation