This change was made for some reason, and not just to annoy developers. The right approach is to put your user interface in another program and communicate with the session through a channel or some other IPC mechanism. The recommendation that services do not provide a user interface is more than 10 years.
You really should try to follow these rules, even if it may seem inconvenient to start with. On the positive side, you will take advantage of keeping the service logic and user interface logic separate
If your services run under the LOCALSYSTEM account, you can check "Allow the service to interact with the desktop" for older services that fail if they cannot display the user interface. But it still will not help you, because the user interface will appear in session 0, where it has never been seen!
I recommend that you read the official Microsoft document describing session isolation 0 .
David heffernan
source share