We're currently upgrading our client side machines (Lenovo laptops and desktops) to Windows 10 64 bit.
We have noticed that the Pharos tracker then throws up an issue whenever a user 'activates' or 'violates'
a rule specified by policy print, i.e. Is not printing in black or white or is not printing in duplex.
Regardless, instead of the policy print warning pop-up, users get a flashing pop-up message stating
"An unexpected error occurred in the application" and will keep flashing for several minutes before
closing unless u kill the browser32.exe process in Task Manager yourself.
At first we were upgrading Windows 10 on top of Windows 7 but was advised against this.
We now uninstall pharos first - upgrade to Windows 10 - then reinstall the tracker.
We still see the same issue. Anyone else come across this??
I've attached a video of the issue for everyone to view.