I created a ticket for this and the proposed workaround is to add /Update to the end of the Classic UI shortcut.
That seems to work for me - however is going to make a big mess come next Monday morning when 2025.2.10 goes live.
DaveO
2 Likes
Bet yet let’s move everyone to SaaS. It’s ready for prime time.
4 Likes
Update - sorry the /Update switch did not work.
Trying Process 2.
DaveO
2 Likes
Won’t be a problem when there is no client 
1 Like
Normally this is an issue on the Epicor side where the deployment folder and / or sysconfig file has not been updated.
Support call I’m afraid.
1 Like
It’s more a joke about the lack of QA. And the headaches caused by every update.
Yes, without a classic client this wouldn’t be an issue. But, there’s no lack of cloud issues post upgrade.
1 Like
Update.
1 Customer:
/Update switch did not work
modify SysConfig file did not work
Download and re-install classic client worked.
2 Customer:
/Update Switch did not work
Modify Configsys file did not work
Download and re-install Classic client - did not work
I will be putting another ticket for Customer 2.
Aaaaaarg! This is turning into a full day.
DaveO
1 Like
Sorry for the hassle. Hopefully you can move to browser by 2026.1