Overview
This article describes a legacy issue in Windows 10 Build 1909 where Uniprint Notify messages from the Popup Client may not appear in the Windows Action Center when expected. This issue affects the client notification display, not the underlying print submission itself.
Applies to
Pharos Uniprint 9.0 and later
Windows 10 Build 1909
Environments using the Uniprint Popup Client Notify component
Symptoms
Users do not see the expected Notify message in Windows Action Center after submitting a print job.
The missing notification may appear only after the user logs out and back in to Windows.
Printing may still complete successfully even though the user does not see the notification prompt as expected.
Cause
The issue appears to be caused by a Windows 10 Build 1909 notification behavior change. Pharos Support was able to reproduce the symptom, but no confirmed Pharos-side root cause or permanent Microsoft fix was identified for this specific behavior.
Resolution
Confirm that the affected workstation is running Windows 10 Build 1909.
Confirm that the environment is using Uniprint 9.0 or later with the Popup Client Notify functionality.
If the expected Notify message still does not display, contact Pharos Support to request the script appropriate for your deployment and guidance on applying it to the Job Information plug-in event on the Print Service.
Notes
This article applies to a legacy Windows 10 Build 1909 scenario and should not be used to diagnose newer Windows 11 or unrelated Notify issues without confirming the same symptom pattern first.
On newer client issues, missing popup behavior may instead involve client listening or firewall conditions, including TCP port 28201, rather than this historical Action Center behavior