I just saw this in the Sage Community and Chat GPT summarized it nicely:
Please note that this appears to be a change that happened at version 2024. The full Sage Community thread is here. And the reason that this is notable is that before v2024 people were seeing a pvxwin64 in the path to executable shown in the service dialog box.
Question:
After upgrading from Sage 100 v2024 Advanced 32-bit to 64-bit, why does the Windows service still reference pvxwin32.exe instead of pvxwin64.exe, and should this path be manually edited?
Explanation (Answer by Russell Libby, Sage):
As of Sage 100 v2024, the Windows service intentionally references pvxwin32.exe regardless of whether Sage is running in 32-bit or 64-bit mode. This change was introduced to simplify switching between modes without needing to uninstall and reinstall the service.
Specifically:
- In 32-bit mode: The service runs the actual
pvxwin32.exe.
- In 64-bit mode: A special "bootstrap" version of
pvxwin32.exe launches, which then automatically runs pvxwin64.exe.
Therefore, it's normal for the service to reference pvxwin32.exe even when running in 64-bit mode, and no manual editing is needed.
------------------------------
Wayne Schulz
wayne@s-consult.comSchulz Consulting
(860) 516-8990
CT
------------------------------