NetSpeek Windows Runtime Service Installation Guide for Individual Devices

This document is a step-by-step guide for installing the NetSpeek Windows Runtime Service (NWRS) on a computer using a Windows operating system. The NWRS is distributed as an MSI and acts an on-premises component that listens for orchestration commands from your NetSpeek Edge VM and performs actions on that PC (for example: display detection, system telemetry, OEM-specific commands, and other functionality).

Note

This guide is for installing NWRS on a single PC manually. At scale, it is likely that installing the MSI on a large fleet of Windows devices will be done via an MDM system such as Microsoft Intune.

Prerequisites

Before beginning the installation, confirm the following:

  • The compute system/device is running a supported 64-bit Windows OS version from the list below:
    • Windows 10
      • Note that only 64-bit OS’es are supported – the 32-bit version of Windows 10 is not supported.
    • Windows 11
    • Windows Server 2016 or later
  • You have the required dependencies installed:
  • The PC is powered on and connected to a routable network from your NetSpeek Edge VM (a network path that allows the Edge to reach the PC’s IP address on port TCP 443).
  • You have administrator rights on the Windows PC (required to install the MSI and, if needed, modify the Windows Firewall or edit configuration under Program Files).
  • Relevant software for your use case is installed on the PC.
  • You have the NetSpeek Windows Runtime Service MSI (PackageInstaller.msi) supplied by NetSpeek.

Step 1. Install the NetSpeek Windows Runtime Service MSI

  1. Locate PackageInstaller.msi (the NWRS installer).
  2. Right-click the MSI file and → Run as administrator.
  3. Follow the installation wizard and complete the install.

The installer does the following:

  • Copies program files and bundled runtime components to the machine.
  • Registers and starts the NetSpeek Windows Runtime Service (internal service name: NetSpeekRuntimeService) within the Windows OS.
  • Configures HTTPS listening on port TCP 443
    • Ensure this port is not used by other software on the Windows OS device

Step 2. Confirm the NWRS is running in Windows Services

Use the Windows Services Console to verify the installer started the service correctly.

  1. Press the Windows button, type services.msc and press Enter
  2. In the list of services, locate NetSpeek Runtime Service.
  3. Confirm:
    • Status shows Running
    • Startup type is Automatic (or matches your organizational policy).
    • If the Service is neither Running nor has a Startup type of Automatic, contact your Organization’s Administrator to configure these settings.

If Status is blank or Stopped:

  • Right-click NetSpeek Runtime Service → Start.
  • If it fails to start, open Event Viewer → Windows Logs → Application and look for errors from NetSpeek or .NET.

Step 3. Network, firewall, and TCP 443

In order for the NetSpeek Edge to orchestrate this PC over HTTPS:

  1. Confirm the hostname or IP address entered in the NetSpeek Canvas matches the network configuration of the Windows device – see details in the NWRS Integration Guide. The NWRS is listening on port TCP 443 for commands from the Edge VM.
  2. If Windows Firewall or other software on the PC blocks inbound HTTPS connections, configure the PC to allow inbound TCP 443 traffic. Depending on your organizational policies, this task may need to be completed by your Windows OS administrator.

Verification

Verification requires configuring an Integration at the tenant level of the NetSpeek platform, and an adding a Windows OS device to a Canvas at the Room level. For details about these steps, and verification once completed, refer to: NetSpeek Windows Runtime Service Integration Guide

Troubleshooting

Installation Issues

  • MSI installation fails or rolls back: Run the MSI as administrator. If problems persist, collect the installer logs or Event Viewer entries and contact NetSpeek Support.
  • Service does not start: Check Event Viewer → Windows Logs → Application for errors tied to NetSpeek, HTTPS, port 443, or .NET.

Connection Issues

  • Confirm the IP address / hostname in the NetSpeek Web Portal match (and firewall rules permit TCP 443 connectivity).
  • Ensure the NetSpeek Edge can route to this subnet (VPN, VLAN, guest Wi‑Fi, and other segmentation approaches often block Edge-to-PC paths).

Support

If you run into any issues during onboarding or have questions, contact NetSpeek Support at support@netspeek.com.