Cloud Print for Windows x64 full changelog

Fixed a bug that caused jobs submitted to Canon M2700 printers that are connected directly to GCP, to be rejected by the printer and sit in the GCP queue in the Error state. This bug may have affected other printer makes and models. Please note that if jobs submitted via CPfW do not print and the GCP management web site indicates the job is in the error state, please report this. We can’t fix problems if we don’t know about them and we don’t have every printer make/model in our lab. We rely on users to let us know when things are not working

Added additional error reporting to try to identify the cause of certain unexplained authentication failures.
Added a screen that appears when uninstalling asking the reason you are uninstalling. This is to try to collect information on how to improve this product and increase adoption.

Modified to support IPP type Windows printers created by the Novell/Micro Focus iPrint client.
Fixed a bug in the Virtual Printer driver that would cause some page sizes to be formatted incorrectly when in landscape mode.
Fixed a second bug in the Virtual Printer driver that caused some page sizes to be positioned .25 inch left and .18 inch high from the correct position on the PDF page uploaded to GCP. If you find you have page positioning issues after this update please contact tech support.
Text files with the .zpl extension will now be sent through GCP as RAW data when submitted via the Submit Job screen or dropped into a printer submission directory.

A change in print formatting was made in v2.3.0 that was supposed to improve monochrome printing (print not dark enough) but had the unwanted effect of making images and some fonts print too dark as well. After researching this, it was decided to roll back the change and modify how we handle grayscale and monochrome printing. For a complete discussion of this issue please consult the online help
Some printers require a code to be sent with print jobs in order to be printed. This is typically an accounting code or security code. Previously CPfW could not handle this requirement. Now, there is a work around to send codes to printers that register themselves with GCP. If you have a need to do this, contact technical support for details

It is no longer necessary for the Controller app to restart with Administrative permission to make configuration changes or control the CPfW service. Regular users can now configure and control CPfW. Administrative permission is still required to install or uninstall.
Fixed several bugs discovered during the extensive research and testing done to address the Google problems with submitting jobs during December.

Fixed a bug introduced in v2.3 that resulted in the error ‘Object Reference not set to instance of an object’ when printing with diagnostic tracing turned off.
Fixed several other bugs in error reporting to our server. Due to these bugs we were not receiving reports for some errors.

Google Cloud Print supports printing from URLs. CPfW now supports this as well. You can submit a web page address (URL) to be printed in one of several ways. CPfW submits that URL to GCP and GCP will download the web resource pointed to by the URL and use it as the content of the new print job. This is very handy for printing web pages just by entering the page URL on the Submit New Print Job screen. See the on-line help for more information about how to submit URLs as print jobs
The Submit New Print Job screen now remembers the last 10 files that have been submitted and loads the most recent file when the screen opens. The last selected printer is also remembered and automatically selected again
Removed specific dependency on the .Net Framework 3.5. CPfW will now run on 3.5 or later
Added an option to Settings to reduce the number of prompts you have to respond to when the Controller restarts in Admin mode

Google suddenly stopped accepting authorization requests from the Controller app. Google would report “your browser is not supported and should be updated”…even though the browsers on the system are current. A change in Internet Explorer configuration is required to fix this Google compatibility problem. Our installer now makes this change and authorization with Google is back to normal.
Determined that changing the password of the Google account CPfW is connected to will result in error 403, Access Denied. If you change your account password you must reauthorize CPfW to access your account. Modified to report this specifically instead of just showing error 403. Same for revoking CPfW’s app permissions in the Google account control panel.
Fixed a corner case bug that would cause the Controller not to record the new authorization code when authorizing with Google. CPfW would continue to use the old authorization code and that could result in access errors.

The Microsoft Image and Document Writer virtual printers are not supported by CPfW. The controller has been updated to not offer such printers for registration with GCP
Fixed a minor bug that could cause registry access denied errors