I have a client I am working with on a Custom Size Issue. PSM is Version 7.2.6 (build 8871). When trying to create a 3x5 inch postcard and using a Konica Minolta C8000/IC-306 v3.01 driver, she can create the Custom size. the problem ossurs when she closes the driver interface the Page Setup reverts back to Letter 8.5 x 11". This only happens on a Win 7 PC. If she does the same thing on Win XP the setting is retained. I have been testing this on two Win 7 and a Win 10 PC and can't duplicate the issue.
My theory is it is related to her User Rights on her PC. This is a large University Printshop setting and she does not have Local Admin right on her PC. I am the Lccal Admin on all of my test PCs.
My real question is-- does she have to have Admin rights on her PC in order for PSM to function correctly? I seem to remember hearing or seeing something to that effect but I can't find any documentation to back it up.
Thanks

PSM doesn't require admin rights for any feature.

Not 100% sure if it is related, but we have identified an issue with page size matching that is not consistently reproducible in all environments. This issue is scheduled to be fixed in 7.2.7.

It may take quite some time before we can officially release 7.2.7, but I can upload a beta version for the client so she can confirm whether it is fixed. I'll send a private message on this forum when it's available, but please note that I won't be able to spend time on it before Monday.

Thank you. This has been an on-going issue for the customer. Her IT just finished removing and reloading PSM and she is still having the issue. I'm sure she and her IT dept would be glad to test the Beta when its available. It's interesting that it occurs in only some environments. I have now tested this issue on six different systems without a problem.

Thanks again

Not sure if you are automatically notified, I sent you a PM.

The issue we fixed was related to page size matching and caused by non-deterministic floating point comparison, which can have different results when running the same binary on different processors. I can't guarantee that this fixes the client's problem - please let us know.