An issue has been identified with Splashtop Remote Service on Windows Server 2025 Standard Edition, related to a Windows library file. This article outlines the symptoms, temporary workaround, and related context.

Issue Overview

Splashtop Remote Service (SplashtopRemoteService) fails to start properly on Windows Server 2025 Standard Edition. The root cause appears to be a delay in the readiness of the a Windows library. As a result, the service waits indefinitely for the DLL to fully initialize, leading to service startup failures.

Temporary Workaround

To mitigate this issue, change the startup type of the Splashtop Remote Service from “Automatic” to “Automatic (Delayed Start)” using the following command:

This adjustment allows for additional time during system boot for the required dependencies to become ready.

Related Articles

• Run a Script - Learn how to deploy scripts in bulk across your Windows Server 2025 environment using Atera.

• Live Manage: Command Prompt -Provides step-by-step instructions for executing scripts individually through Atera’s Live Manage Command Prompt.

Additional Observations

Network Profile Issue:
Ensures that the nlasvc service depends on the DNS service. Service dependencies control the startup order of services to ensure that required services are running before dependent services start.
A known issue with the nlasvc service affects network profile detection on Windows Server 2025, sometimes resulting in a “Public” profile instead of “DomainAuthenticated.” This may be related to broader network stack behavior.
Refer to the Microsoft Community Hub for further context:
Server 2025 Core ADDS DC, Network Profile Showing as "Public"

Edition Specificity:
This issue has only been observed on Windows Server 2025 Standard Edition. According to Splashtop, the Enterprise Edition does not exhibit the same behavior.