font "ArialMT" cannot be found

it does look like there’s an Adobe 25.001.21208 from 2/12. So curious if this is the one with the fix that ​@S_S mentioned.

Tx, We have had plenty of those. Can you confirm that this is the update with the fix? 

25.001.21208 Planned update, Feb 12, 2026

kind regards, 

did not work for mine

this is what I got but I have not tried .. seems like too complicated to fix a small issue. 

and I asked the agent .. no timeline on when this will be fixed .. “THEY ARE WORKING ON THIS”

Here is a temporary workaround for the current font-related bug:

Please uninstall all Adobe-related applications and perform the manual cleanup steps provided below.

Below are the steps to remove Adobe from your computer.

1. >>Open the Control Panel and navigate to Programs and Features.

2. >>Select Acrobat Installation and click uninstall (repeat this step if there is more than one installation). Note: Continue to uninstall even if the app prompts a security alert.

3. >>Navigate to Windows folder (C:/ drive)

4. >>Open Program Files and delete Adobe Folders. Open the 'Common Files' folder. Repeat the same step for the Program Files (x86) Folder.

5. >>While staying in the Windows drive, click on 'view' (top left corner) and check mark 'Hidden Files'.

6. >>Open the 'Program Data' Folder and delete the Adobe folders.

7. >>Go back to the main Windows Drive and open the 'Users' folder.

8. >>Open the folder that matches your profile.

9. >>Delete Adobe folders from within all three folders. (Local, LocalLow, Roaming)

10. >>Open 'Registry Editor' (search 'regedit' in Windows search at the bottom) (Note: If you do not see a folder named Adobe in the mentioned folders, you may skip them.)

11. >>Expand HKEY_CURRENT_USER (click on the arrow beside the folder).

12. >>Further, expand Software and delete Adobe files.

13. >>Collapse HKEY_CURRENT_USER and expand HKEY_LOCAL_MACHINE

14. >>Further, expand Software and delete Adobe files.

15. >>Open your browser, click on the 3 dots in the top right corner, click on settings/extensions (depending upon your browser) from settings open extensions, and delete/remove any Adobe plugins.

16. >>Restart your PC.

Now install the Acrobat Pro 32-bit version:https://trials.adobe.com/AdobeProducts/APRO/Acrobat_HelpX/win32/Acrobat_DC_Web_WWMUI.zip

After downloading, install the application, but do not open it.

Now visit this link and download the release notes from Aug 2025 and download the 32-bit and install it
https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/index.html

Now launch the application.

Once the application is launched, go to Menu > Preferences> updates and uncheck automatic updates.
Then, you may continue to use the application without any disturbance.

Hi, thx! Unfortunately did not worked for my user. I tried it with add a key, then it created a new subfolder, with value “Arial”, and I tried it to add as character sequence, with key + value you mentioned. No change for my user.

For those still experiencing this, and depending on which version you have, you will probably have to remove all the caching done by Adobe.  This is PowerShell that will nuke the ones you need, and you may need to tailor it for you stituations, but it worked after too many days of frustration working on this issue: I will post the PS script at the bottom after I post this explanation for those that want to investigate further:  *** TEST this first.  It also adds a reg key to prevent the ‘buy this bs’ when adobe starts, so your company may not need that part, and a couple of other reg keys, but I feel like most will want those to be there as well.  

The Explanation (We are using the Adobe Acrobat Reader Continuous Release Version 2025.001.21184 64bit)
1. The "Native Framework" Font Cache

In the 2025 version, Adobe started using a shared framework folder that isn't inside the standard "Acrobat" folder. It's often ignored by cleanup scripts.

• Path: %LocalAppData%\Adobe\Adobe (Yes, an "Adobe" folder inside the "Adobe" folder).

• Fix: We need to wipe the TypeSupport and FntCache here.

2. The "DirectWrite" Conflict

The 2025 build uses DirectWrite for high-resolution rendering. If your Windows "Smoothing" or "ClearType" settings are out of sync with the Adobe sandbox, it fails to map Arial MT.

• The Fix: We force Adobe to use its internal rendering engine instead of the Windows system framework.

3. The "AppData Redirect"

Since you saw the file in the users folder but the script didn't see it, there is a high chance the user has Folder Redirection or OneDrive Profile Sync active. The script might be looking at a local folder while Acrobat is actually using a folder redirected to the network or OneDrive.

🛠 The "Master 2025" All-User Nuke

This is a rewritten "Master Script" for NinjaRMM. It targets the new 2025 paths, handles Folder Redirection, and applies the "Reduced Mode" fix so you can actually click "Quit" on that trial screen without a crash.

the script: 

 

Write-Host "--- ADOBE 2025 MASTER FONT & STABILITY REPAIR ---" -ForegroundColor Cyan

# 1. KILL THE HYDRA (Expanded for 2025 processes)
$Procs = "Acrobat", "AcroRd32", "AcroTray", "AdobeCollabSync", "AcrobatInfo", "AcrobatNotificationClient", "AdobeCEFHelper"
Write-Host "Force-closing all Adobe 2025 processes..." -ForegroundColor Yellow
Stop-Process -Name $Procs -Force -ErrorAction SilentlyContinue
Start-Sleep -Seconds 3

# 2. ALL-USER DEEP CLEAN (Local & Roaming)
$Users = Get-ChildItem "C:\Users" -Directory
foreach ($U in $Users) {
    $N = $U.Name
    $Paths = @(
        "C:\Users\$N\AppData\Local\Adobe\Acrobat\DC",
        "C:\Users\$N\AppData\Roaming\Adobe\Acrobat\DC",
        "C:\Users\$N\AppData\Roaming\Adobe\Adobe Type Support",
        "C:\Users\$N\AppData\Local\Adobe\Adobe\FntCache" # New 2025 Path
    )

    foreach ($P in $Paths) {
        if (Test-Path $P) {
            Write-Host "  Purging: $P for $N" -ForegroundColor Gray
            Remove-Item "$P\*" -Recurse -Force -ErrorAction SilentlyContinue
        }
    }
}

# 3. THE 2025 SYSTEM FIXES (Registry)
$Reg = "HKLM:\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown"
if (!(Test-Path $Reg)) { New-Item $Reg -Force | Out-Null }

Write-Host "Applying 2025 Stability & Font Registry Fixes..." -ForegroundColor Yellow

# Fix A: Force 'Reader Mode' to stop the crash when clicking 'Quit' on trial
Set-ItemProperty -Path $Reg -Name "bIsSCReducedModeEnforcedEx" -Value 1 -Type DWORD

# Fix B: Disable the 'New Acrobat' UI (The #1 cause of 2025 rendering bugs)
Set-ItemProperty -Path $Reg -Name "bEnableNewAcrobat" -Value 0 -Type DWORD

# Fix C: Trust System Fonts (Bypasses buggy internal Adobe caches)
Set-ItemProperty -Path $Reg -Name "bAllUserTrustedExecutablePrivileges" -Value 1 -Type DWORD

# 4. REBUILD SYSTEM FONT INDEX
Stop-Service "FontCache" -Force -ErrorAction SilentlyContinue
$WinFontCache = "C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache"
Get-ChildItem $WinFontCache -Filter "*.dat" | Remove-Item -Force -ErrorAction SilentlyContinue
Start-Service "FontCache"

Write-Host "--- REPAIR COMPLETE. PLEASE RE-TEST ACROBAT ---" -ForegroundColor Green