Cirros Windows client 1.3: known issues, all fixed in 1.4
Every known issue across the Cirros Windows client 1.3 line is fixed in Cirros Client 1.4. A workstation on any 1.3 build therefore gets all of the fixes below by moving to 1.4. The issues are grouped by the build that fixed them, newest first, so you can see which ones apply to the version you have.
Tip. To check which version a workstation is running, open the About window from the Cirros tray icon. To move a workstation to Cirros Client 1.4, ask your administrator.
Fixed in 1.3.19
These fixes are in 1.3.19 and every later build, including 1.4.
| Area | What you might have seen | What to do |
|---|---|---|
| Print service | The first print from someone using Direct Submission for the very first time could go missing and never appear in their account. This happened only occasionally. | Upgrade to 1.4. If a first print does not appear, print it again. |
| Print service | A print that had already completed could later show as failed, and its clean-up was delayed. No document content was lost. | Upgrade to 1.4. |
| Print service and print window | After a restart, sign-in or idle period, a healthy computer could show "waiting for printer connection", a stray print-ticket window and Error entries in the print queue. | Upgrade to 1.4. |
| Print window / notifications | Screen readers and voice tools such as Dragon NaturallySpeaking, NVDA and JAWS could not reliably identify the selected field or button in the print-ticket window. Keyboard focus was hard to see, and some controls were announced with duplicate labels. | Upgrade to 1.4. |
| Print service | On PCs that use Windows Fast Startup, the client rarely installed its automatic updates, so a machine could stay on an older version. | Upgrade to 1.4. A full restart, rather than a Fast Startup shutdown, also helps updates apply. |
Fixed in 1.3.18
Build 1.3.18 was not released on its own. Its fixes reached customers in 1.3.19 and are included in 1.4.
| Area | What you might have seen | What to do |
|---|---|---|
| Print service | After upgrading from 1.3.16, or restoring a workstation from a backup, the workstation could lose its identity or fail to open its local data. This could mean the workstation had to be set up again. | Upgrade to 1.4. |
| Print service | Every print job silently disappeared and nothing printed, even though everything looked as if it was running. | Upgrade to 1.4. Until then, restarting the Cirros workstation service, or the computer, restores printing. |
| Print service and print window | A broken print-ticket window reading "could not be loaded" kept appearing, on every print and during background self-test checks. In the worst cases the same few stuck jobs came back repeatedly for hours. | Upgrade to 1.4. Until then, clear any stuck CIRROS-SELFTEST jobs from the Windows print queue to stop the pop-ups. |
| Print service | Print submissions and uploads to the cloud became slower the longer a workstation stayed on without a restart. | Upgrade to 1.4. Restarting the workstation from time to time eases the slowdown in the meantime. |
Fixed in 1.3.17
These fixes are in 1.3.17 and every later build, including 1.4.
| Area | What you might have seen | What to do |
|---|---|---|
| Print service | Security improvements to how print jobs are deleted. | Upgrade to 1.4. |
| Print service | The workstation's local print and notification data could fail to save, or be discarded and recreated when the service started. | Upgrade to 1.4. |
| Print service | Printing, downloading, routing, sending to the print room, merging, and scan-to-cloud uploads (Google Drive and OneDrive) could fail or produce empty or corrupt output for some jobs. | Upgrade to 1.4. |
| Print window / notifications | After the Windows Print Spooler restarted, print notifications stopped appearing until the client was restarted. | Upgrade to 1.4. Until then, restart the Cirros client to bring notifications back. |
| Print service | The workstation could not print because the Cirros printer could not be added, removed or listed. This happened when the Windows Print Spooler was stopped, when the Windows printer driver was missing or damaged, or when the printer name contained an apostrophe. | Upgrade to 1.4. |
| Print service | A print failed to upload with a "zip file is used by another process" error, usually after double-clicking Print to Cloud or retrying quickly. | Upgrade to 1.4. Click Print to Cloud once and wait. |
| Print service | Printing silently stopped and jobs never left the workstation because the local Cirros print server stopped responding. | Upgrade to 1.4. |
| Print service and print window | The print window showed "not responding" and froze for a while when a large document, such as a large PDF, was printing. It could also disappear part-way through the job. | Upgrade to 1.4. |
| Print service | The Cirros printer was missing or unusable, and every attempt to recreate it failed with an "already exists" message. | Upgrade to 1.4. |
| Print window / notifications | A single print job produced two print-ticket windows, or a stray ticket window was left on screen. | Upgrade to 1.4. |
| Print service | The Cirros service showed as running but was not responding, so printing did not work and nothing restarted it. | Upgrade to 1.4. Until then, restarting the Cirros workstation service recovers it. |
| Print service | Scan files could be left on disk after processing, and preview thumbnails could fail to appear for some jobs. | Upgrade to 1.4. |
| Print service | A print job in progress could be interrupted during heavy print load, because the service restarted the local print server when it was only busy. | Upgrade to 1.4. |
| Print service | Cloud print storage could stop working and not recover on its own. | Upgrade to 1.4. |
| Print service | After a Cirros update, printing could fail or behave inconsistently because the Windows print queue was still set up for the previous version. | Upgrade to 1.4. |
| Print service and print window | Cirros client logging silently stopped on some workstations, which made support diagnostics harder. | Upgrade to 1.4. |
| Print window / notifications | While printing a complex document, the progress window could vanish and reappear, briefly show a self-test document, or show a misleading "Processing page: 0". The print itself was not affected. | Upgrade to 1.4. |
| Print service | Some cloud print jobs were stored with the wrong file type, so the cloud side could misread the stored file. | Upgrade to 1.4. |
| Print service | The print window or the print self-test occasionally failed to start in a user session, for example while Windows Explorer was restarting. | Upgrade to 1.4. |
Fixed in 1.3.15 and 1.3.16
These fixes are in 1.3.15 or 1.3.16 and every later build, including 1.4.
| Area | What you might have seen | What to do |
|---|---|---|
| Print service | Security improvements to how the workstation's certificate is protected. | Upgrade to 1.4. |
| Print service | Security updates to third-party components included with the client. | Upgrade to 1.4. |
| Print service | The client's local web page stopped working, or the local web service failed to start or hung, for example after the computer's IP address changed, it moved to another network, or it switched to public mode. | Upgrade to 1.4. Restarting the Cirros workstation service frees the port in the meantime. |
| Print service | The Cirros local cloud service could not be reached over HTTPS from other devices or printers on the network. Connections failed or timed out. | Upgrade to 1.4. |
| Print window / notifications | The print window crashed and disappeared when you clicked, especially double-clicked, its tray icon to open the About window. | Upgrade to 1.4. Until then, click the tray icon once rather than double-clicking. |
| Print service | If the local Cirros print server crashed or was stopped, printing silently stopped and did not recover on its own. | Upgrade to 1.4. Until then, restart the Cirros workstation service or the computer. |
| Print service and print window | Duplicate Cirros print queues could appear, often after a network or spooler disruption. The queue could go offline, or jobs could fail or go to the wrong queue until it was removed and recreated. | Upgrade to 1.4. |
| Print service | Hung or duplicate print window processes were not always cleaned up automatically. | Upgrade to 1.4. |
| Print service | Stopping or restarting the Cirros service could take a long time, appear frozen, or end uncleanly. | Upgrade to 1.4. |
| Print service | When the computer's IP address changed, for example on reconnecting or switching networks, the change was not always detected. On cloud print storage workstations, the web service was restarted unnecessarily. | Upgrade to 1.4. |
| Print window / notifications | Clicking Review My Scanned Files or Review My Print Jobs opened the review window behind other windows, so it appeared as if nothing had happened. | Upgrade to 1.4. |
| Print service | User sign-in and activity reporting could stall or be delayed, for example at logon, when the connection to the local cloud was slow or unavailable. Cost-centre assignments could also be applied unreliably. | Upgrade to 1.4. |
| Print service | On cloud print storage workstations, the service could fail during startup or maintenance if a certificate file had not been created yet. | Upgrade to 1.4. |
| Print service | Finishing a cloud or web-ticket print job could use the wrong file, so the job failed or produced no output. | Upgrade to 1.4. |
| Print service | Web-ticket or print preview thumbnails could appear blank for some jobs. | Upgrade to 1.4. |
| Print window / notifications | The idle print window took keyboard focus from other applications (for example Dragon dictation), appeared in the taskbar and Alt+Tab when it should have been hidden, flickered, and used up system resources over time. | Upgrade to 1.4. |
| Print window / notifications | The print window came to the front only for the first job and stayed hidden for later jobs. At startup, or after a service restart, a small blue box could linger at the bottom left of the desktop, and the window could flicker or show only its top-left corner. | Upgrade to 1.4. |
| Print service | The displayed price did not change when you switched between 1-sided, 2-sided and flip options in the print dialog. | Upgrade to 1.4. |
| Print service | Analysis of a print job could fail or leave temporary files behind, and page counts were occasionally incomplete. | Upgrade to 1.4. |
| Print service | In rare cases, the print and scan review pages could not be reached because the background web service failed to start. | Upgrade to 1.4. |
| Print service and print window | During a print queue restart, the client could briefly show the printer as ready before it was fully back, and report the restart result too early. | Upgrade to 1.4. |
| Print service | After a cloud print or scan job, the automatic close countdown appeared on public or kiosk sessions when it should not, and did not appear when it should. | Upgrade to 1.4. |
| Print service | Clicking the ticket preview thumbnail before the job's PDF was ready opened a broken or empty preview window, even though a "Preview is not ready yet" warning appeared. | Upgrade to 1.4. |
| Print window / notifications | The web print ticket window could occasionally hang, use a lot of CPU or graphics resources, or write excessive error logs on some workstations. | Upgrade to 1.4. |
| Print window / notifications | Choosing Restart Print Queue from the tray menu restarted the queue straight away with no warning, so an accidental click caused an unexpected restart. The client could also report success or failure before the restart had finished. | Upgrade to 1.4. |
Fixed in 1.3.0 to 1.3.11
These fixes are in the earlier 1.3 builds and are all included in 1.4.
| Area | What you might have seen | What to do |
|---|---|---|
| Cirros client | Leftover Web Services for Devices (WSD) printer ports could remain on a workstation and cause print problems. | Upgrade to 1.4. |
| Cirros client | Security and performance update to the browser component used by the client. | Upgrade to 1.4. |
| Print service | Security improvement to how messages between the workstation and Cirros services are signed. | Upgrade to 1.4. |
| Print service | Print jobs could fail intermittently on some configurations. | Upgrade to 1.4. |
| Print service and print window | Print job notifications could generate extra network traffic to mapped print servers and report job status inaccurately. | Upgrade to 1.4. |
| Print service and print window | Large print jobs could be unreliable, some pages loaded slowly, and usernames containing an apostrophe were not handled correctly. | Upgrade to 1.4. |
Still seeing a problem?
If a workstation is already on Cirros Client 1.4 and you still see a problem, contact the Cirros service desk at servicedesk@cirros.net. Please include:
- the Cirros client version, shown in the About window from the tray icon
- the time it happened
- what you saw