08-22-2025 05:40 AM
It is an application done in LabVIEW 2017, Same application is running on Eight Win 7 and Win 10 machines the error occurs on new Win 11 machines , that is connected to domain.
The error has now occurred twice on the two new machines, it appears to be the Modbus library..
Strange the applications runs for days without a problem and then it crashes.... At first I blamed windows for system Updates and restarting . I just need someone to look at lvlog.txt and see if they can make sense of it.
Thank you
08-22-2025 07:00 AM
Have you tried recompiling your LabVIEW 2017 code in a version of LabVIEW that is certified to run on Windows 11?
Bob Schor
08-23-2025 04:17 AM
No, Will look into it.
08-25-2025 01:20 AM
Installers and executables are only guaranteed to work on the operating system they are built on. For example, a Windows 10 installer or executable may not work as expected on a different Windows version (e.g. Windows XP, Windows 8, or Windows 7).
Besides, the first supported LabVIEW version on Windows 11 is 2022 Q3.
Reference:
08-30-2025 02:41 AM
Thank you for response, I take note of the suggestion, but is no guarantee that it is going to work, and to upgrade to the newest version is not currently a option. The symptoms is suggesting some other problem as their is two other windows 11 systems running with no problems (not connected to outside).
I suspect that it has something to do that some of systems being on the domain and that some group policies updates or lack their off is causing the problem. The worst initially was Windows auto update and restart in non working hours and these machines is capturing and monitoring 24/7 Postponing system updates reduced problems, but I believe Teams and Office being online accounts might result in unforeseen problems.
My suggestion to my client is to remove these systems from domain and or internet as these machines not connected is not being affected.