# Printer Issue w/ IPP / Universal driver

**URL:** <https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395>\
**Category:** questions\
**Tags:** c6, windows\
**Created:** [September 25, 2026, 7:01am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395 "2026-09-25T07:01:21Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![PaulMacFarlane](https://clarionhub.com/user_avatar/clarionhub.com/paulmacfarlane/32/4804_2.png) [@PaulMacFarlane](https://clarionhub.com/u/PaulMacFarlane)\
**Post date:** [September 25, 2026, 7:01am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/1 "2026-09-25T07:01:21Z")

</div>

I know in C6 there are issues related to default printers, etc.  
A client that is running C6 apps had a problem (apps wouldn’t run) because the default printer was using the IPP driver.

My question is: Has there been any changes/improvements in later Clarion releases ?  
It seems many recent Windows updates cause stability issues.

---

<div class="post-metadata">

**Author:** ![ThaDaSoft](https://clarionhub.com/user_avatar/clarionhub.com/thadasoft/32/3743_2.png) [@ThaDaSoft](https://clarionhub.com/u/ThaDaSoft)\
**Post date:** [September 25, 2026, 8:44am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/2 "2026-09-25T08:44:55Z")

</div>

I’ve noticed the IPP Driver causing the most issues with HP and Brother Printers - the whole `Printer Spooler` itself in Windows 10/11 is having issues with them - from what I could gather, the printers themselve advertise they support the IPP driver, but don’t actually implement the protocol correctly, causing issues and slower printer spooler.

Seen the issues on C8 and C11 - haven’t tried C12 yet - my recommendation, avoid the IPP Driver if possible as even Windows itself has issues with it - the only brand I noticed working kinda fine with it is Epson (also Oki, but that brand seems to have died) - or the expensive enterprise models from HP.

---

<div class="post-metadata">

**Author:** ![PaulMacFarlane](https://clarionhub.com/user_avatar/clarionhub.com/paulmacfarlane/32/4804_2.png) [@PaulMacFarlane](https://clarionhub.com/u/PaulMacFarlane)\
**Post date:** [September 25, 2026, 8:59am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/3 "2026-09-25T08:59:08Z")

</div>

So, appears Clarion hasn’t addressed this issue.  
Clarion obviously tests the default printer at startup. Not sure why that is necessary.  
Creates a point of failure.  
Sure we can blame the printer and the IPP stuff, but Clarion should not hang on a bad printer.!

---

<div class="post-metadata">

**Author:** ![ThaDaSoft](https://clarionhub.com/user_avatar/clarionhub.com/thadasoft/32/3743_2.png) [@ThaDaSoft](https://clarionhub.com/u/ThaDaSoft)\
**Post date:** [September 25, 2026, 9:14am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/4 "2026-09-25T09:14:51Z")

</div>

As far as I could test, it’s not Clarion which hangs persé - it’s the Windows Print Spooler which hangs, which Clarion waits indefinitely on (this part is stupid, I agree)

---

<div class="post-metadata">

**Author:** ![RichCPT](https://clarionhub.com/letter_avatar_proxy/v4/letter/r/e19b73/32.png) [@RichCPT](https://clarionhub.com/u/RichCPT)\
**Post date:** [September 29, 2026, 9:59pm UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/5 "2026-09-29T21:59:19Z")

</div>

Paul, if you have an IPP printer driver on your computer I wonder what you might find if you ran your .exe with the “Microsoft Application Verifier” and WinDbg?. I was quite surprised to see all the extra .DLL’s that wedge themselves into the simplest of programs. Those two programs together with an AI can find all kinds of things that might be fixable.

---

<div class="post-metadata">

**Author:** ![PaulMacFarlane](https://clarionhub.com/user_avatar/clarionhub.com/paulmacfarlane/32/4804_2.png) [@PaulMacFarlane](https://clarionhub.com/u/PaulMacFarlane)\
**Post date:** [October 2, 2026, 9:48pm UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/6 "2026-10-02T21:48:21Z")

</div>

I actually found the problem but creating a log from SystemTools ProcMon and fed that into Claude for review.

No need to visually read logs anymore. Claude does it better !

---

<div class="post-metadata">

**Author:** ![LANSRAD](https://clarionhub.com/user_avatar/clarionhub.com/lansrad/32/4519_2.png) [@LANSRAD](https://clarionhub.com/u/LANSRAD)\
**Post date:** [October 3, 2026, 12:34am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/7 "2026-10-03T00:34:43Z")

</div>

That’s true for logs from DebugView as well!

---

<div class="post-metadata">

**Author:** ![jkuijt](https://clarionhub.com/user_avatar/clarionhub.com/jkuijt/32/6168_2.png) [@jkuijt](https://clarionhub.com/u/jkuijt)\
**Post date:** [October 3, 2026, 5:12am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/8 "2026-10-03T05:12:21Z")

</div>

Hi,

What was the problem and did you also find a solution?

---

<div class="post-metadata">

**Author:** ![PaulMacFarlane](https://clarionhub.com/user_avatar/clarionhub.com/paulmacfarlane/32/4804_2.png) [@PaulMacFarlane](https://clarionhub.com/u/PaulMacFarlane)\
**Post date:** [October 3, 2026, 6:42am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/9 "2026-10-03T06:42:37Z")

</div>

Installed a normal IP driver for the printer.

As soon as I changed the default printer to something other than the printer with the IPP driver it worked.

---

<div class="post-metadata">

**Author:** ![jkuijt](https://clarionhub.com/user_avatar/clarionhub.com/jkuijt/32/6168_2.png) [@jkuijt](https://clarionhub.com/u/jkuijt)\
**Post date:** [October 3, 2026, 6:56am UTC](https://clarionhub.com/t/printer-issue-w-ipp-universal-driver/9395/10 "2026-10-03T06:56:57Z")

</div>

Thank you Paul for sharing.

Best regards  
Jeffrey
