A few Evolution GUI desktop users have reported problems with their version auto-update ("Version update has failed"), with an additional error message:

This appears only in certain update situations, appears only once, and is due to a minor mis-step in Asure's move to 64-bit readiness. It's unfortunate, but easy to work around.

A user receiving this message should use the standard Windows file explorer, navigate to the path C:\iSystems\Evolution\Client\ and create a new empty folder Win64 and then launch Evolution again. This new folder fills in the missing step, and the update should complete normally.

What's this about?

The Win64\ folder is preparing the way for 64-bit support coming down the road, and—as I understand it—one Evo update got this update logic wrong, so it will show this error. Subsequent software releases do it all correctly.

All AWS bureaus get all Evolution software releases every time, while self-hosted bureaus pick-and-choose, but the end payroll customer only updates themselves when they fire up the desktop client. No bureau has control over this, so some customers who live in Evolution every day get every update, while (perhaps) small monthly payrolls skip numerous intermediate updates.

This is unfortunate, and though I did start investigating which exact specific versions were involved—Asure was very helpful on this front—in practice it doesn't matter: if the customer gets this message, they just have to create the folder and move on.

Are we on/do we require 64 bits now???

No, not yet.

This is just paving the way for the future, and I'm surprised it's going as smoothly as it has been. Asure has put an enormous effort into what I can only call a Herculean task of upgrading this complex application.

Asure has stated that 64 bits on the desktop is supported at least through the end of June, though self-hosted bureaus with 32-bit servers have to start preparing now (I'm working with several bureaus on exactly this).