Problem
After upgrading Windows 10 to 22h2, you are facing an issue with Color Printing. It might be working from administrator accounts, but the student accounts are facing issues such as either the application they are printing from crashes, or it does not bring up the pharos window.
Solution
There could be different reasons behind this issue. Such as, a problem with the driver can change the printer configuration, causing this issue. And the only way for a printer configuration to be updated in the end user workstation is to make a change to the driver for that queue and rebuild the print package or using the Automatic Updater module which will update the configuration of the package installed on the end user's workstation. This might help resolve the problem. See the below article:
https://community.pharos.com/s/article/How-does-the-Uniprint-Package-Automatic-Update-Module-work-1590684875892
You should also verify that "Enable bidirectional support" is not set in the Ports tab for the driver.
The next step will be to point the print queue (The one used for the package) to a real printer, have it update it's settings, then switch it back to using the PharosSecurePort (w/ port pooling enabled for all 10 ports) so that the driver can talk to a real printer to obtain the potential settings to be used.
To point the queue to a real printer you can follow these steps:
Choose a Printer Port from the Printer properties in Print Management:
Choose "Create a new port" and select "Standard TCP/IP Port" from the drop-down menu. Click "Next"
TCP/IP Printer Port Wizard:
Click "Next" to proceed.
Enter the IP address of the printer in the "Hostname or IP address" field. The port name will automatically be filled based on the IP address.
Once this is done switch it back to using the PharosSecurePort (w/ port pooling enabled for all 10 ports).
From Pharos Admin > Output Management > Devices > Select one of the affected devices and click Run Online State Check" at the right hand side.
This should resolve the issue you are facing. However, if you still face any issues, please contact Pharos support and provide the following details:
- Uniprint logs from this location:C:\ProgramData\pharos\logs. Please verify that the logs are configured to be verbose, as illustrated below"
- Kindly also provide us with the windows event log for the server where the application you are printing from crashes or it does not bring up the pharos window while reproducing the issue.
- Result of the Online State Check.