Fix PDFs Not Printing After Mac Time Machine Restore
Question details
The user cannot print PDF files using Adobe Acrobat or Reader after restoring their Mac to a new SSD via Time Machine.

- Product
- Adobe Acrobat, macOS
- Device & OS
- macOS
- Scenario
- Attempting to print PDF documents after completing a system restore using Time Machine.
- Observed behavior
- PDFs fail to print with a CUPS log error stating a temporary spool file cannot be opened, despite other applications like Word and Chrome printing successfully.
Verify that your printer is properly connected and turned on, and confirm that you can print a standard text document from another application to isolate the issue directly to your PDF reader's spooling process.
Reset the macOS Printing System and Reinstall Drivers
Resetting the printing system clears corrupted CUPS configurations and temporary spool files that often cause printing failures following a Time Machine system restore.
A Time Machine restore can sometimes bring over mismatched file permissions or outdated CUPS (Common UNIX Printing System) configurations. Resetting the macOS printing system entirely forces the OS to rebuild these internal structures from scratch, which is usually the most effective fix for spooling errors.
Click the Apple menu in the top left corner, select 'System Preferences', and then click 'Printers & Scanners'.
Control-click (or right-click) anywhere in the list of devices on the left side of the window, then choose 'Reset printing system' from the context menu.
Click 'Reset' in the confirmation dialogue and enter your administrator username and password when prompted.
Once the reset is complete, click the '+' button beneath the empty printer list to re-add your printer. macOS will automatically download and install the latest compatible drivers.

Grant Full Disk Access to Adobe Acrobat
Time Machine restores can alter privacy permissions. Ensuring your PDF reader has Full Disk Access allows it to properly write temporary print spool files.
Use WPS Office to Print PDFs Without Errors
If Adobe Acrobat continues to experience CUPS spool file errors after your Time Machine restore, you can easily open and print your PDF files using the built-in PDF reader in WPS Office, which safely bypasses Acrobat-specific bugs.
- 1. Download WPS Office: Download and install the free version of WPS Office for Mac from the official website.
- 2. Open Your PDF: Launch WPS Office, click on 'Open', and locate the PDF file that previously failed to print.
- 3. Access the Print Menu: Click the 'Print' icon located in the top toolbar or press the Command + P keyboard shortcut.
- 4. Select Printer and Print: Choose your active printer from the drop-down menu, configure your printing preferences, and click 'Print'.

Frequently Asked Questions
Why do PDFs fail to print after a Time Machine restore?
Time Machine restores can occasionally cause system permission mismatches or corrupt the CUPS printing configuration files. When this happens, specific applications might lose the necessary permissions to create temporary spool files required to send the document to the printer.
What is a CUPS spool file error on Mac?
CUPS (Common UNIX Printing System) is the underlying software that manages printing on macOS. A spool file error usually means the system or the application lacks the correct file permissions to read or write temporary print data to the hidden /private/var/spool/cups/tmp/ directory.
Can I print my PDFs using a different application?
Yes. If a specific program like Adobe Acrobat is generating spool errors, opening the exact same PDF in alternative applications like WPS Office, Apple Preview, or a web browser will often bypass the software-specific bug and print perfectly.
Does creating a new user account fix macOS printing issues?
Creating a new macOS user account can be a helpful troubleshooting step. It generates fresh user preference and permission files. If the PDFs print correctly on the new account, the issue is tied to corrupted settings in your primary account rather than a system-wide failure.




