PHPRunner on win 2016 server

This is a known issue, we are looking for a fix but we cannot reproduce it yet. NodeJS is no an issue here as this happens in the client-side Javascript. It looks like it started happening after some Windows update.
I have to add that Windows 2016 Server is not really suitable for running client software, its security model is highly tightened. You will have better luck running any other version of Windows.

I run into the same issue. Good to know, Thank you!

I am trying to remove all windows updates one by one to check , VM server and software purchased for PHPrunner application , unable to change as this will require the repurchase of a new windows VM OS licence
Also ODBC access on server to remote database and Local SQL database , building on my Win 10 PC causes problems with the connections , names not the same , local database sync with server database , security Database table fails due to different server connections.
Tried to build on local machine in desperation and copy to server but permissions and menu changes problems.

We do not have a solution for Windows 2016 server but we can help with "permissions and menu changes problems" on Windows 10, you just need to explain what exactly is happening.

I run my PHPrunner applications output on a cloud based Server 2016 , but I design locally on windows PC VM-Windows ( no issues with Nodes.js locally) (in the first versions of 10.0 PHPrunner, Node.js was a problem if I leave the application open and do not close windows after close before starting application again that may be causing your issue, If you want to try again on 2016 server you might have to restart your RDP before you continue your application) but this does not happen anymore on local computer like window 8.1 or Windows 10.0 with 10.2 PHPrunner, just connect your database from local to the windows 2016 server , design the application locally ( if you can't connect ask your server admin to allow remote connections to the database with IP ) , output to the server and test. Once you get the connection to the database your security issues and permissions should be solved even for testing.
If you pick Windows 2016 R2 to install application.

( in my opinion only )

you are going to run into IIS issues most likely , it is best to run from one system locally then output to server and test . Then move your output to production environment on server domain . I have had the best results this way for years even before Windows 2016 R2.

Node.js was added in 10.0 PHPruner , I believe so that is where the server issue must be . If you want to check if node.js is installed on your server 2016 R2 , go to command line click .type >