Hi everyone, I’m troubleshooting an issue with InTouchView and user logoff behavior on Windows 11 Pro 24H2. Here’s what I’ve found:
I'm having an issue with InTouchView applications within an AVEVA System Platform 2023 R2 SP1 P01 galaxy.
When running on a Windows 11 Pro 24H2 node, the InTouch HMI WindowViewer process (view.exe) does not terminate after the InTouchView application is closed if a user has logged into the application.
If the user opens the application, navigates, and then closes it without logging in or if the user logs off before closing the application, view.exe terminates as expected. However, if the user logs in and subsequently closes the application (either via an internal button, ALT+F4, or the window's close button), the view.exe process remains active in Task Manager.
This leads to multiple hung processes if the application is reopened and closed again, preventing application undeployment or the selection of a different InTouchView application through Application Manager.
Placing LogOff() in the InTouch OnShutdown application script seems to have no effect, because the process still hangs. But explicitly calling LogOff() within the application (for example in a close button) before closing it prevents the issue, allowing view.exe to terminate correctly.
This problem reproduces even on a brand new, clean InTouchView application with minimal functionality beyond enabling user login.
When running the InTouchView applications on the GR node, its process (view.exe) always terminates as expected after closing the application.
The tests were done on a test environment, where the server nodes (GR and AOS) run on Windows Server 2022 Standard and the client nodes (InTouchView) run on Windows 11 Pro 24H2. UAC, antivirus, and firewalls are disabled across all nodes. The user account on the client is a standard Windows user, additionally part of the aaRuntimeUsers, ArchestrAWebHosting, and InTouchOperators groups. The galaxy uses ArchestrA Security.
Has anyone encountered this behaviour, particularly concerning the process not terminating after a user has logged in? Any insights, known bugs, or configuration adjustments would be greatly appreciated.
