Tranquil IT Forum

Hello,

I'm experiencing a problem with some Windows 10 laptops in my remote work environment.
When shutting down a computer (which was connected to the company network via VPN), there are two possible scenarios. Either the WaptExit window appears for a few seconds before closing and allowing the shutdown process to complete, or an "Access Violation" error message (see attached image) appears. If OK is selected, the message continues to appear repeatedly. If Abort is selected, the message disappears, but the PC remains stuck on "Shutting down" until a forced shutdown is performed.
We were able to reproduce the problem on-site without using the VPN, by unplugging the network cable or disabling the network adapter before shutting down the computer. The problem occurs approximately half the time. Therefore, the issue may stem from a change in the network state.
We are using WAPT Community version 1.8.2.7267. The server is on a Linux machine (CentOS release 7.8.2003) and the console is on a Windows Server 2012 R2.

Thank you in advance for your help.
Sincerely

Hello cpam73,
the logs show a name resolution issue, but this isn't necessarily a problem; a network connection isn't always required for installation when shutting down the machine. There must be some non-standard behavior caused by the antivirus and/or the VPN layer during shutdown at the Windows network level. WAPTexit itself only communicates with the WAPT agent on localhost. What VPN and antivirus software are you using?
I'm opening an internal ticket; if you have an enterprise license, you can contact support. If you're on the community platform and have found a fix, please feel free to submit a pull request on GitHub.
Regards,
Denis

Hello CPAM73,

we are experiencing the same problem at CPAM38 (yes, we're neighbors ). This problem appeared when we upgraded to Windows 10 and only affects workstations used for remote work.

We also have a window that appears at startup with error codes, but only when WAPTTray.exe launches at startup. We have disabled this startup for the time being.

I suspect it's a policy issue with our security solution.

You can contact me by email if you'd like to discuss this further.

Have a good weekend,

David Villeneuve