How does Acrobat (64‑bit) actually auto‑update silently now?

Hi,
I have upgraded Windows 11 devices at my company from Adobe Acrobat Reader or Adobe Acrobat Pro to Adobe Acrobat (64‑bit) Unified Installer. I’m trying to understand how Adobe Acrobat (64‑bit) is supposed to update silently and without user interaction.

Adobe Acrobat Reader would update automatically using scheduled task Adobe Acrobat Update Task and AdobeARMservice, but the service is not created when installing Adobe Acrobat (64‑bit)

I can see “Adobe Acrobat Update Task” in Task Scheduler, and it seems like this task is what keeps Acrobat up to date. It downloads the update files correctly, including the 64‑bit manifests and MSPs.

But when the update is ready to install, the updater still needs UAC elevation, and if no admin is logged in, it just stops and shows a prompt. Logs show the updater trying to elevate and failing (ShellExecute failed / SE_ERR_ACCESSDENIED) even though the task was set to “run with highest privileges.”

Adobe’s documentation says Acrobat/Reader can “regularly check for important updates and install them for you,” with Reader defaulting to automatic updates on Continuous track.

The 64‑bit migration article also says the unified 64‑bit app supports automatic updates.But in practice, installing the MSP still requires elevation, and the “auto” part only covers checking & downloading, not silently installing.

My question:
How is Acrobat (64‑bit) supposed to install updates silently without user interaction or UAC prompts?

• Is there still an Adobe‑managed elevated update mechanism for the 64‑bit unified app?
• If so, what component actually performs the elevated install?
• If not, does Adobe expect organisations to deploy every MSP themselves (e.g., via Intune/SCCM) 

Just trying to understand the current intended update path, because right now the scheduled task successfully downloads updates but cannot install them without elevation, which means no silent auto‑updates

I have Intune and Configuration Manager available, but I would rather not use a 3rd party application to update, or have to package the MSP and deploy it every time the application goes vulnerable.

Thanks.