How to Log Printing Jobs on Windows

Written by jason gabriel
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Log Printing Jobs on Windows
Logging printing jobs in Windows is useful to keep track of your completed work. (Thomas Northcut/Photodisc/Getty Images)

For a variety of reasons, you may wish to log the printing jobs that occur on your computer. Fortunately, Microsoft records in an event log every action, warning and error concerning the computer. As print jobs are included in the category of actions, you can thus use Event Viewer to view every print job that has transpired since the last time the log was cleared. If you modify the log size to be very large, the log file will never be cleared, allowing you to track the printing being done on a computer.

Skill level:
Moderately Easy


  1. 1

    Open the "Start" menu.

  2. 2

    Click on "Control Panel" to open the Control Panel window.

  3. 3

    Open "Administrative Tools."

  4. 4

    Open "Event Viewer."

  5. 5

    Click on "System" in the left-hand panel.

  6. 6

    Click on "More Actions" in the right-hand panel.

  7. 7

    Click "View," then "Filter."

  8. 8

    Uncheck "Warning," "Error," "Success Audit" and "Failure Audit." Leave only "Information" selected.

  9. 9

    Click "Print" in the "Event Source" field.

  10. 10

    Press "OK" if you're done; move on to the following steps if you would like to modify the log file settings.

  11. 11

    Click the "General" tab.

  12. 12

    Increase the log size to as high as you'd like. The bigger the log size, the more slowly it will fill.

  13. 13

    Click "Do not overwrite events."

  14. 14

    Repeat steps 1-10 whenever you would like to view print jobs. Note that the "Filter" window also allows you to narrow your search dates.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.