---
title: "Uniprint Notify fails on Windows 10 Build 1909"
slug: "uniprint-notify-fails-on-windows-10-build-1909"
updated: 2024-03-28T14:11:59Z
published: 2024-03-28T14:11:59Z
canonical: "kb.pharos.com/uniprint-notify-fails-on-windows-10-build-1909"
---

> ## 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.

# Uniprint Notify fails on Windows 10 Build 1909

### **Symptom:**

Windows 10 Build 1909 no longer displays the System Notifications produced by the Uniprint Popup Client in the "Action Center" (Windows System Tray notifications). If the user logs out then back in again to the OS those missing Notify Notifications will then be present and can be seen in the "Action Center".

### **Environment:**

Windows 10 Build 1909 Uniprint 9.0 and greater

---

### **Workaround:**

While there is no root cause for the behavior seen on Windows 10 Build 1909 there is a very simple and configurable workaround, to use a "Job Information" Script that produces a Dialog Window with an **OK** button the user can visually see and accept.

See attached script at the bottom that can be applied to the "Job Information" Plug-in Event on the Print Service.

**NOTE:** This behavior was **not** found on the most recent Windows 10 release, being "Build 2004 May 2020 Update".

## Related

- [Sirsi Contact Information](/sirsi-contact-information.md)
- [ERROR: "Database Connection Error" when installing Blueprint Administrator on a remote system](/error-database-connection-error-when-installing-blueprint-administrator-on-a-remote-system.md)
- [Out of memory error when building packages](/out-of-memory-error-when-building-packages.md)
- [Can the Pharos Web Remote be branded with our company logo's or colors?](/can-the-pharos-web-remote-be-branded-with-our-company-logos-or-colors.md)