Enable and Check Print History in Windows

To enable and check print history in Windows, you must first turn on the print job logging feature in the Print Server properties, then view the log in Event Viewer. This article explains how to do both, and how to troubleshoot when the history is missing.

Why Windows Doesn’t Log Prints by Default

Windows does not keep a permanent record of every document you print. The print spooler service manages active print jobs, but once a job finishes, its record is discarded unless you explicitly enable logging. This is a deliberate design choice: logging every print job to disk would add overhead and consume storage, especially in offices with heavy printing. The feature exists, but it is turned off by default in most Windows editions.

How to Enable Print History via Event Viewer

The only built-in way to log print jobs is through the Print Server’s audit settings, which write events to the Windows Event Log. Here are the steps for Windows 10 and Windows 11:

1. Open Event Viewer (press Win + R, type eventvwr.msc, press Enter).
2. In the left pane, expand Applications and Services Logs → Microsoft → Windows → PrintService.
3. Right-click Operational and select Properties.
4. Check the box Enable logging (or set the log size and retention as needed).
5. Click OK. Logging is now active for future print jobs.

To enable logging on a network print server (or a computer that shares printers), you must also configure the server’s audit policy:

1. Open Print Management (type printmanagement.msc in Run).
2. Right-click the server name and choose Properties.
3. Go to the Advanced tab and check Show informational notifications for local printers and Show informational notifications for network printers.
4. Click OK. This makes the PrintService log capture more detailed events.

How to Check the Print History

Once logging is enabled, you can view the print history in Event Viewer. The events appear in the Operational log under the PrintService path mentioned above. Look for Event ID 307 (print job completed) and Event ID 805 (print job submitted). Each event shows the document name, user, printer, and timestamp. To filter for just print events:

• In Event Viewer, select the Operational log.
• Click Filter Current Log… in the Actions pane.
• Enter 307 or 805 in the Event IDs field.
• Click OK to see only print events.

You can also use PowerShell to export the history to a CSV file for analysis. For example, open PowerShell as Administrator and run:

Get-WinEvent -LogName Microsoft-Windows-PrintService/Operational | Where-Object { $_.Id -in 307,805 } | Export-Csv -Path print_history.csv

What to Do if Print History Is Missing

If you have enabled logging but still see no events, check these common causes:

• Logging was disabled after the job – events are only written when logging is on at that moment.
• You are looking at the wrong log – the Operational log is separate from the classic System log. Make sure you are in the PrintService folder.
• The log is full – if the log reaches its maximum size, Windows stops writing new events unless you set the retention to “Overwrite events as needed”.
• Group Policy overrides – in domain environments, a policy may disable print logging. Check with your IT administrator.
• Printer driver or spooler issues – if the spooler crashes, events may not be written. Restart the Print Spooler service.

Alternative Methods to Track Printing

If Event Viewer logging is not sufficient, you have other options:

• Printer’s own job log – many network printers (e.g., HP, Brother, Canon) have a built-in web interface that logs print jobs. Check your printer’s IP address in a browser and look for a “Job Log” or “Print Log” page.
• Print management software – commercial tools like PaperCut or Print Manager Plus can track printing across an entire network, but they require installation and licensing.
• Enable the “Log file” in the printer driver – some drivers have a “Log to file” option in the Advanced tab of the printer properties. This writes a plain-text log of print jobs.

How to Clear or Manage the Print Log

To clear the print history, simply delete the events in the Operational log. In Event Viewer, right-click the Operational log and choose Clear Log…. You can also set the log size and retention policy in the log properties (right-click → Properties). For example, you can set a maximum size of 20 MB and choose “Overwrite events as needed” to keep the log from filling up.

Frequently Asked Questions

Can I see print history from before I enabled logging?

No. Windows only logs events that occur after logging is enabled. If you need a record of past prints, you would have to rely on the printer’s own log (if it has one) or third-party software that was running at the time.

Does print history show the content of the document?

No. The event log only records metadata: document name, user, printer, timestamp, and page count (if the driver provides it). It does not store the file content or a preview.

Why do I only see Event ID 307 but not 805?

Event 805 is generated when a print job is submitted, while 307 is generated when it completes. If a job fails or is deleted, you may see 805 but not 307. Also, some drivers may not trigger 805. You can enable both by ensuring the audit policy is set as described above.

Is there a way to see print history for all users on a shared computer?

Yes, if the computer is the print server (i.e., the printer is connected to it and shared), the Event Viewer log records jobs from all users. However, you need administrator rights to read the log.

Does this work on Windows 7 or Windows 8?

Yes, the same PrintService log exists in Windows 7 and 8, but the steps may vary slightly. In Windows 7, the log is under “Applications and Services Logs” → “Microsoft” → “Windows” → “PrintService” → “Operational”. The enable logging checkbox is in the same place.

Related

• Data Link Protocol: How Layer 2 Frames Data
• AMD ROCm vs NVIDIA CUDA: Compatibility, Performance, Setup
• Grant Terminal Full Disk? macOS Permissions Explained