Skip to main content
January 13, 2026
Question

Acrobat ignores printer passed via /t or printto and uses last UI-selected printer

  • January 13, 2026
  • 1 reply
  • 311 views

Hello,

 

I’m facing an issue with Adobe Acrobat Reader 25.1.20997.0 when doing automated printing.

Issue Scenario:

I have:

  • One physical printer

  • One virtual printer driver

I print PDFs in two ways:

  1. Manually from Acrobat UI
  2. Programmatically from my Virtual printer driver using :
  • ShellExecute with verb = "printto"

Problem

While printing a file from Adobe Acrobat Reader I select the physical printer and the file is printed successfully.

In the next instance, when I use "printto" verb  programmatically from my Virtual printer driver, Adobe Acrobat Reader does not use the printer(my Virtual printer driver) passed via "printto", instead the file is printed to the physical printer selected in the previous instance.

 

This issue occurs in PC with below configuration:
OS: Microsoft Windows 11 Home 24H2
Version: 10.0.26100 Build 26100


I have tried Changing default printer to my virtual printer driver, adding delays, and  retries which do not fix this issue. It looks like Adobe Acrobat Reader caches the last-used printer and ignores the printer name  passed via "printto" verb.

 

  • Is this a known bug or limitation?
  • Is there any supported way to Clear Acrobat’s internal printer cache?
  • Is it possible to programatically force Acrobat Reader to always print to the printer passed via "printto" verb.
  • Can I programatically disable reuse of last UI printer?


Any guidance or fix or workaround would be appreciated.

Thank you.

1 reply

Meenakshi_Negi
Legend
January 13, 2026

Hi pannag17,

 

Thank you for reaching out.

 
Please find below the i
- The “last-used printer” reuse within the same Reader session is expected behaviour.  There’s no single “printer cache” button, but you can effectively clear cached print preferences by closing Reader between jobs, or by resetting Preferences
 
You may try the following to check if that works:
 
1. Use /t with a fresh Reader instance every print job:  Instead of ShellExecute(..., "printto"), spawn Reader directly with /t and force a new process each time. This approach avoids reusing the session that holds the “last-used printer.” Adobe documents /t as the only switch for silent printing to a specific device.
 
2. Close Reader between jobs to clear its session cache: If you must use ShellExecute("printto"), ensure Reader is not running before each call (close it or kill the process after the previous job).
 
3. Reset Reader Preferences if caching seems “sticky”: If the Reader keeps clinging to a removed/default printer, refresh its Preferences:

- Exit Reader.
- Rename the Preferences folder: 

%APPDATA%\Adobe\Acrobat\DC\Preferences
 
Let us know if that helps.
 
Thanks,
Meenakshi
pannag17Author
January 13, 2026

Hello Meenakshi,

 

Thanks for the update.

I still have one doubt. If this is expected behavior from Acrobat Reader, why is this issue not observed in other PCs like Windows 11 Pro ?
I am yet to change the code to use Reader directly with /t and force a new process each time.

 

I will update you with the result.

 

Regards,

Pannag. 

Legend
January 13, 2026

Hi @pannag17,

 

 

Thanks for flagging this—sorry it’s diverting prints to the wrong device.
Please try these steps:

  1. Use the full /t syntax with quotes for all arguments:
    Example: AcroRd32.exe /t "C:\Path\file.pdf" "Printer name" "Printer driver" "Printer port"
    You can list the exact names via wmic printer get Name,DriverName,PortName.
  2. In Windows Settings, turn off “Let Windows manage my default printer,” then confirm your driver and port match the printer properties.
  3. Close Acrobat/Reader and reset preferences (remove %AppData%\Adobe\Acrobat[ Reader]\DC\Preferences), then retry the /t command.
  4. If it still routes to the last UI‑selected printer, run Help → Repair Installation in Acrobat.

If the issue persists, please share the exact command you’re using and the printer’s Name/Driver/Port as shown by wmic. We’ll use that to reproduce and advise next steps.

 

 


Best regards,
Tariq | Adobe Community Team