---
title: "Blueprint Enterprise: When printing from some application I get a Windows \"Bad Image\" error."
slug: "blueprint-enterprise-when-printing-from-some-application-i-get-a-windows-bad-image-error"
tags: ["windows", "Blueprint", "bad", "image"]
updated: 2024-04-23T19:38:28Z
published: 2024-04-23T19:38:29Z
canonical: "kb.pharos.com/blueprint-enterprise-when-printing-from-some-application-i-get-a-windows-bad-image-error"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Blueprint Enterprise: When printing from some application I get a Windows "Bad Image" error.

### **Problem:**

When using the Windows 10 Operating System and printing from some applications I receive a Windows "Bad Image" error like below. The named DLL is part of the Blueprint Print Scout application that assists in obtaining the name of the application being used to print from.

![](https://cdn.document360.io/f4fb58ca-1114-4e59-ba1a-d8f647bd6dcf/Images/Documentation/08ea49bf-5820-45b2-9625-f1e3227e32bd.png)

### **Environment:**

Blueprint Enterprise 5.1 and greater.

Windows 10 Build 1809 and greater.

---

### **Information:**

Pharos Blueprint Enterprise is the leading provider of print management for several reasons, including the ability to deliver data that can tell a story, is actionable, and can be used to chart the progress of an MPS initiative. In that continued quest to create useful data, the “printing application” element was added beginning with Blueprint 4.0. This required configuring a look-up table that matched a file extension (.doc and .docx) to an application (winword.exe). While this worked to a large degree, gaps persisted. In Blueprint 5.0, the Tracker client application was enhanced to better capture the name of the application that created the print job, reducing the gaps in the “printing application” significantly, and introduced as “Application Tracking.” As updates to Blueprint and its Tracker client are made, improvements to this technology continues as well. The Print Scout software for Microsoft Windows continues to feature this technology today. This white paper discusses the technology and process used by the Pharos Print Scout for Application Tracking. Note that any administrative illustrations used in this white paper were created using Blueprint Enterprise 5.3.

This is a result of our application using DLL Injection that is getting rejected by the application. Please see the attached TechNote below.

## Related

- [Uniprint: Getting the error "The printer name is invalid" when attempting to add a queue in Uniprint](/uniprint-getting-the-error-the-printer-name-is-invalid-when-attempting-to-add-a-queue-in-uniprint.md)
- [Blueprint Server Configuration tool fails the Blueprint tracker test with error message "utf/html was returned and utf/xml was expected".](/blueprint-server-configuration-tool-fails-the-blueprint-tracker-test-with-error-message-utfhtml-was-returned-and-utfxml-was-expected.md)
- [Do I have to upgrade through each version of Pharos to get to the latest version?](/do-i-have-to-upgrade-through-each-version-of-pharos-to-get-to-the-latest-version.md)
- [Uniprint Suite - Error: Failed to initialize PsInst32 DLL: Unable to get a list of ports: The operation completed successfully](/uniprint-suite-error-failed-to-initialize-psinst32-dll-unable-to-get-a-list-of-ports-the-operation-completed-successfully.md)

## Attachments

- [Pharos White Paper - Print Scout Application Injection (1).pdf](https://cdn.document360.io/f4fb58ca-1114-4e59-ba1a-d8f647bd6dcf/Images/Documentation/Pharos White Paper - Print Scout Application Injection (1).pdf)