Blueprint PrintScout and Microsoft Windows 10

Document created by Scott Olswold on May 16, 2017Last modified by Scott Olswold on Jan 17, 2018
Version 3Show Document
  • View in full screen mode


Pharos Blueprint Enterprise Service Pack 1 for version 5.2 (released December 2015) provided the first PrintScout that was compatible with Microsoft Windows 10. Since that time, Microsoft has released an Anniversary and Creators update for the operating system, in addition to regular product updates.


Problem Statement

Upon installing the May updates for Microsoft Windows 10, fonts in applications or the operating system may not display properly:

Pasted image at 2017_05_12 12_20 PM.png

Root Cause

At issue is the "application injection" that occurs as part of the operation of PrintScout. The injection seeks to determine what application creates a specific Windows Spooler command so that the software can appropriately track the name of the application (winword.exe, iexplore.exe, notepad.exe, etc.) that generated the print job. As a result of the May updates (including Creator), an operating system application is faulting.



Exclude the "fontdrvhost.exe" application from injection. On the Collector hosting Trackers, go into the Blueprint Administrator application and:


  1. Go to Print Scout > Settings > Application Tracking.
  2. In the “App Name Exclusions” box, click Add and then type fontdrvhost.exe and Apply that change.



As the Scouts check in or are installed, they’ll get the new setting, and things will be back to normal. If you wish to disable application injection entirely for a single workstation or subset of workstations, the following can be deployed as a .REG file to the install base:


Windows Registry Editor Version 5.00



Once applied, the PrintScout service would require a restart to take effect.


NOTE: Disabling Application Tracking for any process does not exclude this application from print job tracking. It simply excludes the jobs from that application from attaching a valid "Application Name" to the print job data. If this data element is important to a reporting/management need, the JobToApplicationMap.xml file (located on the Blueprint Collector under \ProgramData\PharosSystems\Blueprint) can be edited to support additional file name extensions. Once edited, the server's Pharos Systems TaskMaster service must be restarted.