> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Client Installation and Uninstallation Issues

> Diagnose remote Windows Client installation failures — admin share access, UAC, DNS, Active Directory trust issues — and common uninstallation errors.

<Warning>
  **IN SAAS ONLY:** the Windows Client can only be installed locally — none of the remote-installation issues below apply.
</Warning>

Most remote Windows Client installation and uninstallation issues trace back to network configuration or system settings. Before troubleshooting further, confirm the user account has administrative permissions on the target computer, and that it meets the [installation prerequisites](/docs/administration/clients/windows-install-prerequisites).

## "The user does not have the required permissions on the remote host"

<AccordionGroup>
  <Accordion title="There is no access to network shares">
    Remote installation needs access to the target computer's administrative shares.

    **Check it:**

    <Steps>
      <Step title="Try opening the admin share">
        In Windows Explorer, enter `\\<target_computer_IP_or_name>\admin$` in the address bar and press Enter.
      </Step>

      <Step title="Enter credentials">
        In the **Enter Network Password** window, enter administrator credentials.
      </Step>

      <Step title="Confirm access">
        If accepted, the system folder (by default `C:\Windows`) opens.
      </Step>
    </Steps>

    **If step 1 fails:**

    * Run `ping <target_computer_name_or_IP>` from a command prompt. No replies → check the network connection. Replies but still no share access → confirm the firewall is disabled on the target, that the Sharing Wizard is disabled, and that the [Server system service](/docs/administration/clients/windows-install-prerequisites) is running on the target.

    **If step 3 fails (login error):**

    * Confirm the credentials are correct and belong to a domain or local administrator account, that the account's password isn't empty, and try entering the username as `<domain_name>\<username>` (domain-joined) or `<computer_name>\<username>` (workgroup).

    **Fix — enable the Local Account Token Filter Policy** (a known Windows issue that blocks remote installs):

    <Steps>
      <Step title="Open Registry Editor">
        Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System`.
      </Step>

      <Step title="Set the value">
        If `LocalAccountTokenFilterPolicy` exists, set it to `1`. If it doesn't exist, create a new **DWORD Value** named `LocalAccountTokenFilterPolicy` and set it to `1`.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="The DNS service is unavailable">
    Run `ping <computer_name>`. No response means the DNS service may be unavailable on your network — try the target's IP address instead of its name. To fix DNS itself, see your Windows Server troubleshooting documentation (on Windows Server 2003, `netdiag.exe` can help).
  </Accordion>

  <Accordion title="UAC is enabled (Windows 11/10/8/7)">
    If admin shares are reachable but remote Client installation still fails, User Account Control (enabled by default) may be blocking it.

    <Steps>
      <Step title="Open Registry Editor">
        Navigate to `HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System`.
      </Step>

      <Step title="Disable UAC">
        Set the `EnableLUA` value to `0`.
      </Step>

      <Step title="Reboot">
        Restart the Client computer to apply the change.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Active Directory errors">
    Caused by a missing trusted domain object (TDO) representing the trust relationship between a parent and child AD domain — typically seen with two or more replicated domains.

    **Fix:** in **Active Directory Users and Computers**, open the **System** container. If no TDO is present, reset the trust between the parent and child domain controllers.
  </Accordion>

  <Accordion title="Errors in the Service Principal Name (SPN) for the domain">
    Happens when the SPN for the domain hosting a replica hasn't yet propagated to the domain containing the account used to run `Dcpromo.exe` — often just replication latency.

    **Fix:** log in with the child domain's admin, or wait for replication to complete and use the root admin account instead.
  </Accordion>

  <Accordion title="Two computers have the same name">
    A computer in the child domain shares a name with one in the parent domain.

    **Fix:** rename the computer in the parent domain.
  </Accordion>
</AccordionGroup>

## "The network name cannot be found"

Usually caused by one of the two issues above: no access to the remote computer, or no access to network shares.

<Steps>
  <Step title="Check basic connectivity">
    Run `ping <name_of_the_remote_computer>`. No response usually means the remote computer's firewall is blocking access.
  </Step>

  <Step title="Try the Local Account Token Filter Policy fix">
    See [enabling the Local Account Token Filter Policy](#the-user-does-not-have-the-required-permissions-on-the-remote-host) above.
  </Step>
</Steps>

## "The Client computer must be rebooted before Client installation"

If the Client was recently uninstalled, restart the target computer before installing again.

## Client uninstallation issues

<Accordion title="&#x22;The host is unavailable now or turned off. Try again later.&#x22;">
  Shown when clicking **Uninstall Client(s)** for a Client that's offline or can't reach the Application Server. Either wait until it shows online, or uninstall it locally on the Client computer:

  ```bat theme={"system"}
  UninstallClient.exe /key=<uninstallation_key>
  ```

  Replace `<uninstallation_key>` with the actual [Client Uninstallation key](/docs/administration/clients/uninstall#the-client-uninstallation-key).

  <Note>
    By default, `UninstallClient.exe` is located at `C:\Program Files\Ekran System\Ekran System\UninstallClient.exe`.
  </Note>
</Accordion>

<Warning>
  `UninstallClient.exe` and its default path are literal system identifiers, preserved verbatim from source.
</Warning>

## Related

<CardGroup cols={2}>
  <Card title="Windows Client installation prerequisites" icon="list-checks" href="/docs/administration/clients/windows-install-prerequisites">
    Confirm prerequisites are met before troubleshooting further.
  </Card>

  <Card title="Client Troubleshooting" icon="wrench" href="/docs/resources/troubleshooting/client-troubleshooting">
    General Client offline and data-reception issues.
  </Card>

  <Card title="Install Windows Clients" icon="windows" href="/docs/administration/clients/install-windows">
    The remote installation procedure this page troubleshoots.
  </Card>

  <Card title="Uninstall Clients" icon="trash-2" href="/docs/administration/clients/uninstall">
    Standard remote and local uninstallation procedures.
  </Card>
</CardGroup>